Repair breadcrumbs that point at old or unrelated service URLs

Read the trail as a customer

Start on the affected page and read the visible breadcrumb from beginning to end. Ask whether each level helps a visitor understand where they are and move toward a useful broader category. A trail can reflect a normal user route rather than mechanically mirror every segment of the URL. Do not add a city or category level the business does not actually use.

Source checks: Google Search Central: Breadcrumb structured data · Google Search Central: Canonical URL methods · Google Search Central: Crawlable link practices

Click each destination and record its role

Open every breadcrumb link and compare the destination with its label. Record redirects, old hostnames, or categories that no longer exist. A trail labeled Services should not open an unrelated ad page. The service page itself may appear as the final label; check its relationship to the rest of the hierarchy.

Compare the generated structured data

Inspect BreadcrumbList items and their positions, names, and item URLs. The visible trail can be current while plugin output still uses a previous URL structure. Conversely, valid-looking markup can describe a hierarchy no reader can use. Note which theme, plugin, or custom component generates each version so the editor can repair both sources.

Repair the shared trail definitions

Use the affected page and one comparison page.

• Choose the actual current parent destination for the service.
• Update visible links to current preferred URLs.
• Align structured-data labels and order with the intended user route.
• Check required breadcrumb properties through the supported test.
• Avoid old redirect URLs when the final destination is known.
• Verify two templates that share the same generator.

Avoid treating a feature preview as a navigation test

A structured-data result does not show whether a customer can use the trail. Google feature availability can also differ by result context and device; do not sell a guaranteed decoration. The business still benefits from correct, descriptive navigation. Do not create empty parent pages merely to make a trail longer or more keyword-rich.

Record hierarchy changes with the URL inventory

Store the approved parent and service destinations alongside page mappings. Retest breadcrumbs whenever a category, service slug, or domain changes. Check both the rendered page and generated data after the next publish. The immediate measure is coherent navigation and data output, not whether every search screenshot changes.

For a service with more than one reasonable route, choose an understandable trail that reflects the site's actual organization. Ask the editor how alternate trails are implemented before creating duplicate page copies. A visitor should reach the same useful service destination without being forced through several versions of the page.

Illustrative old parent path in the data block

An illustrative /window-repair page displays Home > Services > Window repair. The visible Services link goes to /services, but BreadcrumbList still uses /old-services. The editor updates the shared generator to the current preferred parent and retests another service. The correction aligns data and navigation without promising a search enhancement.

The service inventory records /services as the current parent for both window repair and door repair. Testing the second page confirms that the shared breadcrumb generator is corrected, rather than only one page's visible trail being edited.

Questions about this task