The Pre-Publish SEO Checklist for Blog Posts (24 Checks, No Fluff)

You hit publish… and the post still sits in “Discovered, currently not indexed.” Or it gets indexed, but the snippet looks vague, the wrong URL shows up, and you’re left tweaking headings because you don’t know what else to do.

A pre-publish SEO checklist won’t force rankings, and it won’t rescue a weak angle. What it will do is remove the easy blockers that waste good writing: unclear intent, a promise your first screen doesn’t keep, messy headings, missing internal links, and technical settings that stop Google from crawling or choosing the right canonical.

This checklist gives you a repeatable QA routine for blog posts—from picking one search intent and writing something “only you can add,” to making the snippet specific, verifying crawlability and sitemap signals, and handling the first 48 hours after you go live. One expectation to set early: there is no keyword density target you need to hit. When you want Google’s own explanation of how Search works, start with Google Search Central.

If you want a version you can tick off as you work, use Balzac’s interactive checklist at https://hirebalzac.ai/free-seo-tools/seo-checklist/. It saves your ticks in your browser and needs no signup.

Before You Write: How Do You Pick One Search Intent?

Before you tick anything off an seo checklist before publishing, pick the one search intent your post will satisfy. Intent drives everything that follows: the angle, the outline, the examples, and even whether your title and headings feel right to a searcher.

Start by writing one primary query as a full sentence or phrase, the way someone would actually search. Keep it singular. “On-page SEO checklist” and “technical SEO checklist” are related, but they lead to different pages and different expectations.

Write the primary query: Choose the best-fit phrase, not a pile of variants. If you need two distinct queries to cover the topic, you probably need two posts.
Decide the job-to-be-done: Is the searcher trying to learn, compare, or complete a task? A “blog post seo checklist” search usually wants a scannable, step-by-step QA list, not a theory piece.
Set the success condition: Define what a satisfied reader can do after reading. Example: “I can run a pre-publish check in 10 minutes and know what to fix.”

Scan What Ranks and Reverse-Engineer the Pattern

Google the primary query in an incognito window, then scan the first page without overthinking it. You are looking for patterns, not copying competitors.

Content type: Are results mostly checklists, guides, templates, or tools?
Content format: Do they use short sections, long essays, or downloadable docs?
Content angle: Are they aimed at beginners, in-house marketers, agencies, ecommerce, SaaS?

If every top result is a checklist, Google is telling you the dominant intent is “give me a checklist.” Fighting that with a personal essay usually loses.

Open a few ranking pages and note what they all cover. Those are your “table stakes” items for an on-page seo checklist or blog post QA flow. Then list what they skip, gloss over, or explain poorly.

Your last pre-draft step is to choose one thing only you can add. That can be original screenshots from your CMS, a decision rule (when to ignore a warning vs fix it), a copy-paste template, or a hard boundary like “no keyword density target.” If you cannot name your unique contribution in one sentence, you are not ready to draft.

On-Page SEO Checklist: What Must Be True on the Page?

Your “only you can add” angle has to show up on the page in a way Google and readers can parse fast. This on-page SEO checklist is the minimum QA pass before you hit publish.

Title tag: Write a unique title that matches the query and fits 50-60 chars. Put the main topic first, then the qualifier (for example: “for SaaS founders”, “step-by-step”, “with templates”).
Meta description: Summarize the page in 150-160 chars. Treat it like ad copy for the exact search intent. If you cannot describe the page plainly, the draft is usually unfocused.
Exactly one H1: Use exactly one H1 that states the page topic. Keep it close to the title, but do not force them to match word-for-word.
Logical headings: Use H2s for the main steps or sections, H3s for sub-steps. Headings should read like an outline someone could follow without the paragraphs. Paste the draft into Balzac’s heading structure checker to see the outline and spot a missing H1 or a skipped level.
Answer Near the Top: Put the direct answer, definition, or “what you’ll do” in the first screen of content. Google explains that it works to “understand what pages are about” by analyzing content and context, so make the topic obvious early (see Google Search Central).
Readability Pass: Cut throat-clearing intros, shrink long sentences, and replace vague verbs (“improve”, “optimize”) with actions (“add an internal link to the pricing page”). If you want a quick sanity check, run the draft through Balzac’s Readability Checker.
Length Fits the Task: Match the intent. A “definition” query needs a tight explanation and examples. A “how to” query needs steps, screenshots, and edge cases. Ignore any “minimum word count” rule.
Images Have Useful Alt Text: Write alt text for meaning, not for keywords. Describe what the image shows (for example: “Google Search Console Coverage report showing Excluded pages”). Leave decorative images empty (alt="").
Internal Links Make Navigation Easier: Link to the next best page for a reader: the related guide, the product feature, the glossary definition. Use descriptive anchor text that names the destination.
Sources Back Up Claims: When you state a fact that could be disputed, cite a primary source (Google Search Central docs, standards bodies, vendor docs). If you cannot source it, rewrite it as an opinion, a process, or a clearly hypothetical example.

