# What happens to breadcrumbs after a website migration? > In a migration, breadcrumbs commonly break in one of three ways, and each weakens how your site structure is communicated. First, the new platform rebuilds the breadcrumb trail with the wrong hierarchy, or a flat one, so it no longer reflects how your pages actually nest. Second, the breadcrumb links carry over but point at old URLs, so they 404 or rely on redirects after the move. Third, the breadcrumb structured data is dropped, so the markup that could show your hierarchy in search results disappears. Breadcrumbs do two jobs: they help visitors and crawlers understand where a page sits in your structure, and their structured data can appear in search results as the path to the page. So after a migration you rebuild the breadcrumb trail to mirror your real, new hierarchy, point its links at the new URLs, and restore the BreadcrumbList structured data so it matches the visible trail. None of this is a major ranking lever on its own, but a broken or missing breadcrumb removes a clear structural signal and a useful navigation aid. WPBuildAI scans your site and returns the URL list and structure, so you can rebuild breadcrumbs that reflect how your pages actually nest after the move. Source: https://wpbuildai.com/what-happens-to-breadcrumbs-after-migration/ By lawrence-arya ยท 2026-06-10 --- In a migration, breadcrumbs commonly break in one of three ways, and each weakens how your site structure is communicated. First, the new platform rebuilds the breadcrumb trail with the wrong hierarchy, or a flat one, so it no longer reflects how your pages actually nest. Second, the breadcrumb links carry over but point at old URLs, so they return 404 or rely on redirects after the move. Third, the breadcrumb structured data is dropped, so the markup that could show your hierarchy in search results disappears. Breadcrumbs do two jobs: they help visitors and crawlers understand where a page sits in your structure, and their structured data can appear in search results as the path to the page. So after a migration you rebuild the breadcrumb trail to mirror your real, new hierarchy, point its links at the new URLs, and restore the BreadcrumbList structured data so it matches the visible trail. None of this is a major ranking lever on its own, but a broken or missing breadcrumb removes a clear structural signal and a useful navigation aid. WPBuildAI scans your site and returns the URL list and structure, so you can rebuild breadcrumbs that reflect how your pages actually nest after the move. Not every rich result has survived the past year, which is reason to verify rather than assume: Google [retired FAQ rich results in May 2026 and removed the associated reporting in June](https://searchengineland.com/google-to-no-longer-support-faq-rich-results-476957), so check current documentation for whichever types you depend on before treating old behaviour as the baseline. ## What breadcrumbs do To know why they matter in a migration, start with their two jobs. As a navigation aid, the breadcrumb trail shows a visitor where they are in your site, the path from the home or a top section down to the current page, so they can move up the hierarchy easily. As a structural signal, the trail, especially its BreadcrumbList structured data, tells search engines how your pages relate, and that path can appear in search results in place of a plain URL, as the [breadcrumb structured data](https://developers.google.com/search/docs/appearance/structured-data/breadcrumb) guidance describes. So breadcrumbs are both a usability feature and a way of expressing and displaying your site structure. A migration can damage either role, which is why they are worth checking rather than assuming they came across with the rest of the design. ## Failure one: the hierarchy rebuilds wrong The first breakage is structural. The breadcrumb trail is generated from your site hierarchy, how pages nest under sections and categories, and a new platform builds that trail from its own understanding of your structure. If the migration changes how pages are organized, or the new platform defaults to a flat or different hierarchy, the breadcrumb no longer reflects your real structure, showing a wrong or shortened path. This is closely related to preserving your overall structure and internal links, covered in [preserving internal links when migrating](/how-to-preserve-internal-links-when-migrating), because breadcrumbs are an expression of that same hierarchy. The fix is to rebuild the trail so it mirrors how your pages actually nest on the new site, which often means configuring the new platform's breadcrumb logic to match your intended structure rather than accepting its default. ## Failure two: breadcrumb links point at old URLs The second breakage is the URL one, the same problem that affects other links in a migration. Each step in a breadcrumb is a link to a parent page, and if those links carry over pointing at old URLs, they break or bounce through redirects after the move. A breadcrumb that links to the old category URL is a small but real broken link, and it undercuts the navigation aid it is meant to provide. The fix is to ensure every breadcrumb link points at the new URL of its parent, just as you would update any internal link, following the [site move](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) discipline. Because breadcrumbs are generated, fixing the generation to use new URLs usually corrects them site wide at once, rather than page by page. ## Failure three: the structured data is dropped The third breakage is the invisible one. The BreadcrumbList structured data is what lets your breadcrumb path appear in search results and confirms your hierarchy to search engines, and a migration can drop it if the new platform or theme does not output it, or if it relied on a plugin that did not move. The visible breadcrumb might still show on the page while the underlying markup is gone, so the loss is easy to miss. Restoring it means making sure the new platform outputs valid BreadcrumbList markup that matches the visible trail, the same kind of invisible signal preservation as canonical tags and other schema, covered in [does changing platform affect schema markup](/does-changing-website-platform-affect-schema-markup). Keep the markup and the visible breadcrumb in agreement, since markup that disagrees with what is shown is discounted. ## Keep the visible trail and the markup in agreement A theme that runs through all three failures is consistency: the breadcrumb a visitor sees, the links it contains, and the structured data behind it should all tell the same story about your hierarchy. After a migration, it is possible to fix one and not the others, leaving, say, a correct visible trail with stale markup, or correct markup with links pointing at old URLs. That inconsistency weakens the signal, because search engines trust markup that matches the page. So treat the breadcrumb as a single feature with three aligned parts, and verify all three together: the hierarchy is right, the links point at new URLs, and the structured data matches what is shown. This is the same accuracy principle as [which structured data types matter](/which-structured-data-types-matter-for-seo-and-ai): the markup must mirror the visible content. ## Steps to fix breadcrumbs after a migration 1. **Map your real hierarchy** of sections, categories, and pages. 2. **Rebuild the breadcrumb trail** to mirror that hierarchy on the new site. 3. **Point every breadcrumb link** at the new URL of its parent. 4. **Restore BreadcrumbList structured data** that matches the visible trail. 5. **Confirm consistency:** hierarchy, links, and markup all agree. 6. **Spot check inner pages**, not just the homepage, after launch. ## Worked example: rebuilding a category trail Imagine a content site with a clear hierarchy, sections containing categories containing articles, moving to a new platform. After the move, the team checks the breadcrumbs and finds two problems: the new platform built a flat trail that skips the category level, and the breadcrumb structured data is not being output at all. The visible links also point at the old category URLs. They reconfigure the platform's breadcrumb logic so the trail shows the full path from section to category to article, matching the real hierarchy, and they update the links to the new category and section URLs. They enable BreadcrumbList markup that mirrors the visible trail. They spot check several inner articles to confirm the trail, links, and markup all agree. The breadcrumbs again express the site structure correctly and become eligible to show as the path in results, because all three parts were rebuilt in agreement, the same care as restoring [canonical tags](/what-happens-to-canonical-tags-after-migration). ## Limitation: breadcrumbs are a minor, structural signal It is fair to keep this in proportion. Breadcrumbs are a useful navigation aid and a structural signal that can enhance how your pages appear, but they are a minor ranking factor at most, so fixing them will not lift a page that ranks poorly for content reasons, and losing them will not collapse a page that is otherwise strong. Their value is in clarity and usability, helping visitors and crawlers understand your structure, and in the chance of a tidier search appearance, not in a ranking boost. So restore them because a broken structural signal and navigation aid is worth fixing, and because consistency across your markup matters, but do not expect breadcrumbs to move rankings on their own. They are part of a coherent, well structured site, which is the real goal. ## Common mistakes - Accepting the new platform's flat or wrong breadcrumb hierarchy. - Leaving breadcrumb links pointing at old URLs. - Losing the BreadcrumbList structured data when a plugin or theme changes. - Fixing the visible trail but leaving the markup stale, or the reverse. - Checking only the homepage and missing broken breadcrumbs on inner pages. ## Key points After a migration, breadcrumbs often break in one of three ways: the hierarchy rebuilds wrong or flat, the breadcrumb links point at old URLs, or the BreadcrumbList structured data is dropped. Rebuild the trail to mirror your real new hierarchy, point every breadcrumb link at the new URL of its parent, and restore the structured data so it matches the visible trail, keeping all three parts in agreement. Spot check inner pages, not just the homepage, since breadcrumbs are generated and a default can be wrong site wide. Breadcrumbs are a navigation aid and a structural signal that can appear in results, but a minor ranking factor, so restore them for clarity and consistency rather than expecting a ranking gain. They are part of a coherent, well structured site. WPBuildAI scans your site and returns the URL list and structure, so you can rebuild breadcrumbs that reflect how your pages actually nest after the move. Send your web address for a free analysis. Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.