# Will migration affect my Google Discover traffic? > A migration does not have to affect your Google Discover traffic, but Discover is more fragile than search, so the move has to protect the specific things Discover rewards: being indexed, having large high-quality images, and clear freshness and quality signals. Discover is not query-based; it surfaces content in a feed based on quality, interest, and engagement, and eligibility depends on your pages being indexed and carrying a large image, at least 1200 pixels wide, with the max-image-preview:large setting allowed. So if the migration breaks indexing, drops or shrinks your featured and Open Graph images, or scrambles publish signals, Discover traffic can fall sharply. Protect them and it holds. Because Discover is volatile even without a migration, expect some normal fluctuation regardless. WPBuildAI preserves your URLs and indexing, keeps your large images and image settings intact, and carries your publish signals across, so the things Discover depends on survive the move. Source: https://wpbuildai.com/will-migration-affect-google-discover-traffic/ By lawrence-arya ยท 2026-06-18 --- A migration does not have to affect your Google Discover traffic, but Discover is more fragile than search, so the move has to protect the specific things Discover rewards: being indexed, having large high-quality images, and clear freshness and quality signals. Discover is not query-based; it surfaces content in a feed based on quality, interest, and engagement, and eligibility depends on your pages being indexed and carrying a large image, at least 1200 pixels wide, with the max-image-preview:large setting allowed. So if the migration breaks indexing, drops or shrinks your featured and Open Graph images, or scrambles publish signals, Discover traffic can fall sharply. Protect them and it holds. Because Discover is volatile even without a migration, expect some normal fluctuation regardless. WPBuildAI preserves your URLs and indexing, keeps your large images and image settings intact, and carries your publish signals across, so the things Discover depends on survive the move. ## Discover is a feed, so it rewards different things than search The reason Discover needs its own thought is that it does not work like search. Search answers a query; Discover, as Google's [documentation on Discover](https://developers.google.com/search/docs/appearance/google-discover) explains, surfaces content in a feed based on what it judges a person will find interesting, drawing on quality, topical interest, and engagement rather than a search term. That difference changes what protects your traffic. In search you defend rankings for queries; in Discover you defend eligibility, which rests on being indexed, having a compelling large image, and signaling freshness and quality. So a migration that would be fine for search can still hurt Discover if it quietly damages one of those, which is why Discover deserves a specific checklist rather than being folded into general SEO. ## Indexing is the floor Everything in Discover starts with being indexed. Content that is not in Google's index cannot appear in the feed, so the first and largest risk in a migration is anything that breaks indexing: a stray noindex, a robots.txt block carried from staging, or broken URLs that were never redirected. Preserve your URLs, apply 301s where addresses change, and confirm pages stay indexed, exactly as a [careful site move](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) requires. This is the same discipline that protects search rankings, and it is the foundation for Discover too, because a page dropped from the index loses both at once. If Discover traffic vanishes after a migration, a broken indexing signal is the first thing to check. ## Images are the make-or-break signal Discover leans on images more heavily than search does, and this is where migrations often quietly fail. Discover favors large, high-quality images, generally at least 1200 pixels wide, and it needs the max-image-preview:large setting allowed so Google may show the big preview the feed depends on. A migration that shrinks your featured images, drops the Open Graph images, or tightens the image-preview setting can cut Discover eligibility even when the text is intact. So preserve your images at full size, keep the large-preview setting, and make sure the [Open Graph and featured images survive the move](/what-happens-to-open-graph-images-after-migration). Keeping images fast and well-sized also helps your [Core Web Vitals](https://web.dev/articles/vitals), which supports the engagement Discover rewards. ## Freshness and quality signals Discover favors content that is timely and genuinely engaging, so the signals of freshness and quality matter. Preserve your publish dates and update signals, since [posts keeping their publish dates](/do-posts-keep-publish-dates-after-migration) is part of how freshness reads, and avoid resetting every date to launch day, which can misrepresent old content as new and confuse the signal. Keep publishing after the migration too, because a feed rewards an active, quality source, and a sudden silence around launch can cost momentum. Since engagement and interest concentrate on a minority of strong pieces, as the [Ahrefs study](https://ahrefs.com/blog/search-traffic-study/) pattern of concentration suggests, protect the freshness and quality of your best content first, and keep the cadence going. ## Expect volatility either way Set the right expectation, because Discover is genuinely unstable by nature. Even with nothing changed, Discover traffic spikes and drops as Google's feed decisions shift, so a noisy chart after a migration is not automatically a migration problem. The way to read it is to separate the normal volatility from a real break: if indexing, images, and freshness were preserved, fluctuation that trends back to normal is just Discover being Discover. A sustained collapse, by contrast, points to a broken signal to hunt down. So do not panic-diagnose every dip, but do confirm the fundamentals are intact, and give Google time to reprocess the recrawled site before concluding anything. ## Steps to protect Discover traffic in a migration 1. **Preserve URLs and indexing**, with 301s where addresses change. 2. **Keep large, high-quality images**, at least 1200 pixels wide, on your content. 3. **Allow max-image-preview:large** so Google can show the big preview. 4. **Carry publish dates and freshness signals** across rather than resetting them. 5. **Keep publishing after launch** to maintain source momentum. 6. **Separate normal volatility from a real break** before diagnosing a drop. ## Worked example: holding a feed-driven traffic source Consider a lifestyle publisher that got a large, spiky share of its traffic from Google Discover, powered by strong articles with big lead images. Migrating off WordPress, the team treated Discover as its own risk: they preserved every URL and confirmed pages stayed indexed, carried the featured and Open Graph images across at full size, kept max-image-preview:large allowed, and preserved the original publish dates. They kept publishing on their normal schedule through launch. Discover traffic wobbled for a couple of weeks, as it always did, but it did not collapse, because none of the signals it depends on had broken. Had they shrunk the images or reset the dates, the story would have been very different. ## Limitation: Discover is never guaranteed It is honest to bound this. You can preserve every signal perfectly and still see Discover traffic move, because Discover is a feed Google controls, eligibility is not a guarantee of appearance, and Google can change what it surfaces independent of anything you did. Discover also is not something you can directly optimize into like a ranking; you make content eligible and compelling, and Google decides. So treat the migration goal as protecting the indexing, images, and freshness that keep you eligible, while accepting that Discover traffic is inherently uncertain and will fluctuate regardless of a clean move. Preserving the signals maximizes your odds; it does not lock in the traffic. ## Key points A migration does not have to affect your Google Discover traffic, but Discover is fragile, so the move must protect the specific things it rewards: indexing, large high-quality images, and freshness. Keep your URLs and indexing intact with 301s, preserve featured and Open Graph images at full size with max-image-preview:large allowed, carry publish dates across rather than resetting them, and keep publishing after launch. Discover is volatile by nature, so separate normal fluctuation from a real break before diagnosing a drop, and check indexing and images first if traffic collapses. Remember that Discover is a feed Google controls, so eligibility is not a guarantee, and the aim is to maximize your odds, not lock in the traffic. WPBuildAI preserves your URLs and indexing, keeps your large images and image settings intact, and carries your publish signals across, so the things Discover depends on survive the move. Send your web address for a free analysis. Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.