Blog SEO Checklist: Check Every Post Before and After You Publish

Good blog posts still go unseen for ordinary reasons. The title is vague, the post answers a question nobody asks that way, no other page links to it, the images have no description, or a stray setting keeps the page out of search. Each of these takes a minute to fix at publishing time and much longer to find afterwards.

This blog SEO checklist is built to be used once per post, in order, by whoever presses Publish. It is for company blogs, personal blogs and small publications on any CMS, and it takes about 15 minutes for a finished draft. It does not promise that a post will rank or draw visitors. It makes sure that nothing you control stands in the way.

Short answer: Before publishing a blog post, confirm it answers one clear search intent, has a unique title and a short readable URL, uses headings and descriptive image alt text, links to and from related pages, and is indexable. After publishing, inspect the URL in Search Console and review performance after several weeks.

Before you begin

You need edit access to the CMS, a way to view the page source or a page-inspection tool, and Google Search Console for the site. If Search Console is not set up, start with Set Up Google Search Console: Complete Website Owner Checklist.

Choose one primary topic before you open the list. A post that tries to answer five questions usually answers none well. If you have not researched the topic yet, Keyword Research for Small Business: A Free, Step-by-Step Process shows a simple process.

One caution applies to everything below. Google's guidance says to create content primarily for people, and treats content made mainly to attract search visits as a warning sign. Use the list to remove obstacles, not to engineer a post around a phrase.

Step-by-step instructions

Step 1: Before writing, pick one query and check what searchers expect

Name the phrase a reader would type, then search it and look at what comes back: guides, product pages, lists, definitions, videos? The dominant page type tells you what fits. A 3,000-word essay for a query that returns short definitions answers a question nobody asked. Search Intent: How to Match Each Page to What Searchers Want goes deeper.

Check your own site next. If a post already covers the topic, update it instead of writing a competitor. Two posts chasing one query split links and clarity. Finally, list what only you can add: your own data, a photo of the real product, a worked example, a mistake you made. Google's self-assessment questions ask whether content offers original information and goes beyond the obvious. If your list is empty, the post is unlikely to stand out.

What success looks like: One sentence reading "This post helps [reader] do [task]", plus two or three things that make it different.

Step 2: Write the title, URL and description

Title. Google builds title links mainly from the title element and may also use the visible main heading, so make both say the same thing. Keep each title unique, descriptive and concise, with the topic first. Google says there is no length limit but long titles are cut to fit the screen. Why Google Rewrites Title Tags and How to Write Titles That Stick covers when Google swaps your text.

URL. Use readable words, such as /blog/how-to-clean-a-dishwasher-filter, not an ID. Keep it short, use hyphens, and do not change it after publishing unless you add a permanent redirect. See SEO-Friendly URLs: How to Build Readable, Stable Web Addresses.

Meta description. Google says snippets mostly come from page content and sometimes from the meta description. Write one or two accurate sentences, unique to the post. It invites the click; it is not a ranking lever.

What success looks like: Title, URL and description describe the same single topic, and none duplicates another post.

Step 3: Structure the post for scanning

Use one h1 for the post title and h2/h3 for sections. Google's guide says heading number and order do not matter for Search, but headings help readers navigate and heading order helps screen readers. See Heading Structure for SEO: Use H1 to H6 for Meaning, Not Style.
Answer the main question near the top in one to three plain sentences, then expand. This serves hurried readers; it does not guarantee a featured snippet.
Phrase some headings as the questions readers ask.
Use short paragraphs, lists for steps and tables for comparisons.
Show who wrote the post. Google recommends accurate bylines where readers expect them and warns against invented authors or credentials.
Skip word-count targets. Google lists targeting a word count based on a supposed Google preference as a warning sign. Write until the question is answered, then stop.

What success looks like: A reader who scans only the headings and first paragraph can tell what the post says.

Step 4: Prepare images

Google recommends sharp images near relevant text, descriptive alt text, short descriptive filenames (dishwasher-filter-removed.jpg, not IMG00023.JPG), and standard <img> elements, because it does not index CSS background images. Set width and height so the page does not jump while loading, and compress files before upload. Alt text should say what the image shows in context, not list keywords. See How to Write Alt Text: Examples for Every Type of Image and How to Compress Images for the Web Without Losing Quality (Complete Guide). For link previews, check your Open Graph Tags and Twitter Cards setup.

What success looks like: Every meaningful image has useful alt text, a clear filename and a modest file size.

Step 5: Add internal and external links

Google says every page you want indexed should receive a link from at least one other page on your site, links should be real <a href> elements, and anchor text should be descriptive and concise. Work in both directions:

Link from the new post to two to four related posts or service pages, where they help the reader.
Edit two or three older relevant pages so they link to the new post. Otherwise it may become an orphan.
Cite reputable external sources for claims that need them, and say what the reader will find.

