Redirect Checker
Check HTTP redirect chains and status codes
How to use Redirect Checker
- 1Enter the source URL to test with the desired ultimate destination address.
- 2Enter the requested header, e. g. User-Agent or Authorization.
- 3Views the complete redirection chain and the final HTTP status code.
Redirect HTTP
Chain = URL0→ (301/302) URL1→(...) URL(state code)The re-direction chain increases the delay, and if a link is reached by multiple jumps to the standard page, it may undermine the analysis data or SEO.
Single clean 301 best preserves the link weight; multiple-jumping chains dilute the weight and slow the user ' s first byte time.
The difference between 301 and 302 is not just "permanent vs temporary": **301 will pass the page weight (SEO's PageRank concept) to the new address, 302 not**. The site has to be re-edited and changed domain names in 301, and the use of 302 will result in the search engine continuing to index its old address, and the weights cannot be moved. In addition, 301 will be permanently cached by browsers and, if wrongly matched, users may jump -** test 301 with a traceless window or curl to avoid being misled by local caches. **
** Redirected chain is performance and SEO's invisible killer**: A→B→C adds a full RRTT to each jump, and three jumps can add hundreds of milliseconds; search engines can reduce capture efficiency and even abandon chains that are above 3. Common causes: HTTP→HTTPS once, [email protected], table of contents slash once, underwritten once. The solution would be to complete all regularizations at the edge node (CDN/Reverse Agent) at once** and jump to the final address with a single rule.
| Status Code | Meaning | Retention of method | Cacheable | Typical uses |
|---|---|---|---|---|
| 301 | Redirect permanently | For most read GET | Cacheable | Domain name migration, HTTP→HTTPS |
| 302 | Interim reorientation | For most read GET | Can not open message | Temporary maintenance, A/B testing |
| 307 | Interim reorientation | Strict reservations | Can not open message | Save POST temporary jump |
| 308 | Redirect permanently | Strict reservations | Cacheable | Retain permanent POST jump |
| 303 | See Other | Replace with GET | Can not open message | POST Post Jump to Result Page |
| meta refresh | HTML Class Jump | — | — | Not recommended, SEO |
HTTP Redirect status code differentiation
Frequently asked questions
301 or 302. How?
Permanent migration is 301 to convey SEO weights; temporary or A/B tests 302.
Why avoid re-directional chains?
Each jump increases the number of trips and may lose the source data and ranking signals.
How long should re-direction wait?
Redirection should be instantaneous (without delay) and browsers should follow immediately.
What about redirecting?
Typical scenario: HTTPS station is behind the CDN, which returns with HTTP and the station requests HTTPS, and then circulates indefinitely. Scrutinizing step: 1 tracks the complete jump chain with curl-I-L; 2 checks for multiple layers of re-direction (CDN, Nginx, application layer each with one); 3 confirms whether the X-Forwarded-Proto head is correctly passed and whether the source station judges the protocol accordingly. Repair: Allows the source station to make only one judgement or to standardize the UDP protocol at the CDN level.
302 will pass SEO weight?
Traditionally not, but Google announced in 2016 that "302 is used as a hint rather than a directive" - if you keep 302 for a long time, Google will judge itself and treat it by 301. But Bing, 100 degrees, and so on, the syntax of 302 is temporary. ** The normative approach remains the determination of permanent migration for 301, without relying on the error of the search engine. ** Short-term activity page, A/B test for 302.