Your client moved to a new domain three months ago. The 301s are set, the change of address is submitted, the sitemap is uploaded, Googlebot can crawl the pages. Nothing is indexing. The Page Indexing Report says 98 percent of URLs are “crawled, currently not indexed.” You ran the technical checklist. Everything passes. So what is left?
According to a theory Marie Haynes published in October 2026, there is a reason that is not technical. Google re-runs a site quality assessment when a domain migrates, and the new domain is now being judged against stricter originality standards than the old one was. If the content on the new domain is commodity, Google will crawl it and choose not to index it. The site is not broken. It is not being found. It is being read and judged as not worth indexing.
This is a hard claim, and Haynes says so herself. It is a theory, not a confirmed mechanism. But the case studies she describes fit a pattern that agencies keep hitting without a name for it, and the practical path out of it is concrete even if the underlying mechanism is not fully settled.
The Exact Scenario That Refuses To Resolve
Here is the case Haynes walked through in her review of a site that blogs on a hobby topic. The site had performed well for years, then started a slow decline over the last twelve months. Just before the quality review began, the owner had started migrating to a new domain. The migration was done correctly on every technical axis:
- Change of address submitted in Google Search Console
- Every old URL mapped to its new URL with a 301 redirect
- Internal links updated to point at the new domain
- Google confirmed it could crawl the new site
- A fresh sitemap generated and uploaded for the new domain
Four months later, the Page Indexing Report showed 98 percent of URLs as not indexed. Worse, the pages that Google reported as indexed, some 33 of them, had the same result when inspected individually. Each one showed “crawled, currently not indexed.” Google was finding the pages. It was reading them. And it was choosing not to index them.
The Live Test in Search Console returned the same answer on every page checked. Each one reported the page was available to be indexed if certain conditions were met. Two of those conditions, a manual action and a duplicate of another page, were clearly not the case. The canonical pointed at the new site. The old page redirected properly. A third condition remained: the page quality must be high enough to warrant indexing. That is the condition nobody’s technical checklist covers.
98%
Of URLs showing “crawled, currently not indexed” four months after a technically correct domain migration. Only the homepage was indexed. The technical checklist passed on every item.