Avoid "click here" anchors. Internal Linking Strategy: Link Your Pages for People and Crawlers goes further.

What success looks like: At least one existing page links to the post, and the post's own links use descriptive anchors.

Step 6: Check structured data, if your template adds it

Article markup is optional. Google lists no required properties, only recommended ones: headline, image, datePublished, dateModified and author. It says the markup can help Google show better titles, images and dates, and that features are never guaranteed. If your theme or SEO plugin already outputs it, check that the values match the page and do not add a second copy by hand.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Clean a Dishwasher Filter",
  "datePublished": "2026-11-04T09:00:00+00:00",
  "author": { "@type": "Person", "name": "Sam Example", "url": "https://example.com/about/sam" }
}

Article Schema Markup: Add Accurate JSON-LD for Articles and Posts has the full pattern.

What success looks like: Any markup matches the visible title, author and dates, and the Rich Results Test reports no critical errors.

Step 7: Run the technical check, then publish

Confirm these on the preview or live URL:

Check	How to confirm
Indexable	No `noindex` in the meta robots tag or `X-Robots-Tag` header; not blocked in robots.txt
Canonical	The canonical tag points to the post's own final URL
Status	The URL returns 200 with no redirect chain
Mobile	The page reads properly on a phone
Sitemap	The post will appear in the XML sitemap

If a staging setting is blocking search engines, remove it now. How do I fix "Blocked by robots.txt"? helps if you find a problem. Keep categories simple: one sensible category per post, and no tag pages that list a single post.

What success looks like: The URL passes every row.

Step 8: Inspect after publishing, and review later

Paste the live URL into the URL Inspection tool in Search Console. If the page is available, you can request indexing, but that is a request, not an instruction. Google says changes can take from a few hours to several months to show. Check the sitemap includes the post (How do I submit a sitemap to Google?), and use Page Indexing Report Explained: Every Status and What to Do if the status is unclear.

Then set two reminders: four to eight weeks after publishing, and again at six to twelve months. At the first, open the Performance report for the page. Impressions without clicks point at the title and opening; neither points to indexing or internal links, so check those before rewriting. At the second, decide whether to update. Do not change the date unless the content changed substantially; Google advises against altering dates to look fresh. Read the Search Console Performance Report: Clicks, CTR and Position explains the numbers, and Content Audit: How to Review Every Page and Decide What to Do covers reviewing a whole blog.

What success looks like: Search Console shows the URL as crawlable, and a review date is on the calendar.

What can a blog SEO checklist not do?

It cannot make a post better than the idea behind it, and it cannot decide what Google shows. A checklist removes avoidable technical and editorial problems. Whether a post earns clicks depends on how useful it is compared with other pages, and Google makes the final call on crawling, indexing and ranking.

Final verification checklist

The post targets one topic and one search intent, and no other post already covers it.
The title, main heading and URL describe the same topic and are unique on the site.
The meta description is unique and accurately summarises the post.
The main answer comes early and headings are clear.
Images have descriptive alt text, short filenames, dimensions and compressed files.
The post links to related pages, and at least one existing page links to it.
Any structured data matches the visible content and validates.
The page is indexable, canonical, returns 200 and is in the sitemap.
Authorship and dates are accurate, and a review date is scheduled.

Common mistakes to avoid

Publishing with a staging "discourage search engines" setting still on. Check the robots meta tag on the live page.
Rewriting an old post as a new one. Update the original so links and history stay in one place.
Stuffing keywords into titles and alt text. Google's spam policies define keyword stuffing as filling a page with keywords until it reads unnaturally.
Burying the answer under a long personal introduction. Lead with the point.
Forgetting internal links. A post nothing links to is hard to find for crawlers and readers.
Bulk-publishing thin or auto-generated posts. Google's spam policies cover scaled content abuse: large amounts of unoriginal content with little value. Fewer, better posts are safer.
Changing a URL without a redirect. Add a permanent redirect from the old address.
Judging a post after a week. Wait several weeks.

Frequently asked questions

How long should a blog post be for SEO?

As long as it takes to answer the question well. Google says content length alone does not affect ranking and lists chasing a word count as a warning sign.

How often should I publish?

Often enough that each post is carefully made. Google's guidance sets no posting frequency, and a steady schedule of useful posts beats a burst of weak ones.

Do I need the keyword in the URL?

Readable words in a URL help people. Google's guide says keywords in URL paths have hardly any ranking effect, so do not contort a URL to include one.

Do I need schema markup on a blog post?

No. Article markup is optional and Google does not guarantee any appearance from it. Add it if your platform makes it easy and the values are accurate.

How soon will my post appear in Google?

It varies. Make sure the page is indexable and linked, submit your sitemap and check Search Console after a few weeks.

Official references

Next step: Try the free website sample to see how your own site does on a few of these checks. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.