If you do these checks, you remove the common on-page failure modes: unclear topic, weak snippet, messy structure, and unsupported claims.

Blog Post SEO Checklist: How Do You Make the Snippet Clickable?

A weak snippet wastes the work you put into a blog post SEO checklist. Searchers decide fast: “Is this exactly for my query, and can I trust it?” Your title tag and meta description are your promise. Keep them specific, match the intent you chose, and avoid hype you cannot support in the first screen.

Use this mini seo checklist to make the snippet clickable before you hit publish:

Say what it is: include the core topic and format (checklist, template, guide) in the title.
Say who it is for: “for blog posts,” “for WordPress,” “for SaaS founders,” only if the page truly targets that audience.
Match the page: if the post has 24 checks, the snippet should not promise “the complete SEO system.”
Make the benefit concrete: “catch indexing blockers” beats “boost rankings.” You control QA, not Google’s results.
Remove fluff words: “best,” “ultimate,” and “2026” add length fast and rarely add meaning.

Write Title Tags and Meta Descriptions That Earn Clicks

Keep your title tag tight. GrowthVector recommends 50-60 characters for a unique, keyword-focused title. Put the main query near the front when it reads naturally. Write for humans first, then sanity-check that Google can understand the topic without guessing.

Write a meta description that previews the on-page experience. GrowthVector recommends 150-160 characters. Treat it like a two-sentence pitch: what the reader will get, plus a credibility cue (for example, “includes crawlability, sitemap, canonical, and share preview checks”).

Expect Google to rewrite snippets sometimes. Google generates titles and snippets from multiple page signals when it thinks it can help users. Google documents this behavior in Search Central’s title links guidance. Your job is to provide clean inputs: a clear title tag, a descriptive H1, and an early answer that matches the query.

Before publishing, paste your draft title and meta into Balzac’s SERP preview tool: SERP Snippet Checker. Use it to catch truncation, duplicated phrasing between title and description, and vague wording that makes the result blend into the page.

Technical SEO Checklist Before Publishing: What Should You Verify?

A clickable snippet still fails if Google cannot crawl, index, or confidently pick the right URL. This technical SEO checklist before publishing focuses on the few checks that prevent the most painful “why isn’t this ranking?” surprises.

Use a short, stable URL: Keep it readable, avoid dates unless the content is time-bound, and do not change it after promotion. In WordPress, set the permalink before you share the post anywhere.
Confirm the page is crawlable and indexable: Check for a noindex meta tag, an X-Robots-Tag: noindex header, or a robots.txt rule that blocks the path. Google can only index what it can fetch. Google’s own overview of crawling and indexing starts at Google Search Central.
Make sure the page is in your XML sitemap: Your CMS or SEO plugin (Yoast SEO, Rank Math, All in One SEO) usually handles this, but verify the sitemap actually includes the new URL and returns a 200 status.
Set the canonical URL intentionally: If the post has one public version, self-canonical is fine. If you publish variants (for example, campaign copies), point canonicals to the primary version so Google knows which URL you want indexed.
Pass a mobile-friendly reality check: Open the post on a real phone. Look for unreadable text, sticky headers covering the H1, and popups that block the main content.
Check performance with PageSpeed Insights: GrowthVector’s checklist recommends 90+ on desktop and 80+ on mobile. For Core Web Vitals targets, use LCP within 2.5 seconds, INP under 200ms, and CLS below 0.1. When scores are bad, the usual fixes are image sizing/compression, fewer third-party scripts, and removing heavy sliders.
Add structured data only when it matches the page: Use schema.org types that describe what is actually on the page (for example, Article). Avoid stuffing markup for features you do not qualify for. Google’s documentation changelog says FAQ rich results stopped appearing in Google Search from May 7, 2026 (what Google still shows), so FAQ markup will not change how the page looks in Google.
Preview the social share card: Verify Open Graph tags (og:title, og:description, og:image) and Twitter Card tags so links look right in Slack, LinkedIn, and X. In WordPress, Yoast SEO and Rank Math both include social preview settings.

How Do You Check Crawlability, Sitemaps, and AI Crawlers Fast?

