Stop Publishing “Meh” Pages: A Content QA System

If you publish a lot of content, you already know the feeling.

You hit publish, you feel productive for like 11 seconds, then you open the page and it is just… fine. Not bad. Not great. Not something you would actually share with a friend.

A “meh” page.

And the worst part is, “meh” is expensive. It costs you crawl budget, internal link equity, editorial time, and trust. It clogs your site with stuff that kind of targets a keyword but does not really deserve to rank. Or it ranks and nobody clicks. Or they click and bounce because the page feels thin.

So this is a simple content QA system you can actually run. Not a theoretical checklist that sounds good in a Notion template. A real workflow you can use before you publish, and again after the page has data.

This is also where tools like SEO.software fit nicely, because the whole point is to make QA repeatable. Not heroic. Not dependent on one senior editor being in a good mood that day.

What a “meh” page looks like (and why it keeps happening)

Most “meh” pages share a few traits:

• The intro is vague. It does not commit to what you will learn or what you should do next.
• The structure is generic. You can tell the outline was pulled from the same top 10 SERP pattern.
• The page answers the keyword, but not the intent. Or it answers intent A while Google is rewarding intent B.
• It has no lived in details. No examples, no numbers, no screenshots, no opinions, no constraints.
• The on page basics are technically present, but not useful.

And if you are using AI in your workflow, the risk goes up. Raw model output tends to sound confident and empty at the same time. If that sounds familiar, you will like this piece: Stop “sloppypasta”: why raw LLM output tanks quality.

The fix is not “write more.” The fix is a QA system that forces the page to prove it deserves to exist.

The Content QA System (two gates, one score)

Here’s the framework:

Gate 1: Pre publish QA (does this page deserve to go live?)

This is about clarity, usefulness, uniqueness, and basic SEO correctness.

Gate 2: Post publish QA (did this page earn its spot?)

This is about performance signals, upgrades, and decisions: improve, merge, or prune.

To make it practical, we will use a simple scoring method:

• Green: good to publish as is.
• Yellow: publish only if you fix the flagged items.
• Red: do not publish. Yet.

You can do this in a doc, a spreadsheet, or inside your content workflow tool. If your team is already building repeatable ops, this kind of structure pairs well with an agile content structure for SEO teams, because it turns “quality” into something you can actually ship in sprints.

Gate 1: Pre publish QA (the 12 checks)

1) The page has a real job to do

Write one sentence:

“What is the job of this page?”

Not “rank for keyword X.” The job. Examples:

• Help a founder choose between two approaches.
• Give a step by step they can follow today.
• Make a buyer feel safe enough to start a trial.

If you cannot define the job, the page will drift. And drift creates filler.

2) The search intent is matched, not guessed

Before you edit the draft, scan the SERP and answer:

• Are the top results mostly guides, lists, tools, templates, comparisons, or product pages?
• Are they short and punchy or long and thorough?
• Are they beginner or advanced?

If your page is “ultimate guide” but the SERP is dominated by quick checklists, you are fighting gravity.

This matters even more now that modern SERPs steal clicks with AI answers, snippets, and SERP features. You want to optimize for being the chosen result, not just a ranked result. Related read: Modern SERPs are stealing clicks: optimize content that ranks and gets clicked.

3) The opening earns the scroll

Your first 8 to 12 lines should do three things:

• Say who this is for.
• Say what outcome they get.
• Say what you will cover, in plain language.

If your intro begins with “In today’s digital landscape…” you already know.

4) The page has “information gain”

This is the big one. Ask:

“What is in this page that would not be obvious if I read three other articles?”

Information gain can be:

• a mini framework
• a real example
• a template
• a POV (with reasoning)
• a specific process you actually run

If you are using AI, this is where you force originality. This framework helps: How to make AI content original (SEO framework).

5) Structure is skimmable, not just “SEO formatted”

A good structure is not H2 spam. It is a path.

Quick check:

• Every H2 should be a question the reader actually has, or a step they must do.
• Every section should end with a takeaway, not trail off.

If you want a cleaner upstream input, you can also start from a tight brief. Here’s a solid reference: SEO content brief template (example).

6) Claims are backed by something

“Backed” can be data, a source, a screenshot, a real example, or a clear limitation.

If you say “internal linking improves rankings,” show:

• a simple method
• what to link
• how many links
• what anchor text patterns to avoid

Speaking of which, internal links are one of the easiest places to be “meh.” Too many sites sprinkle random links and call it strategy. Use a system: Internal linking: a simple system for content sites.

7) E-E-A-T is visible on the page

Not as a badge. As evidence.

• Who wrote it and why should I believe them?
• Are there specifics that suggest experience?
• Is it updated?
• Does it cite credible references when needed?

A practical checklist here helps: E-E-A-T content checklist for expert pages that rank.

8) On page SEO is clean (but not robotic)

This is where “meh” pages often over optimize. Or forget basics.

Quick pass:

• Title tag is specific and not clickbait.
• H1 matches the promise.
• Subheads include related terms naturally.
• Images have a reason to exist.
• The page answers the main question early, then expands.

If you need a structured review, use a checklist like this: SEO content optimization checklist.

9) UX signals are respected

If the page is unpleasant to read, it will not perform. Even if it ranks.

Look for:

• long paragraphs that should be split
• walls of bullets with no explanation
• tables with no interpretation
• missing jump links on long pages
• no clear next step

