Key takeaway
Keep corporate website URLs clean by splitting addresses into four layers—locale prefix, stable section directory, readable slug, and controlled parameters—and six rules: lowercase hyphens, no .html/.php suffixes, no years or names, uniform slashes/casing, locked slugs, and no raw IDs.

When a corporate website launches, teams spend most of their energy on homepage visuals and messaging while assigning URLs on the fly. Two years later, the address bar shows the debt: products live at /page?id=482, legacy pages still carry /about_us.html, an evergreen buying guide sits at /2024-selection-guide, non-ASCII titles turn into long %E4%BC%81%E4%B8%9A... strings when shared in chats or emails, and /Services/Website, /services/website, and /services/website/ all serve the same service page as separate links.
Keeping URLs clean over years of updates does not require clever tricks. Split every business URL into four layers with clear jobs—locale prefix, stable directory, readable ASCII slug, and controlled query parameters—and enforce six naming rules from day one. This guide covers URL naming for new sites and new business pages; batch 301/308 migration for legacy redesigns and launch-day robots.txt, sitemap, canonical, and hreflang setup belong to adjacent technical workflows.
The Four Layers of a Corporate Website URL
- Language
- Section path
- Stable topic slug
- Parameters with a defined purpose
Messy URLs usually happen when language, section category, page identity, and temporary list filters are jammed into the same string. Giving each layer one job keeps marketing, product, and engineering aligned:
1. Locale Prefix /{locale}/: Separating Language Versions
Bilingual or multilingual sites should identify language at the very front of the path—such as /zh/... and /en/... (or via dedicated subdomains or ccTLDs depending on deployment). In Google Search Central's guide on managing multi-regional and multilingual sites, Google recommends giving each language version its own distinct URL rather than swapping text via cookies, browser headers, or IP detection—and explicitly marks locale query parameters (like site.com?loc=de) as Not recommended. Putting the locale in the prefix avoids ugly -cn or -en slug suffixes. See our Multilingual & Global Website Solutions for how bilingual routes fit together.
2. Stable Section Directory: Reflecting Enduring Business Structure
After the locale prefix comes a shallow directory—such as /services/, /solutions/, /projects/, /blog/ (or /insights/), and /guides/. Name directories after lasting content types and buyer tasks, not internal departments or one-off campaigns.
Clean directories prevent slug collisions (for instance, /en/services/website vs. /en/guides/website) and make section-level analytics easy to aggregate. Always generate root-relative (/en/...) or full canonical links in templates: Google's URL structure best practices warn that parent-relative links like ../../category/stuff can produce infinite broken URL paths when nesting changes.
3. Readable English Slug: Naming the Page Permanently
The slug is the short, lasting name for one page—such as business-website-url-naming or servo-drive-s200. Keep it to 2 to 5 descriptive English words that summarize the permanent topic rather than copying a full marketing headline.
It helps to distinguish protocol support from practical sharing. Google's URL documentation supports words in your audience's language under UTF-8, provided non-ASCII characters are percent-encoded in <a href> attributes. In day-to-day B2B work, however, copying a non-ASCII URL into email clients, PDF proposals, CRM notes, or chat tools produces an unreadable wall of %E4%BC%81%E4%B8%9A... codes that teammates cannot verify by sight and that often break across line wraps. Using short lowercase ASCII English slugs—shared 1:1 across /zh/... and /en/...—keeps links readable everywhere and simplifies bilingual CMS mapping.
Also avoid rendering distinct pages via # URL fragments (such as /#/products/servo): Google Search generally does not support fragments for changing page content, recommending real URLs via the History API instead.
4. Controlled Query Parameters (?topic=..., ?page=...): View State Only
Parameters after ? should stay strictly limited to temporary view states or safe pre-selection: category filters (?topic=websites), pagination (?page=2), site search (?q=...), and safe service pre-selection on a consultation form (?service=website).
Guard two boundaries carefully: core business pages must have path slugs rather than /page?id=482, and parameters must use standard = and & syntax from a minimal allowlist. Google warns that additive filtering parameters (stacking colors, sorting, and tracking tags) trigger URL explosion and redundant crawl targets, and recommends never placing session IDs—let alone personal user inputs—inside URLs.
Six Naming Rules for Long-Term URL Maintenance
1. Use Lowercase Letters and Hyphens (-) Between Words
Separate words exclusively with hyphens (-). Google explicitly recommends hyphens over underscores (_) or mashed words because underscores bind tokens together in code (format_date), whereas hyphens clearly signal word boundaries. Avoid spaces (%20) and CamelCase as well.
2. Leave Out Technical Extensions Like .html or .php
Search engines can crawl .html files (Google's own docs even include .html in sample links), so dropping extensions is about decoupling public addresses from backend software. Sites often outlive their initial stack—moving from static .html or .php to a modern headless CMS or Next.js router. Extensionless paths (/en/services/website) ensure backend upgrades never break printed or shared links.
3. Never Hardcode Years, Version Numbers, or Staff Names
Unless a page is strictly an annual historical archive, keep 2024, v2, and employee names out of evergreen service, product, or guide URLs. When you refresh a guide the next year, hardcoded years force a lose-lose choice between looking outdated or breaking existing links. Put dates and authors in page metadata instead.
4. Enforce One Site-Wide Rule for Trailing Slashes and Casing
Following IETF STD 66, URLs are case-sensitive: Google treats /APPLE and /apple as distinct URLs, and /en/services/website vs. /en/services/website/ are technically distinct paths. Serving HTTP 200 on multiple variants creates duplicate URLs that—as Google's guide on consolidating duplicate URLs explains—split ranking signals, complicate analytics tracking, and waste crawl time. Standardize on all lowercase and one trailing-slash policy (always omit except /, or always include), redirect alternate forms, and keep all internal links consistent.
5. Lock Published Slugs When Editing Page Titles
Teams refine headlines regularly as messaging sharpens. Unless a page's fundamental topic changes, never automatically overwrite an existing published slug when an editor updates the title. In your CMS, allow title-to-slug generation only on new drafts, then lock the slug once published so bookmarks, sales emails, and cross-links stay intact.
6. Use Descriptive Slugs Instead of Database IDs
Numeric IDs and UUIDs belong inside your database primary key, not in /article?id=482 or /products/a3f9c2. Google advises descriptive words over long ID numbers, and readable slugs let editors and sales reps recognize what a link opens at a glance without clicking through.
Messy vs. Maintainable URLs Across Six Scenarios (Hypothetical Examples)
Note: All URLs below use the fictional domain https://example.com as hypothetical examples solely to compare naming patterns; they do not represent real client pages.Scenario | Messy URL Pattern (Hypothetical) | Clean, Maintainable URL (Hypothetical) | Key Maintenance Improvement |
|---|---|---|---|
Product | | | Removes |
Service | | | Strips org codes, mixed casing, underscores, hardcoded year, and |
Bilingual | | | Moves locale to the prefix, drops language params and redundant |
Article | | | Replaces encoded non-ASCII strings and years with a stable evergreen slug |
Search | | | Drops |
Pagination | | | Enforces lowercase, hyphens, and slash rules; keeps only controlled |
Clean URLs also underpin broader search health—as explained in How SEO and GEO Work Together, stable URLs and canonical paths form part of the shared technical foundation for discovery and verification.
Website URL Naming Audit Checklist
[Website URL Naming Audit Checklist]
1. Four-Layer Structure (Architecture Review)
- [ ] Language versions use distinct /{locale}/ prefixes or domains—never ?lang= query params.
- [ ] Directories (/services/, /solutions/, /projects/, /blog/) map to lasting content types, not internal departments or campaigns.
- [ ] Internal links use root-relative or full canonical URLs rather than fragile ../../ links.
- [ ] Filters, pagination, search, and safe form pre-selection use only controlled params (?topic=, ?page=, ?q=) with no session IDs or personal inputs.
2. Page Slug Hygiene (Pre-Publish Check)
- [ ] Lowercase ASCII letters and numbers only, separated by hyphens - (no _, spaces, CamelCase, or non-ASCII characters).
- [ ] No .html or .php extensions, and no #/ fragments used to serve content.
- [ ] Evergreen pages omit years, versions, and staff names, using 2–5 semantic words instead of database IDs.
3. Site-Wide Consistency & CMS Safeguards
- [ ] Lowercase normalization and one trailing-slash policy are enforced site-wide via redirects.
- [ ] CMS editorial workflows lock published slugs when page titles are edited.
- [ ] Menus, buttons, and cross-links point directly to the single canonical URL form.Boundaries and Next Steps
Applying these four layers and six rules keeps a new corporate site's URLs predictable as content grows. Keep the scope boundary clear: if you are redesigning an older site with legacy .html or ID-based URLs already in circulation, inventory those old paths and plan permanent redirects before switching routes; indexing controls (robots.txt, noindex, sitemap.xml) and cross-language tags (rel="canonical", hreflang) follow in launch configuration.
If you are planning a new bilingual website or organizing an existing sitemap, explore ChengXuYuan's Corporate Website & Standalone Site Services or bring your draft navigation and current URL list to our consultation page for a structural review before development begins.