TECHNICAL SUITE · ERRORS & REDIRECTS

Find broken redirects, chains, loops and canonicals.

Map every redirect across your site, identify dead ends and canonical mismatches, and get the exact fix for each one, ready for whoever owns your redirect rules. A migration mapped once by hand, never re-checked, is how a chain sits broken for months.

You are here · the workflow

CRAWL → DIAGNOSE → PRIORITISE → FIX → VERIFY → MONITOR

The technical surface · this page covers

Crawl & discoveryIndexabilityRenderingRedirectsSchemaContentInternal linksPerformanceCrawlabilityAssets

Part of Technical Suite's six-stage loop. See the full system →

Common challenges

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 every broken one should arrive with its exact chain and the page it should point to.

How SEORCE does it: every redirect and canonical is mapped on every crawl. Every chain, loop and redirect that ends in a dead page is diagnosed with the full chain shown and the live destination it should point to. Redirect rules live in your server or CMS, so the change stays with a person.

Try it

Click the button. Trace the chain.

A simulation of the diagnosis that runs on every crawl. /checkout-old routes through two old URLs and ends in a 404.

/checkout-old3 hopsDemo data
/checkout-old
→
/checkout-v2
→
/checkout-final
→
404
Where it shows up

Chain length, across the whole site.

1 hop · healthy2,860
2 hops312
3+ hops94
Ends in a 40428
Loops back on itself6

406 redirects and canonicals need a decision, each shown with its full chain and the page it should point to.

What AutoFix does here

Canonicals it applies. Redirects it diagnoses.

Applied automatically

  • ✓Self-referencing canonical mismatches with one correct URL

Diagnosed, not auto-applied

  • →Redirect chains, at any length
  • →HTTP/HTTPS and www/non-www redirect standardisation
  • →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
What you'll see

Inside every redirect and canonical.

The chain

Hop by hop

301→301→200
  • Source URL and full redirect chain, hop by hop
  • Final destination and its status code
Canonical & index

Where it should resolve

● Self ● Cross-page
  • Canonical target, self-referencing or cross-page
  • Indexability of the destination page
Fix status

Eligible, then verified

  • AutoFix eligibility, per redirect
  • Verification status after each fix

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
  • Applied automatically: self-referencing canonical tags with one correct URL
  • Diagnosed, never auto-applied: every redirect chain, 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

Last reviewed 15 October 2026 by the SEORCE team.

Common questions

Frequently asked about redirects.

Updated 18 September 2026

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.

No. Redirects are diagnosed, not changed automatically, because the rules live in your server or CMS. Each chain is shown hop by hop with the live page it should point to, ready for whoever manages your redirects.

They are diagnosed too, and picking the right destination for them 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 rather than only 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.

Free to start

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.

3,000+ users · Free forever plan, no card needed