You keep your Google sitelinks through a migration by keeping the structure they are built from intact, because sitelinks are generated automatically from your URLs, your navigation, and your internal linking, not set by hand. So the way to hold onto them is to preserve the same URLs, or 301 them to matching pages, keep the same clear navigation and internal-link structure, and keep your page titles descriptive, so Google continues to recognize the same important pages under your brand. Expect some flux right after launch, since Google re-evaluates the new site over a few crawls, and sitelinks can briefly change or disappear before settling. If the structure is faithful, they return. WPBuildAI rebuilds the site with the same URLs, navigation, and internal links, and maps every URL to a verified 301, so the structure your sitelinks depend on carries straight through the move.

The first thing to accept is that you do not set sitelinks; Google generates them. There is no field that pins them, and the old Search Console tool that let you demote a sitelink is gone. Google’s own guidance is that sitelinks are chosen automatically from your site’s structure. That sounds like it leaves you powerless, but it is actually the key to keeping them: since they come from structure, preserving the structure preserves the inputs Google used to choose them. So the whole strategy for a migration is not to find a setting to protect, but to make sure the site Google recrawls looks structurally like the site it built the sitelinks from.

It helps to know the raw material. Google assembles sitelinks from signals that together say which pages are central to your site: a clear navigation that points to your main sections, strong internal linking to those pages, descriptive page titles and headings, and stable URLs that resolve. In effect, sitelinks are Google’s read of your hierarchy, its best guess at the handful of pages a visitor searching your brand most likely wants. That is why a well-organized site with confident internal linking earns them and a muddled one does not. Since traffic and importance concentrate on a minority of pages anyway, as the Ahrefs study shows, sitelinks are largely Google surfacing the pages you already treat as important through how you link to them.

A sitelink is a link to a specific page, so the most direct way to break one is to break the page it points to. If a URL that was showing as a sitelink 404s after the migration, that sitelink cannot survive. So preserve your URLs wherever you can, and where a URL must change, 301 it to the matching page, exactly as a careful site move requires. This is the same URL discipline that protects rankings generally, applied to the specific pages Google chose to feature. Keeping the addresses stable means the pages behind your sitelinks keep resolving, so Google has no reason to drop them for want of a working target.

Keep the navigation and internal linking consistent

Beyond the individual URLs, sitelinks depend on the shape of the site, so preserve that shape. Keep the same main navigation, pointing to the same key sections, and keep the internal linking that signals which pages are important, since that is a large part of how Google infers your hierarchy. A rebuild is a tempting moment to reorganize everything, but scrambling the navigation and internal links tells Google the hierarchy changed, and it will re-derive sitelinks from the new picture rather than keep the old ones. Preserving your internal linking through the migration is therefore not just good for rankings; it is specifically what keeps your sitelinks recognizable. The platform itself is not the factor here, as the Backlinko analysis of ranking signals makes clear; the structure is.

Expect some flux, then recovery

Set the right expectation for the days after launch. Even with a faithful rebuild, Google has to recrawl the new site and re-establish its read of your structure, and during that window sitelinks can wobble, change, or briefly vanish. This is normal re-evaluation, not a failure, and it is not a signal to start changing things in a panic. Help it along by submitting a fresh sitemap so Google discovers the new pages quickly, then give it the crawls it needs. If the structure genuinely carried over, sitelinks re-form over the following weeks. The mistake to avoid is reacting to the temporary flux by reorganizing the site, which only resets the clock.

  1. Preserve your URLs, and 301 any that must change to the matching page.
  2. Keep the same navigation pointing to the same key sections.
  3. Preserve internal linking to your important pages so the hierarchy is clear.
  4. Keep titles and headings descriptive so Google can label the pages.
  5. Submit a current sitemap so the new structure is discovered quickly.
  6. Wait through the flux and monitor, without reorganizing in the settling window.

Consider a company whose brand search showed six sitelinks, to its product, pricing, about, blog, contact, and support pages. Migrating off WordPress, the rebuild kept every one of those URLs identical, reproduced the same top navigation pointing to the same sections, and preserved the internal links that led to them, with descriptive titles unchanged. A fresh sitemap went in at launch. For about two weeks the sitelinks flickered, dropping to a few and then filling back in as Google recrawled. Because nothing structural had actually changed from Google’s point of view, the full set of sitelinks re-formed, and the brand result looked the same after the move as before it.

It is honest to bound this. You can preserve every input perfectly and still not command the exact sitelinks you had, because they are algorithmic and Google can change which it shows, how many, or whether it shows any, independent of your migration. Preserving structure maximizes the odds and speeds recovery, but it is influence, not control. Sitelinks also track your brand’s overall standing, so a site with weak structure or authority may show few regardless. Treat the goal as giving Google every reason to keep featuring your pages, while accepting that the final decision, and some ongoing variation, is Google’s.

Common mistakes

  • Treating sitelinks as a setting to configure, when they are generated from structure.
  • Letting a featured page’s URL 404 instead of preserving or 301-ing it.
  • Reorganizing navigation and internal links during the rebuild, resetting Google’s read.
  • Panicking at the normal post-launch flux and changing things, which restarts the clock.
  • Skipping the fresh sitemap, so Google is slow to rediscover the new structure.

Key points

You keep your Google sitelinks through a migration by preserving the structure they are generated from, because they are algorithmic, built from your URLs, navigation, internal linking, and titles, not set by hand. Keep the same URLs or 301 them to matching pages so featured pages still resolve, keep the same navigation and internal linking so the hierarchy reads the same, keep titles descriptive, and submit a fresh sitemap. Expect the sitelinks to wobble for a couple of weeks while Google re-evaluates the new site, and resist reorganizing in that window, since that only resets the process. Sitelinks are ultimately Google’s call and never guaranteed, so the aim is to give it every reason to keep showing your pages. WPBuildAI rebuilds the site with the same URLs, navigation, and internal links, and maps every URL to a verified 301, so the structure your sitelinks depend on carries through. Send your web address for a free analysis.

Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.