Page URLs (Slugs)

Page URLs (Slugs)

Effective Date: February 1, 2026   Last Updated: February 12, 2026

Hibu Policy

All page URLs on a Hibu One Smart Site must follow standardized slug formatting.


Slug rules apply sitewide. Certain page types — including Service Area Pages (SAPs) and Geo Pages (GEOs) — require defined structural patterns.


Dynamic URL segments (SAPs city-st) are system-controlled and must not be manually modified.


URL integrity is part of overall site architecture and must remain consistent across all builds.

Page URLs (Slugs): At-a-Glance

Category Standard
Definition A slug identifies a specific page in a URL
Formatting Lowercase, hyphenated, no special characters
Naming Reflects navigation label and page topic
Length Concise and literal
SAP Pages Keyword defined; city-state dynamically appended
GEO Pages Keyword + city-state required structure

Definition

A URL slug is the portion of a web address that appears after the domain and identifies a specific page.

  • Example:  domain.com/residential-painting-services
  • In this example, /residential-painting-services is the slug.
  • The slug communicates page content to both users and search engines.

Purpose / Why It Matters

Hibu standardizes slugs to:

  • Maintain consistent site architecture
  • Support SEO clarity and keyword alignment
  • Prevent formatting errors and duplication
  • Enable scalable dynamic page generation
  • Protect long-term site integrity


Slug structure is not stylistic — it is structural.

Universal Slug Formatting Rules (All Pages)

These rules apply to every page unless otherwise specified.

  • Use the navigation label as the basis for the slug.
  • Use hyphens to separate words ( /roofing-services ).
  • Do not use underscores.
  • Use lowercase characters only.
  • Do not use special characters ( # & % + * = @ ~ ^ $ ), punctuation, or symbols.
  • Keep slugs concise, literal, and readable.
  • Avoid unnecessary filler words.
  • Do not create duplicate or conflicting paths.
  • Do not manually alter system-controlled segments (SAPs /city-st)
  • Avoid unnecessary filler words
the at
and to
of our
for your
with best
in top

Service Area Pages (SAPs) URL Structure

Service Area Pages follow a structured format that includes a defined keyword and a dynamically generated city-state value.

  • Parent Service Area Page (PSAP): /contact/keyword-service-area/
  • Dynamically Generated SAPs:  /contact/keyword-service-area/ city-st
  • Example: com/contact/residential-painting-service-area/ king-of-prussia-pa
  • Important: The city-st portion is automatically generated based on the connected location collection. Users do not manually enter or modify this segment.

Geo Page URL (GEOs) Structure

Geo Pages follow a required keyword + city-state structure.

  • Structure: /contact/keyword-city-st
  • Example: /contact/residential-painting-king-of-prussia-pa
  • The structure is standardized.
  • The city-state follows the city-st format.
  • The city-state segment is not manually formatted outside system rules.