On-Page SEO Checklist Before You Publish a Post
Most on-page SEO damage happens in the ten minutes before you hit publish. You've written the post, the ideas are good, and you just want it live. So the title tag gets whatever you typed into the headline field, the meta description is blank, and the images are still named IMG_4821.jpg.
None of those things are fatal on their own. Together, they're the difference between a page that gets crawled, understood, and ranked, and one that quietly sits on page four forever.
This checklist is the one I run before publishing anything. It takes about ten minutes and it's ordered so the highest-leverage items come first.
Before you publish: the 12-point on-page checklist
1. Does the page target one clear query?
Read your headline and ask: what would someone type into Google to find this? If you can't answer in one sentence, the page is trying to do too much. Split it or pick a lane.
One page, one primary intent. Supporting topics belong in their own posts, linked from this one.
2. Is your title tag written for the search result, not the page?
Your H1 and your title tag are two different things, even though most CMS platforms default them to the same text.
The title tag is what shows in search results. It should:
- Lead with the thing people are searching for, not your brand
- Stay short enough that it isn't truncated in results
- Read like a sentence a human would click, not a keyword list
If your CMS auto-fills the title tag from the headline, check it manually. Headlines written for readers often make poor search snippets.
3. Is the meta description actually written?
Google rewrites meta descriptions constantly, so this isn't about controlling the snippet. It's about giving Google good raw material and giving yourself a shot at a click.
Write one or two sentences that state what the page delivers and why it's worth clicking. Skip the vague summary. If the meta description field is empty, you've handed Google nothing to work with.
4. Does your H1 match the page's promise?
There should be exactly one H1, and it should describe what the page is about. If your theme renders the site name as an H1 on every page, that's a template problem worth fixing — it dilutes every page on the site.
5. Do your H2s tell a story on their own?
A useful test: read only your H2s, top to bottom. If a reader could follow the argument from the headings alone, your structure is working. If they read like random labels, rewrite them.
Headings also help search engines understand which parts of the page matter. They're not decoration.
6. Have you linked to at least two or three relevant pages on your own site?
Internal links are the most under-used on-page lever. They pass context to search engines and keep readers on your site.
Before publishing, add links to:
- A related post that expands on a sub-topic
- A page that converts (a service page, product page, or signup)
- Any older post you're building on
Use descriptive anchor text. "Click here" tells a search engine nothing about the destination.
7. Are your images named and described properly?
Three things per image:
- Filename —
internal-linking-checklist.jpg, notscreenshot-2024.png - Alt text — a plain description of what the image shows, for screen readers and search engines
- File size — compress before uploading, and use a modern format where it makes sense
If the image is purely decorative, an empty alt attribute is correct. Don't stuff keywords into alt text.
8. Does the first paragraph answer the question?
Readers and search engines both look at the top of the page to decide if it's relevant. Don't warm up with three paragraphs of context. State the answer, then explain it.
9. Is the URL short and readable?
/on-page-seo-checklist beats /2024/03/12/how-to-do-on-page-seo-for-your-blog-post-final-v2. Set the slug before publishing — changing URLs later means redirects.
10. Have you added structured data where it genuinely applies?
Structured data helps search engines understand what a page is. It does not guarantee a visual rich result.
Be realistic about what schema gets you today:
- FAQ rich results now appear only for authoritative government and health sites. Adding FAQPage markup to a general business blog will not produce a dropdown in search.
- HowTo rich results were discontinued entirely.
- Article and Breadcrumb markup still help search engines parse your content and can influence how your page is displayed in some contexts.
If you add markup, validate it with Google's Rich Results Test or the Schema Markup Validator before publishing. Both are current tools; older Google structured-data helpers have been retired.
11. Is there one clear next step for the reader?
On-page SEO and conversion overlap here. A page that ranks but gives the reader nowhere to go is a wasted visit. Decide what you want them to do next — read another post, book a call, buy — and make that obvious.
12. Have you checked how the page looks on a phone?
Most of your traffic will be mobile. Before publishing, load the draft on your phone and check that headings aren't wrapping awkwardly, images aren't overflowing, and tap targets are big enough to hit.
The mistakes that quietly undo good on-page work
A few things I see repeatedly on sites that are otherwise well-optimized:
- Keyword stuffing the first paragraph. It reads badly and it doesn't help. Use the phrase where it fits naturally and move on.
- Publishing with a placeholder slug.
/untitled-3is a missed opportunity and a redirect waiting to happen. - Linking out to competitors in the opening paragraph. Fine later in the piece, bad in the first screen.
- Forgetting to update older posts. When you publish something new, go back and link to it from your most relevant existing page. That's how a blog builds authority instead of a pile of disconnected posts.
- Never looking at the data. Publishing is the start, not the end. Check impressions and clicks after a few weeks and adjust the title or intro if the page is getting impressions but no clicks.
Run this checklist once, then automate it
The first time you run through these twelve items it'll feel slow. By the third post it takes ten minutes, and you'll start catching things in the draft rather than after publication.
If you want to know which of these issues are already live on your site — missing meta descriptions, thin pages, orphaned posts, broken internal links — run a free audit and work through the findings in priority order. It's faster than auditing pages one at a time.
For more checklists and step-by-step fixes, browse the guides library.
More guides · Compare audit tools · Run a free website audit