Audit a page plan before it becomes a publishing problem
The audit turns a structured page plan into page-level Ready, Review, and Blocked decisions. It checks deterministic structure first, then adds content-risk findings when body text is available.
Last updated
What the audit checks
The audit is designed for pre-publish page sets, not for scoring an entire website.
- Required and malformed fields
- Duplicate URLs, titles, headings, and declared intent
- Canonical, indexability, parent relationships, and unresolved placeholders
- Content similarity and page-specific value when body text is available
How to start
If you already have a page plan, import the CSV directly. If the plan still needs to be generated from structured data, build it with Page Matrix and let the same audit evaluate the result.
- Existing CSV → run the audit
- Structured dimensions or row data → build a Page Matrix
- Before publishing to an existing site → run Existing Site Guard
Read the decision, then the rule
Ready, Review, and Blocked are derived from the rules that actually ran. Every issue code links to its public rule reference so the trigger, reason, and recommended fix stay attached to the result.
Coverage is part of the result
A missing or bounded measurement is never silently treated as a pass. Body-text checks need body text, very large sibling groups can use bounded comparison, and cross-template near-duplicate detection uses a candidate search rather than an exhaustive all-pairs comparison.
Next action
Use the rule reference when a page needs a decision, or continue through the Docs in order.