For any seo checklist before publishing, the fastest checks are the boring ones: can Google fetch the URL, can it discover it in your sitemap, and are you accidentally blocking modern crawlers you actually want. You can validate all three in a few minutes, before you waste time tweaking copy.

Fast Crawlability Checks (Robots, Noindex, Canonical)

Start with the two blockers that cause the most head-scratching: robots rules and indexing directives.

Check robots.txt for the specific URL: Use Balzac’s Robots.txt Checker and test the exact path you plan to publish. Look for a Disallow that matches the directory (common with staging folders, tag archives, and parameter paths).
Confirm the page is indexable: In your CMS or SEO plugin (Yoast SEO, Rank Math, Shopify, Webflow settings), confirm the page is not set to “noindex” and you are not outputting a noindex meta robots tag. Also check for an X-Robots-Tag: noindex header if you use a reverse proxy like Cloudflare.
Verify canonical points to itself: Your canonical URL should usually match the published URL for a standard blog post. Fix canonicals that point to a different page, a parameter URL, or HTTP when the site uses HTTPS.

Fix anything that blocks crawling or indexing. Ignore “warnings” that do not change fetchability, for example a robots rule that blocks an internal search results path you never want indexed.

Sitemap Checks You Can Do Before and After Publish

Make sure the URL will be in a sitemap: If your CMS generates sitemaps automatically (WordPress, Webflow, Shopify), confirm posts of this type are included. If you manage sitemaps manually, generate or update one with Balzac’s Sitemap Generator.
Validate the sitemap is reachable: Open the sitemap URL in a browser. You want a clean XML response, not a login page, redirect loop, or 404.
After publish, confirm discovery in Google Search Console: Submit the sitemap in Google Search Console (if you have not already) and use URL Inspection to see whether Google found the URL through the sitemap or internal links. Google documents how crawling and indexing work in Search Central.

Check AI Crawlers Are Not Blocked by Accident

If you care about being cited in AI answers, treat AI bots like a separate technical surface area. Teams often block them unintentionally with a broad robots rule or a security layer.

Run Balzac’s AI Crawler Checker to spot disallows for common AI user agents.
Fix blocks that apply site-wide or to your blog directory. Keep blocks that protect private areas like admin paths, checkout, or account pages.

This blog post SEO checklist step is simple: block what must stay private, allow what you want indexed and cited, then ship.

After You Publish: What Should You Do in the First 48 Hours?

You shipped the post, and your seo checklist before publishing did its job: the page is public, crawlable, and worth indexing. The next 48 hours are about two things you still control: helping Google discover the URL, and getting real people to it so you can spot obvious problems fast.

Request indexing in Google Search Console (URL Inspection): Open Google Search Console, paste the full URL into URL Inspection, then click Request indexing if the page is eligible. Treat this as a request, not a guarantee. Google decides when and whether it crawls and indexes. Google describes crawling and indexing behavior in Google Search Central.
Verify the live URL is the one you meant to publish: Check the canonical tag, the title tag, and the meta description on the live page. CMS edits, SEO plugins, and caching layers can ship something slightly different than your draft.
Promote with trackable links: Share the post in the places your audience already pays attention (newsletter, LinkedIn, community, partner email). Add UTM parameters so you can separate “real distribution” from “random traffic.” Use Balzac’s UTM Builder to generate consistent utm_source, utm_medium, and utm_campaign tags.
Watch for obvious UX and rendering issues: Open the post on mobile and desktop, then test it in an incognito window. Look for broken tables, missing images, cookie banners covering the first screen, or a sticky header hiding your H1. Fixing these quickly protects engagement signals like back-to-SERP behavior.
Log a review date: Put a calendar reminder to revisit the post. Use a shorter window for fast-changing topics and a longer window for evergreen guides. On review, check Search Console queries, refresh screenshots, and update any cited docs that changed.

What to Do If Indexing Looks Stuck

If Search Console shows “Discovered, currently not indexed” or similar statuses for a while, do not panic and do not start changing the URL. Recheck the basics (noindex, canonical, internal links to the new post, sitemap inclusion), then improve the page itself: tighten the early answer, add missing steps, and cite sources for any claims. That is the fastest path from “published” to “worth indexing” in any blog post SEO checklist.

The Most Common SEO Checklist Mistake: Treating It Like a Ranking Recipe

When a page sits in “Discovered, currently not indexed,” many people respond by running an SEO checklist before publishing harder. They tweak headings, add a few internal links, and call it “optimized.” The page still underperforms because checklists are QA, not a ranking recipe.

