Redirect status codes explained
| Code | Name | When to use |
|---|---|---|
| 301 | Moved permanently | Use for permanent moves. Passes link signals. |
| 308 | Permanent redirect | Like 301 but keeps the request method. |
| 302 | Found (temporary) | For temporary moves. |
| 307 | Temporary redirect | Like 302 but keeps the method. |
| 200 | OK | The final page loaded. |
| 404 / 410 | Not found / Gone | A dead end. Fix or redirect the link. |
Why redirects matter for link building
- Before you pitch: a resource page that redirects to the homepage is gone; your pitch should change.
- Broken link building: a link that redirects to an unrelated page is still a reason to suggest your replacement.
- Your own links: if you moved a page that has backlinks, a single 301 to the new URL keeps their value. A chain of three hops slows crawling and users.
- Links you placed: check the link points at the final URL, not an old one that redirects.
Chains and loops
A chain is A → B → C. Each hop adds latency, and Google documents that Googlebot follows up to 10 hops. Point links and internal redirects straight at the final URL. A loop (A → B → A) never resolves; the tool stops after 10 hops and you will see the repeating URLs.
Notes on accuracy
The check runs from Cloudflare's network. Sites that redirect by country, device or cookie may behave differently for you. JavaScript and meta-refresh redirects are not followed, because they happen in the browser, not in the HTTP response.