The Pre-Publish SEO Checklist for AI-Written Articles

Run through this before you hit publish: a 50-60 character title tag, a meta description under 160 characters, one clean heading hierarchy, alt text on every image, 3-7 internal links, Core Web Vitals inside Google's thresholds (LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1, per web.dev), and zero unverified stats. That's the short version of the seo checklist before publishing a blog post — the long version, with the reasoning and sources behind each item, is below.

Photo: faith goble · BY

Why You Need an SEO Checklist Before Publishing a Blog Post

AI drafting tools made writing the fast part. Checking the draft is now the bottleneck, and it's the part that actually determines whether the post ranks. A checklist exists so you're not relying on memory to catch the same five mistakes every time — a missing meta description, an H2 that skips to H4, an image with no alt text, a claim with no source.

Google has been explicit that it doesn't grade content differently because AI wrote it. Its spam policies apply "regardless of how content is created" and call out "using generative AI tools or other similar tools to generate many pages without adding value for users" as the actual violation — not automation itself. In other words: the checklist isn't about proving a human touched the post. It's about proving the post is worth ranking.

The 17-Point Checklist at a Glance

The rest of this article walks through why each row matters and what Google (not a rank-tracking tool) actually says about it.

On-Page Basics: Title, Meta Description, URL

Google's own SEO Starter Guide keeps its title tag advice loose: a title should be "unique to the page, clear and concise, and accurately describes the contents of the page." It doesn't set a character limit. The practical target comes from the SERP itself: Backlinko's on-page SEO guide recommends keeping titles to 50-60 characters (about 600 pixels) so Google doesn't truncate or rewrite them in the results, and meta descriptions under roughly 160 characters (120 on mobile) so the full sentence displays.

Practically: write the title for the human scanning ten blue links, not for an algorithm. Put the keyword near the front, skip the clickbait brackets, and make sure it's not a duplicate of another post's title on your own site — Google's guide flags "unique to the page" for a reason, since duplicate titles across a blog confuse which page should rank for what.

For meta descriptions, Google's guidance is that they should be "short, unique to one particular page, and includes the most relevant points of the page." Google doesn't use the meta description as a ranking signal, but it's still the reader's first impression in the results — and it's the one field a lot of publishing checklists skip entirely because a CMS will auto-generate something if you leave it blank.

URL slugs get the same treatment: Google recommends "descriptive URLs" over random identifiers. /blog/seo-checklist-before-publishing beats /blog/post-4471.

Content Quality: What the Checklist Can't Skip

A checklist that only checks formatting will still let a weak post through. Google's Starter Guide asks for content that's "easy-to-read and well organized," "unique," "up-to-date," and above all "helpful, reliable, and people-first" — and that framing (E-E-A-T: experience, expertise, authoritativeness, trustworthiness) is what its human quality raters are trained to look for, AI-written or not.

The two checks that catch the most problems before publish:

Every number has a live source. If a draft cites a statistic, a price, or a study name, open the source page and confirm the number is actually there before it ships. This is the single highest-leverage check on the list — a wrong or made-up stat is the kind of error that gets a post flagged manually, and it undermines the reader's trust in everything else on the page. We wrote about the mechanics of this in our piece on whether AI-generated content is bad for SEO — the short version is that Google doesn't penalize AI assistance, but it does penalize inaccuracy and low effort, and those two things travel together more often in AI drafts than in edited ones.

Word count matches intent, not a template. There's no universal "ideal" length. A checklist item is better phrased as: does this post cover what the top-ranking pages for this query already cover, at the depth they cover it? A 600-word post competing against 2,000-word guides is thin; a 3,000-word post answering a question that needs three sentences is padding.

Images: Alt Text and File Size

Google's guidance on alt text is simple: it should be "a short, but descriptive piece of text that explains the relationship between the image and your content." That's an accessibility requirement first and an SEO signal second — screen readers depend on it, and Google Images indexing depends on it too.

The file-size half of this check gets skipped constantly. An uncompressed 4MB hero image is one of the fastest ways to blow your Largest Contentful Paint budget (more on that threshold below). Compress before upload, not after a PageSpeed Insights report tells you to.

Internal and External Links

Google recommends "appropriate anchor text" on internal links "so users and search engines can easily understand what your linked pages contain before they visit." A checklist target of 3-7 internal links per post gives you room to connect a new article to the cluster it belongs to without turning every third word into a hyperlink. We go deeper on the system behind this in our internal linking guide — the short rule is that every link should be one a reader would actually click, not one placed to hit a quota.

External links matter for a reason that's easy to forget mid-deadline: they're what let a reader (or an AI answer engine) verify your claims without leaving the page. Link the primary source — the vendor's docs, the association's report, the government dataset — not a blog that summarized it. A post that never links outward reads as unverifiable, whether or not that's fair.

Technical Checks: Core Web Vitals, Canonical Tags, Structured Data

