On-Page SEO Checklist for Blog Posts: A Repeatable Pre-Publish and Post-Publish Audit
A reliable blog post SEO checklist helps you catch avoidable problems before publication and gives you a clear process for improving the page after search data becomes available. Use this audit to review intent, page elements, links, media, technical settings, and performance without treating SEO as a one-time task.
Overview
On-page SEO is the work of making a page understandable, useful, and easy to navigate for both readers and search systems. It includes visible elements such as the headline, headings, copy, images, and links, as well as supporting details such as the URL, metadata, structured data, mobile presentation, and indexability.
The purpose of this checklist is not to force a keyword into every available field. A stronger process starts with the reader's question, confirms that the article satisfies the likely search intent, and then checks whether the page communicates its purpose clearly. The same workflow can be used for a new draft, a scheduled post, or an older article that needs a blog SEO audit.
Before starting, record the page URL or draft location, target topic, intended reader, publication date, and the person responsible for the review. A simple spreadsheet, project board, or editorial calendar can track the status of each check. For a broader publishing system, see this editorial calendar template for bloggers.
Pre-publish and post-publish checks at a glance
| Area | Before publishing | After publishing |
|---|---|---|
| Search intent | Confirm the format and depth match the reader's question. | Compare the page's queries and landing-page behavior with the original intent. |
| Title and description | Write a clear title and useful meta description. | Review how the result appears in search and test a revision when appropriate. |
| Headings and copy | Check hierarchy, coverage, clarity, and natural topic language. | Identify unanswered questions, outdated sections, or weak passages. |
| Links | Test internal and external links and use descriptive anchor text. | Check for broken, redirected, or newly relevant links. |
| Media and mobile | Check image relevance, accessibility, layout, and small-screen presentation. | Review rendering and engagement signals for usability problems. |
| Indexing and performance | Confirm canonical, indexability, structured data, and basic loading setup. | Verify the live URL and monitor indexing, visibility, and page experience. |
What to track
1. Search intent and content fit
Write down the question the post is meant to answer and the action the reader should be able to take afterward. Then compare the draft with pages or formats that appear relevant for the same topic, without copying their wording. Ask:
- Is the reader looking for an explanation, instructions, a comparison, a list, or a decision guide?
- Does the introduction answer the main question quickly?
- Does the article provide enough context for a reader who is new to the subject?
- Are important qualifications, steps, examples, or limitations missing?
- Does the format match the promise made by the headline?
Use keyword research as a way to understand language and related questions, not as a substitute for editorial judgment. The keyword research workflow for bloggers can help connect a topic to search intent before outlining.
2. Title, meta description, and URL
The title should state the subject and offer a precise reason to read. Keep it specific rather than stuffing it with variations of the target phrase. Check that the title is distinct from other posts on the site and accurately reflects the page.
Write a meta description that summarizes the benefit or scope of the article. It should make sense as standalone copy and should not promise information the page does not provide. Treat the description as a useful preview, not as a place to repeat every keyword.
Keep the URL short, readable, and tied to the enduring topic. Avoid unnecessary dates, internal project labels, and complicated strings. If an existing page already has a stable URL, do not change it casually; a URL change requires a deliberate redirect and link review.
3. Headings, copy, and readability
Use one clear page heading, followed by a logical hierarchy of sections and subsections. Headings should help a reader scan the article and understand what each section contributes. Do not select heading levels solely for visual size; use styling for appearance and HTML levels for structure.
Review the opening paragraphs for clarity, then remove repetition, vague claims, and unnecessary throat-clearing. Break long blocks into manageable paragraphs, use lists where they improve scanning, and define specialist terms when they first appear. A readability checker can identify dense sentences, but a human edit is still needed to judge accuracy, tone, and usefulness.
Check that the primary topic appears naturally in the title, introduction, a relevant heading, and the body where appropriate. Related language should arise from the subject itself. Do not add awkward keyword variations merely to increase phrase frequency.
4. Internal and external links
Add internal links where they help the reader continue learning or complete a related task. Anchor text should describe the destination rather than relying on vague phrases such as “click here.” For example, link to an article about internal linking for blog posts when the reader needs a deeper linking process.
Before publishing, open every important link and confirm that it reaches the intended page. Review external references for relevance and durability. After publication, repeat the check for older posts because destinations can change, pages can be removed, and newer articles may become better internal-linking targets.
5. Images, accessibility, and mobile presentation
Every image should have a purpose: explain a process, illustrate an example, orient the reader, or support the page's subject. Use a descriptive file name when practical, provide useful alternative text for meaningful images, and use an empty alternative attribute for decorative images if the CMS supports it. Avoid placing essential instructions only inside an image.
Preview the article on a narrow screen. Check for clipped tables, oversized images, awkward line breaks, unreadable text, intrusive elements, and buttons or links that are difficult to use. Also confirm that captions, lists, embeds, and code examples remain understandable outside the desktop editor.
6. Structured data, indexing, and technical settings
Confirm that the page uses the appropriate content type in the CMS and that any structured data accurately describes what is visible on the page. Do not add fields simply because they are available. Review schema examples when your publishing platform, theme, or content format changes.
Check the canonical URL, indexability setting, sitemap inclusion, and preview or staging restrictions before release. The exact controls vary by CMS, so record the locations of these settings in your internal publishing notes. After publication, open the live page in a private browser window and verify that it is accessible at the intended URL.
7. Performance and measurement setup
Confirm that analytics or measurement tags are present according to your site's standard setup, and record the page's publication date. Check that images and embeds are not unnecessarily heavy and that the page remains usable while loading. You do not need to turn every performance measure into a publishing gate, but serious layout or usability problems should be fixed before promotion.
For the post-publish review, record impressions or visibility, clicks, average position where available, engaged visits, and meaningful actions. Treat these as clues rather than isolated verdicts. A page with limited visibility may need a stronger match to intent, while a page that attracts visits but fails to support the reader may need clearer structure or a better next step.
Cadence and checkpoints
Run the full checklist before each new post. For an existing article, use a lighter monthly check for high-priority pages and a broader quarterly review for the rest of the library. A practical sequence is:
- Draft stage: confirm the topic, reader question, format, and outline. A content brief template for bloggers can make these decisions visible before writing begins.
- Pre-publish stage: complete the page-element, link, media, mobile, and technical checks. Assign each issue a status: fix now, fix after launch, or no action.
- Early live check: open the published URL, test the main links, inspect the mobile layout, and confirm that the page is available as intended.
- Search-data checkpoint: once the page has accumulated enough data to reveal patterns, compare actual queries and behavior with the original content brief.
- Quarterly refresh: update examples, links, screenshots, recommendations, and technical guidance that may have changed.
- Annual system review: reassess the checklist itself, the CMS workflow, schema examples, reporting fields, and ownership of each task.
Keep a change log with the date, issue, action taken, and expected reason for the change. This prevents repeated edits based on memory and makes it easier to distinguish a content improvement from a technical fix.
How to interpret changes
Do not react to every short-term movement. First check whether the page, search landscape, site navigation, tracking setup, or promotion schedule changed. Then compare like periods and look for patterns across several related pages when possible.
If the page receives impressions for related questions but earns few visits, review the title, description, and the match between the visible result and the reader's intent. If it receives visits but readers do not continue, inspect the introduction, page structure, internal links, and clarity of the next step. If visibility is limited, revisit the topic scope, supporting internal links, and whether the article offers a distinct answer.
Separate content problems from technical problems. A missing canonical, blocked page, broken link, or mobile layout issue requires a different response from an article that simply needs better examples. Make one or two meaningful changes at a time when possible, then record what changed so the next review has context.
When to revisit
Use this on-page SEO checklist for every new blog post, then schedule the live-page review rather than leaving it to chance. Revisit sooner when the article covers a changing tool, platform, process, product, regulation, or search feature; when a reader reports an error; when a key link breaks; or when the CMS or site design changes.
For evergreen articles, a quarterly refresh is a sensible default. Check whether examples still make sense, links still work, screenshots reflect the current interface, and the article answers the questions readers are actually bringing to it. Once a year, review the checklist itself and update the technical recommendations, schema examples, CMS instructions, and reporting fields.
To put the process into practice today, choose one scheduled post and complete the pre-publish column. Add a reminder for the live check, save the baseline information, and record every decision. For older content, begin with pages that already matter to your audience, then connect them to your topic cluster and internal linking plan. A repeatable audit will not replace good writing, but it will make good publishing habits easier to maintain.