What should be on a pre-publish blog post checklist?

A solid pre-publish checklist covers four categories totaling 25-35 items: editorial (grammar, fact-checking, tone, brand voice consistency), SEO (title tag, meta description, primary keyword usage, internal linking, schema markup), technical (broken link check, image alt text, page speed, mobile rendering), and distribution (social cards, email newsletter snippet, sharing utm parameters). Wirecutter's internal pre-publish process has 47 items; The Verge's has 31; HubSpot's public checklist has 26. The optimal count depends on your team — fewer items risks missed quality issues, too many items get rushed through. Rather than maximizing items, prioritize the ones that catch real errors. The 2025 Content Operations Benchmark from CMI found teams with 20-30 item checklists had 67% lower post-publish issue rates than teams with no formal checklist, while teams with 50+ items had only marginal improvements over 30-item checklists. Build the checklist around the errors your specific publishing workflow tends to make.

How do I check for broken links before publishing?

Use a dedicated link checker — manual visual inspection misses 30-50% of broken links because they look fine in the editor but 404 in production. Free tools: W3C Link Checker (web-based, slow but free), Screaming Frog (free for under 500 URLs, paid above), Dr. Link Check (free with limits). Paid tools: Ahrefs Site Audit, Semrush Site Audit, both bundled in their $129-499/mo plans. For single-post checks, the easiest workflow is to copy your post into a Google Doc and use the Markup Health Check extension, or paste into Notion and use Notion AI to "verify all hyperlinks". For systematic monitoring of an entire blog, run Screaming Frog monthly on your sitemap and review the 4xx/5xx report. Common broken-link sources: links to sites that redirected without preserving paths, links to deleted pages on partner sites, mistyped URLs that look right in the editor, and amphtml links that point to mobile-only stale URLs.

What accessibility checks should I run before publishing?

At minimum: image alt text presence and quality (not "image1.jpg"), heading hierarchy (single H1, then H2/H3 cascade without skips), color contrast on text and CTAs (WCAG 2.1 AA: 4.5:1 for body text, 3:1 for large), keyboard navigability (every interactive element reachable via Tab), and screen reader semantic structure (proper landmarks: main, nav, footer). Tools: Axe DevTools (free Chrome extension, the industry standard), WAVE (web-based), Lighthouse (built into Chrome DevTools). The 2026 ADA Title III lawsuit count for inaccessible websites passed 4,200 in the U.S. — accessibility violations carry both legal and ethical risk. Beyond pre-publish checks, set up automated accessibility testing in CI (axe-core in playwright, jest-axe in unit tests) so issues are caught at deploy time rather than after publish. WebAIM's 2025 Million Top Websites Audit found 96% of homepages had detectable WCAG failures, with 72% related to low-contrast text and missing alt text — both completely preventable by checklist.

Should the publishing checklist include schema validation?

Yes — schema markup errors prevent rich SERP results and are silent failures (your page still renders, but Google strips your stars/price/breadcrumbs). Test every published page through Google's Rich Results Test (search.google.com/test/rich-results) which validates JSON-LD against current Google requirements. The 2025 update tightened many fields: Product schema now requires offers.url and offers.priceValidUntil for sales, Article schema requires datePublished AND dateModified in ISO 8601, FAQPage schema must have all questions visible on the page (not just in JSON-LD), Recipe schema requires totalTime in ISO 8601 duration format. Common pre-publish checklist items: validate JSON-LD parses, validate against schema.org current type definitions, validate Google Rich Results Test passes, check Search Console for warnings on similar pages from the past 30 days. Schema App ($25-300/mo), Yoast Premium, and RankMath Pro automate the validation; for hand-rolled JSON-LD, manual validation per post is the only option.

How do I QA images before publishing?

Image QA covers six dimensions: alt text (descriptive, not "image1.jpg"), file format (WebP for photos, SVG for logos/icons, PNG only for transparency), file size (under 200KB per image for blog posts; aggressive compression below 100KB for hero images), dimensions (max display size + 2x for retina, then progressive lazy-load), aspect ratio (consistent within a post, no random sizes), and licensing (verify usage rights, especially for stock photos and AI-generated images). Tools: TinyPNG (free, browser-based compression), Squoosh.app (free Google-built compression with format conversion), Cloudinary (paid CDN with automatic optimization). For AI-generated images: confirm your provider grants commercial use (Midjourney standard plan, DALL-E via ChatGPT, Stable Diffusion under various licenses) and disclose AI use per your content policy. Image SEO: optimize file names (linen-apron-cross-back.jpg, not IMG_4851.jpg), use the height/width attributes to prevent layout shift (Cumulative Layout Shift is a Core Web Vital), and add structured-data ImageObject if claiming primary image rights for AI overviews.

