Search and Organic Discovery
On-Page SEO Review
Review a page's title, headings, intent coverage, evidence, links, media, structured data, canonical signals, indexability, and reader outcome.
Free editable Markdown · SEO specialists, editors, and web teams ·
Accessible HTML preview
Blank template
The downloaded file contains the same fields in editable Markdown.
Purpose and content
- URL
- [Canonical candidate]
- Primary reader job
- [Intent]
- Expected page type
- [Guide, tool, help, product, other]
- Distinct contribution
- [Evidence, workflow, tool, or experience]
- Competing site URL
- [Overlap or None]
- Last substantive review
- [YYYY-MM-DD]
- Primary success outcome
- [Reader behavior or task]
- Content gap
- [What remains incomplete]
Visible and technical review
- HTML title
- [Exact]
- Main heading
- [Exact]
- Meta description
- [Exact]
- Canonical
- [Exact destination]
- Robots/index status
- [Index/noindex and response]
- Language and alternates
- [Declared and available]
- Structured data
- [Type and visible support]
- Internal links in/out
- [Relevant pathways]
- Media
- [Alt, caption, dimensions, value]
- Status and rendering
- [HTTP response and important content]
Final checks
- Page fully satisfies its primary intent.
- Important claims are sourced and current.
- Title and headings are specific without forced repetition.
- Canonical and index directives match editorial ownership.
- Structured data matches visible content.
- Links and media improve reader understanding.
- Mobile, keyboard, and rendered states were inspected.
- Deployment, validation, and monitoring ownership are recorded.
How to use this template
- Define the intent, canonical owner, reader outcome, evidence, and current overlap.
- Review visible title, heading path, answer coverage, examples, links, media, and next action.
- Compare technical indexability, canonical, language, metadata, and schema with visible content.
- Test the deployed page across relevant devices, navigation paths, and rendered states.
- Prioritize fixes by reader and discovery impact, then validate and monitor documented changes.
Confirm purpose before individual elements
State the primary reader job and verify that the page delivers it with useful depth, evidence, and an appropriate next step. Check overlap with other site URLs and confirm why this page should be the canonical owner. A technically tidy page with thin, derivative, or mismatched content is not a successful review. Evaluate the opening, major questions, examples, limitations, and update status before adjusting title length or heading wording.
Align visible and machine-readable signals
Compare the HTML title, main heading, canonical URL, robots directives, status code, language, alternate-language links, and structured data with the visible content. They need not be identical strings, but they should describe the same page and entity. Structured data must reflect information users can see. Verify images have purposeful alternatives and dimensions, links lead to relevant destinations, and internal anchor text explains the relationship. Avoid hidden copy and repetitive anchors created only for crawlers.
Validate the deployed experience
Inspect the final URL on mobile and desktop, with JavaScript behavior where relevant. Confirm important content is available to the rendered document, navigation works, and no overlay blocks the task. Check performance data in context rather than applying one threshold blindly. After changes, crawl the URL, inspect source or rendered output, and monitor Search Console over an appropriate period. Record deployment date and unrelated changes so later analysis does not attribute every movement to one edit.
See the fields in context
Fictional example: repair-event schedule
Mend Hall is an invented service, and the audit details are illustrative.
- Intent: Find a current fictional repair event and understand what items are accepted.
- Issue: The title says “Events,” while the H1 says “Community,” and an old canonical points to the homepage.
- Content fix: Add dated schedule, accepted-item boundaries, accessibility contact, and last-checked ownership.
- Technical fix: Use a self-referencing canonical and event schema only for visible, current fictional event details.
- Validation: Check the deployed status, source, rendered content, internal links, and Search Console after release.
Frequently asked questions
Is repeating the primary keyword in every heading helpful?
No. Use descriptive headings that guide readers and include relevant terminology naturally where accurate.
Should every page include structured data?
No. Add supported types only when they accurately represent visible content and follow applicable requirements.
Can a canonical fix duplicate content by itself?
It is one signal, not a substitute for coherent URL, link, sitemap, redirect, and editorial decisions. Resolve the underlying ownership clearly.
When should the page be reviewed again?
Set triggers for material content, product, policy, evidence, template, or technical changes, plus a risk-based periodic review.