What Google’s Own Documentation Says About Originality
Google updated its helpful content documentation to describe the “main content” of a page, the part that fulfils the searcher’s need. Inside that definition, the emphasis that matters here is originality. Google describes it as “the extent to which the content offers unique, original information or perspectives that aren’t already available on other websites.”
Read that against the typical agency site. A lot of SEO agency content is commodity. “How to get more leads,” “the best CRM for small business,” “SEO checklist 2026.” The content is well written and thorough. It is not original. It says the same thing the top ten results already say, in the same order, with slightly different examples. It used to index because the domain had age, backlinks, and a track record. On the new domain, those signals are gone. What is left is the content itself, and the content fails the originality test.
Haynes asks the obvious question: if this is the standard, why was the old domain tolerated? Her answer is that the old domain had a site-quality score built from years of original content. The migration resets that score. The new domain is judged on its own content, and if that content is mostly commodity, the score comes in low and the indexing follows.
The Five-Point Test: Suppressed Or Just Not Yet?
Before you spend four months on a content rebuild, run this test to establish whether the new domain is actually being suppressed or just slow to process. Migrations take time. Google has said this explicitly, and some of the “nothing is indexing” cases resolve on their own in 6 to 8 weeks. The test separates the two, and it takes an afternoon.
Point 1: Originality ratio
Take your top 20 pages by old-domain traffic. For each one, ask: does this page offer information or perspective that is not already available on the top ten results for its target query? Score each page as original, partially original, or commodity. If more than 60 percent of the sampled pages are commodity or near-duplicates of the old domain, that is the problem. The index decision is being made on content quality, not crawl access.
Point 2: Unique pages live before GSC submission
Count how many genuinely new pages are live on the new domain. Not pages that were moved. Pages that did not exist on the old domain. Google’s indexing systems weigh the new domain’s own original output. If you have moved 200 commodity pages and written zero new ones, the domain’s originality signal is effectively zero. The rule of thumb: do not submit the sitemap to GSC until 10 or more genuinely unique pages are live. Submitting earlier just tells Google what it already knows, which is that the domain has no original content yet.
Point 3: Live Test output on 10 sampled pages
Run the Live Test in GSC on 10 pages across the new domain. If every page returns “available to index if the quality threshold is met” and the index check returns “crawled, currently not indexed,” the technical stack is confirmed healthy and the quality signal is the active constraint. If some pages index and others do not, look at what the indexed ones have in common. Usually it is the new, original content. That is your signal of what Google is responding to.
Point 4: The time checkpoint
If the migration is under 6 weeks old, the “crawled, currently not indexed” status may be a processing delay. Google has said migrations can take time. Set a hard checkpoint at 8 weeks. If the index count has not moved meaningfully by then, treat it as a quality suppression and start the content path. If it is still moving upward at 8 weeks, wait another 4 and re-check.
Point 5: Homepage vs. subdirectory behavior
In the case Haynes described, only the homepage indexed after four months. That pattern is a strong quality-suppression signal. Crawling access that works on the homepage but not the subdirectory pages means Google is reaching the site and making a per-page index decision. A crawl-blocking problem would show the opposite: no pages indexed, including the homepage, because the crawl itself is failing. If your pattern matches “homepage only,” the quality signal is the active constraint.
| Test point | What you check | Suppression signal |
|---|---|---|
| 1. Originality ratio | Top 20 pages scored original vs. commodity | More than 60% commodity |
| 2. Unique pages live | Genuinely new pages on the domain | Fewer than 10 live |
| 3. Live Test | 10 sampled pages, GSC output | All “quality threshold” condition |
| 4. Time checkpoint | Weeks since migration, index count trend | No movement past 8 weeks |
| 5. Homepage pattern | Which pages index, if any | Homepage only after 4+ months |
The LLM Originality Audit Haynes Recommends
Haynes’s practical next step is to run an originality audit on the previously top-performing pages before deciding the domain’s future. The method she describes is to use an LLM on each page and ask a specific question: what does this page say that is not already available on the top ten results for its target query? The answer to that question, applied across the site’s top pages, is the originality ratio from test point 1. If the answer is “nothing” or “the examples are slightly different,” the page is commodity and the domain’s index prospects are constrained by content, not crawl.
Run the audit before you decide the path forward. It takes a day for a 50-page site and it changes the decision you are about to make. A site where 40 of 50 pages have genuine original value has a different problem than one where 12 of 50 do. The first one is worth the content wait. The second one may be worth a fresh start on a new domain with brand new content from page one.
The Three Paths Forward
Once the test says “this is a quality suppression, not a delay,” there are three paths. Each has a different cost profile and a different realistic timeline. Pick the one that matches the client’s situation, not the one that sounds better in the pitch.
Path A: Add genuinely new content to the existing domain
Produce a small number of original, high-value articles on the new domain. Not another 50 commodity posts. Five to ten pieces that answer a real question with data, analysis, or perspective that is not in the top ten results anywhere. The open question Haynes raises is whether Google evaluates the value of individual new pages or whether the overall site-quality score, already dragged down by the commodity content, hinders indexing of the new pages as well. In practice, the answer has been: Google does index the new original pages even on domains with a weak overall score, but slowly, and the old commodity pages keep failing. The new pages become the anchor content that pulls the domain’s index forward.
Path B: Wait longer with a defined checkpoint
If the migration is under 8 weeks old and the originality ratio is acceptable, the simplest path is to wait. Set a hard checkpoint at 8 weeks. If the index count has not moved meaningfully, escalate to Path A or Path B. The checkpoint matters because “wait longer” without a date is how a quality suppression becomes a 12-month problem. The defined checkpoint is what keeps the situation honest.
Path C: Start completely over on a new domain
If the originality ratio is worse than 40 percent and the client has the budget and the timeline for it, the cleanest path is a new domain with brand new content written from page one. No migration, no moved commodity pages, no reset quality score to recover from. The new domain’s only content is original. It indexes as the original content ships, with no commodity baggage dragging the score down. The cost is the backlink profile and domain age, both of which have to be rebuilt. For most client sites with a meaningful backlink history, that cost is real and the Path A option is the better default. Path C is the right answer when the content library is fundamentally commodity and the client’s brand is not tied to the old domain.
The migration reset the quality score. The technical stack is doing its job. What the new domain has to earn back now is originality, and it earns it one genuinely new page at a time.
What To Tell The Client
The client’s question is “we did everything right, why is nothing working.” The honest answer is: the migration was technically correct, and the problem is not technical. Google is reading the new domain and judging the content. If the content is mostly commodity, the judgment is low and the index follows. That is not a fix. It is a content strategy decision.
Frame the conversation around the originality ratio, not the crawl report. The crawl report says “98 percent not indexed.” The originality ratio says “41 of our 50 top pages are commodity.” The second number is actionable. It tells you exactly what to do and how much. The first number is a symptom. The second is the cause.
The specific number to put in the client report: the percentage of top pages that pass the originality test, and the count of genuinely new pages needed to pull the index forward. A report that says “41 of 50 pages are commodity, we need 10 new original pages, and the sitemap should not be submitted until those are live” is a report the client can act on. A report that says “the domain is not indexing” is a report that stalls for another quarter.
What The Technical Team Actually Does During The Eight-Week Window
The client has a question that the originality conversation does not answer: what happens to the technical side while the content path runs? The answer is that the technical work is not done, it is waiting on the content, and the agency that does not explain that distinction is the one the client asks to “fix the indexing” in week four of an eight-week wait.
During the window, the technical team’s job is to hold the migration in a verifiable state. The 301s are live and the redirect chain is one hop from old to new, not two. The canonical tags on the new pages point at the new URLs, not the old ones. The change of address is confirmed in Search Console, and the sitemap is uploaded but not resubmitted on a loop. The Live Test on the ten sampled pages returns the “quality threshold” condition, which is the expected answer and the one that means the technical stack is healthy. The work in this window is confirmation, not action. Each confirmation gets written down in the account notes so the next person on the account does not re-run the same test and see the same answer and start the “fix” conversation again.
There is one technical action that is allowed and useful during the window: the original content that ships gets its sitemap entry added the day it is live. The sitemap submission is not the constraint, and the resubmission is what triggers the re-crawl of the new pages. The ten new original pages that are the Path A investment go into the sitemap as they ship, and the index check on those specific pages is what tells you whether the quality threshold is being met page by page. The pages that index are the proof the content path is working, and the pages that do not are the ones that need another look at the originality test.
The one technical action that is not allowed during the window is the robots.txt experiment. A client who is not indexing will ask whether the robots file is blocking something, and the answer in a technically verified migration is no, the crawl is happening, the index decision is the constraint. Chasing the robots file during the eight-week window is how the account burns the wait on a constraint that was already ruled out in the technical verification. The answer to the client is the Live Test output, not the robots file.
FAQ

