Find broken redirects, chains, loops and canonicals.
Map every redirect across your site, identify dead ends and canonical mismatches, and let AutoFix collapse the simple ones automatically. A migration mapped once by hand, never re-checked, is how a chain sits broken for months.
You are here · the workflow
The technical surface · this page covers
Part of Technical Suite's six-stage loop. See the full system →
Redirects mapped once. Never checked again.
- A migration gets redirects mapped once, by hand, from a spreadsheet. Nobody re-crawls after launch, so a chain that dead-ends sits there for months.
- URLs get restructured a second time, and a second time, and each round adds another hop to redirects nobody's tracking. Chains grow silently.
- A canonical tag points to the wrong page, and search engines quietly index the version you didn't want indexed instead of the one you did.
- The first sign anything's wrong is a traffic drop, weeks after the actual cause.
What needs to happen: redirects and canonicals need to be checked on every crawl, not once at launch and never again — and the ones with an obvious correct fix shouldn't need a ticket.
How SEORCE does it: every redirect and canonical is mapped on every crawl. Chains under three hops with a live, indexable destination are collapsed automatically by AutoFix. Longer chains, loops, and redirects ending in a dead page are diagnosed with the exact chain shown — picking the right destination there is a judgement call, so it stays with a person.
Click the button. Watch the chain collapse.
A simulation — but the exact mechanic that runs on a real crawl. /checkout-old routes through two dead hops before reaching the live page.
Chain length, across the whole site.
406 redirects and canonicals need a human decision. AutoFix already closed the 2-hop chains on its own.
One correct answer, or a judgement call.
Ships automatically
- ✓Chains under three hops, ending in a live indexable page
- ✓Self-referencing canonical mismatches with one correct URL
- ✓HTTP/HTTPS and www/non-www redirect standardisation
Diagnosed, not auto-applied
- →Chains of three hops or more
- →Redirects that end in a 404 or a noindex page
- →Loops — a redirect that eventually points back to itself
- →Canonical pointing to a page that isn't indexable
Inside every redirect and canonical.
Redirects feed straight into indexability.
What does Errors & Redirects check?
Errors & Redirects maps every redirect and canonical tag across a site during the continuous crawl. It flags chains — two or more redirects in sequence — loops, redirects that end in a 404 or a noindex page, and canonical mismatches including self-referencing and cross-page canonicals. AutoFix collapses chains under three hops automatically when the final destination is a live, indexable page, repointing the original URL directly and logging a before-and-after diff. Chains of three hops or more, redirects ending in a dead page, and canonical decisions that depend on judgement are diagnosed with the exact chain shown, left for a person to resolve.
Key facts
- Maps redirect chains and canonical tags across the whole site, every crawl
- Ships automatically: chains under three hops ending in a live page, HTTP/HTTPS and www standardisation
- Diagnosed, not auto-applied: longer chains, redirects ending in a 404, loops, non-indexable canonical targets
- Every automatic fix is logged with a before-and-after diff and reversible at any time
Frequently asked about redirects.
Two or more redirects in sequence before reaching a final page — URL A redirects to B, which redirects to C. Each extra hop adds latency and risk that the chain breaks somewhere in the middle.
Chains under three hops, where the final destination is a live, indexable page. AutoFix repoints the original URL directly at that destination, skipping the intermediate hops.
These are diagnosed, not auto-applied, because picking the right destination is a judgement call. The exact chain and where it breaks is shown, ready for a person to decide.
Yes. Canonical tags are audited alongside redirects, including self-referencing canonicals, cross-page canonicals, and cases where a canonical points to a non-indexable page.
Yes. A full crawl maps every redirect and keeps checking after launch, not just once on migration day, so a chain that dead-ends doesn't sit there for months before anyone notices.
Yes. Every AutoFix change is logged with a before-and-after diff and can be rolled back from the fix history at any time.
Find every broken path on your site.
Chains, loops, dead ends and canonical mismatches — mapped across the whole site, not the pages you thought to check.