The catalog moved from /shop/ to /catalog/. Visitors already see the new breadcrumbs, but the JSON-LD—the page’s structured data for search engines—still contains old links. This happens when the visible navigation and markup get their URLs from different settings, or one of them remains cached.
Open a specific product page and compare the two paths. Breadcrumbs show where the page sits in the site structure; they do not replace the canonical URL or, on their own, determine which address should be indexed.
Compare the names and URLs at each step
For example, a lighting product page might look like this:
| Step | Visible link | URL in JSON-LD | Correct URL |
|---|---|---|---|
| Catalog | /catalog/ | /shop/ | https://example.com/catalog/ |
| Lighting | /catalog/lighting/ | /shop/light/ | https://example.com/catalog/lighting/ |
Open the new links and make sure they lead to the corresponding sections. You cannot fix the markup by replacing a single prefix if the move also changed the names and URLs of individual categories.
For a product in multiple categories, find out which path the site displays as primary. There may also be several meaningful paths. The important thing is that each reflects the actual site structure, rather than a page the current visitor happened to arrive from.
Read every BreadcrumbList on the page
Find BreadcrumbList—the description of the breadcrumb trail—in every JSON-LD block. One block may be generated by the template, another by an SEO plugin. Fixing one block does not remove old links from the other. Check the source HTML and the result after JavaScript runs if the markup is generated in the browser.
Keep name, position, and item for each step. Numbering starts at 1 and reflects the order of the path. The URL should correspond to the specified section, not point to the homepage through a generic fallback.
In Google’s requirements, item may be omitted from the last step; in that case, the URL of the page containing the breadcrumb is used. So the absence of this field in the last item is not, by itself, a reason to report an error. See the BreadcrumbList documentation.
Fix the generator and category source
Ask a developer to identify where the markup gets the old path. Possible sources include the category field, a plugin setting, a hard-coded URL in the template, or a cache. Updating the visible menu does not necessarily change this data.
Example markup for the new path:
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem", "position": 1, "name": "Каталог",
"item": "https://example.com/catalog/"
},
{
"@type": "ListItem", "position": 2, "name": "Освещение",
"item": "https://example.com/catalog/lighting/"
},
{ "@type": "ListItem", "position": 3, "name": "Светильник Пример" }
]
}Replace the example with your own data. After clearing the cache, check what happens when the product is saved normally in the CMS: the old URL should not reappear during a routine product page update.
Check old URLs separately
Changing the JSON-LD does not configure redirects. If a section has moved, the old URL should be handled according to the migration plan. Check where it leads and whether there is a chain of unnecessary redirects.
Internal links should point directly to the active URL. Review the menu, links in text, and sitemap: old paths may remain there regardless of the breadcrumbs. The right approach differs when a category is removed without a replacement versus when it is simply renamed.
Check the product page using different entry points
Open the product directly, then through the new category, and through an old saved link. The markup should describe the correct path in each case, without depending on the current session history. Repeat the same check on a separate product in another category.
Enter the public URL in Google’s Rich Results Test and run the test. Open the detected breadcrumbs and review the errors and item order. Save the result alongside the table of corrected URLs. For other discrepancies, see the Schema.org errors guide; for how to build markup, see the structured data guide. After the move, check the affected pages with a technical audit.