A domain migration can fail for a reason no technical audit will catch: when the old content was thin or templated, Google’s quality systems may decline to index the replacement, no matter how clean the new code is.
What this means for you
- Technical fixes can’t repair a quality problem rooted in thin or duplicate content.
- Redirects pass link signals; they don’t carry a quality verdict.
- Templated layouts fare worse as quality standards tighten.
- A real rebuild means original copy, real structure, and sustained proof of quality.
- Skipping the content fix during a migration usually just repeats the failure.
The migration that should have worked
Writing for Search Engine Journal on October 16, 2026, SEO consultant Marie Haynes described sites that refuse to index after migrating, even when every technical box is checked: change of address submitted, redirects mapped, internal links updated, sitemap generated. She stresses the theory is unproven and published to start discussion.
Haynes is known for diagnosing Google algorithm hits, which is why the theory is getting discussion rather than dismissal. It remains her hypothesis, not confirmed Google guidance.
Her documented case was a hobby blog, not a small business, where Search Console reported roughly 98% of URLs not indexed after the move. Small businesses hit the same scenario when they rebrand, switch providers, or retire an outdated site, and when rankings don’t follow, the usual assumption is a broken redirect rather than a content problem that was there all along.
For a service business depending on local search, the gap between indexed and not indexed is the difference between a site that generates calls and one that sits invisible.
Her theory is specific: a migration triggers a fresh quality review, and Google’s standards for that review have tightened. Search Console lists page quality as one reason a valid page may not be indexed, which is the hook for her argument. The signal she thinks matters most is originality.
For a small business site made mostly of stock copy and a generic layout, that explanation lands close to home. It’s part of why a quality rebuild has to mean more than moving old pages to a new address.
Thin content doesn’t reset with a new domain
Google’s own guidance on creating helpful content describes the kind of page that struggles no matter the domain: copy built to fill a template, pages that could describe any business in any city, and content that exists mainly to hold a lead form.
A one-page site with a hero image, three paragraphs of boilerplate, and a contact form fits that description closely. So does a five-page template where only the city name changes between locations.
A plumbing company with three paragraphs about quality service repeated across five city pages is the textbook case; a restaurant site with a gallery and a PDF menu but no real description of the food is another.
The same logic applies to a site that never migrates. Haynes argues Google’s quality standards are now much stricter than when thin pages were first published.
None of that is unusual, and it isn’t against any rule. It is simply the kind of page Google’s ranking systems are built to deprioritize, and that evaluation travels with the business, not the URL.
What templated signals to a quality system
The Helpful Content system was folded into Google’s core ranking systems in the March 2024 core update, so there is no longer a separate classifier to lift. Quality scoring now sits inside the systems that rank every page.
The accompanying March 2024 spam update introduced a policy against scaled content abuse: mass-produced pages made mainly to rank rather than help readers. Google’s policy targets that intent, so a handful of templated small-business pages is not automatically a violation, though it can look similar.
Backlinks are the usual suspect, but Google’s documentation says permanent redirects don’t cause a loss of PageRank, so a correctly redirected domain isn’t starting from zero. That is part of why Haynes looks past links and at the content itself.
It also explains why the same content can rank passably for years and then vanish once a move prompts a fresh evaluation.
A migration doesn’t reset a site’s quality score. It invites a fresh, stricter review the old domain never had to pass — our paraphrase of an unproven theory.
That is the proposed mechanism behind migrations that stall with no visible technical cause: the new domain gets evaluated on its own merits, and content that was never original enough to stand alone fails that test.
The Core Web Vitals trap
Site owners often chase Core Web Vitals next, assuming slow loading is the real blocker. The thresholds are unchanged, per web.dev: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1, each at the 75th percentile of real visits.
Google replaced First Input Delay with Interaction to Next Paint in March 2024, so advice built on the older FID benchmark is outdated.
Hosting matters, though uptime is not a documented ranking factor; sustained outages mainly interfere with crawling and can push pages out of the index.
On WordPress, heavy plugin stacks and unoptimized images are common causes of poor scores, and trimming them is worth doing regardless. But a fast page built on thin content is still thin.
Passing all three is good practice on any migration. It will not, by itself, fix a quality problem that lives in the content rather than the performance layer.
Here’s what separates a site that keeps losing rankings from one built to hold them.
| Signal | Templated site | Quality rebuild |
|---|---|---|
| Page copy | Boilerplate repeated across pages | Unique copy written for the business |
| Structure | Same layout per page or location | Pages built around specific services |
| Legal pages | Missing or generic | Present and specific to the business |
| Update cadence | Untouched for years | Monthly content and technical updates |
| Monitoring | None or unused | Analytics tracked and acted on |
What a quality rebuild actually requires
A quality rebuild starts with original writing for every page, not reworded boilerplate. Service pages get built around what the business actually does, not a generic template with the city name swapped out.
Technical fundamentals still matter inside that rebuild: clean URL structure, one clear topic per page, internal links between related services, and legal pages that match the business rather than a boilerplate template.
Ongoing maintenance matters as much as the initial build. Update cadence isn’t a documented ranking factor, but a maintained site stays accurate, and accuracy is what the quality guidance asks for.
Originality matters more than page count. A tightly built five-page site with unique content will often outperform a ten-page site padded with filler.
Analytics and testing close the loop. Without tracking what visitors actually do on the site, there’s no way to know whether the rebuild solved the original problem or just moved it.
Why small business sites fall into this trap
Many small businesses already have a strong Google Business Profile with nothing solid behind it, or an aging site that still pulls traffic and converts almost none of it. Both situations usually trace back to the same root cause.
The pattern shows up the same way again and again.
- A Google Business Profile with strong reviews but a thin or outdated website behind it
- A site built years ago on a page builder that hasn’t been touched since
- Service pages that read the same for every city or neighborhood served
- No blog, no case studies, nothing that demonstrates real experience
The fix is rarely more pages or flashier design. It is original content, clear structure, and visible proof over time that the site is maintained rather than abandoned.
That takes patience as much as consistent execution, but it is the only path that actually sticks.
If the current site still isn’t producing leads, the problem is often the content strategy, not just the design. ProXSites builds original, maintained sites instead of reshuffling the same template onto a new domain.
Sources
- Marie Haynes, Search Engine Journal, Oct 2026
- Google Search Central, helpful content guidance
- Google Search Central Blog, March 2024 spam policies
- web.dev, Core Web Vitals
Disclosure: ProXSites publishes this post and sells website builds and maintenance, so it has a commercial interest in the advice here. We have no affiliation with Google or Marie Haynes Consulting, and Haynes’ migration theory is her unproven hypothesis, not Google guidance.