Why does a technically correct migration still result in zero indexing?
The technical checklist covers crawl access, redirects, and sitemap submission. It does not cover the quality threshold that Google applies to each page when it decides whether to index it. A migration resets the domain’s quality score, and if the content on the new domain is mostly commodity, Google will crawl it, read it, and choose not to index it. The “crawled, currently not indexed” status in the Page Indexing Report is that choice, not a crawl failure.
How long should I wait before treating it as a quality suppression?
Set a hard checkpoint at 8 weeks post-migration. Google has said migrations can take time, and some “nothing is indexing” cases resolve on their own within that window. If the index count has not moved meaningfully by 8 weeks, treat it as a quality suppression and run the five-point test to confirm before starting the content path.
What is “crawled, currently not indexed” actually telling me?
It is telling you that Google reached the page, read it, and made a per-page index decision. The page is not blocked. It is not duplicate. It is not subject to a manual action. The condition that failed is the quality threshold. In a post-migration context, that threshold is being applied against the new domain’s originality record, which for a freshly migrated site is thin or nonexistent.
Should I submit the sitemap to GSC now or wait?
Wait until 10 or more genuinely new pages are live on the domain. Submitting the sitemap earlier tells Google what it already knows: the domain has moved, the redirects work, and the content is mostly commodity. The sitemap submission is not the constraint. The original content is. Submit it when the content is ready.
Does the quality suppression affect the old domain’s remaining pages?
The suppression applies to the new domain’s index decisions. The old domain’s pages, if still live and not redirected, retain their own index status. The redirect is what moves the index signal to the new domain, and that is where the quality assessment now applies. If the old domain is fully redirected and the new domain is suppressed, there is no fallback index state to rely on. The new domain’s content is the only thing that can move the index forward.
Where Verified Leads Fit For Migration Clients
Every migration case starts with the same underlying question: what is the client’s content actually worth, and is the domain’s future worth the cost of the content path? That assessment is where most agencies lose the next nine months of revenue, because the client sees a “technical fix” timeline and the agency sees a content strategy decision that needs to be made before the next renewal conversation.
Verified leads compress the assessment step for the content strategy half. You get clients who have already shown a need, with a contact whose email and phone a human has checked, so the strategy conversation starts the same week instead of the same quarter. Exclusive, internet-verified leads close at 6 to 12 percent against 1 to 3 percent on a cold list, which matters when the migration decision is a six-figure engagement. Read more about how verified B2B leads work.
The math on the content path is not close. Ten new original pages at $2,000 a page is a $20,000 content investment. One saved migration that keeps a $80,000 a year retainer from churning returns that four times over in the first year. The real risk is not the content cost, it is the diagnosis: a client who waits 12 months on a “technical fix” for what is a content problem has lost a year of organic pipeline. See our SEO lead packages or how to position the content strategy conversation.
Want a sample before you commit?
Ask us for a free sample list of verified leads in your niche. You review the data quality before you spend anything.
LeadPot delivers qualified leads for agencies that need predictable pipeline. See how SEO agencies find qualified leads or explore our lead generation packages.
Related: Your Client’s New Domain Won’