The section is now called “Catalog,” but the breadcrumbs and mobile menu still show the old name, and the footer links to the old path. Check the name and address in each of these places. Changing the section heading does not update separate menu entries or footer links.
Is only the name changing, or the URL too?
A link with an accessible href makes it possible to find the target page and check its purpose. Official documentation.
If “Shop” becomes “Catalog,” the /shop/ path can stay the same. In that case, the task concerns interface text and does not require an invented migration. If the URL is changing too, that creates separate work involving routes and historical entry points. Before making changes, record the new name and decide whether /shop/ is being preserved. The menu name, section heading, and title can use different wording for their respective purposes, but they should not contradict one another. Identify which editorial mentions of the old name retain historical meaning. Do not automatically replace “Shop” in every old article: it may describe an earlier version of the site.
Which entry points to check
| Navigation element | Where to check separately | What to update | Required result |
|---|---|---|---|
| Desktop menu | First entry point | Update the label and href | Correct section |
| Mobile menu | Separate source | Check separately | No old name |
| Breadcrumbs | Page hierarchy | Update the data | Current path |
| Old URL | External links | Decide on a redirect | Preserve the destination |
Open the regular and mobile menus
Open a public page as a guest on a wide and a narrow screen. For a hidden mobile menu, check the actual elements after opening it, not just the source HTML. Find which settings generate the old label and path. If one component is used in multiple places, update its data or input parameters. If the regular menu, mobile menu, and footer are stored in separate CMS entries, update each one. Check the navigation cache, which may be independent of the page content. A current H1 does not prove that the menu has received its new configuration.
To find links to the old path:
In the browser console, find links that still use the old catalog path:
[...document.querySelectorAll("a[href]")].filter(a => new URL(a.href).pathname.startsWith("/shop/" )).map(a => ({ текст: a.textContent.trim(), адрес: a.href }));Run the check after opening the mobile menu. If the URL stays the same, the links found are valid: only the label needs updating. If the path is changing, new internal links should point directly to it.
Check the /shop/ to /catalog/ migration
Suppose you are changing /shop/ to /catalog/. The new URL should show the same catalog, and the old one should lead to it through a permanent redirect, such as 301. Check an individual product page separately: renaming the root section does not necessarily mean changing the paths of all product pages. In your table, distinguish the renamed root from child URLs that are staying the same. Then open the old URL directly, the new URL directly, and both through the navigation. This helps reveal an overly broad rule that sends every /shop/... URL only to the catalog root.
Update the sitemap only if the address changes
When the URL changes, set the page's preferred address in the canonical, update the sitemap, and check the redirect from the old path. Internal links should point directly to the new destination. If the path stays the same, do not change these signals automatically. Check the Open Graph link preview label and the installed web app name from the manifest if the product actually uses them for this public section. They may retain the old label independently of the menu. Do not declare the whole site updated based on one tab. Mark the places you checked: menu, footer, breadcrumbs, heading, Open Graph, and the installed web app name, if there is one. This makes it clear where the old name remains.
Recheck all public entry points
Open the menu, footer, breadcrumbs, and the link back from a product page. The name is current and does not get cut off on a phone. If the path changed, the old URL leads to the appropriate new one; the individual product page has kept its own address.
Read also: SEO requirements for a website redesign and Checking redirects when migrating to a new domain. Website checks are available on the reChecker technical audit page.