Blog / Technical SEO /
How to audit links inside navigation components
Here’s a funny thing about navigation links: they’re on every page, and almost nobody looks at them.
They come from a shared component, so once they’re built they fade into the background. Meanwhile, a menu item quietly points to an old URL that redirects, or to a page that’s gone, or to a page that’s changed so much the label no longer fits.
Auditing the links inside your navigation components keeps the main routes through your site direct and easy to understand. And because one component can appear on hundreds of pages, a small fix here goes a long way.
Inventory components and destinations
List the primary, secondary, footer and mobile navigation components, along with breadcrumbs and any reusable local menus. Record the component, label, target URL, rendered destination and status. Crawl the site and inspect the source markup where needed; a visual review alone may miss hidden mobile states or links generated from a CMS menu.
Check for redirect chains, broken links, unexpected external domains and destinations that have changed purpose. A working status code doesn’t guarantee that the target answers the label. That’s the check I find crawlers miss most, so I click through the main items myself. Review language variants, trailing slash rules and query parameters according to the site’s routing conventions.
Review from the visitor’s perspective
Ask whether labels describe the destination clearly and whether the hierarchy helps visitors predict where a link leads. Don’t rename a label just to match a keyword if it makes the menu harder to understand. I’d always rather a visitor find the page than a menu read like a keyword list. Check that keyboard focus, mobile expansion and current-page states work after any structural change.
If a redirect is intentional for legacy visitors, keep it where appropriate, but update the navigation source to the direct destination when the route is equivalent. Confirm the page owner agrees before pointing a prominent menu link elsewhere. Navigation changes can affect many templates, so check the shared component’s use and preview key page types.
Validate and record exceptions
After edits, recrawl and manually test the menus on desktop and mobile. Confirm that each item loads the expected page and that no link has been removed without a replacement decision. Record exceptions such as temporary campaign links with an owner and review date.
A tidy navigation system helps visitors move without surprises.
Check links that are generated dynamically
Some menus are assembled from CMS entries, language settings or user permissions. A static crawl may inspect only one state. Open the menu at common viewport widths, test keyboard interaction and inspect any logged-in or locale-specific version the site supports. Confirm that the active state indicates the current section and that expandable items can be opened without a pointer.
If links are generated from a navigation data source, update that source rather than patching the rendered HTML. Confirm the component has not been duplicated with a different menu configuration. Review how missing or unpublished pages are handled so a menu entry does not remain after its destination is removed.
Keep link labels and information architecture aligned
A label should help someone predict the destination in familiar language. If the destination changes, review whether the label still makes sense. Avoid stuffing a menu with every page; group related content in a way that reflects how visitors look for it. Search visibility is not a reason to expose a confusing hierarchy.
When changing navigation, consider whether breadcrumbs and in-content links still provide a coherent route. A menu audit can reveal broader architecture problems, but do not solve all of them through one label edit. Record the intended hierarchy and discuss substantial changes with the site owner, especially when visitors rely on established terminology.
Review after deployment
Test the deployed menu on a representative set of pages and confirm that cached versions update. Ask another person to complete a common task using the navigation, without explaining where to click. Their hesitation can expose labels or groupings the team takes for granted. It’s one of my favourite tests, because it costs nothing. Record the results and address the highest-impact confusion first.
Avoid changing navigation without a fallback
Before removing or renaming a menu item, identify how visitors currently reach the destination and whether another path remains obvious. A section may be used by existing customers even if the page receives little search traffic. Ask the content owner whether the destination is still needed and agree on an alternate route before taking it out of a prominent menu.
If the destination moves, update breadcrumbs, related links and any help documentation that points to the old location. Test keyboard focus order and the expanded state after changes. Ensure the menu does not become too long on mobile or hide important actions below an unpredictable scroll. A change that looks tidy on desktop can make the route harder on a small screen.
Keep a record of the previous structure and the reason for the change. If feedback shows that visitors can’t find a section, the record makes it easier to restore or adjust the route.
Use a representative test set
Choose pages that use different navigation variants: a standard content page, a product or service page, and a page with a distinct footer or mobile menu. Check the same key destinations from each. This can reveal a template that inherited an outdated component or a locale menu with a different target. Record which pages were sampled so a later audit can repeat the checks.
When you find a broken destination, confirm whether the page was intentionally unpublished or accidentally removed. Coordinate with its owner before restoring it or redirecting the link. A small source edit can be low risk, but changing a global menu affects the entire site and deserves a deployment check. After publishing, test at least one page from each component instance.
Related reading
- Identifying internal links that point through redirects
- Checking whether important pages are reachable through internal links
- How to review crawl paths after a navigation redesign
For a quick start, open your site on your phone, expand the mobile menu and tap every item. How many land exactly where the label promised?