Question 1

How many posts per month can a small team realistically produce without losing quality?

Accepted Answer

For a team of 1–2 people responsible for writing and review: 4–8 posts per month with genuine original inputs, brief-driven differentiation, and a meaningful review pass is realistic. Beyond that, something has to give — usually the original inputs (briefing gets skipped) or the review pass (sameness goes unchecked). The right question isn't "how many can we produce?" but "at what volume can we consistently maintain the three elements that prevent sameness?" That varies by team, topic complexity, and process maturity. It's better to publish 4 genuinely differentiated articles than 12 pieces of scaled content.

Question 2

Does Google actually penalise AI content?

Accepted Answer

Google has been explicit: it doesn't penalise AI content per se — it penalises content that's unhelpful, lacks original value, or was created primarily to rank rather than to serve users. The mechanism isn't "is this AI?" — it's "does this help?" AI content that contains original data, real expertise, and a genuine point of view can rank well. AI content that's templated, generic, and indistinguishable from the dozens of other articles covering the same ground is subject to the same demotion as any other low-quality content. The label matters less than the output. The 2024 core update specifically targeted "scaled content abuse" — scale was the problem, not the tool used.

Question 3

What's the fastest way to add original perspective to a content piece?

Accepted Answer

The fastest paths: (1) Add a "what we've seen in practice" section with a specific observation from your own client work or experience — even one real example changes the tone of an entire article. (2) Take a clear position in the introduction: "most guides recommend X, but in our experience Y works better because..." — this sets up a differentiated article from the first paragraph. (3) Add a section that addresses the common mistake or the thing most articles get wrong — this is original by construction, because it requires you to have read the existing content and formed a view of its shortcomings. Any of these takes 15–30 minutes to add to a draft and materially changes the quality signal.

Question 4

Should we use subject matter experts for every article?

Accepted Answer

Not necessarily for every article — but the most important pieces in each cluster benefit significantly from SME input. The practical model: use SME input for pillar pages (where depth and authority matter most) and for any article where your team doesn't have direct experience of the topic. For spokes on topics where the content team has firsthand experience, that experience can be the original input without additional SME interviews. The goal isn't always to have an expert write or review — it's to have original information in the brief before the writing starts. A 30-minute interview with a practitioner who has done the thing the article describes produces more original material than hours of research into existing articles.

Question 5

How do I know if our existing content library already has scaled sameness?

Accepted Answer

Read five of your articles back to back and ask whether you could swap a paragraph from one into another without anyone noticing — if the answer is yes across most of your library, you likely have a sameness problem. A more concrete check: take your top 10 traffic-driving pages and search their core claims; if everything stated could be found, in roughly the same form, in the first page of search results for the same query, the content isn't differentiated. This audit is worth doing before scaling further, since fixing the brief process matters more than producing more volume of the same kind of content.

Question 6

Is it worth slowing down publishing to fix a sameness problem?

Accepted Answer

Usually yes, if the alternative is continuing to add volume to a library that isn't differentiating. Pausing new production for a few weeks to fix the brief process — building in original-input requirements and a differentiation review — costs less than continuing to publish generic content that risks demotion later and needs the same fix applied retroactively to dozens more pages. The fix is a process change, not a one-time content rewrite, so it's a short-term slowdown for a permanent improvement rather than an ongoing tax on every future piece.

content quality

How to Scale Content Without Becoming ‘Scaled Sameness’

AI-Assisted Content Workflows That Don’t Tank Quality