What's the difference between an SEO audit and a publishing checklist?

A publishing checklist is run per article before publish (5-15 minutes total). An SEO audit is run periodically across the entire site (1-4 hours, monthly or quarterly). The checklist catches per-page issues; the audit catches site-wide patterns. Both are needed. Per-page checklist items: keyword in title, meta description under 160 chars, schema valid, internal links to related posts, alt text on all images. Site-wide audit items: indexability across the site, sitemap completeness, broken backlinks, duplicate content patterns, mobile-vs-desktop content parity, page speed distribution, internal-link graph health. Tools that do both: Ahrefs ($129-499/mo, strong on backlinks and audit), Semrush ($129-499/mo, similar feature set), Screaming Frog ($259/year, technical SEO crawler), Sitebulb ($35-50/mo, technical SEO with explanations). For solo creators, monthly Screaming Frog crawl + per-post checklist covers 90% of SEO needs at minimal cost.

Should the checklist include social media preview cards?

Yes — the Open Graph and Twitter Card metadata controls how your post renders when shared on Facebook, LinkedIn, X/Twitter, Slack, Discord, iMessage. Misconfigured cards (missing image, wrong title, broken description) reduce social click-through by 40-60% per HubSpot's 2025 social referral benchmark. Per-post checklist items: og:title (60-65 chars), og:description (140-160 chars), og:image (1200×630px, under 5MB), twitter:card type ("summary_large_image" for blog posts), twitter:title, twitter:description, twitter:image. Test the rendering: paste your URL into the Facebook Sharing Debugger (developers.facebook.com/tools/debug), the LinkedIn Post Inspector, or X's Card Validator (deprecated since 2023, but Twitter cards still work). For consistent visual cards, generate them dynamically — Vercel OG Image, Cloudinary, or Bannerbear can produce branded social cards from each blog post's metadata at deploy time, eliminating the manual upload step.

How long should the publishing checklist take to complete?

For a single blog post, 8-15 minutes is the right range. Faster than 5 minutes means you're skipping items; slower than 20 minutes means the checklist is bloated or the post has a lot of content needing review. The Verge's editorial team self-reports 12 minutes per post; Wirecutter's deeper review averages 22 minutes per post (with separate fact-checking pass). For long-form content (>3,000 words) or content with multiple embedded media, expect 20-30 minutes. The trick to keeping checklist time bounded: automate everything that can be automated. Schema validation, link checking, accessibility testing, image compression, and meta tag presence can all run in CI/CD against the staging environment. The human checklist then only covers items requiring judgment: editorial quality, fact-checking, brand voice, distribution strategy. Teams that combine automation + judgment-only checklists report 4-6 minutes per post in 2025 surveys.

Should different content types have different checklists?

Yes. Long-form articles (>2,000 words) need fact-checking and source citation steps that aren't needed for short news updates. Product reviews need FTC disclosure and pros/cons schema markup. Tutorials need code-block syntax highlighting and downloadable file integrity. Press releases need AP-style validation and dateline format. Email newsletters need the same content + UTM parameters + send-time A/B test setup. Maintain a base 15-item checklist that applies to all content, then add 5-10 type-specific items per content category. The 2025 CMI Content Operations Benchmark found teams with type-differentiated checklists had 38% fewer post-publish issues than teams with a single unified checklist. Our generator supports this — provide the content type (blog post, product review, press release, email newsletter, tutorial) and it produces a tailored checklist instead of a generic one.

How do I validate page speed before publishing?

Run PageSpeed Insights (pagespeed.web.dev) on the staging URL or local preview before publishing, targeting 90+ on mobile. Core Web Vitals targets in 2026: LCP (Largest Contentful Paint) under 2.5s, INP (Interaction to Next Paint) under 200ms, CLS (Cumulative Layout Shift) under 0.1. Fail any of these and Google's ranking signal degrades, with an estimated 8-12% search-traffic penalty for "Needs Improvement" pages per Backlinko's 2025 study. Common pre-publish speed issues: large unoptimized images (resolved by WebP + lazy-load), embedded YouTube videos (resolved by lite-youtube-embed library), too many tracking scripts (resolved by single-tag manager via GTM), missing CDN caching (resolved by Cloudflare or hosting provider). Tools beyond PageSpeed Insights: WebPageTest (free, deeper waterfall), Lighthouse CI (automated in deploy pipeline), Calibre ($83-499/mo, monitoring + alerts). Set up a monthly speed-regression check across your top 50 traffic pages.

