On-Page SEO Checklist: 20 Factors That Matter, With a Do/Don't for Each
On-page SEO is the page-level QA pass I would run before publishing or updating a URL. This article uses an author-defined checklist structure, not Google's official factor list: the goal is to align one page with one search intent, make the page promise clear, support the answer with evidence, and remove avoidable confusion before the page goes live.
What you will learn
- How to review one page before publishing.
- How to separate intent match from keyword-density thinking.
- How title, meta description, H1, headings, examples, links, media, and schema fit together.
- How to improve a weak draft without promising rankings.
Short answer: The checklist is a publishing workflow, not a ranking guarantee.
Publishing pages but not sure the basics are right? Book a content audit and get intent, title, headings, internal links, schema boundaries, and page usefulness reviewed before the next batch goes live.
What on-page SEO should mean before publishing
Google’s documentation emphasizes helpful content, clear titles, useful snippets, crawlable links, image context, and structured data that describes visible information. An editor should turn those mechanics into a practical review, not a superstition list.
If technical blockers are suspected, use the confirmed technical SEO guide first; this article assumes the page can be published and reviewed.
Visual slot: Add a real screenshot/photo/diagram here: real page draft audit screenshot placeholder with no fake Search Console or ranking data. Replace this block with the final visual later.
The checklist I would run
Short answer: The item count is this article's structure, not Google's official list.
| Checklist item | What to check | Do | Don't | Evidence |
|---|---|---|---|---|
| Intent | One main search job | Write for the task | Mix unrelated intents | SERP and brief |
| Title | Clear page label | Make it specific | Promise too much | Draft title |
| Meta description | Useful preview | Summarize value | Stuff keywords | Snippet review |
| H1 | Matches promise | Align with title | Use vague headline | Page draft |
| Opening | Fast answer | Set scope | Delay the answer | First screen |
| Headings | Logical sections | Guide scanning | Use decorative headings | Outline |
| Answer blocks | Quote-ready answers | Be concise | Make giant paragraphs | Body copy |
| Examples | Proof of usefulness | Show real workflow | Invent data | Editor notes |
| Checklist item | What to check | Do | Don't | Evidence |
|---|---|---|---|---|
| Evidence | Support claims | Show proof | Invent results | Sources |
| Internal links | Useful next steps | Link naturally | Force anchors | Link map |
| Anchor text | Reader expectation | Be descriptive | Over-optimize | Body copy |
| CTA | Logical next action | Match intent | Oversell | Page goal |
| Images | Support the page | Add context | Use filler media | Media brief |
| Alt context | Image meaning | Describe use | Stuff terms | Image review |
| Structured data | Visible content | Follow guidelines | Promise rich results | Schema note |
| Freshness | Current usefulness | Update stale parts | Change dates only | Review log |
| Readability | Clear flow | Cut clutter | Pad length | Editor pass |
| Final QA | Pre-publish check | Review in CMS | Skip preview | QA notes |
| Measurement | Post-publish review | Use real data | Forecast outcomes | Search Console |
| Scope | Content boundary | Stay on promise | Add every topic | Brief |
Visual slot: Add a real screenshot/photo/diagram here: do and don't example card placeholder showing real draft text only. Replace this block with the final visual later.
Search intent and page promise
Search intent is the editorial contract. The page should answer the job implied by the query before it tries to add every related idea.
A strong page promise says who the page is for, what decision it helps, and what it will not cover.
| Search intent signal | What it suggests | Page response | Risk | Next action |
|---|---|---|---|---|
| How-to query | Needs steps | Show workflow | Too much theory | Add process |
| Checklist query | Needs QA list | Use scannable table | Wall of text | Add table |
| Comparison query | Needs criteria | Show differences | False winner | Add caveats |
| Template query | Needs editable format | Show fields | Fake download | Use visible template |
| Service query | Needs fit proof | Explain process | Overclaiming | Add evidence |
Visual slot: Add a real screenshot/photo/diagram here: intent match worksheet placeholder using real SERP notes and editorial brief, no fake metrics. Replace this block with the final visual later.
Title, meta description, and H1 alignment
Google's title link and snippet documentation supports writing useful, descriptive page information, but it does not create fixed character rules for every page.
The title, meta description, and H1 should point to the same promise without copying each other mechanically.
Short answer: Titles and descriptions should clarify the promise, not follow fake universal lengths.
Visual slot: Add a real screenshot/photo/diagram here: title and meta review screenshot placeholder using real draft fields, no fake SERP screenshot. Replace this block with the final visual later.
Headings, sections, and answer blocks
Headings are editorial scaffolding. They should help a reader scan the page and help the team see whether the answer is complete.
Short answer blocks are useful when a section needs a clear, quotable answer before the nuance.
Short answer: A heading should earn its place by making the next section easier to understand.
Evidence, examples, and page usefulness
Useful pages include examples, decisions, definitions, evidence, limitations, and next actions. They do not need invented numbers to feel specific.
If a claim needs proof, show the source, method, or internal evidence. If none exists, soften the claim.
Internal links, anchors, and next steps
Internal links should help readers move to the next useful page. They can support discovery and context, but they do not guarantee crawling, ranking, or sitelinks.
For technical cleanup, link to the technical SEO guide; for CMS-specific cleanup, use the confirmed WordPress SEO guide when relevant.
Visual slot: Add a real screenshot/photo/diagram here: internal link review diagram placeholder using real same-language URLs only. Replace this block with the final visual later.
Images, media, and structured data boundaries
Images and media should support the page promise. Use descriptive context and avoid fake screenshots, fake content scores, or fake validation output.
Structured data should describe visible content and follow Google structured data guidelines. It is not a rich result or ranking guarantee.
Visual slot: Add a real screenshot/photo/diagram here: final pre-publish QA checklist placeholder with real page fields, media notes, and schema boundaries. Replace this block with the final visual later.
Common on-page SEO mistakes
- Treating keyword density as an SEO requirement.
- Calling the checklist Google's official factor list.
- Writing title and meta rules as fixed character limits.
- Adding internal links only for anchor text manipulation.
- Using schema for content that is not visible on the page.
- Promising rankings, snippets, AI citations, traffic, leads, or revenue.
What I would check first
Assume a service page draft has a vague H1, a meta description that lists keywords, no answer in the opening, and internal links added at the end with generic anchors. I would rewrite the page promise, align the title and H1, add a concise opening answer, move evidence into the relevant section, and replace generic anchors with useful next-step links.
The change log would say what was improved and what still needs real page data after publishing. It would not forecast rankings, snippets, traffic, or conversions.
Publishing pages but not sure the basics are right? Book a content audit and get intent, title, headings, internal links, schema boundaries, and page usefulness reviewed before the next batch goes live.
FAQ
Is this Google's official on-page SEO factor list?
No. It is an author-defined publishing QA checklist for page-level review.
Does completing the checklist guarantee rankings?
No. It can improve clarity and reduce avoidable issues, but it does not guarantee rankings, indexing, traffic, or snippets.
Is keyword density still required?
No. Do not use keyword density as a required metric; focus on intent, clarity, usefulness, and evidence.
How should I write a meta description?
Write a useful page preview that matches the page promise; do not treat character length as a universal Google rule.
Do internal links guarantee crawling or sitelinks?
No. Internal links can support discovery and user navigation, but they do not guarantee crawling, rankings, or sitelinks.
Does schema guarantee rich results?
No. Structured data should describe visible content and follow guidelines, but it does not guarantee rich results.
Source notes
Official Google Search Central sources were used for SEO starter guidance, helpful content, title links, snippets, crawlable links, images, and structured data behavior. The checklist count is the article's author-defined structure, not a Google standard.
AIO facts were not forced into visible copy because this guide does not make AI Overview or AI citation claims.