In short: Google now explicitly warns against a fake author, meaning invented names, AI-generated headshots and made-up credentials on bylines. Audit your bylines this week so no page carries a fake author, and fix any thin author pages.
Table of Contents
On October 1, Google quietly added one paragraph to its “Creating helpful, reliable, people-first content” guidance page. It wasn’t there in the version from June 8. The new text reads: “Avoid using deceptive authorship information. Fabricating creator profiles (such as by using AI-generated headshots, made-up names, or false credentials to make content appear as if it was written by human experts) is a form of deception.” Google goes on to say that kind of deception “makes a page untrustworthy to both users and our automated quality systems, and is a signal of a low-quality page.”
That’s a narrow, specific line in a long guidance document, and most of the coverage this week has stopped at reporting that it exists. The more useful question for anyone running a small business blog is what to go check on your own site before this becomes a ranking problem rather than a policy footnote.
Fake Author Signals Targeted by Google Policy
Google explicitly flags three specific patterns of deceptive authorship in its updated guidance:
- AI-generated headshots: Using synthetic or artificial facial images to stand in for a real author photo.
- Made-up author names: Inventing completely fictional individuals for bylines.
- False credentials: Claiming professional expertise or qualifications that do not exist to imply human authority.
Notice what’s not on that list. A byline that says “AllCloudHost Editorial Team” isn’t deceptive if it’s honest about being a team voice rather than a specific person. A guest contributor using their real name and real background isn’t affected at all. The guidance targets fabrication specifically: a stock photo or AI render presented as “written by Jane Carter, Senior SEO Strategist” when no such person exists, or when “Jane” didn’t write the piece and has no real claim to the credential attached to her name.
This sits alongside language Google already uses in its Search Quality Rater Guidelines, so it’s not a new concept to the raters who’ve been scoring pages against E-E-A-T criteria for a while. What changed is that it’s now explicit in the public-facing guidance rather than only in the internal document raters work from.
The 3-Step Fake Author Audit for Your Website
Pull up every post on your site that has an author byline and ask three questions about each one.
- Step 1: Verify the author photo. Check whether the image is a genuine photograph of the person whose name is attached, or if it is a stock image, a generic avatar, or an AI-generated rendering. If you don’t know, that’s itself a sign nobody on your team has checked in a while.
- Step 2: Confirm real human identity. Verify whether the name corresponds to a real person who had a tangible hand in creating the content. Placeholder names left over from theme templates or invented names used to make thin content operations look staffed both violate this principle.
- Step 3: Validate professional credentials. Audit any listed titles, certifications, or backgrounds. A “Certified Hosting Specialist” label attached to a made-up bio is a primary false-credential signal, even if the surrounding content is accurate.
None of this requires new tooling. It requires someone opening the author archive page on your own CMS and looking at it the way a skeptical reader, or a Google rater, would.
A concrete before-and-after helps. “Written by Alex Morgan, Chief Hosting Strategist with 20 years of enterprise infrastructure experience,” attached to a generated headshot and a name nobody on the team recognizes, is exactly the fabrication Google is describing. “Written by the AllCloudHost support team, drawing on the migration and uptime issues we handle for customers every week,” with no invented individual and no invented credential, says something true and is arguably more specific and more trustworthy for a reader trying to judge whether the advice is grounded in real experience. The second version doesn’t claim a person who doesn’t exist; it claims something the business can actually back up.
How WordPress Sites End Up With a Fake Author Problem by Accident
Most small sites don’t set out to fabricate an author. It happens by default. A theme ships with a sample “Admin” or “Editor” user and a generic stock headshot in its demo content, and nobody swaps it out before launch. A freelance writer is onboarded under a placeholder account called “Content Team” that the agency never renames. A plugin that auto-generates author bio boxes pulls a royalty-free photo because no real photo was uploaded to that user’s profile. None of these started as deception, but they land in exactly the category Google is now calling out, and they’re worth checking for specifically because they’re invisible to whoever built the site and easy for a visitor, or a rater, to spot.
If your site runs on multiple contributor accounts, check each WordPress user profile under Users in wp-admin, not just the bylines visible on the front end. A profile photo pulled from Gravatar defaults, a bio field left on its placeholder text, or a display name that doesn’t match any real person on your team are all the kind of leftover default that this guidance now has a name for.
Permitted Authorship Practices Versus a Fake Author
To clarify what remains fully compliant, review these accepted publishing formats that do not violate the updated policies:
- Anonymous publishing: Content published without any specific author byline.
- Team or brand bylines: Corporate or editorial team attribution (e.g., “AllCloudHost Editorial Team”).
- AI-assisted writing disclosure: Explicitly stating that AI research or drafting tools were utilized alongside human oversight.
It’s worth being precise here because the alarmed headlines this week (“Google bans fake bylines and AI-generated headshots”) can make it sound broader than it is. Google hasn’t banned anonymous content, team bylines, or AI-assisted writing. The guidance is about deception, not disclosure. A post that says “Written by our editorial team using AI research tools” is honest about its process. A post that invents “Sarah Mitchell, 15 years in web hosting” for a byline nobody can verify, attached to a face nobody has met, is the thing being flagged.
That distinction matters for any small business without a dedicated editorial staff. You don’t need to hire named experts to satisfy this guidance. You need to stop implying you have them when you don’t.
Why a Fake Author Problem Connects to More Than Classic Search Rankings
Fake authorship doesn’t just risk a ranking penalty in traditional search. AI answer engines like ChatGPT, Perplexity, and Google’s own AI Overviews increasingly weigh source credibility when deciding what to cite and summarize, and a page with fabricated authorship signals is a weaker candidate for citation on that same trust logic, even before any human reader notices. It’s part of a broader run of content-quality enforcement from Google this year; the August 2026 spam update targeted a different symptom of the same underlying problem: sites manufacturing signals of quality and expertise they hadn’t earned. Authorship authenticity is the latest specific signal added to that enforcement, not a one-off policy change sitting on its own.
It’s also not hard to see why fake author profiles are a comparatively easy thing for an automated system to catch at scale, even without reading the content itself. The same stock headshot or AI-generated face can turn up attached to different names across many unrelated sites, and a credential claim that can’t be matched to any real, verifiable person is a pattern a classifier can flag far more cheaply than it can evaluate the actual quality of the writing underneath it.
Fixing it without overcorrecting
If your audit turns up a problem, the fix is usually simpler than the anxiety around finding it. Replace a stock headshot with a real photo of whoever wrote or oversaw the piece, even an informal one taken on a phone. If genuinely nobody specific “wrote” a page because it came out of a template or a tool, attribute it honestly to the team or brand rather than inventing a person. If a credential in a bio isn’t accurate, either remove it or replace it with what’s actually true, even if that’s less impressive. A bio that reads “our support team, who handles hosting migrations daily” is more credible, not less, than a fabricated expert with vague made-up accolades.
The sites most exposed here aren’t the ones using AI tools in their writing process, which Google’s guidance doesn’t touch. They’re the ones that built fake human identities around that process specifically to borrow trust they hadn’t earned. That’s a narrower group than the headlines suggest, but if you’re in it, this is the week to stop.
Further reading: Google Search Central: Creating helpful, reliable, people-first content.