SEO URL structure audit work should make important pages easier for people and search engines to understand without creating unnecessary migrations. Google’s October 2026 documentation update clarified why hyphens are preferred to underscores as word separators, but separators are only one part of a reliable URL system.
A useful audit also checks path logic, parameters, case, encoding, fragments, internal links, canonicals and sitemaps. This guide provides a practical workflow for finding risks, deciding what needs action and avoiding a mass rewrite that causes more problems than it solves.
What Google’s updated guidance says
Google’s URL structure best practices recommend descriptive URLs, words in the audience’s language and hyphens between words. Google explains that underscores have historically marked concepts that belong together in programming, while hyphens clearly indicate a word boundary.
The same document recommends standard parameter encoding, as few unnecessary parameters as possible and percent encoding where required. It also warns that URL paths are case-sensitive and says fragments should not be used to change page content. These points affect crawling, duplication and maintenance as much as readability.
This does not mean every old underscore URL must change today. A stable, indexed URL can have links, history and campaign dependencies. Treat Google’s advice as a design standard for new URLs and a diagnostic signal for existing ones, not permission for an unplanned site-wide replacement.
Build the audit inventory
Export URLs from the CMS, XML sitemaps, analytics landing pages, Search Console, server logs and a site crawl. Add paid-campaign destinations and important URLs from email, social profiles and external listings. This exposes pages that a crawler alone may not discover.
Record the response code, indexability, canonical, title, internal-link count, sitemap status, traffic, conversions and last update. Group URLs by template: service, product, category, article, filter, search, profile and file. Kayaar’s 60-minute SEO audit is a useful first pass before this deeper URL review.
Pattern
Audit question
Typical action
Words joined with underscores
Is this a new template or a stable indexed URL?
Use hyphens for new URLs; migrate old URLs only with a justified plan.
Tracking or session parameters
Do they change page content or only measurement?
Keep tracking out of internal links and align canonical signals.
Upper- and lower-case variants
Does the server return the same content at both forms?
Choose one case and redirect variants consistently.
Fragment-driven content
Can unique content be reached only after a hash?
Give indexable content a crawlable URL and use appropriate routing.
Encoded characters
Are reserved and non-ASCII characters handled consistently?
Use standards-compliant percent encoding in links where needed.
Run the SEO URL structure audit
Check path meaning. Confirm that each directory and slug reflects the real content hierarchy. Avoid adding folders merely to repeat keywords. A short path is useful when it remains clear and maintainable.
Review separators. Flag underscores, spaces, repeated hyphens and words joined without separators. Use hyphens for new word boundaries. Do not automatically redirect a valuable legacy URL only to satisfy this preference.
Classify parameters. Mark which parameters change products, filters, language, sorting, tracking or sessions. Keep the standard key=value format with ampersands between pairs. Remove internal tracking parameters that generate duplicate crawl paths.
Test case handling. Request upper- and lower-case versions. If both return a successful response with the same content, select a preferred form and implement consistent redirects, links, canonicals and sitemap entries.
Inspect fragments. A fragment such as #section can move a user within a page, but it should not be the only identifier for indexable content. Test JavaScript applications to ensure important states have crawlable URLs.
Validate encoding. Review Arabic, accented, emoji and reserved characters in both browser display and HTML links. Use valid percent encoding where required, and test the exact production URL rather than assuming the CMS handles every character correctly.
Compare technical signals. Internal links, canonical elements, redirects and XML sitemaps should agree on the preferred URL. Google’s canonical troubleshooting guide recommends checking Google’s selected canonical, technical configuration and whether clustered pages are sufficiently different.
Decide whether to keep, clean or migrate
Keep a stable URL when the pattern is imperfect but harmless and a change offers little user or operational value. Document the exception and apply the better convention to new content.
Clean a pattern without changing the main URL when you can remove tracking from internal links, correct canonical tags, stop session IDs, standardise sitemap entries or block infinite crawl combinations.
Migrate when the current structure creates real confusion, duplication, security risk or an unmanageable platform limitation. Map every old URL to the closest replacement. Kayaar’s content consolidation checklist helps decide when pages should remain distinct, use canonicals, redirect or be removed.
Handle language and regional paths carefully
Arabic and English content can use readable audience-language URLs, but the site needs one consistent policy. Do not canonicalise a useful Arabic page to English simply because the topic overlaps. Align language paths with visible content, hreflang, navigation and sitemaps.
Review Kayaar’s regional SEO guide before changing country or language folders. A neat-looking path cannot compensate for incorrect localisation or forced redirects.
Deploy changes with rollback controls
Test proposed routes in staging. Verify status codes, redirect destinations, canonical tags, internal links, hreflang, forms, analytics and campaign parameters. Avoid redirect chains and do not send unrelated retired pages to the homepage.
Ask marketing, development and analytics owners to approve the same map. A technically correct redirect can still break an advertisement, saved customer link, form journey or reporting rule. Pause any URL whose dependencies are unclear, then resolve the ownership question before release.
Prepare a before-and-after URL map, assign an owner and record the release time. Kayaar’s website relaunch sign-off checklist provides a wider framework for controlled releases.
After launch, crawl both old and new lists, inspect priority URLs in Search Console and monitor errors, impressions, landing sessions and conversions. Allow time for recrawling and canonical re-evaluation before judging the migration. For help prioritising patterns safely, contact Kayaar.
FAQs
Are hyphens better than underscores in URLs?
Google recommends hyphens because they clearly separate words, while underscores have historically indicated concepts that should remain joined.
Should existing underscore URLs be changed immediately?
No. Evaluate traffic, links, dependencies and migration risk first; use hyphens for new URLs and change legacy URLs only when the benefit justifies it.
Do URL parameters always create duplicate content?
No. Some parameters change useful content, while others control tracking, sorting or sessions. Classify their function before deciding how to handle them.
Are uppercase and lowercase URLs different?
URL paths are case-sensitive. If a server exposes the same content at several case variants, choose one format and align redirects and signals.
Can a fragment identify indexable page content?
Google advises against using fragments to change page content. Important indexable states should have crawlable URLs with appropriate routing.
