Fix verification guide

How to verify an SEO fix without running another full crawl.

A full crawl is the right tool for a new site-wide inventory. It is often unnecessary when the immediate question is narrower: did the exact reference, tag, or response you repaired actually change?

Complete evidenceExplicit boundariesVerifiable outcomes
01

Keep the original evidence immutable

The crawl that created the task should remain available as historical evidence. Store a targeted result beside it with its own timestamp, scope, attempts, cache context, and rule version.

If a fresh check fails, the correct outcome is an inconclusive verification—not a mutation of the original finding.

02

Choose the correct verification role

  • Re-parse source pages for links, canonicals, hreflang, and schema references
  • Re-fetch targets for response, redirect, and asset outcomes
  • Recompute the rule using the same stored normalization model
  • Record URLs that could not be fetched instead of subtracting them from the denominator
03

Escalate to a full crawl when scope is global

Orphan detection, complete sitemap coverage, site-wide duplication, and some graph rules depend on a complete inventory. A targeted check should say when it cannot establish that inventory.

Private beta

Turn the next crawl into a repair system.

Bring a recurring technical SEO workflow. We will show how Amplitera keeps the evidence, handoff, and verification connected.

Request early access