Kudzokera kumashure & zviratidzo zvestatus

Kudzoreredza Kuongorora

Dzvanya pane chero URL's redirect chain hop by hop, uye uwane avo vanobhadhara iwe rankings.

Kutevera kuzere kwechikwata Hapana kumbopinda

Zvinoenderana neRedirect Chain…

Kukumbira chero hop munzira uye kuverenga yake status code.

Chii chinonzi hutano redirect. Mumwe hopping, 301 kana 308 yenguva dzose yekufambisa, uye 200 pakupedzisira, pasina mabhaisikopo, pasina mabhureki, pasina kudzoka pakati peHTTP neHTTPS kana www uye kwete-www. Kana chero imwe hopping inowedzera kuwedzera kwechikwereti chekubatanidza uye inoka peji, saka tarisa kune iyo URL.

Maitiro ekutevera redirect chain yeURL

Maitiro maviri kubva kuURL kuenda kutsvaira, imwe-hop redirect.

1

Pedza URL

Enter the full URL you want to test, including https, for example https://example.com/old-page. This is the starting point of the trace.

2

Kutevera kudzokera

Tinya Track redirects uye isu tinotevera chero hop sezvaiita browser kana crawler, tichinyora chero URL uye yakakodzera HTTP status yakati yadzokera.

3

Ona hop chain

See each step colour-coded by status (green for a permanent 301 or 308, amber for a temporary 302, 303 or 307, red for a 4xx or 5xx error), with the final destination at the end.

4

Kuita basa pazviyeuchidzo

Rega ongorore nyaya dzakanyorwa (mabhawa akareba, nguva pfupi yekudzokorora kwenguva pfupi, mabhureki, akateedzana HTTP uye HTTPS) uye gadzirisa kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite kuti zviite.

Kudzosera mibvunzo

A 301 ndeimwe yenguva dzose yekudzokorora: inotaura injini dzekutsvaga kuti peji rachinja zvakanaka, rinopa masimba ekutsvaga pamwe neiyo nyowani URL, uye iro zita rinoshandura iyo nzvimbo muindex. A 302 (neakanyanya kuomarara 303 ne307) ndeimwe nguva: inoti "iyo peji iri nguva pfupi yadarika, chengetedza iyo yekutanga indexed." Iyo yakapusa pfungwa ndeye kushandisa 302 yemugwagwa uyo uri chaizvo wenguva dzose, saka iwe unochengeta iyo yapfuura URL muindex uye haugone kuisa masimba ekutsvaga pane iyo nyowani. Yemugwagwa wenguva dzose, shandisa 301 (kana 308, iyo inochengeta nzira yayo).
Yeah, a little bit, and it adds up. Every extra hop is another request the browser and the crawler have to make before reaching real content, so the page feels slower and every redirect can shed a small amount of link equity. Google generally follows several hops, but it doesn't have to follow forever, and long chains waste crawl budget on large sites. The fix is simple: keep it to a single hop by pointing the source URL straight at the final destination instead at another redirect. If page A redirects to B redirects to C, update A to point directly at C.
A 404 zvinoreva "hapana chakawanikwa": peji rarasikirwa, asi inogona kudzokera, saka injini dzekutsvaga dzinoramba dzichiongorora kwenguva. A 410 zvinoreva "rakaremara": iwe wakabvisa zvakaipa uye hazvina kudzokera. Kana iwe uchitora peji uye hauna chinhu chekudzokera, 410 inoti crawlers kuti iite kubva muindex nekukurumidza uye zvakachena kupfuura 404, uye inobvisa kukumbirazve URL iwe hauna kumbobvira wafunga kudzokera. Usashandisa 301 kana paine shanduko yakanaka yekutumira vashanyi; shandisa 410 kana peji rarasikirwa uye kudzokera kwaizove kwakaipa.
A redirect loop happens when URLs send visitors back and forth without ever landing on a real page: A redirects to B and B redirects back to A, so the browser gives up with a "too many redirects" error. Find the cycle by tracing the chain (this tool stops and flags it), then break it: decide on one canonical destination and make everything point there, or turn one of the URLs into a real 200 page. Common causes are conflicting rules, such as one for HTTP to HTTPS and another for www that disagree, or a trailing-slash rule fighting a CMS redirect. Resolve the conflict so a single, consistent rule wins.

Kuona yako redirects pa scale?

Kuongorora mamirioni e URLs yezvidimbu zvemabhawa, maloops uye nguva pfupi yekudzokorora iyo inofanira kunge iri yakasimba, uye kusvikira

✓ Free tool: imwe URL panguva imwe Site-wide audits: akatungamirira zvirongwa

Bulk redirect mapikicha, zvakarongwa re-cheki mushure mekugara, uye ma alerts apo a clean 301 chisingaperi anoshandura mu chain kana 404. Ona michina pamitengo peji.

Ona anotungamirirwa mapurogiramu →
Developer API

Usashandisa neprogramming

Nekudaro, iwe unogona kuisa iyo API muPro uye API zvirongwa, uye wozoibatanidza kune yako CI, CMS, kana dashboards.

curl -X POST https://seo.bike/api/v1/redirect-check \ -H "Authorization: Bearer sk_live_yourkey" \ -H "Content-Type: application/json" \ -d '{"url": "http://example.com/old-page"}'
OK
{ "ok": true, "result": { ... } }
Kuwana API key → Metered, per-call pricing. Free tier yemutauro chirongwa pamusoro.
Cheka chero peji rewebsite yako, kwete rimwe nerimwe pamwechete
Pro inobatanidza Google Search Console, inowana yega yega peji Google yakakwira, yega yega yakakuvadzwa peji uye yega yega peji iyo inoramba yakaderera, uye inonyora zvaunofanira kugadzirisa pane yega yega.
Ona sei Pro inoita