Future-Proof URL Slugs: Skip Dates, Numbers and Rewrites
Short answer A future-proof slug names the thing the page is about and nothing that can change: no year, no "top 10", no price, no staff name, no ".html". Then you can update the page for years without touching its address. Google says keywords in the URL have hardly any ranking effect, so never rewrite a working slug to chase one.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callThe rule: name the topic, not the moment
The slug is the last part of a page address: in `yoursite.com/water-heater-repair/`, the slug is `water-heater-repair`. A future-proof slug describes what the page will always be about. Anything that can go stale (a year, a count, a price, a person, a promotion) belongs in the page title and text, which you can edit freely.
The web's inventor put the goal plainly:
"A cool URI is one which does not change." (W3C, "Cool URIs don't change")
He also said designing an address "mostly means leaving information out" (same page).
| Put in the slug | Leave out of the slug |
|---|---|
| The service or topic: `drain-cleaning` | The year: `drain-cleaning-2026` |
| The thing people search for: `kitchen-remodel-cost` | Counts: `7-signs-you-need-a-new-roof` |
| A city, if the page is only about that city: `roof-repair-plano` | Prices or offers: `99-dollar-tune-up` |
| Lowercase words joined by hyphens | Staff names: `dr-lee-whitening` |
| Status words: `new`, `latest`, `draft`, `best` | |
| File endings and software: `.html`, `.php`, `cgi-bin` | |
| ID numbers: `?p=123` |
Should you put the year in a URL slug?
Not on a page you plan to keep current. A "2026 price guide" at `/hvac-prices-2026/` is out of date on January 1. You either leave a stale year in the address or change the address and set up a redirect. Put the year in the title instead; the slug `/hvac-prices/` stays right forever.
Dates do fit one kind of page: something that happened once and won't be rewritten, like a news post or meeting notes. The W3C page backs this: it calls the creation date "one thing which will not change" and suggests dates for dated documents. For a service business, that's rare. Service pages, cost guides and FAQs all get updated.
On WordPress, check this setting. Its documentation says WordPress by default uses addresses "that have day and name in them" (WordPress.org, Settings Permalinks screen). For pages you will keep updating, the "Post name" option (`yoursite.com/sample-post`) is the one with no date. Pick it before you publish, not after.
Numbers, prices and names
- Counts. `/5-ways-to-lower-your-energy-bill/` breaks the day you add a sixth. Use `/lower-your-energy-bill/`.
- Prices and offers. `/49-dollar-cleaning/` is wrong after the next price change. The offer goes on the page.
- People. Staff leave. The W3C page warns that "People quit organizations and hand things on" (W3C). A dentist's page on whitening outlasts the hygienist who started it.
- Brands and tools. `/carrier-ac-install/` is a problem if you switch suppliers, unless the brand is the service itself.
- Promotional words. `best`, `cheap`, `top`, `new` age badly and add nothing.
Folders: fewer levels, fewer future moves
Every folder in an address is something you might rename later. If your pages live at `/services/residential/plumbing/drain-cleaning/` and you later drop "residential", every page under it gets a new address.
A small business site rarely needs more than one level: `/drain-cleaning/` or `/services/drain-cleaning/`. Google says folders help it learn how often parts of a large site change (Google's SEO Starter Guide), but that matters for sites with many URLs, and the same guide says not to "drop everything" to reorganize.
Format rules that never go out of date
These come from Google Search Central's URL structure guidelines:
- Words, not ID numbers. "When possible, use readable words rather than long ID numbers in your URLs."
- Hyphens, not underscores. Google recommends hyphens because they help "users and search engines better identify concepts in the URL."
- One case. Google treats `/APPLE` and `/apple` as different addresses. Stick to lowercase.
- Your customers' language. Use the words your audience uses. A Spanish page gets a Spanish slug.
Does a keyword in the slug help ranking?
Barely. Google's own guide says:
"From a ranking perspective, the keywords in the name of the domain (or URL path) alone have hardly any effect beyond appearing in breadcrumbs." (Google Search Central, SEO Starter Guide)
Breadcrumbs are the small path Google sometimes shows above a result. So a clear slug helps people read the result, but it is not a ranking lever. That is the main reason not to rewrite slugs on pages that already rank: the gain is near zero, and every change is a chance to break links.
When should you change a slug anyway?
Only when the slug is now wrong, not just imperfect. Examples: you stopped offering the service the slug names, it carries an old business name, or it holds a year on a page you now keep current.
When you do, set up a permanent (301) redirect from the old address to the new one. Google says these redirects "don't cause a loss in PageRank" (its term for credit from links) and should stay "generally at least 1 year" (Google Search Central, Site moves with URL changes). Check your platform: Wix "automatically creates a 301 redirect" when you change a page's slug, but not for blog posts (Wix Help Center). Then update your own menus, your Google Business Profile link and any ad landing pages.
The 30-second test before you publish
Ask of each word in the slug: will this still be true in five years if I update the page?
- Is there a year, month or number? Remove it, unless the page is about a one-time event.
- Is there a price, person, brand or "new/best/top"? Remove it.
- Is there `.html`, `.php` or a string of digits? Remove it if your platform allows.
- Are there more than two folders? Flatten them.
- Is it lowercase with hyphens, in your customers' language? Then publish.
Example
A roofer's yearly cost guide
The page `/roof-replacement-cost-2024/` drew calls for two years. Each January the owner either left a stale year or moved the page. The next version lives at `/roof-replacement-cost/`; the title says "2026 prices" and changes each year while the address stays put.
A dental office's offer page
`/new-patient-special-99/` went stale when the offer rose to $129. Renamed `/new-patient-offer/` with a 301 from the old address, it can carry any price.
A cleaning company's blog post
`/10-spring-cleaning-tips/` grew to 14 tips. The owner kept the old slug: it still works, already ranks, and changing it would gain nothing. Future posts skip the count.
FAQ
Is a long slug bad?
Length itself isn't a stated Google rule. Shorter slugs are easier to read and share, and removing stale words usually makes them shorter anyway.
Should I remove stop words like "and" or "for"?
Only if the slug still reads naturally. `/kitchen-and-bath-remodel/` is fine; cutting "and" gains nothing.
Can I put my city in the slug?
Yes, if the page is only about that city. If you might serve more areas from the same page, leave the city out.
Will AI or voice search change slug rules?
No sign of it. Google's URL guidance is about readable words, hyphens and stable addresses. Nothing ties slug wording to voice or AI answers.
My old slugs have dates. Should I fix them all?
No. If they work and rank, leave them. Fix only the ones you'll keep updating, with a 301 for each.
Different for you?
- You're updating or merging old pages: Content decay: update, merge or delete.
- Traffic fell after you changed addresses: Why traffic dropped after a redesign.
- You're writing the rest of the page: On-page SEO for service pages.
- You're choosing a website platform: Is Wix or Squarespace bad for SEO?.
- You'd rather have someone set up addresses and redirects: SEO & GEO Agent.