How to Fix Unreadable URLs: Short, Lowercase, Hyphenated
Your audit flagged pages whose URLs are hard to read: too long, nested too deep, or full of uppercase letters, underscores, encoded characters, file extensions, numeric IDs or tracking and session parameters. The score depends on the share of crawled pages with these patterns. By the end of this guide you will have clean slugs like /blog/url-structure, 301 redirects from every old address, and internal links, canonicals and sitemaps pointing at the new URLs.
Why it matters
A readable URL is shown in Google results, pasted into chats and quoted by AI assistants as the source link. Descriptive slugs help users trust the click and give search engines a light relevance signal. Inconsistent casing and parameters also create duplicate URLs for the same content (/Shoes and /shoes are different URLs to a crawler), which splits link equity and wastes crawl budget. Changing URLs without redirects causes 404s and lost rankings, so the redirect step matters as much as the rename.
What you need
Step-by-step fix
Export every URL and flag the problem patterns
Crawl the site and export all HTML URLs with status 200 into a spreadsheet. Add a column for each pattern the audit penalizes and filter with formulas or regex:
- Uppercase letters:
[A-Z] - Underscores, spaces or encoded characters:
_|%20|%[0-9A-F]{2} - File extensions:
\.(php|aspx?|html?)$ - Query strings or session IDs:
\?|sessionid|sid=|PHPSESSID - Length over ~75 characters or more than 3–4 folder levels
Sort by organic traffic so you know which URLs need the most careful handling.
=OR(EXACT(A2,LOWER(A2))=FALSE, REGEXMATCH(A2,"_|%20|\?|\.(php|aspx?|html?)$"), LEN(A2)>75, LEN(A2)-LEN(SUBSTITUTE(A2,"/",""))>6)
Write down your URL rules before renaming anything
Agree on one pattern so editors don't reintroduce bad slugs. A practical rule set:
- Lowercase a–z, digits and hyphens only
- 3–5 meaningful words per slug, drop filler like "the", "and", "final"
- Maximum two folders below the root (/blog/slug, /widgets/slug)
- No file extensions, no dates unless the content is news, no internal IDs
- No trailing-slash inconsistency: pick with or without and enforce it
Decide also which URLs you will not change: low-value pages with external backlinks and steady traffic may be better left alone if they only have a minor issue like length.
Good: /guides/readable-url-structure Bad: /Guides/Readable_URL_Structure.html Bad: /2019/03/14/blog/category/seo/the-complete-guide-to-url-structure-for-beginners-final-v2
Change the slugs and permalink pattern in your CMS
Set the site-wide permalink pattern first (for example WordPress Settings → Permalinks → Post name), then edit the individual slugs you flagged. Keep the old URL in your spreadsheet next to each new one as you go; that column becomes your redirect map. Most CMSs let you edit the slug in the page's SEO or URL settings panel. Do this on staging first if you are changing a whole folder pattern.
old_url,new_url /Products/Blue_Widget.html,/widgets/blue-widget /index.php?page_id=42,/about /blog/2019/03/the-complete-guide-to-url-structure-final,/blog/url-structure
Add 301 redirects from every old URL
Each old URL must return a single 301 (or 308) hop to its new address, never a chain or a 302. On Nginx, a map file scales to thousands of rules. Also add a catch-all that lowercases any URL containing capitals, so stray links like /Widgets/Blue-Widget still resolve. Reload the server after editing (sudo nginx -t && sudo systemctl reload nginx).
# /etc/nginx/conf.d/redirects.conf (http block)
map $request_uri $redirect_to {
default "";
include /etc/nginx/redirects.map;
}
# inside server { }
if ($redirect_to) {
return 301 $redirect_to;
}
# /etc/nginx/redirects.map
/Products/Blue_Widget.html /widgets/blue-widget;
"/index.php?page_id=42" /about;Update internal links, canonicals and sitemaps
Redirects are a safety net, not the fix. Search-and-replace old URLs in content, menus, footers and templates so internal links point straight at the new address. Check that each page's <link rel="canonical">, hreflang tags, Open Graph og:url and structured data url values use the new URL. Regenerate the XML sitemap so it lists only the new, 200-status URLs.
<link rel="canonical" href="https://www.example.com/widgets/blue-widget"> <meta property="og:url" content="https://www.example.com/widgets/blue-widget">
Stop parameters and session IDs from being linked
Filter, sort and tracking parameters (?sort=price, ?utm_source=, ?sessionid=) should never appear in internal links or the sitemap. Store sessions in cookies instead of URLs, strip UTM tags from internal navigation, and give faceted pages a canonical pointing to the clean category URL. If a filtered page deserves to rank, give it its own static path such as /widgets/blue rather than /widgets?color=blue.
<!-- on https://www.example.com/widgets?sort=price&color=blue --> <link rel="canonical" href="https://www.example.com/widgets">
Verify redirects, then recrawl and monitor
Test a sample of old URLs from the command line: each should show one 301 and land on a 200. Then recrawl the site and confirm the flagged-URL count has dropped and no internal links hit a redirect. Submit the new sitemap in Google Search Console (Indexing → Sitemaps) and watch Pages → "Page with redirect" and "Not found (404)" over the next few weeks.
curl -sIL https://www.example.com/Products/Blue_Widget.html | grep -Ei '^(HTTP|location)' # Expected: # HTTP/2 301 # location: https://www.example.com/widgets/blue-widget # HTTP/2 200
Platform-specific notes
WordPress
Set Settings → Permalinks → Post name to remove ?p=123 and date folders. Edit individual slugs in the block editor sidebar (Post → URL). WordPress stores _wp_old_slug and redirects changed post slugs automatically, but not changed page parents or categories; use the Redirection plugin, Yoast SEO Premium or Rank Math (Rank Math → Redirections) for those. Remove /category/ with your SEO plugin's strip-category-base option only if you add redirects.
Shopify
The /products/, /collections/, /pages/ and /blogs/ prefixes are fixed and cannot be removed; focus on the handle. Edit it under the product's Search engine listing → URL handle and keep 'Create a URL redirect' ticked. Bulk redirects can be imported as CSV via Content → Menus → View URL redirects (older admins: Online Store → Navigation → URL Redirects).
Wix
Edit slugs in the page's Settings → SEO basics → URL slug; Wix offers to create a 301 automatically. Manage or bulk-import redirects in Dashboard → Marketing & SEO → SEO → URL Redirect Manager. Dynamic page and blog prefixes (/post/) are set in the collection or blog settings.
Webflow
Change the slug in Page settings or in the CMS item's Slug field (CMS collection slugs change every item URL). Add 301s in Site settings → Publishing → 301 redirects; it supports wildcard capture groups like /old-blog/(.*) → /blog/%1. Republish to apply.
Next.js
Rename the folder or file under app/ (or pages/) to change the route, then add entries to redirects() in next.config.js. permanent: true sends a 308, which search engines treat like a 301; use statusCode: 301 if you need the classic code. For lowercase enforcement, add a middleware.ts that redirects when pathname !== pathname.toLowerCase().
Check that it worked
✅ How to verify
- Run curl -sIL on 10–20 old URLs and confirm each returns one 301/308 hop to a 200 page with a lowercase, hyphenated path.
- Recrawl the site and confirm no indexable URLs contain uppercase, underscores, file extensions, session parameters or more than 3–4 folders, and that no internal links point to redirecting URLs.
- Re-run the audit and check the Readable URL structure check now passes or flags a much smaller share of pages.
- In Google Search Console, use URL Inspection on a few new URLs and check the Pages report over 2–4 weeks for new 404s.
⚠️ Common mistakes
- Renaming URLs without redirects, or using 302s, which turns ranked pages into 404s or leaves Google indexing the old address.
- Creating redirect chains (old → interim → new) when a URL has been renamed more than once; always point every historic URL directly at the final one.
- Leaving old URLs in menus, canonicals and the XML sitemap, so crawlers keep requesting redirects and the old URLs linger in the index.
- Rewriting every URL on the site for a minor length issue, risking traffic on well-ranked pages for little gain; prioritize URLs with IDs, parameters, uppercase and underscores.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Will changing my URLs hurt my SEO?
Expect a short dip of a few days to a few weeks while Google recrawls. With clean one-hop 301s, updated internal links and a fresh sitemap, rankings typically recover fully. Without redirects, you lose the ranking and backlinks of every renamed page.
Are hyphens or underscores better in URLs?
Hyphens. Google treats a hyphen as a word separator, so blue-widget reads as two words, while blue_widget can be read as one token. Hyphens are also easier to read when a link is underlined.
How long should a URL be?
There is no hard limit for ranking, but aim for under about 75 characters and 3–5 words in the slug so the full URL shows in search results and stays readable when shared. Cut filler words, dates and repeated folder names first.
Should I remove dates and IDs from blog and product URLs?
Remove them for evergreen content and products, since they make URLs longer and suggest the page is outdated. Keep dates only on genuinely time-bound content like news, and if your platform requires an ID, place it at the end of a descriptive slug rather than using the ID alone.