- Paste up to 500 old addresses, or give the old sitemap, and MrKeyword follows each one hop by hop.
- Each address gets a verdict: OK, broken, not redirected, wrong host, to homepage, temporary, chain or not checked.
- An optional new website sets the host every redirect should end on.
- It runs live and stores nothing. A workspace can run 20 checks a day.
- Download the results as CSV and work through the addresses that need attention.
What the Site Migration checker does
After a move, every old address should answer with one permanent redirect to a working page that matches it. The checker requests each old address and follows the redirects, recording every status code and the final address. It then says what is wrong with the ones that do not meet that rule.
You can paste the old addresses, one per line, or give the old sitemap. A sitemap index is read one level deep, and up to 500 addresses are checked per run. If you give the new website, the checker also confirms that every redirect ends on that host.
What each verdict means
| Verdict | What it means | What to do |
|---|---|---|
| OK | One permanent redirect to a working page. | Nothing. |
| Broken | The chain ends in an error page, a loop or no valid location. | Point the old address at a live page. |
| Not redirected | The old address still answers on its own. | Add a permanent redirect. |
| Wrong host | It ends on a different host than the new site. | Send it to the new host. |
| To homepage | It lands on the homepage instead of a matching page. | Redirect to the closest matching page. |
| Temporary | It uses a 302 or 307. | Use a 301 or 308 for a permanent move. |
| Chain | More than one redirect. | Link the old address straight to the final page. |
| Not checked | The address was skipped, for example because the run was capped. | Run it again with fewer addresses. |
The results table shows the old address, the status codes in order, the final address and the reason. The summary counts each verdict, so the size of the job is clear before you open the table.
When to run it
-
Right after the switch
Run the old sitemap as soon as the new site is live. Broken and homepage redirects are where migrations lose rankings, and they are cheapest to fix on the first day.
-
A week later
Run it again. A redirect that worked on day one can break when a page is renamed or a rule is changed. The second run catches that.
-
After any URL change
If you rename a section or move a service page, check the addresses that pointed at it. A chain is easy to create and easy to miss.
What the checker does not do
- It does not change your redirects. It reports what each address does today.
- It does not store the results. They stay in the view until you leave it, and the CSV is the record.
- It does not check more than 500 addresses per run, or more than 20 runs a day per workspace.
- It does not read pages behind a login or a block. Those addresses are reported as broken or not checked.
- It does not judge whether the new page is a good match beyond the address and the host. Read the final address in the table.
Site Migration in each plan
The checker is available on every plan. A workspace can run 20 checks a day, and each run can check up to 500 addresses. See pricing for the limits.
Questions and answers
Site Migration questions
How many addresses can I check?
Up to 500 per run, from a pasted list or the old sitemap. A sitemap index is read one level deep.
Does it store the results?
No. The check runs live and nothing is stored. The results stay in the view until you leave it, and you can download them as CSV.
What counts as a good redirect?
One permanent redirect (301 or 308) to a working page that matches the old address. If you give the new website, the redirect must also end on that host.
Why is a redirect marked temporary?
It uses a 302 or 307. For a permanent move, use a 301 or 308 so search engines treat the old address as replaced.
Why is a redirect marked to homepage?
The old address lands on the homepage instead of a matching page. That usually loses the value of the old page; redirect to the closest match instead.
How often can I run it?
A workspace can run 20 checks a day. Run it right after the switch and again a week later.
Sources
- Redirects and Google Search — Google Search Central, on permanent and temporary redirects
- Site moves with URL changes — Google Search Central, on moving a site and keeping the old URLs working
- Change of address — Google Search Console Help, on telling Google about a move