How does this compare to using Google Sheets or Notion templates?

Google Sheets and Notion templates work fine for fixed checklists you reuse manually. Limitations: they're generic (same checklist for blog posts, product reviews, and press releases), they don't reflect 2025-2026 best practices unless you maintain them, and they require manual updates when you add new content types or platforms. Our generator produces a tailored checklist per content piece based on your inputs (type, length, presence of media, target platforms), incorporating current SEO/accessibility/schema requirements. We don't replace your task management — paste the generated checklist into Notion, Linear, ClickUp, Asana, or whatever you actually use to track publish workflows. The output is markdown-formatted for easy paste-and-track. For teams already running well-tuned manual checklists, our tool is overkill; for teams without a checklist or with a stale one, the per-post tailoring catches issues a generic template misses.

What's the right way to handle a checklist failure?

Pre-publish checklist failures should always be fixed before publishing, not noted-and-published-anyway. The reason: failures compound. A broken link in one post becomes a broken link plus a missing alt text plus a malformed schema in three posts, and over months your site quality erodes invisibly. Track failures by category in a simple spreadsheet — what failed, why, who caught it. Patterns will emerge: "image alt text fails 40% of the time" means the writer process needs an alt-text-as-you-go habit. "Schema validation fails 25% of the time" means the dev process needs automated schema validation in CI. The 2025 Atlassian Content Workflow Survey found teams that reviewed checklist-failure patterns monthly had 73% fewer recurring issues than teams that just fixed-and-moved-on. The checklist isn't just a quality gate — it's a diagnostic for systemic process gaps that need fixing upstream.

Free Publishing Checklist Generator

Tailored pre-publish checklist for blog posts. SEO, accessibility, social, schema. Free, instant.

4.6on G2

4.8on Trustpilot

Used by 25,000+ marketers

What this tool does

Publishing Checklist Generator delivers fast, reliable results for tailored pre-publish checklist for blog posts. seo, accessibility, social, schem.

Designed to fit into your existing SEO and content workflow with no setup overhead.

How to use it

Five steps.

Pick your content type

Select blog post, product review, press release, tutorial, email newsletter, or landing page — drives type-specific checklist items.

Specify length and media

Indicate word count range, presence of images/video/code blocks, and target distribution platforms — adds items only relevant to your post.

Generate the checklist

Click Generate to receive 20-30 tailored items split across editorial, SEO, technical, and distribution categories.

Paste into your workflow tool

Copy the markdown output and paste into Notion, Linear, Asana, ClickUp, or Google Docs — wherever you actually track publish work.

Run per post and track failures

Run the checklist on every publish; log failures in a separate sheet to spot patterns and refine the checklist over time.

When teams use it

Six common workflows.

Solo blogger with no formal QA process

A solo content creator publishing 2-4 posts per week needs a 10-15 minute checklist that catches broken links, missing alt text, schema errors, and stale meta tags before publish — without adopting an enterprise content ops stack.

Marketing team coordinating multi-author content

A 4-8 person content team with multiple writers needs a shared pre-publish checklist enforced consistently regardless of who's on point, ensuring brand voice and quality are uniform across the publication.

Agency shipping client content at scale

A content agency publishing 60+ posts per month across 12 client accounts needs per-client tailored checklists (different brand voices, different schema needs, different distribution platforms) that scale without consuming senior editor hours.

Newsroom or news publication

A news team publishing breaking news under tight deadlines needs a 3-5 minute fast-publish checklist plus a 15-minute deeper-review checklist for evergreen content, with explicit fact-checking steps.

Product marketing publishing launch content

A product marketing team launching a new feature with blog post + email + social + landing page needs a coordinated checklist across all four assets, ensuring messaging consistency and proper UTM tracking before launch.

Compliance-heavy industries (finance, health)

A financial services or healthcare publisher with regulatory disclosure obligations needs a checklist that includes specific compliance review steps (SEC disclaimers, FDA-relevant claims, HIPAA-aware language) before publish.

Platform guides

