Free SEO & social tool
Site Migration Checker
Check that old URLs still land on the new site, that redirects are permanent, and that no staging leftovers hide it from search.
- Free
- No sign-up
- Results in seconds
Full audit
This is one part of the full report
Speed, Core Web Vitals, UX, SEO and security in one free report, graded A+ to F, with AI fixes for your platform.
What it checks
URL mapping
Each sampled old URL on the new site: kept, redirected, missing or sent to the home page.
Redirect quality
301 versus 302, chains, and home page redirects Google treats as soft 404s.
Content carried over
Title, description, H1, canonical, hreflang and structured data on pages that load on both sites.
Staging leftovers
Noindex tags and headers, and a robots.txt that blocks every crawler.
Canonicals and sitemap
Canonicals, sitemaps and robots.txt lines that still point to the old domain.
Suggested redirects
Rules for missing URLs, matched against the new sitemap, for Nginx, Apache, Netlify, Vercel and Next.js.
Questions
Can I check before the new site is live?
Yes. Enter the staging or new address as the new site, and we request each old path there as a dry run. After the switch, we follow each old URL’s redirect instead.
How many URLs do you check?
Up to 12 per run, from the old sitemap or the home page’s links: the home page first, then a spread across sections. For every URL, paste your full list into the redirect map generator.
Why is a redirect to the home page a problem?
Google treats it as a soft 404, so the old page’s rankings aren’t passed on. Redirect each URL to its closest new page.
Should I use 301 or 302 redirects?
301 or 308 for a migration. A 302 or 307 tells search engines the move is temporary, so they may keep the old URL in results.