You launched the migration on a Tuesday. By Thursday, organic traffic dropped 60%. This guide covers why Google struggles to re-index after migration, how to diagnose what's broken, and how to use a Bulk Index Request to compress a potential 3-month recovery into days.
Not to say congratulations. To ask why pages that ranked on page one for three years had simply… vanished. Why Google was showing the old domain, the new domain, sometimes neither — and why Search Console was throwing errors you had never seen before.
You did everything right. The redirects were mapped. The sitemap was updated. The canonical tags were in place. And yet, Google was behaving like your new website didn't exist.
This is not a fringe scenario. This is the most common post-migration experience for SEO professionals, developers, and site owners in 2026 — and it happens because indexing is the step most migration guides treat as automatic when it is anything but.
When you migrate and Googlebot encounters old URLs, it doesn't simply swap old for new. It runs every affected URL through a 5-stage process.
Googlebot gets a 301/308 and reads the Location header. Nothing has changed in the index yet.
The new URL joins a queue with billions of others — competing for crawl attention across the entire web.
HTML download, JS execution, full render. Server errors or blocked resources stop the process here.
Content evaluation plus PageRank transfer via redirects. Google notes this can take weeks.
Old URL de-indexed. New URL takes its place. Rankings begin migrating.
Between Stage 1 and Stage 5 exists the Indexing Gap — the window when old pages are being removed while new pages haven't been added yet.
For a small, high-authority site, this might last 3–5 days. For a large e-commerce site on a new domain with thousands of URLs? The gap can stretch to months. The entire goal of this guide is to close that gap with active submission via Bulk Index Request.
Google Search Console shows three distinct states that most people treat as synonymous. They are not.
| Status | What It Means | What to Do |
|---|---|---|
| Discovered – not indexed | Google knows the URL exists but hasn't crawled it yet | Active submission via Bulk Index Request |
| Crawled – not indexed | Google visited the page but chose not to index it | Fix content/quality first, then resubmit |
| Indexed | Page is in Google's index and eligible to rank | Monitor with Bulk Index Checker |
The most dangerous assumption in post-migration SEO is treating "I submitted my sitemap" as equivalent to "my pages are indexed." A sitemap moves pages from unknown → discovered. Crawling and indexing still have to happen — and they can fail independently.
Not all migrations create equal indexing disruption. Calibrate your recovery strategy to your migration type.
| Migration Type | Disruption | Organic Timeline | With Bulk Index Request |
|---|---|---|---|
| HTTP → HTTPS | Low–Moderate | 1–3 weeks | 1–4 days |
| Subdomain → Subfolder | Moderate | 2–4 weeks | 3–7 days |
| URL Structure Change | Moderate | 2–5 weeks | 3–7 days |
| CMS Migration (same URLs) | Moderate | 1–3 weeks | 2–5 days |
| Domain Migration | High | 4–12 weeks | 1–3 weeks |
| Domain + CMS + URLs + Redesign | Critical | 3–6 months | 2–5 weeks |
When you move to a new domain, you don't just lose rankings temporarily — you lose crawl budget allocation. A new domain starts with essentially zero crawl history, which means Googlebot visits infrequently and cautiously. That is exactly why passive strategies fail for domain migrations — and why active submission via Bulk Index Request is essential.
For each root cause: detection method and fix — so you can move from diagnosis to resolution without leaving this page.
Old URL → Intermediate → New URL (2+ hops) wastes crawl budget. Chains of 3+ hops often cause Googlebot to abandon the destination.
Detect: Crawl old URLs in Screaming Frog with redirect following. Filter for 2+ hops.
Fix: Flatten every redirect to a single hop, then resubmit via Bulk Index Request.
After migration — especially to a new domain — Google may crawl only a tiny fraction of pages per day.
Detect: GSC → Settings → Crawl Stats. 5,000 pages with 50 crawled/day = a budget problem.
Fix: Improve TTFB, trim low-value crawl paths, and use Bulk Index Request to bypass the queue.
Staging noindex / X-Robots-Tag headers left in production. Google obeys noindex immediately and completely.
Detect: Crawl for noindex in HTML and headers. Verify rendered HTML in GSC URL Inspection (JS-injected noindex is common in 2026).
Fix: Remove all production noindex directives, then resubmit. Recovery usually takes days.
Canonicals pointing to old domain, staging, HTTP, or the wrong page create confused signal loops.
Detect: Export all canonicals and compare each to its live URL. Any mismatch is a problem.
Fix: Self-referencing canonicals only. Fix mismatches, then resubmit.
Without verification you cannot submit sitemaps, use Change of Address, or monitor coverage.
Detect: Check that the new domain appears as a verified property in Search Console.
Fix: Verify via DNS, submit sitemap, use Change of Address, then supplement with Bulk Index Request. Connect accounts in Connect GSC.
404s on old URLs tell Google the page is gone — historical signals are lost permanently if no redirect exists.
Detect: Crawl the old sitemap list. Map every 4xx with a new equivalent to a 301.
Fix: Prioritize pages with the most backlinks and traffic first.
CSR (React/Vue/Angular) pages that look blank to Googlebot do not get indexed meaningfully.
Detect: GSC URL Inspection → View Crawled Page → Screenshot. Also test Rich Results Test.
Fix: Implement SSR/SSG; put critical content in the initial HTML payload.
Internal links still pointing to old URLs force redirect hops on every crawl path.
Detect: Crawl the new site; filter internal links that return 3xx instead of 200.
Fix: Update all internal links to final canonical URLs — one of the highest-ROI post-migration fixes.
Old URLs in the sitemap — or no sitemap for the new domain — slows discovery dramatically.
Detect: Confirm only live 200, indexable URLs are listed for the new property.
Fix: Submit a clean sitemap in GSC; remove old sitemaps.
No technical error — competition for crawl attention in 2026 is higher than ever.
Detect: Decision tree clears all technical blockers but pages stay "Discovered".
Fix: Stop waiting. Bulk Index Request pushes URLs into Google's processing pipeline directly.
Are your new pages returning 200?
NO → Fix server errors / missing pages first
YES → Continue
Do your pages have noindex tags?
YES → Remove immediately, resubmit
NO → Continue
Are canonical tags self-referencing and correct?
NO → Fix canonicals, resubmit
YES → Continue
Is the new domain verified in GSC?
NO → Verify GSC, use Change of Address
YES → Continue
Are there redirect chains (2+ hops)?
YES → Flatten to single-hop, resubmit
NO → Continue
Is JavaScript rendering content correctly?
NO → Implement SSR/SSG, resubmit
YES → Continue
Technical foundation is sound → Google hasn't prioritized crawling yet
Use Bulk Index Request to force submission →Three variables control speed: domain authority & crawl history, site size, and technical cleanliness.
| Migration | Site Size | Organic Timeline | With Bulk Index Request | Traffic Recovery |
|---|---|---|---|---|
| HTTP → HTTPS | Under 500 | 1–2 weeks | 1–3 days | Parallel with indexing |
| HTTP → HTTPS | 5,000+ | 3–6 weeks | 3–7 days | Parallel with indexing |
| URL Restructure | Under 500 | 2–3 weeks | 2–4 days | 1 week post-indexing |
| URL Restructure | 5,000+ | 4–8 weeks | 5–10 days | 1–2 weeks post-indexing |
| Domain Migration | Under 500 | 3–6 weeks | 3–7 days | 2 weeks post-indexing |
| Domain Migration | 5,000+ | 8–16 weeks | 2–3 weeks | 2–4 weeks post-indexing |
| Full Migration | Under 500 | 4–8 weeks | 1–2 weeks | 2–3 weeks post-indexing |
| Full Migration | 5,000+ | 3–6 months | 3–6 weeks | 4–8 weeks post-indexing |
Daily organic revenue × Days of delay = Cost at risk
Example: $45,000/month organic → $1,500/day. A 90-day delay puts $135,000 at risk.
Cost at risk: $1,500 × 14 = $21,000
Savings: $114,000 — the conversation becomes risk management, not tool cost.
Work through this sequence. Do not skip steps. Each depends on the one before it.
Add and verify before anything else. Use DNS verification. Then connect Google Search Console to Bulk Index Checker for ongoing monitoring.
Old property → Settings → Change of Address → new property. Without this, Google treats the new domain as unrelated.
Only new, live, 200-status, non-noindexed URLs with accurate timestamps. No redirects, no 404s.
Confirm 200s, no noindex, robots.txt open, self-referencing canonicals, new internal links, HTTPS everywhere.
| Tier | Page Types | Action |
|---|---|---|
| Tier 1 | Revenue pages | Submit immediately |
| Tier 2 | High-traffic content | Within 24 hours |
| Tier 3 | Supporting content | Within 72 hours |
Step 6: Run your full URL list through Bulk Index Checker first — so you don't waste quota on already-indexed pages.
Step 7: Submit Tier 1 & 2 via Bulk Index Request — concurrent API submission, not one-by-one URL Inspection.
Most passive indexing advice was written for a different era of the web.
A sitemap tells Google pages exist. It does not guarantee crawl, index, or a timeline. Your sitemap is one file among hundreds of millions.
~200 URLs/day, sequential, browser-based. A 5,000-page site = 25 days of clicking. Impossible for agencies managing multiple migrations.
Unindexed pages can't rank, contribute to AI answers, or appear in AI Overviews. Indexing delays exclude you from Google's entire knowledge surface.
| Method | Speed | Scale |
|---|---|---|
| XML Sitemap | Days to weeks | Passive — Google decides when |
| GSC URL Inspection | Hours to days | ~200 URLs/day maximum |
| Bulk Index Request | Minutes to hours | Thousands of URLs concurrently |
The exact workflow. No filler. No vague advice.
30 min
Export live URLs. Include only 200, non-noindexed, self-canonical pages. Exclude redirects, errors, duplicates. Sort by tier.
15 min
Run the list through Bulk Index Checker for a true before/after metric and to skip already-indexed URLs.
Minutes
Upload to Bulk Index Request. Concurrent Indexing API processing with real-time confirmation.
48–72h
Bulk Index Checker verifies via live Google results — not delayed GSC cache.
Ongoing
Fix via decision tree, resubmit, re-verify. Move from 60% → 85% → 95%+ systematically.
Submitting is the accelerant. Monitoring tells you whether it's working.
Every 2–3 days
Indexed ↑ · Discovered ↓ · Crawled-not-indexed (content issues if ↑)
Daily
Fast daily signal of indexing progress (imperfect but useful)
Every 3 days
GA4 vs pre-migration baseline; segment by landing page
Daily (Tier 1)
Expect dip then recovery within 1–2 weeks of indexing
Every 48–72h
Live SERP confirmation — track obsessively until 95%+
| Time | Expected |
|---|---|
| 24 hours | Tier 1 starting to appear |
| 48–72 hours | 50–70% confirmed indexed |
| Week 1 | 80–90% indexed; Tier 1 rankings begin |
| Week 2 | 90–95% indexed; Tier 1–2 recovering |
| Week 3–4 | 95%+; full ranking recovery underway |
| Week 6–8 | Near-complete for clean pages |
"Crawled – not indexed" increasing
Content quality / duplication — improve or merge
Indexed but rankings stuck
Authority transfer still in progress — verify redirects
Index count plateauing
Technical blocker on subset — re-crawl non-indexed
Indexed then dropping out
Google re-evaluated against indexing — content issue
Spike in "Excluded by noindex"
Accidental noindex in a recent deploy — check immediately
These turn a 2-week recovery into a 6-month disaster.
Mass homepage redirects are treated as soft 404s. You lose per-page authority. Fix: 1:1 topical redirect mapping — non-negotiable.
Google needs 6+ months for full signal transfer. Keep redirects 12 months minimum — ideally forever.
Without it, Google must infer the domain relationship. Use it: 2 minutes in GSC Settings.
You're blind in the critical window. Verify the new property days before launch, then Connect GSC.
Malformed canonicals from find-and-replace are worse than none. Crawl and verify every canonical after batch edits.
Google evaluates the mobile version. Test Tier 1–2 via Mobile-Friendly Test before Bulk Index Request.
3xx/4xx URLs in sitemaps signal poor maintenance and can reduce crawl rate. Audit before submit.
Pages can fall out of the index. Schedule recurring Bulk Index Checker audits — weekly, then bi-weekly, then monthly.
Composite case study from real recoveries on Bulk Index Checker infrastructure. Identifying details generalized.
A mid-size e-commerce retailer migrated from brandstore-online.com to brandstore.com: 12,400 pages, new domain, Magento → Shopify, redesign, and URL restructure. Redirects mapped. GSC set up. Sitemap submitted.
Two weeks later: 14.9% indexed · organic traffic −71% · revenue −68% · 6,800+ “Discovered – not indexed”.
| Problem | Pages | Severity |
|---|---|---|
| Redirect chains (2–3 hops) | 4,200 | Critical |
| Canonicals → old domain | 1,100 | Critical |
| robots.txt blocking /collections/ | 800 | Critical |
| Crawl budget starvation | 4,453 | High |
Indexed Pages
1,847 → 11,800
Week 2 → Week 6
Weekly Sessions
15.1k → 48.4k
vs 52k baseline
Weekly Revenue
$44k → $127k
vs $138k baseline
Top 10 Keywords
89 → 287
vs 312 baseline
6 weeks to 95.2% indexation with Bulk Index Request. Projected organic timeline without intervention: 4–6 months.
Google indexing after migration — timelines, redirects, sitemaps, and when to force submission.
Without proactive intervention, Google typically takes 2 weeks to 6 months depending on migration type, site size, domain authority, and technical health. HTTP-to-HTTPS on high-authority domains can recover in days. Full domain migrations for large sites with errors can take 4–6 months. Using Bulk Index Request compresses these timelines to days or weeks.
Most common causes in order: (1) accidental noindex from staging, (2) redirect chains, (3) incorrect canonicals, (4) GSC property not verified, (5) crawl budget starvation, (6) JavaScript rendering failures. Use the decision tree above to identify yours.
Not permanently — if redirects are correct and maintained long-term. Signal transfer via 301s often takes 4–12 weeks. Permanent loss happens when redirects are incorrect, missing, or removed too early.
Yes — 301 transfers PageRank and ranking signals. Some signal loss occurs (exact % unpublished). Multiple hops increase loss. Never use 302 for permanent migrations.
A sitemap is a passive discovery signal. Bulk Index Request uses the Google Indexing API to actively push URLs into Google's processing pipeline — bypassing the discovery queue and compressing weeks into days.
Google visited and chose not to index — not a queue delay. Usually thin/duplicate content or weak intent match. Fix content first; resubmitting alone will not change the outcome.
Both are permanent and transfer signals. 301 is the conventional choice for page migrations. Use 308 only when you must preserve the original HTTP method.
No — and doing so would harm you. External links flow through 301s to the new domain. Disavowing removes that equity. Keep redirects active.
Update all hreflang annotations to new URLs immediately. Old-URL hreflang creates redirect/canonicalization loops that can collapse international rankings.
Yes, with limits: GSC URL Inspection (~200/day), sitemaps, new backlinks, and internal linking. For hundreds or thousands of pages, Bulk Index Request achieves in hours what manual methods take weeks to do.
Join 300+ SEO professionals who trust Bulk Index Checker to get migrated pages indexed fast. Upload your URL list, submit through Google's Indexing API, and verify results through live SERP data — in minutes, not months.
