Audit workflow guide
How to turn repeated SEO findings into root-cause repairs.
A report with one row per occurrence is complete but hard to execute. A report that hides occurrences behind one summary is easy to scan but impossible to verify. A root-cause audit needs both layers.
Keep the counting units distinct
- Occurrence: one captured match
- Affected entity: the page, target, or asset with the condition
- Source page: where a reference or markup literal was delivered
- Root-cause group: the likely shared repair surface
Group without destroying evidence
Normalize URL identity before counting, but retain the original literal needed for diagnosis. Store every source-target pair, then group by stable context such as template path, schema node, attachment, or normalization rule.
Verify at the repair surface
After a shared template fix, re-check the source pages that carried the repeated occurrence. The number of repaired rows should be a measured outcome, not a multiplication assumption.
Connect a site and run the workflow yourself.
Get the full technical SEO toolkit on every plan. Choose the number of websites you need and use the same crawling, investigation, and verification workflow.
Get access →