On-Page SEO Audit
A complete on-page SEO checklist for auditing any landing page or article. Covers title tags, meta, technical signals, content quality, and internal linking.
Checklist preview
- Title tag is unique and under 60 characters
- Title includes the primary keyword
- Meta description is present and under 160 characters
- Meta description matches page intent
- Single H1 tag, relevant to target keyword
- Header hierarchy is logical (H1 → H2 → H3)
- No heading used purely for styling
- Canonical tag present and self-referencing
- Page is not blocked (robots.txt / noindex)
- Structured data is present and valid
- URL is short, lowercase, hyphen-separated
- Page loads under 3 seconds on mobile (CrUX / PageSpeed)
- No broken internal links on the page
- Primary keyword appears in the first paragraph
- Content fully answers the search intent
- No thin content or excessive repetition
- Images have descriptive alt text
- All images are optimized (format, size)
- Page links to relevant internal pages
- Anchor text for internal links is descriptive
- No orphan page (at least one internal link pointing here)
- og:title is set
- og:description is set
- og:image is present and 1200×630
Use this checklist before publishing a new page or as part of a periodic content audit. It covers the signals that matter for both rankings and user experience.
Who uses this
SEO specialists auditing client pages, content editors doing pre-publish checks, and developers doing technical SEO passes before a site launch.
How to adapt it
The checklist covers the common baseline. Extend it for your context:
- Add “FAQ schema is present” for informational pages
- Add “Page is in the XML sitemap” for newly published content
- Add “Hreflang is set correctly” for multilingual sites
- Remove the Open Graph section if you’re auditing pages where social sharing doesn’t matter
Workflow
Pre-publish: Run before a page goes live. Fail items become a task list for the editor or developer.
Content audit: Run on existing pages as part of a quarterly review. Save each run — you’ll have a before/after record when you re-run after fixes.
Client reporting: Export run history as CSV to include in an audit report.