Integrate with major platforms.

WordPress

Generate the checklist for "blog post" type.
Install Pre-Publish Checklist plugin or PublishPress Checklists ($79-249/year).
Import the generated items into the plugin's settings.
Configure required vs optional items; required items block publish until checked.
Train all authors on the workflow before rollout.

Notion

Generate the checklist as markdown.
Create a Notion template with the checklist as a nested checkbox list.
Save as a template in your content database.
New blog post pages instantiate the checklist automatically.
Track completion status across posts via filtered views.

Linear (engineering-style)

Generate the checklist.
Create a Linear template (project or issue level) with the items as sub-issues.
Each new content piece becomes a Linear project; checklist items become sub-tasks.
Use Linear's automation to require all items closed before "publish-ready" status.
Review checklist completion in monthly retrospectives.

Asana

Generate the checklist.
Create an Asana project template with the items as a section of subtasks.
New content pieces clone the template.
Use Asana custom fields to track per-item status (passed/failed/n-a).
Set rules to block "ready for publish" until all required items pass.

Google Docs / Sheets

Generate the checklist as markdown or table.
Paste into a Google Doc as a checkbox list, or a Sheet as a row-per-post tracker.
Share with editors; assign owners per item if multi-author.
Maintain a "checklist-failures" log over time to spot patterns.
Monthly review of failure log to update the checklist itself.

Grigora vs. alternatives

Side-by-side.

Capability	Publishing Checklist Generator	PublishPress	Notion Templates	Asana	Google Sheets
Free tier available	Yes — unlimited	Free with limits	Free template only	Free trial	Free
Tailored per content type	Yes	Limited	Manual	Yes	Manual
Markdown output for any tool	Yes	No	Yes	No	Yes
Automation-aware (CI vs manual)	In output notes	No	No	No	No
2025-2026 best-practice updates	Yes	Slow	Stale	Yes	Stale
Required vs optional flagging	In output notes	Yes (Pro)	Manual	Yes	Manual
Pricing for solo creator	Free	$79-249/yr	Free template	$49-149/mo	Free
Schema/SEO/a11y items in baseline	Yes	SEO only	Generic	Yes	Manual

Common errors and fixes

Eight issues users hit.

No checklist run at all

Cause: Solo creator publishing without any pre-publish QA process.

Fix: Adopt even a 10-item baseline checklist; the 2025 CMI benchmark found 67% lower post-publish issue rates with formal checklists.

Generic checklist for all content types

Cause: Used a single template for blog posts, product reviews, and press releases.

Fix: Tailor by type — product reviews need FTC disclosure, press releases need AP-style validation, tutorials need code-block QA.

Checklist items vague ("Check SEO")

Cause: Drafted in 5 minutes without specifics.

Fix: Replace vague items with specific, verifiable checks: "Title tag under 60 chars" not "Check SEO".

No automation for repeatable checks

Cause: Manually validating links, schema, and accessibility per post.

Fix: Move automatable checks (link checker, schema validator, axe-core a11y) into CI/CD; reserve human checklist for judgment items.

Schema validation skipped

Cause: Assumed Yoast/RankMath handled it correctly without verifying.

Fix: Run Google Rich Results Test on every published page; plugins generate but don't guarantee current Google requirements.

Open Graph image missing or broken

Cause: Default theme didn't auto-set og:image; per-post upload skipped.

Fix: Add og:image to every post (1200×630px, under 5MB); use Vercel OG or Bannerbear for auto-generated cards from post metadata.

Heading hierarchy skips levels

Cause: Used H1, H3, H4 without H2 because of styling preference.

Fix: Use sequential H1 > H2 > H3; style separately. Skipped levels break screen-reader navigation and confuse Google's content extraction.

Page speed below 90 on mobile

Cause: Large hero image, embedded YouTube, multiple tracking scripts.

Fix: Compress hero to WebP under 100KB, use lite-youtube-embed, consolidate tracking via GTM; target 90+ Lighthouse mobile.

Original data

2026 study.

67%

Reduction in post-publish issues with formal checklist (CMI 2025)

12 min

Average pre-publish checklist time per post (Verge)

8-12%

Search-traffic penalty for failing Core Web Vitals

96%

Homepages with detectable WCAG failures (WebAIM 2025)

Frequently asked questions

Twelve answers.

Related free tools

Other utilities.

Try Publishing Checklist Generator now

Free, unlimited, no signup.

Try the Tool