SEO Migration Planner & Validator
Free, no signup. Run the migration in order: create a redirect map, verify what deployed, check the old URLs, compare the sitemaps, then spot-check historical snapshots. Your project stays in this browser unless you export it; public verification requests use the site's bounded fetch service.
Saved in this browser.
Readiness at a glance
No migration steps have run yet.
Build the redirect map
Paste the pre-migration URL set and the intended destination set. Exact/strong matches start accepted; weak or unmatched rows stay for review.
Recommended: bring in the full version 2 project so pattern rules, manual overrides, 410 decisions, and review states stay intact. The text fields below remain a quick-start fallback.
Verify deployed redirects
Tests accepted 301 map rows against the live old URLs. Correct means a direct 301 reaches the mapped destination as a 2xx.
Only accepted map rows are checked. Rate-limited rows remain clearly marked as not evaluated.
Bulk status check
Check how the old URL set resolves today. This is intentionally a separate operational view from whether each URL reaches its expected mapped target.
Checks every old URL through the bounded, host-aware batch runner. Large lists can take a while.
Compare XML sitemaps
Fetch the old and new sitemaps through the same protected proxy used by the Sitemap Validator, then compare their absolute URL lists.
Wayback spot checks
Look up up to five accepted old URLs in the Internet Archive. This establishes historical coverage; it does not prove a redirect or content equivalence.
This tool uses the Internet Archive’s Wayback Machine. If it helps, consider supporting the archive. We’re not affiliated.
Migration readiness summary
Use Print / save PDF to hand off this scoped record. It declares skipped steps rather than implying they passed.
Checks run from our server; we fetch the URL you enter and don't keep the results. The URL lists, map, and report are stored only in this browser. Optional verification, status, sitemap, and Wayback steps request the public URLs you enter through their respective bounded endpoints. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Migration loss analyzer
Compare user-selected pre/post windows around launch. Cohorts and overlays show correlation; they do not prove causation.
Sample report Static workflow example
Spring domain migration
- Step 1: Redirect map — complete (48 accepted, 2 review)
- Step 2: Verify redirects — partial (one rate-limited row not evaluated)
- Step 3: Bulk status — not run
- Step 4: Sitemap diff — complete (3 added, 1 removed)
- Step 5: Wayback checks — complete (5 sampled)
Follow-up signals need review; one step not run.
This demonstrates state handling and report shape, not results from a real migration.
How to use it
- Paste complete old and new URL inventories, build the map, and review every weak or unmatched suggestion.
- Deploy only accepted redirects, then verify those live old URLs.
- Run the separate bulk-status view to find old URLs that still error or resolve unexpectedly.
- Compare old/new child sitemaps and spot-check accepted old URLs in the Archive.
- Export the browser project and print the readiness summary with all skipped states visible.
What each step produces
- Map tier/review — strength of the suggested URL match and the human acceptance state.
- Verification verdict — whether an accepted row deployed as the expected direct 301 to a 2xx target.
- Bulk status — operational resolution of every old URL through bounded batches, separate from expected target matching.
- Sitemap diff — absolute URLs added to or removed from the supplied child sitemaps.
- Wayback — archive capture counts for up to five accepted old URLs.
How project data is stored
Map matching, review state, project persistence, and reporting run in the browser. Verification and status use bounded redirect/status endpoints, sitemap comparison uses the protected sitemap fetcher and validator, and archive checks use cached CDX responses. Each step writes an explicit state into the exported project.
Features
- Five ordered migration workstreams in one browser project.
- Human review preserved alongside deterministic URL matching.
- Live redirect/status verification with honest unavailable rows.
- Sitemap additions/removals and bounded archive spot checks.
- JSON import/export and printable agency summary.
Limitations
The tool does not deploy redirects, crawl every new page, authenticate, call GSC, or prove content equivalence. Large bulk-status runs are paced in bounded host-aware batches; archive checks are capped at five accepted rows and the map preview at 40 rows. Browser storage can be cleared; export important projects. A completed workflow remains a scoped QA record, not a guarantee of traffic or index preservation.
Frequently asked questions
What does the SEO Migration Planner & Validator store?
The project name, URL sets, map, review decisions, and completed-step results are stored in this browser. You can export a JSON project or print the report.
Does the redirect mapper deploy redirects?
No. It suggests matches and records review decisions. Deployment happens in your server, CDN, or platform, after which the verification step can check accepted rows.
What counts as a correct verified redirect?
The verification step requires a direct 301 from the accepted old URL to its mapped destination, ending in a successful 2xx response.
Does a Wayback snapshot prove content equivalence?
No. It only establishes that an archived capture was returned for a sampled old URL. It does not verify the redirect or compare old and new content.
Can skipped steps appear as passed?
No. The report preserves not-run, partial, error, and complete states so an incomplete workflow is not presented as release-ready.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Rate this tool
Feature requests for Migration Command Center
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Informazioni sullo strumento
Segui un flusso di migrazione SEO in cinque passaggi: crea e verifica una mappa dei reindirizzamenti, controlla i reindirizzamenti distribuiti, verifica lo stato dei vecchi URL, confronta le sitemap e controlla alcuni archivi Wayback.
Gratuito, senza registrazione. Decisioni e prove restano nel browser finché non esporti il progetto.
Funzionalità
- Mappa dei reindirizzamenti con revisione umana delle corrispondenze esatte, forti e deboli.
- Verifica dei reindirizzamenti 301 verso una destinazione finale 2xx.
- Controllo in blocco dello stato dei vecchi URL e confronto delle sitemap XML.
- Controlli Wayback limitati e report stampabile pronto per la consegna.
Come funziona
Ogni passaggio registra il proprio stato esplicito nel progetto esportato. Le corrispondenze sono deterministiche, le verifiche usano endpoint limitati, il confronto delle sitemap lavora su URL assoluti e i controlli Wayback si basano su risposte CDX memorizzate.
Limitazioni
- Il servizio non distribuisce reindirizzamenti, non esegue la scansione di tutte le nuove pagine, non autentica account, non chiama GSC e non dimostra l’equivalenza dei contenuti.
- Le elaborazioni in blocco sono limitate per host; gli archivi sono limitati a cinque righe accettate e l’anteprima della mappa a 40 righe. Un flusso completato resta un record QA circoscritto, non una garanzia di traffico o conservazione nell’indice.
Domande frequenti
Cosa conserva il pianificatore di migrazione SEO?
Nome del progetto, set di URL, mappa, decisioni di revisione e risultati dei passaggi completati vengono conservati nel browser. Puoi esportare un progetto JSON o stampare il report.
Il mapper dei reindirizzamenti distribuisce i reindirizzamenti?
No. Suggerisce corrispondenze e registra le decisioni di revisione. La distribuzione avviene sul tuo server, CDN o piattaforma; dopo puoi verificare le righe accettate.
Che cos’è un reindirizzamento verificato corretto?
Il vecchio URL accettato deve restituire direttamente un 301 verso la destinazione mappata, che deve terminare con una risposta 2xx.
I passaggi ignorati possono apparire come riusciti?
No. Il report conserva gli stati non eseguito, parziale, errore e completato, così un flusso incompleto non viene presentato come pronto alla pubblicazione.
Uno snapshot Wayback dimostra l’equivalenza dei contenuti?
No. Dimostra solo che un’istantanea d’archivio è stata restituita per un vecchio URL campionato; non verifica né il reindirizzamento né il confronto del contenuto.