Navigation and breadcrumb labels sometimes drift from what a page is actually called or about — an inherited default, an abbreviation nobody standardised, a leftover from a rename — and standardising them to accurately reflect each page’s actual title and content makes your structure genuinely easier to follow and to parse.
Navigation & breadcrumb label standardisation
Navigation and breadcrumb labels standardised to match what each page actually is.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to review current navigation and breadcrumb labels across the site
- Confirmation of any specific naming convention you want followed, if you have a house style
- Confirmation of whether this applies to the main navigation, breadcrumbs, or both
This or something else?
| Your navigation or breadcrumb labels are inconsistent or inaccurate and need standardising | This fix covers it |
| You want a completely new menu structure, not just label wording standardised | Menu restructure from supplied spec, in the Content Implementation category |
| You want the visible breadcrumb trail implemented for the first time, not existing labels standardised | Breadcrumb implementation & markup, in the Technical SEO Implementation category |
| You want breadcrumb schema for search engines, not the visible label wording | Breadcrumb & Article schema implementation, in the Schema & Machine Readability category |
What we do
- Review current navigation and breadcrumb labels against each page’s actual title and content
- Identify inconsistent, outdated, or unclear labels
- Standardise labels to accurately and consistently reflect each page
- Apply any specified naming convention consistently
- Verify the updated labels display and function correctly
- Check for consistency between main navigation and breadcrumb labels for the same pages
What is included
- Navigation and breadcrumb labels standardised, grounded in each page’s actual title and content
- Consistency verified between navigation and breadcrumb labels
- Any specified naming convention applied uniformly
- A written before-and-after summary
Not included
- Restructuring the menu’s actual organisation or hierarchy — a separate, related fix if that’s also needed
- Implementing a visible breadcrumb trail for the first time, a separate, related fix if it doesn’t already exist
- Breadcrumb schema for search engines, a separate, related, complementary fix
- Ongoing standardisation as new pages are added
Questions about this fix
Why would my navigation labels have drifted from my actual page titles?
Often through incremental changes over time — a page gets renamed but its menu label doesn't get updated to match, or different people add menu items using their own shorthand rather than a consistent convention.
Will this change my actual page titles, or just how they're labelled in navigation?
Just the navigation and breadcrumb labels — this doesn't touch the actual page titles or content themselves, only how they're referred to in your site's navigational elements.
Does this restructure my menu's organisation?
No, this addresses label wording and consistency specifically; reorganising the actual structure or hierarchy of your menu is a separate, related fix.
Will this affect my breadcrumb schema if I already have it set up?
We check for consistency between visible labels and any existing schema, flagging a mismatch if one exists, though updating the schema itself would be a separate, related fix if a change is needed there too.
Is this worth doing if I only have a handful of inconsistent labels?
Even a small number of inconsistent or confusing labels can meaningfully affect how clearly visitors understand your site's structure, so it's worth addressing regardless of scale, though the scope of work would obviously be smaller.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.