Will Google Penalise AI-Written Posts? How Revnu Checks Them

Google ranks helpful, accurate posts however they were written, and that includes posts written with AI. Its published guidance says it ranks content on whether it's helpful and reliable, however it was made. What it acts against is pages churned out in bulk to game rankings, with little value for the reader, whether a person or a tool wrote them.

So the real question is whether each post answers a real question accurately. That's also what gets a post cited by ChatGPT, Perplexity, Gemini and Google AI Overviews: clear, specific, sourced answers. See how AI engines choose what to cite. This page covers what Revnu does on every post to make that true, the quality bar each post clears, and how to read every post yourself before it goes live.

What Google says about AI-written content

Three Google Search Central pages cover it:

• "Google Search's guidance about AI-generated content" (February 2023). Google rewards high-quality content however it's produced.

• "Creating helpful, reliable, people-first content". The questions Google asks of any page: is it accurate, original and written for the reader rather than for search engines.

• Spam policies, "Scaled content abuse". Producing many pages mainly to manipulate rankings, with little value, breaks the policy no matter how the pages were made. Generative AI is the first example it gives.

Rankings are Google's call. Revnu controls what goes into each post and how fast posts go out.

How Revnu picks what to write

Revnu writes on its own every day, on topics tied to a real signal: the buyer questions AI answers leave you out of, the searches Google already shows you for, the keywords you want and the gaps in your competitors' coverage. A topic you name always comes first. When a page of yours already covers a question but doesn't answer it, Revnu rewrites that page instead of adding another, so every post covers new ground.

Every draft carries a short Why This Post note in the editor, naming the signal it came from, so you can judge the topic before you approve it.

How each post is written and fact-checked

Revnu writes every post from your Product Facts and your own best writing, in your voice, and its own multi-stage fact-check verifies every claim before anything can publish. Claims about your product must match your Product Facts. Facts about the outside world must match a source Revnu read. Sources must be live pages, and nothing on your Never Say list gets through. Where a post takes a position, it argues for how your business solves the problem, never against tools like yours or the category you sell in.

Before your first post, Revnu writes Product Facts from your own site: what your product does, its features, integrations and pricing. You can read and edit them in Settings > Memory > Product Facts.

Each post's Fact-check panel in Visibility > Posts shows what was checked and what changed.

The quality bar every post clears

Revnu holds back anything that falls short, including:

• A post that failed the fact-check. If the check found a claim that contradicted the facts, or a correction didn't apply, the post is marked Failed and doesn't publish on its own. Revnu usually fixes it or writes a replacement before it asks you anything. If a Failed post sits there, ask Revnu to rewrite it.

• A post that names anything on your Never Say list. It's stopped the same way, and Revnu rewrites the wording before it asks you to approve it.

• Made-up proof. No invented customers, quotes, hours saved, ROI, rankings or market share. A customer named in your account isn't permission to use them in a post.

• Ranked lists that crown you. Comparison posts are written from each competitor's current public documentation and compare how things work. Revnu doesn't publish "top 10" lists with invented winners or rankings that put you first.

• Private sources. Nothing from your chats, calls or internal tickets is cited.

• More than Google can index. Revnu starts at one post a day and goes up to five as Google indexes your posts faster, so Google keeps up with every post. Ask for fewer and it slows down straight away. Ask for more and it steps up one post a day each week.

When no public source covers a claim, the post can still go out. In a held post, Revnu points those claims out so you can check them before approving.

Teach Revnu your facts and your rules

Two sections in Settings > Memory steer every post:

• Product Facts is the source for every claim about your product. Fix a wrong fact here once and every later post uses the correction. Short, literal lines work best, for example "Minimum plan: 5 seats" or "We no longer sell the desktop app".

• Never Say is a list of things that must never appear in a post: a claim, a word, a retired product, a competitor's name. One per line.

Enlarge

Or tell Revnu in chat, and it records the fact and fixes the live posts that carry the old claim:

We don't offer a free plan any more. Remember that, and fix any live post that says we do.

Control what gets published covers editing live posts.

Read every post before it goes live

On Pro, Blog Posts is set to Just Do It by default. A finished post publishes as soon as it passes the checks. To read every post first:

1. 1

   Open your approval settings

   Open Settings and choose the Agent tab. Find What Needs Your Approval.

2. 2

   Set Blog Posts to Ask Me First

   Switch the Blog Posts row off, so it reads Ask Me First.

   Enlarge

3. 3

   Approve each post when it's ready

   Open the post and click Approve & Publish. Nothing publishes until you do.

Drafts already waiting lose their publish time. Revnu keeps writing at its usual pace, and each post waits for you. The same setting covers Revnu's edits to posts that are already live. Switch it back to Just Do It whenever you like.