The mistake is treating each checkbox like a ranking lever. Google does not rank pages because you hit a magic count of headings or keywords. Google ranks pages it can crawl and index, then chooses the one that best satisfies the query. Google explains the basics of how it finds, understands, and ranks pages in Google Search Central.

Why “Checking Boxes” Still Fails

Three failure modes show up over and over in any blog post SEO checklist workflow.

Wrong intent: Your page answers a different question than the query implies. Example: the query wants a quick pre-publish QA list, but your post starts with a long history of SEO and buries the checklist.
Weak differentiation: You publish the same list everyone else published. If the top results already cover the basics, Google has little reason to swap yours in. Add something specific: decision rules, screenshots from Google Search Console, a copy-paste template, a “when to ignore this warning” section.
Unsupported claims: You promise outcomes (“this will boost rankings”) without evidence. That forces readers to bounce and forces you to keep rewriting. Replace claims with verifiable mechanics (what you changed, what it affects) and cite primary docs when you state facts.

This is why “keyword density” advice wastes time. There is no density target that guarantees performance, and stuffing terms often makes the page less clear.

Use your on-page SEO checklist as a final pass for clarity and trust:

Intent check: Read the title, H1, and first screen. Do they answer the exact query without warm-up?
Difference check: Write one sentence: “This page is worth clicking because…” If you cannot finish it, add something only you can provide.
Claim check: Circle every sentence that sounds like a fact. Add a source, rewrite as an opinion, or remove it.
Snippet reality check: Make sure the title and meta describe what the page actually delivers. Overpromising earns clicks and loses trust.

FAQ: Do SEO Checklists Work, and When Should You Update One?

A good seo checklist catches preventable mistakes, then gets out of the way. It improves your odds by removing blockers (noindex, messy snippet, unclear headings), but it cannot force rankings. Google still decides what to crawl, index, and rank based on how well your page satisfies the query and how it compares to alternatives. Google explains the basics in Google Search Central.

Quick Answers to Common Checklist Questions

Do SEO checklists work? Yes, as QA. Use an on-page SEO checklist to make the topic obvious, the snippet accurate, and the page easy to scan. Use a technical checklist to prevent “published but invisible” problems like blocked crawling or accidental noindex.
Is there a keyword density target? No. Write to satisfy one intent, then edit for clarity. Use the primary term where it fits naturally (title, H1, early answer), and use related terms where they help precision. Do not count percentages.
How many internal links should I add? Add as many as a reader would click to keep moving. Link to the next-step page (pricing, setup guide, glossary), and link to supporting pages when you reference a concept you already covered elsewhere. Stop when links start to feel like a navigation menu stuffed into a paragraph.
When should I update a checklist or an article? Update when reality changes: the SERP shifts (new formats, different intent), your screenshots no longer match the product, your claims need fresher sources, or Search Console shows the page losing queries you still want. For checklists, update when Google documentation changes or your CMS changes how it outputs titles, canonicals, or sitemaps.
How do I adapt this blog post SEO checklist to a niche, like “electrician SEO checklist”? Keep the same framework, then swap the intent and examples. In Google Search Console, use Performance to see the exact queries people use (for example, “emergency electrician near me,” “electrical panel upgrade”). Build pages that match those intents: service pages, location pages, and proof items (licenses, service area, reviews) that matter for that trade. The checks stay the same, but the “only you can add” content changes.

If you treat a checklist like a ranking recipe, you will miss the real work: matching intent, adding something original, and backing up claims.

If You Want This Done for You, Balzac Can Write and Publish It

Most teams fail on SEO because they skip the hard parts you cannot “checkbox” into existence: tight intent, real differentiation, and clean execution across content, CMS, and Search Console. If you want the outcome without owning every step, you can hand the workflow to Balzac.

Balzac is an AI SEO agent that researches topics, writes articles, and publishes them to WordPress, Webflow, Wix, GoHighLevel, or any site via a webhook. It also connects to Google Search Console and tracks each article through practical states like live, indexed, ranking, and cited by AI. That means the routine in this seo checklist before publishing becomes a consistent system instead of a recurring calendar task.

If you want to try it, Balzac includes 3 free articles with no card. Use those to validate the full loop end-to-end: pick a topic, publish, request indexing in Search Console, then see what queries and impressions show up over time.

Your next step is simple: run this checklist on your next post, then decide what you want to keep doing manually and what you want to automate.

Balzac writes and publishes articles and handles many of these checks for you, with 3 free articles to try.

Sources

Complete SEO Checklist - GrowthVector.io