New Domain Not Getting Indexed: A Rebrand Recovery Plan
A rebrand migration can fail despite valid redirects, so recovery depends on separating URL-move defects from canonical, indexing, and content-value signals.
· 13 min read
A site that had averaged more than 1.3 million Google impressions across three months reportedly lost about 90% of its impressions four days after a rebrand. For teams facing a new domain not getting indexed issue, the practical payoff is a repeatable way to separate migration defects from broader indexing and content-eligibility problems before changing thousands of URLs.
The case comes from an r/bigseo post in which the site owner reported moving roughly 1,900 pages on August 12, 2026, using one-to-one 301 redirects, new canonicals, XML sitemaps, and Search Console Change of Address. The owner then reported that many new URLs appeared as “Crawled – currently not indexed,” while Google continued selecting some old-domain URLs as canonicals.
That combination should not be treated as proof of one cause. It is a diagnosis problem involving the redirect map, Google’s canonical selection, page-level index eligibility, and the signals available across both domains.
Start with the reported timeline, not a theory
The source owner reported a move on August 12, 2026, initial stability for several days, and a sharp decline around August 16. The source excerpt also says that a spam update rolled out a couple of days after that decline, but it does not provide verified rollout start or completion dates. No precise update timeline should therefore be used to assign causation.
The reported sequence makes a quality or ranking-system overlap worth investigating, but it does not establish that an update caused the loss. A domain migration can itself prompt Google to recrawl, consolidate duplicates, reassess templates, and reevaluate destination URLs. Several events can occur in the same week without one explaining all of them.
A useful working table separates reported facts from recommendations and hypotheses:
| Period | Reported observation | What the team should test |
|---|---|---|
| Before August 12 | About 1.3 million impressions over three months | Which URL templates supplied the lost impressions? |
| August 12 | New domain launched with 301s and Change of Address | Are old URLs mapped one-to-one to equivalent new URLs? |
| First few days | Roughly 1,900 new pages initially indexed | Did Google crawl and render the destinations successfully? |
| Around August 16 | Impressions reportedly fell about 90%; average position neared 100 | Is the loss limited to one template or spread across the site? |
| Following period | New URLs were crawled but excluded; old URLs remained canonical in some cases | Are canonical, redirect, sitemap, and internal-link signals aligned? |
This distinction prevents an expensive wrong turn. Rebuilding content will not repair a redirect chain or an accidental noindex; rewriting redirects will not necessarily make a large group of low-differentiation pages eligible for indexing.
Why a new domain not getting indexed can be two problems
“Not indexed” is not a single technical diagnosis. Google can discover a URL, crawl it, render it, consolidate it with another URL, choose not to index it, or index it without showing it for meaningful queries. Each stage requires different evidence.
In the source owner’s account, Google crawled many new pages but did not retain them in the index, while some old URLs were still selected as canonicals. That creates two separate investigation tracks:
- Does Google accept the old-to-new URL relationship?
- Does Google consider the destination URL suitable to retain and surface?
A 301 is a strong move signal, not an unconditional command to index the destination. Google’s documentation on redirects and Google Search recommends permanent server-side redirects such as 301 or 308 for permanent moves. Its canonicalization guidance also explains that canonical selection uses multiple signals rather than a single tag or status code.
For example, a finance publisher with 2,200 earnings previews, result analyses, and call summaries could have technically valid redirects yet still need to demonstrate why each replacement page offers distinct value. Conversely, a useful page may remain excluded if the old URL, sitemap, internal links, and canonical tag send Google conflicting signals.
For a wider prioritization framework, see Audra’s guide to whether non-indexed pages affect SEO. Coverage states are evidence to investigate, not verdicts on an entire domain.
Verify migration mechanics before changing content
The source owner’s report includes several standard migration actions, but a checklist item being completed does not confirm that every URL behaves correctly. Testing five homepage variants is inadequate for a move involving roughly 1,900 pages.
Build a representative redirect sample
A team should export the top old URLs by clicks and impressions for the 90 days before the move. The sample should include the homepage, major category pages, the highest-value templates, URLs with external links, and a random long-tail set.
For every row, verify that:
- The old URL returns one server-side 301 or 308, rather than a 302, meta refresh, or JavaScript redirect.
- The redirect reaches the equivalent new URL in one hop.
- The new URL returns HTTP 200 and is not blocked by
robots.txtor anoindexdirective. - HTTP, HTTPS, www, and non-www variants resolve to one preferred final URL.
- Query parameters do not redirect users and crawlers to an irrelevant page.
Google’s site-move documentation recommends mapping old URLs to their new locations and monitoring the move. “Equivalent” matters: redirecting hundreds of detailed earnings pages to a category page or homepage is not a page-level migration.
Check canonical signals as a package
The strongest canonical setup is consistent across several surfaces: a self-referencing canonical on the new URL, a permanent redirect from the old URL, internal links pointing to the new URL, and a sitemap containing the new URL. Conflicting hreflang annotations, structured-data URLs, navigation links, or legacy sitemap entries can weaken that package.
Google selecting an old URL as canonical does not prove why it did so. It means the team should inspect the exact pair: the old URL’s redirect response, the new page’s declared canonical, rendered HTML, duplicate variants, and internal linking. It is better to describe this as an investigation than to assume Google interpreted any one signal as low quality.
Hostname inconsistency creates another duplicate cluster. Teams can review how to fix Google choosing www as canonical when both www and non-www versions complicate a domain move.
Use Search Console exports to locate the actual loss
The source post does not provide a verified third-party comparison or commenter analysis. The following workflow is a recommendation based on the owner’s reported symptoms: compare performance and index data at the URL and template level rather than relying on sitewide averages.
Export Search Console performance data for two comparable periods, such as the 28 days before August 12 and the 28 days after launch. Where seasonality matters, compare the same weekday mix and keep a longer 90-day view available for context.
Segment by page type and outcome
For the reported finance-publishing example, useful segments include:
- Earnings previews
- Quarterly results analyses
- Earnings-call summaries
- Company hub pages
- Editorial explainers
- Homepage and major navigation pages
For each segment, compare clicks, impressions, average position, index state, declared canonical, Google-selected canonical, and last crawl date. If company hubs and editorial pages remain visible while one templated earnings-page type disappears, that is evidence for a template-specific review. If nearly every template loses visibility and old canonicals persist widely, the migration implementation deserves more attention.
The analysis should also distinguish old URLs that still receive impressions from old URLs that are merely reported as indexed. Legacy URLs can remain in Google’s systems while a move is consolidating; their presence alone is not proof of a failed migration. A persistent pattern of old selected canonicals paired with excluded new equivalents is more actionable.
Where pages are indexed but still earn no visibility, the diagnosis differs. Audra’s page indexed but no impressions troubleshooting guide addresses that separate post-indexing problem.
Treat “Crawled – currently not indexed” as an eligibility signal
“Crawled – currently not indexed” means Google fetched a URL but had not selected it for indexing at that time. It is neither a permanent penalty label nor a guaranteed diagnosis of thin content. Google may revisit the decision as crawl, duplication, technical, and content signals change.
The source owner described AI-generated pages based on company filings and earnings-call transcripts, with additions such as official-source links and comparisons between expectations and reported results. Those additions may improve usefulness, but they should be evaluated page by page rather than assumed to resolve an indexing issue.
Google’s guidance on generative AI content does not prohibit AI-assisted content as a category. Google’s spam policies describe scaled content abuse as producing many pages primarily to manipulate rankings without adding value. The practical question is not whether a tool was used, but whether a page gives a reader a clear benefit beyond a rearranged filing, transcript, or newswire summary.
A useful review compares 30 to 50 excluded URLs with 10 URLs that remain indexed or perform well. Reviewers can assess source accuracy, unique analysis, repetition, visible authorship, update practices, and whether the page answers a specific investor question faster or better than the primary document alone.
Rebuild the weakest template before changing the whole site
A recovery plan should avoid publishing another 2,000 lightly altered pages, but it should also avoid deleting useful content without evidence. The better approach is to identify the weakest recurring template and improve a controlled cohort first.
Elements of a stronger earnings page
A higher-value results page may contain:
- The exact reporting period, filing date, and direct primary-source references.
- Revenue, EPS, guidance, and prior-period comparisons in a structured snapshot.
- A clear explanation of what changed and why it matters for that named company.
- Explicit labels separating reported facts, consensus expectations, and editorial analysis.
- Original charts or calculations derived from filing data.
- Material management commentary from the earnings call, with context rather than transcript restatement.
- A named editor or transparent methodology explaining automated extraction and human review.
- Links to prior-quarter coverage that support continued research.
The goal is not simply more words. A 1,500-word transcript paraphrase may remain interchangeable with other summaries, while a 500-word page with accurate calculations, transparent sourcing, and specific context can be more useful.
Starting with the 25 to 50 pages that previously earned the most clicks creates a measurable experiment. The team can materially improve that cohort, then compare crawl activity, canonical selection, index status, and impressions with unchanged pages. That design does not promise a Google response within a fixed period; it produces clearer evidence than changing every variable at once.
Use Google inspection and a local crawl together
The source owner reported that Bing indexed the new domain normally. That is useful evidence that URLs may be accessible to another search engine, but it does not validate Google indexing or ranking. Bing and Google use different systems for crawling, canonicalization, indexing, and ranking.
Google Search Console’s URL Inspection tool should be used on a deliberate set of pages: an old URL Google still selects, its new replacement, an excluded new URL, a revised high-value page, and a successfully indexed page. Compare live-test results, rendered HTML, robots directives, declared canonical, Google-selected canonical, and the fetched response.
A local crawl complements that URL-level work. In Audra, a team can crawl the old and new hosts, then use the redirect, canonical, internal-link, and page-audit outputs to export a prioritized list of old-host links, redirect chains, non-self-referencing canonicals, and repetitive page patterns. That list can be matched against Search Console URL samples, rather than treating either crawl data or Search Console alone as the full diagnosis.
Keep the old domain active while signals consolidate
Turning off the old domain immediately after a rebrand is a preventable risk. The old domain should stay registered and continue serving its one-to-one permanent redirects while the move remains incomplete.
Google’s site-move guidance recommends maintaining redirects and monitoring the transition. It does not provide a universal number of weeks after which an old domain can safely be retired. The appropriate duration varies by crawl frequency, site size, external-link profile, server reliability, and how quickly old URLs are replaced.
Teams should monitor at least five indicators:
- Old URLs still selected as canonicals.
- New URLs indexed and receiving impressions.
- Redirect failures, crawl errors, and Googlebot server-log activity.
- High-value external links still pointing to legacy URLs.
- Internal links, XML sitemaps, schema URLs, and hreflang references that retain the old host.
Updating social profiles and requesting backlink changes can support the move, but neither replaces a correct redirect map. A rebrand explanation on the new homepage may help users, but it is not a substitute for URL-level migration signals.
Run a 30-day recovery experiment, not a Google timetable
When impressions are down roughly 90%, a 30-day plan can organize work. It must not be read as a promise that Google will recrawl, reindex, or restore rankings within 30 days. Recrawl and evaluation timing varies, and a lack of immediate movement is not by itself proof that a change failed.
Days 1–5: establish a baseline
Export data from both Search Console properties, identify the top 100 lost old URLs, and crawl old-to-new pairs. Verify status codes, robots directives, canonicals, sitemaps, and internal-link targets.
Days 6–12: classify the failure
Label URLs by template, index state, selected canonical, and traffic loss. Decide whether the evidence points primarily to old-domain canonical retention, exclusions in one template, a crawl or rendering defect, or ranking losses among indexed pages.
Days 13–21: improve a representative cohort
Select 25 to 50 high-value pages in the most affected template. Add distinct analysis, transparent sourcing, stronger internal pathways, and visible methodology. Keep the remaining variables as stable as possible.
Days 22–30: monitor signals and choose the next test
Check whether revised pages are crawled, whether Google selects the new canonical, and whether index coverage or impressions change relative to unchanged pages. Continue fixing verified technical inconsistencies. If the cohort has not been recrawled or had adequate observation time, the result is still unknown; repeated requests for unchanged URLs are not a substitute for evidence-based testing.
FAQ
Why is my new domain crawled but not indexed after a domain migration?
Google may crawl a destination URL without choosing to index it immediately. Teams should check exact redirect equivalence, declared and selected canonicals, robots directives, duplicate variants, internal links, sitemaps, and the page’s distinct user value. Compare the old and new URL pair in Search Console instead of treating the coverage label as a complete diagnosis.
How long does Google take to transfer indexing to a new domain?
There is no fixed migration timetable. A smaller site with clean one-to-one redirects may consolidate faster than a site with thousands of URLs, frequent publishing, conflicting signals, or weak destination equivalence. Google recommends monitoring the move, and the old domain should continue serving permanent redirects until the transition is demonstrably stable.
Can an algorithm update affect a site during a rebrand?
Yes. A site remains subject to Google ranking and spam systems during a migration, but overlapping timing does not prove causation. In the reported case, the decline began around August 16, 2026, and the source says an update followed a couple of days later. That supports investigation, not a definitive attribution.
Does AI-generated content stop Google from indexing pages?
AI use alone does not automatically prevent indexing. Google’s published guidance focuses on whether automated or AI-assisted publishing adds value for users, especially at scale. Each page should offer accurate, distinct utility beyond reorganizing readily available source material, with transparent sourcing and a clear reason for the page to exist.
Should a site request indexing for every excluded page?
No. Indexing requests are most useful after a real technical issue is fixed or a high-priority page is materially improved. Bulk requests do not resolve canonical conflicts, weak redirects, or repetitive content. Testing a focused group of improved URLs provides more useful evidence than repeatedly submitting thousands of unchanged pages.
Sources
- https://www.reddit.com/r/bigseo/comments/1xpbf92/after_rebranding_new_domain_not_getting_indexed/
- https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
- https://developers.google.com/search/docs/crawling-indexing/301-redirects
- https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls
- https://developers.google.com/search/docs/essentials/spam-policies
- https://developers.google.com/search/docs/fundamentals/using-gen-ai-content
- https://support.google.com/webmasters/answer/9012289?hl=en