Here’s a good UX oriented QA list: UX signals that boost SEO (content checklist).

10) The page is not duplicating something you already published

This is silent “meh” poison. Cannibalization.

Before publishing, search your site for the topic and ask:

• Do we already have a page that could be expanded instead?
• Should this be a section inside an existing guide?
• Are we creating two mediocre pages instead of one great page?

Later, in Gate 2, you will make harder calls. There is a whole process for that: SEO content pruning: delete, update, merge.

11) It passes the “human edit” test

Read it out loud. Seriously. You will hear the fake smoothness.

Fix:

• repeated phrasing
• generic transitions
• over explained basics
• sections that say nothing new

If you want your team to level up here, not just “edit for grammar,” this helps: Content writing skills that improve SEO rankings.

12) The page has a clear next step

This is where you can be subtle and still effective.

If the article mentions systems and automation, a natural next step is:

• “Run this QA checklist manually.”
• Or use a workflow that bakes QA into production.

If you are already publishing at scale, this is where SEO.software is worth a look. It is built around research, writing, optimization, and publishing with automation, but you still keep control. The point is not to publish more “meh.” It is to publish faster without lowering standards.

A simple scoring sheet (copy this)

Give each item a 0, 1, or 2.

• 0 = missing
• 1 = okay but weak
• 2 = strong

Total possible: 24.

• 20 to 24: Green, publish.
• 15 to 19: Yellow, fix the 0s first, then publish.
• 0 to 14: Red, do not publish yet.

This avoids endless debates. And it trains writers over time because they can see exactly where the page is failing.

Gate 2: Post publish QA (the 30 day reality check)

A “meh” page can look great on publish day. Then it flatlines.

So you need a second gate. I like doing this at 14 days (light pass) and 30 to 45 days (real pass), depending on crawl frequency and site size.

Here’s what to look at.

1) Is the page getting impressions but no clicks?

This usually means:

• title and meta are weak
• you are ranking for the wrong intent
• SERP features are eating the click

Fix: rewrite the title to match the actual promise, add specificity, and make sure the first screen delivers fast.

2) Is it getting clicks but people bounce?

Usually:

• intro does not match the title
• the page takes too long to get to the answer
• formatting is exhausting
• the content feels generic once they land

Fix: tighten the opening, add a quick answer block, improve examples, and clean layout.

3) Is it not ranking at all?

Then you need to diagnose:

• keyword was too competitive
• page is cannibalized
• internal links are weak
• the content does not cover the topic deeply enough

This is where an actual content audit view helps. You can run audits and spot quick wins, thin content, and underlinked pages. Related: SEO content audit tools for quick wins and the platform page for the built in audit: Content audit.

4) Decide: refresh, merge, or prune

Do not “just update it” as a habit. Pick an action.

• Refresh if the page has traction but needs better intent match or depth. Use: Content refresh checklist to optimize old posts for higher rankings.
• Merge if you have multiple pages targeting the same cluster and none are strong.
• Prune if it has no traction, no links, and no strategic value.

And yes, this is where content velocity can hurt you. Publishing a lot of average pages is not a flex. It is debt. More on that tradeoff: Content velocity vs quality in SEO.

The part people avoid: QA for AI assisted content

If you use AI to draft, you need one extra rule:

Never QA the words first. QA the thinking.

Because AI can produce a clean paragraph that says absolutely nothing. So you review:

• is there a unique angle?
• are there real constraints and steps?
• are we just paraphrasing competitors?

Also, do not over obsess about “will Google detect AI.” The bigger problem is low value content. Still, if this is a concern for your team, here is a sane overview: Google detect AI content signals.

And if you are automating content creation, you need to be honest about where it works and where it backfires. This is worth reading before you scale: Content writing automation: when it works, when it backfires.

How SEO.software fits into this (without turning QA into more work)

A good QA system fails when it is too manual. People skip it when they are busy, and they are always busy.

So the goal is:

• standardize the checklist
• make it part of the workflow
• reduce the time between draft and publish without lowering quality

That is basically the positioning of SEO.software. It helps you research and generate content, optimize it with on page checks, add internal links, and publish to your CMS. But the real win is you can make QA a repeated step inside that pipeline.

If you want to see what an end to end process looks like, this is a good reference: An AI SEO content workflow that ranks. And if you are comparing tools and features for optimization, here: AI SEO tools for content optimization.

A quick “minimum standard” before you ever publish again

If you want a simple rule starting tomorrow, use this minimum bar:

1. The intro makes a specific promise.
2. The page includes at least one original element (framework, template, example, data, or POV).
3. The structure is skimmable and ends with clear takeaways.
4. On page SEO basics are correct, without stuffing.
5. Internal links are intentional, not random.
6. There is a clear next step.

If you want a checklist you can hand to a writer today, this is a good one to adapt: SEO friendly content checklist (example).

And then just run Gate 2 in 30 days. No excuses. Even if it is painful. Especially if it is painful.

Wrap up

“Meh” pages are not neutral. They are a slow leak.

A content QA system fixes that by making quality measurable and repeatable. You stop publishing because you are behind schedule, and start publishing because the page earned it.

If you are building a content engine and want the workflow side to be easier, you can check out SEO.software at seo.software. Connect your domain, generate a strategy, and build QA directly into how you research, write, optimize, and publish. That is the whole game. Consistency.