Redirect checker: where do your old links go?

Enter the address above. We request it the way a browser does, without following redirects automatically, so we can record each hop: its status code, where it points next, and the page it finally lands on. Paste a list of up to 50 addresses to check them all at once.

A 301 (or 308) is permanent: Google shows the new address in search results and treats it as the one to index. A 302 (or 303 or 307) is temporary: Google keeps showing the old address. Use a permanent redirect for any page that has moved for good, such as in a migration.

An old address that redirects to another that redirects again before reaching the final page. Each hop slows the page down and adds a point of failure. Google’s crawlers follow up to 10 hops, but it’s better to point every old address straight at its final page.

Not when they’re done well. A permanent, server-side redirect from an old page to its closest new page tells Google the new address should take the old one’s place. Problems come from chains, loops, temporary redirects for permanent moves, and sending many old pages to one unrelated page, such as the home page.

In Site settings, open the Publishing tab and add each old path and its new address under 301 redirects, then publish the site. You can redirect a whole folder with a wildcard, and import a CSV of redirects, which replaces the existing list, so export it first.

A redirect in the page’s HTML rather than from the server. Google follows an instant meta refresh as permanent and a delayed one as temporary, but a server-side 301 or 308 is the most reliable choice. This checker flags meta refreshes it finds.