# How do I keep my featured snippets after a migration? > You keep featured snippets through a migration by protecting two things: the page's ranking and the exact piece of content the snippet was pulled from. A featured snippet is drawn from a page that ranks well for a query, lifting a concise answer, a list, or a table directly into the results, so it depends on both the page staying highly ranked and the specific content staying intact. That means the migration musts are the usual ones plus one extra. Set a 301 from the old URL to the new one so the ranking transfers, carry the content and metadata across in full so the page keeps its position, and preserve the precise structure the snippet used, the short answer paragraph, the ordered steps, or the comparison table, without rewording or reformatting it. If the migration changes the URL without redirecting, or restructures the answer into something different, the snippet usually disappears. The honest caveat is that featured snippets are volatile and never guaranteed, so the goal is to avoid disturbing what won the snippet, not to claim you can lock it in. WPBuildAI scans your site and returns each page's content and structure, so you can see exactly which passages earned snippets and confirm they survive the move. Source: https://wpbuildai.com/how-to-keep-featured-snippets-after-migration/ By lawrence-arya ยท 2026-06-10 --- You keep featured snippets through a migration by protecting two things: the page's ranking and the exact piece of content the snippet was pulled from. A featured snippet is drawn from a page that ranks well for a query, lifting a concise answer, a list, or a table directly into the results, so it depends on both the page staying highly ranked and the specific content staying intact. That means the migration musts are the usual ones plus one extra. Set a 301 from the old URL to the new one so the ranking transfers, carry the content and metadata across in full so the page keeps its position, and preserve the precise structure the snippet used, the short answer paragraph, the ordered steps, or the comparison table, without rewording or reformatting it. If the migration changes the URL without redirecting, or restructures the answer into something different, the snippet usually disappears. The honest caveat is that featured snippets are volatile and never guaranteed, so the goal is to avoid disturbing what won the snippet, not to claim you can lock it in. WPBuildAI scans your site and returns each page's content and structure, so you can see exactly which passages earned snippets and confirm they survive the move. Some result types have simply gone, so check what you are protecting still exists: Google [retired FAQ rich results on 7 May 2026 and dropped the reporting and Rich Results Test support in June](https://searchengineland.com/google-to-no-longer-support-faq-rich-results-476957), which means part of the old snippet playbook now protects nothing. ## What a featured snippet actually depends on To protect snippets, understand what they are made of. A featured snippet is a passage that Google lifts from a ranking page to answer a query directly at the top of results, as described in the guidance on [featured snippets](https://developers.google.com/search/docs/appearance/featured-snippets). Two conditions hold it in place. First, the page has to rank well for the query, because snippets are chosen from strong results, not from nowhere. Second, the page has to contain the specific, well structured passage that answers the query cleanly, a tight paragraph, a clear ordered list, or a table. A snippet is therefore the intersection of ranking and a quotable passage. A migration can threaten either, so keeping snippets means protecting both at once, not just keeping the page live. ## Protect the ranking with redirects and complete content The first half of the job is the standard migration discipline, because a snippet cannot survive on a page that loses its ranking. Set a 301 from the old URL to the new one, so the page's position transfers rather than collapsing into a 404, as the [site move](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) and [redirects](https://developers.google.com/search/docs/crawling-indexing/301-redirects) guides describe. Carry the page's content and metadata across in full, so it keeps the relevance and signals that earned its rank. If the page drops in ranking because the migration mishandled its URL or thinned its content, the snippet goes with the ranking, regardless of whether the passage is intact. So everything that protects normal rankings, covered in [migrate WordPress without losing SEO](/migrate-wordpress-without-losing-seo), is the foundation for keeping snippets too. ## Protect the exact passage that won the snippet The second half is specific to snippets and easy to overlook. The snippet was pulled from a particular passage, and that passage has to survive the migration in the same form. If your snippet was a concise definition paragraph, keep that paragraph as it was; if it was a numbered list of steps, keep the list with the same structure; if it was a table, keep the table. The danger is a well meaning rewrite or reformat during the move, turning the clean list into prose, or rephrasing the tight answer into something longer, which removes the exact content the snippet relied on. So before you let anyone redesign or rewrite during the migration, identify the snippet passages and mark them as content to preserve verbatim, not to improve. ## Identify which pages and passages hold snippets You cannot protect what you have not identified, so find your snippets before the move. Search Console shows which queries and pages drive impressions and clicks, and you can see which of your pages hold featured snippets for their queries. Snippets concentrate on a minority of strong pages, consistent with how unevenly traffic distributes, as the [Ahrefs study](https://ahrefs.com/blog/search-traffic-study/) shows, so the list is usually manageable. For each snippet page, note the exact passage that is being featured. This gives you a short, specific protection list: these pages must keep their rank, and these passages must survive unchanged. With that list in hand, the migration can proceed without quietly destroying the content that earns your snippets. ## Do not let a redesign reformat your answers Migrations often coincide with redesigns, and redesigns love to reformat content into new components, which is exactly where snippets die. A new template might convert your clean numbered list into a styled but differently structured element, or wrap your concise answer in extra design that changes how it reads to a crawler. Visually it can look better; structurally it can lose the snippet. So when a redesign accompanies the migration, treat your snippet passages as constraints: the new design must preserve the plain, liftable structure of those answers. This is the same care that helps content be quoted by AI features, discussed in [how to get cited in Google AI Overviews](/how-to-get-cited-in-google-ai-overviews), because both depend on clean, self contained answers that a machine can lift. ## Verify the passages survived after launch After the migration, confirm both halves held. Check that the snippet pages return 200 at their new URLs via the redirects, and that the featured passages are present in the same structure. Then watch Search Console over the following weeks to see whether the snippets persist, recover, or drop, so you can act if a specific page lost its passage or its rank. Because snippets are volatile, some movement is normal and not always caused by the migration, but a clear loss across your snippet pages right after launch points to a migration cause you can investigate, the same diagnostic approach as a broader [SEO drop after a redesign](/fix-seo-drop-after-website-redesign). Verification turns snippet protection from hope into something you can confirm. ## Steps to keep featured snippets through a migration 1. **Identify your snippet pages** and the exact featured passages before the move. 2. **301 each snippet page's URL** to its new address. 3. **Carry content and metadata across** so the page keeps its ranking. 4. **Preserve the featured passage** verbatim: the answer, list, or table. 5. **Stop a redesign** from reformatting those passages. 6. **Verify after launch** that the pages and passages survived, and watch Search Console. ## Worked example: protecting a how-to snippet Imagine a site that holds a featured snippet for a how to query, where Google features a clean numbered list of steps from one page. Before migrating, the team identifies the page and notes that the snippet is the numbered list. During the move they 301 the page's URL, carry its full content and metadata, and specifically preserve the numbered list in the same structure, resisting the new template's tendency to restyle it into a different element. After launch they confirm the page loads at its new URL and the list is intact, then watch Search Console. The snippet persists, because both its ranking and its exact passage survived. Had they let the redesign convert the list into a paragraph, the snippet would likely have dropped even with the ranking intact, which is the subtle way migrations lose snippets. ## Limitation: snippets are volatile and never guaranteed It is essential to be honest here, more than on most topics. Featured snippets are chosen algorithmically and are inherently volatile; they can appear, change, or vanish at any time, with or without a migration, and a competitor can take one by publishing a better answer. So you cannot guarantee a snippet survives, and you should not promise it. What you can do is remove the avoidable causes of loss by keeping the page ranking and the passage intact, which gives the snippet its best chance. Frame the work as protection, not control: you are making sure your migration is not what loses the snippet, while accepting that snippets move for reasons outside any migration, much like the general volatility behind [URL change effects on SEO](/what-happens-change-wordpress-site-url-seo). ## Common mistakes - Protecting the page's ranking but letting a redesign reformat the snippet passage. - Changing the snippet page's URL without a 301, removing its source. - Rewriting or condensing the exact answer that earned the snippet. - Not identifying which pages hold snippets before the migration. - Assuming a snippet is guaranteed and not verifying after launch. ## Key points You keep featured snippets through a migration by protecting both the page's ranking and the exact passage the snippet was pulled from. Identify your snippet pages and their featured passages first, then 301 each URL, carry content and metadata across so the page keeps its rank, and preserve the precise answer, list, or table verbatim, stopping any accompanying redesign from reformatting it. Verify after launch that the pages and passages survived, and watch Search Console. Be honest that snippets are volatile and never guaranteed, so the goal is to make sure the migration is not what loses them, not to promise they persist. This protection sits on top of normal ranking preservation, the same foundation as [migrating WordPress without losing SEO](/migrate-wordpress-without-losing-seo). WPBuildAI scans your site and returns each page's content and structure, so you can see exactly which passages earned snippets and confirm they survive the move. Send your web address for a free analysis. Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.