Learn
SEO-Friendly URL Structure: What Matters and What Does Not
URLs are a weak ranking signal and a strong usability one. Most URL advice optimises the wrong one of those, and the cost of changing them is high.
Run a fresh DomainLens audit and use the report as your priority list.
What actually matters
A URL is read by people in search results, in shared links and in the address bar. It should be short enough to read, descriptive enough to predict what is behind it, and stable enough that it never has to change.
Its ranking contribution is small. Keywords in the URL are a minor signal that Google has repeatedly described as such, so a well-named URL is worth having and is not worth a migration.
| Property | Matters? | Why |
|---|---|---|
| Readable and descriptive | Yes | Click-through and shareability |
| Stable over time | Yes, a lot | Changing costs links and rankings |
| Hyphens between words | Yes | Underscores are not word separators |
| Lowercase | Yes | Paths are case-sensitive on most servers |
| HTTPS | Yes | A confirmed ranking signal |
| Keyword in the slug | Slightly | A minor signal |
| Short over long | Slightly | Usability more than ranking |
| Folder depth | Barely | Click depth matters; path depth does not |
The conventions worth following
- Hyphens, not underscores — Google treats a hyphen as a word separator and an underscore as a joiner.
- Lowercase everywhere, with a redirect from mixed case, since /Page and /page are different URLs on most servers.
- One trailing-slash convention, enforced with a redirect from the other form.
- Words, not IDs, where the CMS allows it — /guides/redirect-chains beats /node/4821.
- No dates in URLs for evergreen content, so updating it does not make the URL a lie.
# Good
https://example.com/guides/redirect-chains
# Works, less readable
https://example.com/guides/redirect_chains
# Two different URLs on most servers
https://example.com/Guides/Redirect-Chains
# Dated, so updating it makes the URL misleading
https://example.com/2019/03/redirect-chains
# Opaque
https://example.com/index.php?id=4821&cat=7The myths
The depth myth causes real harm, because it drives flat structures where thousands of pages sit at the root with no hierarchy for either users or crawlers.
- Folder depth hurts rankings. It does not — click depth from the home page matters, and a page three folders deep can be one click away.
- URLs must be under a certain length. There is no threshold; readability is the constraint.
- Stop words must be removed. Removing "the" and "for" makes some slugs less readable for no measurable gain.
- Keywords in the URL are a major factor. Google has described them as minor, repeatedly.
- Trailing slash affects ranking. It does not — consistency does, because the two forms are different URLs.
Changing URLs is expensive
Renaming a URL means redirecting it, updating every internal link, waiting for Google to reprocess, and accepting that some external links will never be updated. That cost is worth paying when the current structure is genuinely broken and not worth paying to insert a keyword. Get it right at launch; after that, leave it alone unless something is actually wrong. See the migration checklist if you do have to change it.
How DomainLens contributes
URL structure itself is a design decision rather than an audit finding. What an audit catches is the consequences — the mixed-case duplicate, the missing trailing-slash redirect, the parameter variant competing with the clean URL. DomainLens reports the canonical and redirect behaviour that reveal those. See duplicate content .
- Do keywords in URLs help SEO?
- Slightly. Google has consistently described it as a minor signal. A descriptive URL is worth having for readability more than for ranking.
- Hyphens or underscores?
- Hyphens. Google treats them as word separators; underscores join words together.
- Does URL length matter?
- Not as a ranking factor. Shorter URLs are easier to read and share, which is a usability argument rather than an SEO one.
- Should I change existing URLs to improve them?
- Rarely. The cost — redirects, lost external link value, reprocessing time — usually exceeds the benefit unless the current structure is genuinely broken.