Three numbers to check in Google Search Console or PageSpeed Insights before a post goes live, per web.dev's Core Web Vitals documentation:

These are measured at the 75th percentile of real page loads, separately for mobile and desktop — so a fast desktop score doesn't guarantee a passing mobile score. A single blog post rarely tanks a site's Core Web Vitals on its own, but an unoptimized hero image or an embedded widget can push an otherwise-healthy page over the LCP threshold.

Canonical tags matter mainly for posts that get syndicated or exist at more than one URL (a /blog/ version and an AMP or print version, for instance) — point the canonical at the version you want indexed.

Structured data is worth the ten minutes it takes to add, in JSON-LD, per Google's own numbers: Rotten Tomatoes saw a 25% higher click-through rate on pages enhanced with structured data, Food Network reported a 35% increase in visits after converting most of its pages, and Nestlé measured an 82% higher click-through rate on pages with rich results. Article schema is the baseline for a blog post; whether it produces a visible rich result depends on the query and result type Google decides to show.

One current exception worth knowing: FAQ schema stopped producing rich results in Google Search as of May 7, 2026. Google's own documentation confirms it's "dropping the FAQ search appearance, rich result report, and support in the Rich results test in June 2026," with Search Console API support ending in August 2026, according to Search Engine Journal's coverage. That doesn't mean drop the FAQ section — it means stop adding it for the rich snippet. See the next section for why it still belongs in the checklist.

The GEO Check: Write for AI Answers, Not Just Rankings

The newest item on any 2026 checklist isn't a Google ranking factor at all — it's whether ChatGPT, Perplexity, or Google's AI Overviews can lift a paragraph out of your post and use it as a direct answer. That requires the same discipline a good editor already enforces, applied more strictly:

• Answer the query in the first two sentences, with the number or verdict stated plainly, so the paragraph works as a standalone quote.
• Define entities on first mention — don't assume the reader (or the model summarizing your page) already knows what a term means.
• Keep a FAQ section, even without the schema markup. AI answer engines pull FAQ-formatted Q&A directly from page content, not just from structured data, which is why the format still earns its place on the page. We cover the mechanics of getting cited this way in our guide to getting cited by ChatGPT, Perplexity, and AI Overviews, and in our breakdown of how AI Overviews are changing blog traffic.

This is also where the same fact-checking discipline from the content-quality section pays off twice: an AI Overview that cites your post is repeating your numbers verbatim to someone who never visits your site. If a stat is wrong, you don't get a chance to correct it in the comments. Our note on AI slop detection and what platforms are watching for covers the flip side of this — how thin, unsourced AI content gets flagged, which is exactly what a real checklist prevents.

Who's Actually Running This Checklist

For a solo founder or a two-person team, running 17 checks by hand before every post is realistic for the first five or six posts and then quietly stops happening. That's usually where a technical SEO checklist for a new site and a per-post checklist like this one diverge in practice — the site-wide technical items get set up once, but the per-post items need to survive every single publish, including the ones done at 11pm before a deadline.

Full disclosure: we build a tool for this. Rankody runs the research, writes the draft with sourced citations, and checks most of this list automatically — title length, meta description, internal links, alt text, structured data — before a human ever approves it. It doesn't replace judgment on the content-quality checks (a person still decides if the post is actually good), but it removes the formatting checks that are easy to forget under deadline pressure. See Rankody's pricing if that's useful, and if not, the checklist above works fine as a manual process too.

FAQ

Do I need to run all 17 checks on every single post? Most of them, yes — title, meta description, alt text, and internal links take under two minutes to verify and catch the errors that are easiest to miss. The content-quality and fact-checking items take longer but matter more; don't skip those to save time.

Does AI-generated content need a different checklist than human-written content? No. Google's spam policies apply "regardless of how content is created," so the bar is the same either way — the checklist should be stricter about fact-checking AI drafts in practice, since unverified stats are a more common failure mode in AI output than in edited human writing.

Is there an official character limit for title tags? No, Google's own guidance only asks for titles to be clear, concise, and unique to the page — it doesn't set a character count. The practical reason to stay near 50-60 characters is still valid: it keeps Google from truncating or rewriting your title in the search results.

Should I still add FAQ schema if it doesn't create a rich result anymore? Keep the FAQ section in your content regardless. Google stopped showing FAQ rich results in search as of May 2026, but AI answer engines still pull well-formatted Q&A directly from the page text, so the format still earns placements you can't see in a rank tracker.

What's the single most important check on this list? Verifying every stat, price, and named claim against a live source before publishing. It's the check most likely to be skipped under deadline pressure, and the one most likely to get a post penalized or simply distrusted if it's wrong.

Run the checklist before you publish, not after Search Console flags the problem three weeks later.

Rankody researches your market, writes sourced long-form articles, and publishes on schedule — every piece waits for your approval first. Three articles free, no card. Analyze my site