How to Check Redirects and Redirect Chains
A redirect is a forwarding from one address to another. For search, it is important not only where it leads but also what code it uses, how many steps are in the chain, and whether link weight is lost along the way. You can check all this with a free redirect checker: it goes through the chain to the end and shows each step.
What Codes Mean
| Code | Meaning | When Appropriate |
|---|---|---|
| 301 | Moved permanently | Address change, merging www and non-www, switching to https |
| 302 / 307 | Temporary | Promotions, maintenance, geo-redirects — but not for migrations |
| 308 | Permanently, preserving request method | Analog of 301 for forms and APIs |
| Meta-refresh and JS redirect | Redirecting via the page | Undesirable: the bot sees it later and worse |
What to Look for in the Result
- Chain length. One step is the norm. Three or more — loss of speed and risk that the bot won't reach the end.
- Mixed codes. A chain like 302 → 301 → 200 signals that the migration is only half set up.
- Loops. An address that returns to itself completely kills the page for search.
- Final code. The chain should end with 200, not 404 or another redirect.
- Scheme and host. After all steps, the address should match the canonical: https, the required version with or without www.
Why This Matters for Link Promotion
Links lead to a specific address. If it redirects, the weight will still reach the final page with a permanent redirect — but it’s better to promote the final address right away. If the promoted page has already moved after launch, set up a 301 from the old address: you won’t need to redo the publications, see “Can I Delete or Change a Publication”.
What to Check Alongside
Response codes for the list of addresses and response headers — there you can see caching and canonical hints, which often create unnecessary steps.