Ka whakarerekē ngā waehere āhua

Ka whakahōu te kaitirotiro

Follow any URL's redirect chain hop by hop, and catch the ones costing you rankings.

E whai ana i te mekameka katoa Kāore he whakaingoatanga

I muri i te mekameka whakateretanga...

E tono ana i ia whakarerekētanga me te whakaako i tōna waehere āhua.

He pēhea te āhua o tētahi whakarerekētanga ora. One hop, a 301 or 308 for a permanent move, and a 200 at the end, with no chains, no loops, no bouncing between HTTP and HTTPS or www and non-www. Each extra hop sheds a little link equity and slows the page, so point the source straight at the final URL.

He pēhea te whakataki i te mekameka whakarerekē o tētahi URL

E whā nga hipanga mai i tētahi URL ki tētahi tīpako tīariari, kotahi.

1

Paki te 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

Whakataki i ngā whakateretanga

E whakatūpato ana te whakatūpato i ngā whakarerekētanga, ā, ka whaia whakahau i te āhua o te kaitiaki, te kaitiaki rānei, e tuhituhi ana i ia URL me te tūnga HTTP tika i hoki mai ai.

3

Ka pānui te mekameka hop

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

E mahi ana ki ngā whakamātautau

Review the flagged issues (long chains, temporary redirects for permanent moves, loops, mixed HTTP and HTTPS) and fix them so the source points straight at the final URL in one hop.

Ka whakateretia ngā pātai

A 301 is a permanent redirect: it tells search engines the page has moved for good, passes the ranking signals along to the new URL, and the target replaces the source in the index. A 302 (and its stricter siblings 303 and 307) is temporary: it says "the page is briefly somewhere else, keep the original indexed." The practical trap is using a 302 for a move that is actually permanent, so you keep the old URL in the index and you don't cleanly consolidate ranking signals onto the new one. For a permanent move, always use a 301 (or 308, its method-preserving equivalent).
Heoi, he iti, ā, ka tāpiri. He āhua anō ētahi atu tono e hiahiatia ana e te kaimahi whakataki me te kaimahi whakataki i mua i te tae ki ngā ihirangi pono, kia pōturi ake ai te pātaka, ā, ka taea e ia whakarerekē te whakawātea i tētahi iti o te pānga. Ko te Google i te nuinga o te wā e whai ana i ngā whakarerekētanga maha, engari kāore e hiahiatia kia whai i te wā katoa, ā, ko ngā mekameka roa e whakawātea ana i te pūtea whakarerekē i ngā paetata nui. He ngāwari te whakaoti: ka pupuri i tētahi whakarerekētanga kotahi mā te tohu i te URL pūtake i te tauwāhi whakamutunga, kaua i tētahi atu whakarerekētanga. Mēnā ka whakarerekē te pātaka A ki B ki C, ka whakahōu A ki te tohu hāngai ki C.
A 404 means "not found": the page is missing, but it might come back, so search engines keep checking for a while. A 410 means "gone": you removed it on purpose and it isn't returning. When you deliberately retire a page and have nothing to redirect it to, a 410 tells crawlers to drop it from the index faster and more cleanly than a 404, and it stops them re-requesting a URL you never intend to restore. Use a 301 when there is a good replacement to send visitors to; use a 410 when the page is genuinely gone and a redirect would be misleading.
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.

E kite ana i ōna whakarerekētanga i te tauine?

The free checker traces one URL at a time and is rate-limited. Auditing thousands of URLs for broken chains, loops and temporary redirects that should be permanent, and catching new ones before they cost you rankings, is part of the managed service.

✓ Waihoki te utauta: kotahi URL i te wā Whakamātautau i te wāhi katoa: ngā mahere whakahaere

Ko ngā mahere whakarerekē nui, ngā arotakenga anō i muri i te hekenga, me ngā mōhiohio ina huri te 301 mārō ki tētahi mekameka, ki tētahi 404 rānei. Tirohia ngā mahere i runga i te pātaka utu.

Tirohia ngā mahere whakahaere →
Ka whakawhanakehia te API

Ka whakamahia i roto i te papatono

Every tool is available through one authenticated REST API on the Pro and API plans. Wire it into your CI, CMS, or 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": { ... } }
Ki te whiwhi i tētahi kī API → Ka whakawāteatia, ka whakawāteatia te utu-i-te-rongo. Tauwhāiti mo te utauta whakawhitiwhiti i runga ake nei.
Check every page of your site, not one at a time
Pro connects Google Search Console, fetches every page Google skipped, every broken page and every page that ranks low, and writes what to fix on each one.
See how Pro works