Use this on-page SEO checklist before publishing a blog post to confirm that the page matches search intent, is easy to understand, can be discovered by search engines, and gives readers a useful next step. The workflow also creates a repeatable record for monthly or quarterly reviews, so SEO becomes part of your editorial process rather than a last-minute keyword check.
Overview
On-page SEO is the work you can control on the page itself: the topic, wording, structure, links, media, and publishing settings. A strong pre-publish review does not mean adding a keyword to every heading or trying to satisfy a mechanical score. It means checking whether the finished article clearly serves a defined audience and search purpose.
Run the review after the draft has been edited for accuracy and readability, but before publication. If several people work on the page, assign an owner to each unresolved item. This prevents common gaps, such as an editor assuming that the writer checked the URL or a developer assuming that the editor reviewed the indexing setting.
For topic selection and search intent, use the keyword research workflow for bloggers. A content brief template can also record the primary question, audience, supporting subtopics, and preferred result format before writing begins.
What to track
1. Search intent and topic coverage
- Primary question: Write down the question or task the reader expects the page to address.
- Result type: Decide whether the page should be a tutorial, comparison, definition, checklist, review, example, or another format.
- Useful coverage: Check that the article answers the main question directly and covers necessary supporting concepts without drifting into unrelated subjects.
- Audience fit: Remove unexplained jargon, assumptions, or examples that do not fit the intended reader.
Do not treat a list of related phrases as a substitute for coverage. The better test is whether a reader can complete the intended task after reading the article.
2. Title, description, and URL
- Write a descriptive title that communicates the page’s benefit or subject without exaggeration.
- Keep the main topic apparent in the title, while preserving natural language for readers.
- Create a meta description that accurately summarizes the page and gives a reason to open it. Avoid promising information the article does not provide.
- Use a short, readable URL that reflects the topic. Avoid unnecessary dates, filler words, confusing abbreviations, and duplicate variations.
- Check the page title shown in the browser or content management system separately from the visible headline if your platform supports both.
Titles and descriptions are invitations, not places to repeat every target phrase. Review them alongside the finished article so they describe the actual page.
3. Headings, readability, and editorial quality
Use one clear page heading, then organize the article with logical subheadings. A reader should be able to scan the headings and understand the argument or process. Place important explanations near the section where they are needed rather than hiding them in a distant conclusion.
Before publishing, check the opening paragraph, sentence length, list formatting, examples, and transitions. A readability checker can identify dense passages, but editorial judgment should decide what to change. Also verify facts, dates, product details, instructions, and links. If AI helped produce the draft, follow a separate AI content editing checklist for accuracy, originality, voice, and unsupported claims.
4. Links and page relationships
- Add internal links where they help readers understand a concept or take the next step.
- Use descriptive anchor text that tells readers what the destination contains.
- Confirm that links work, point to the intended page, and are not repeated without a clear reason.
- Link to the new article from relevant existing pages when appropriate.
- Identify whether the article is a guide, supporting page, comparison, or other part of a topic cluster.
Use the internal linking strategy checklist to review both links within the draft and links that should be added from older content. Internal links should improve navigation and context, not simply increase their count.
5. Images, entities, and structured information
Give every meaningful image a useful alt description that explains its purpose or content. Decorative images may need different treatment in the CMS. Check file names, dimensions, captions, and placement where these affect comprehension or page performance.
Review whether the article uses the important names, concepts, tools, places, or definitions that a reader needs to understand the subject. This is an entity and context check, not an invitation to force terminology into the copy. Add definitions or brief explanations when a term could be ambiguous.
If the page qualifies for structured data supported by your site and CMS, confirm that the markup matches the visible content. Validate the implementation with an appropriate testing or inspection tool, and record the result. Structured data should describe the page accurately; it should not be added merely as a ranking shortcut.
6. Page experience and publishing controls
- Preview the page on a phone and a larger screen.
- Check that text, buttons, tables, embeds, and images fit the layout.
- Confirm that the page loads through the intended secure URL and that canonical settings are correct for your site structure.
- Verify that the page is not accidentally marked noindex, password-protected, unpublished, or blocked from normal discovery.
- Check the visible author, publication date, updated date, categories, and other CMS fields for accuracy.
- Confirm that the XML sitemap, navigation, or relevant category page can include the article according to your site setup.
CMS labels vary, so document the exact location of these settings for your team. After publication, inspect the live URL rather than relying only on the editing screen.
Printable pre-publish review table
| Check | Status | Owner | Completion date |
|---|---|---|---|
| Search intent and audience are documented | Pass / Needs work | ||
| Title, meta description, and URL are accurate | Pass / Needs work | ||
| Headings and article structure are logical | Pass / Needs work | ||
| Facts, examples, and claims have been reviewed | Pass / Needs work | ||
| Internal and external links work and add context | Pass / Needs work | ||
| Images, alt text, and media display correctly | Pass / Needs work | ||
| Structured data is relevant and validated when used | Pass / Needs work | ||
| Mobile preview, canonical, and indexing settings are correct | Pass / Needs work | ||
| Live-page inspection and post-publish checks are assigned | Pass / Needs work |
Cadence and checkpoints
Use three checkpoints instead of treating SEO as a single event.
- During planning: Record the target question, intended reader, result format, internal-link opportunities, and any required evidence or updates.
- Before publication: Complete the full checklist, assign unresolved work, preview the page, and confirm publishing controls.
- After publication: Inspect the live URL, confirm that the page is accessible as intended, and note its initial performance baseline in your reporting system.
For established pages, review the checklist monthly when the article supports an important business or educational goal, and at least quarterly for a broader content library. A Search Console reporting template can help connect the checklist to impressions, clicks, queries, and page-level changes without relying on memory.
How to interpret changes
A performance change is a signal to investigate, not proof that one checklist item caused the result. Compare a reasonable period with a previous period and separate page-level changes from wider site changes.
- Impressions rise but clicks do not: Review whether the title and description accurately communicate the page’s value and whether the visible result matches the searcher’s intent.
- Clicks rise but engagement is weak: Compare the promise in the search result with the opening section. Readers may be arriving for a different task than the article supports.
- Traffic falls: Check for indexing, canonical, redirect, broken-link, layout, or content changes before rewriting the entire page.
- Several related pages decline: Review internal links, topic overlap, templates, and site-wide technical changes rather than changing only one paragraph.
- The article receives impressions for unexpected queries: Decide whether to clarify the current article, add a useful section, or create a separate page. Avoid forcing unrelated terms into the existing piece.
Record what changed, when it changed, what evidence supports the diagnosis, and what action you will test. This creates a useful editorial history for the next review.
When to revisit
Revisit this on-page SEO checklist quarterly for evergreen content, and sooner when a page shows a meaningful change in visibility, clicks, conversions, or reader behavior. Also reopen the review when the search intent changes, a core product or process changes, an important link breaks, or the CMS introduces new publishing fields.
Refresh the workflow when search documentation, schema guidance, analytics features, or your publishing platform changes. Rather than rewriting every page immediately, first update the checklist, test the new process on a small group of representative articles, and document any new verification steps.
For a structured refresh, use the quarterly content refresh workflow. Then add completed reviews to your content calendar so future checks have an owner and a date. The practical next step is simple: copy the table into your editorial system, mark each item as pass or needs work, and do not publish until every unresolved item has a clear owner or an explicit reason to defer it.