An on-page SEO audit turns a vague optimization task into a repeatable review of one URL. This checklist helps you examine search intent, page structure, content coverage, links, technical settings, usability, and conversion elements, then record each issue with a clear owner, priority, fix, and verification date.
Overview
A blog post SEO audit should answer one practical question: can the page satisfy the visitor who arrives from its target search query, and can search engines understand, access, and represent it accurately?
The aim is not to add keywords wherever space is available. It is to identify obstacles that make a useful page difficult to discover, interpret, read, navigate, or act on. A strong audit also separates evidence from preference. For example, a missing descriptive title is a concrete issue; a disagreement about whether a heading sounds elegant may be an editorial preference.
Use the audit for an existing URL before a substantial update, after a noticeable change in performance, or as part of a planned quarterly maintenance cycle. Keep one row per issue in a spreadsheet or project board using these columns:
- URL and audit date: Record the exact page and the date reviewed.
- Area: Use categories such as intent, content, metadata, links, media, technical SEO, usability, or conversion.
- Issue: Describe the problem in observable terms.
- Priority: Mark it high, medium, or low according to likely impact and effort.
- Owner: Assign the person responsible for the fix.
- Fix: State the action required, not merely the desired outcome.
- Verification date and result: Confirm that the change was published and checked.
For related planning work, compare this process with the SEO content brief template and workflow. A brief defines what a page should accomplish; an audit checks whether the published page delivers it.
What to track
1. Search intent and page purpose
Write the target query, the likely reason behind it, and the job the page is expected to perform. A query may indicate a need to learn, compare options, complete a task, or find a specific resource. Review the page from that visitor’s perspective:
- Does the opening section confirm that the page addresses the query?
- Does the format match the task, such as a guide, checklist, comparison, or explanation?
- Are important answers easy to find without forcing readers through unrelated background?
- Does the page make its intended next step clear?
If the page is targeting several unrelated intents, record that as a structural issue. It may need a narrower focus, clearer sections, or separate supporting pages. Use keyword clustering for blog topics when deciding whether related queries belong on one URL or across a content group.
2. Content and heading structure
Check that the main heading describes the page accurately and that headings create a logical hierarchy. The title, introduction, H2s, H3s, lists, examples, and conclusion should work together rather than repeat the same point.
Review topical coverage by comparing the page with its brief, known audience questions, and the subtopics needed to complete the reader’s task. Avoid treating a word count as a quality target. A shorter page can be more useful when it is focused, while a longer page may need consolidation if it repeats low-value material.
Check factual accuracy, examples, dates, screenshots, and outbound references. If the article contains claims that can become outdated, add an editorial note or review trigger. A content style guide can make these decisions consistent across the site; see the content style guide template for blogs.
3. Keyword placement and metadata
Confirm that the primary topic is represented naturally in the page title, main heading, introduction, and relevant subheadings. Related language should appear where it helps explain the subject, not as forced repetition. Also review the URL slug for clarity, stability, and unnecessary words.
Inspect the title tag and meta description separately from the visible introduction. They should accurately set expectations and distinguish the page from similar URLs. Record whether the title is truncated, vague, duplicated, or misaligned with the actual content. Use the title and meta description optimization framework for a more detailed metadata review.
4. Images, media, and readability
Every meaningful image should have useful alternative text that communicates its purpose. Decorative images should not receive descriptive text that distracts from the content. Check captions, filenames, dimensions, and placement when they affect understanding or page usability.
Run the article through a readability review, but treat the result as a diagnostic rather than a pass-or-fail grade. Look for long sentences, dense paragraphs, unexplained terminology, weak transitions, and unclear instructions. The blog post readability score guide can support this part of the audit.
5. Internal links and conversion elements
Check whether the page links to useful supporting and parent content with descriptive anchor text. Links should help readers continue their task, not merely increase the number of links on the page. Also look for orphaned pages, links to redirected or irrelevant URLs, and opportunities to link from related articles back to this one.
Review the page’s conversion or next-step element. It might be a sign-up, download, product explanation, contact action, or link to a deeper guide. The action should match the visitor’s stage and the page’s purpose. Avoid adding a prominent call to action that interrupts the answer before the reader receives useful information. For a dedicated linking review, use the internal linking strategy and audit checklist.
6. Technical settings and page experience
Verify that the URL is indexable when it is intended for search, returns the expected status, and is not blocked by an accidental directive. Check the canonical setting, sitemap inclusion where applicable, redirects, and duplicate versions of the page. Confirm that structured data, if used, accurately describes visible content and follows the requirements of the platform implementing it.
Review the page on a phone and a desktop-sized screen. Look for horizontal scrolling, hidden headings, difficult tap targets, intrusive overlays, broken media, slow-loading sections, and layout movement that interferes with reading. These checks do not replace technical monitoring, but they often reveal issues a content-only review misses.
Cadence and checkpoints
Use a three-stage workflow so the audit remains practical:
- Before publication: Confirm intent, heading structure, metadata, links, images, structured data, mobile presentation, and conversion elements.
- After fixes: Reopen the live URL, check the rendered page rather than only the editor preview, and mark each issue verified or unresolved.
- Monthly or quarterly: Review priority URLs, performance changes, outdated examples, broken links, and recurring audit failures across the site.
A monthly review is appropriate for important pages or sites that publish and change frequently. A quarterly review is usually more manageable for a stable evergreen library. Record the baseline date, the changes made, and the next planned review so the audit does not become a one-time document.
Pair page-level findings with the blog content performance dashboard template. Performance data can identify which URLs deserve a deeper audit, while the audit explains what may need to change. Do not assume that every ranking or traffic movement is caused by an on-page issue.
How to interpret changes
Prioritize issues using three questions: how directly does the problem affect the visitor’s task, how broadly does it affect search understanding or access, and how feasible is the fix? A missing primary answer near the top of the page may deserve more attention than a minor wording preference. A broken canonical or accidental no-index setting should be escalated because it can affect the URL’s ability to appear as intended.
Look for patterns across audit records. If many pages have vague title tags, the problem may belong in the editorial workflow rather than in individual rewrites. If internal links are consistently missing, update the publishing checklist and content brief. If pages are technically sound but fail to satisfy intent, revisit topic selection, query grouping, and the page format.
When results change after an update, compare the before-and-after record rather than relying on memory. Note what changed, when it changed, and which metric or observation prompted the review. Keep conclusions cautious: an improvement may have several contributing factors, and a decline may require more investigation before a fix is chosen.
When to revisit
Reaudit a blog post on its planned monthly or quarterly cadence, and sooner when one of these triggers occurs:
- The page’s target query, audience, product, or recommended process changes.
- Search performance, clicks, impressions, or engagement changes enough to justify investigation.
- The content contains dates, screenshots, tools, regulations, product details, or examples that may have become outdated.
- The CMS, site template, analytics setup, linking structure, or structured-data implementation changes.
- A related article is published, creating a new internal-link opportunity or possible topic overlap.
- A technical issue, accessibility concern, mobile problem, or broken media is reported.
To use this template immediately, choose one important URL, duplicate the audit columns in a spreadsheet, and record no more than the issues you can act on. Assign owners and dates, make the highest-priority fixes, verify the live page, and schedule the next review. Over time, the completed records become more than a checklist: they reveal the recurring editorial and technical problems that your publishing workflow should prevent.