Google’s Fake Author Warning: What Nonprofits, Associations and Small Publishers Should Change in Their Bylines

Google now warns site owners directly against fake author information. In early October 2026 it added a paragraph to its guidance on creating helpful content. It says made-up names, AI-generated headshots and false credentials are "a form of deception," and that deception is "a signal of a low-quality page."

This piece walks through what Google added and when, what the rater guidelines already said, and Google’s view of AI-assisted writing. It then sorts common byline habits into fine and stop, and covers author pages in WordPress and Drupal.

The short version: real people, organization bylines and honest editor credits are all fine. Invented experts, stock-photo authors and inflated credentials are what Google named. If your site has a fake author profile, retire it and credit the real writer or the organization. Then make sure each byline leads to a real page about that person or team.

What Google added about fake author information

The change is on Google’s Creating helpful, reliable, people-first content page, in the section that asks "Who" created the content. That section already asked: "Do pages carry a byline, where one might be expected?" It also said: "We strongly encourage adding accurate authorship information, such as bylines to content where readers might expect it."

The new paragraph follows. It opens: "However, avoid using deceptive authorship information." Then it gives Google’s definition:

"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."

It closes: "Any form of deception makes a page untrustworthy to both users and our automated quality systems, and is a signal of a low-quality page."

The target is fabrication: a person who does not exist, or credentials someone does not hold. Google also names its automated systems here. It does not say how it detects a fake author or describe a penalty.

When the change appeared

The page shows "Last updated 2026-10-05 UTC." Search Engine Roundtable and Search Engine Land both reported the new paragraph on October 6, 2026. As of October 10, Google’s Search Central documentation updates log has no entry for it.

The author paragraph was the second change to this page in a week. According to Search Engine Roundtable, Google added a "Main content" section the same day it updated its generative AI guidance. The updates log dates that guidance change October 1. The new section lists what quality raters judge: effort, originality, talent or skill, and accuracy.

The effort definition matters for content teams. Google defines effort this way: "The extent to which human work went into creating the content or the systems powering it." It also says: "Attribution or giving credit to other sources doesn’t replace the need for original effort."

Search Engine Roundtable noted that Google once told it the company was not worried about fake author information. That has changed.

This is quality guidance, separate from the September spam update. We covered the spam update’s dates in our September 2026 spam update recap. For how spam updates differ from guidance changes, see what a Google spam update is.

What the quality rater guidelines already said

Google’s raters work from the Search Quality Rater Guidelines. The current PDF is dated September 11, 2025. It already treated fake creator details as untrustworthy.

Section 4.5.3 covers sites with "deliberately inaccurate or misleading information about the website or content creators" used "to make the website appear trustworthy." It says: "All pages or websites using deception of any type should be rated Lowest because they are Untrustworthy."

The same guidelines make room for organizations. They define a content creator as "the individual(s) or entity (business, organization, etc.) who created the content on a webpage." An association can be the author.

Raters do not set rankings. Google’s helpful content page says: "Search raters have no control over how pages rank." The new paragraph puts the rater view into the guidance site owners read.

What Google says about AI-written content and personas

Google names "AI-generated headshots" as one example of a fabricated profile. It does not name AI personas as a separate category. An AI persona with a made-up name and an invented bio fits the definition either way. So does a persona whose articles are AI-drafted and presented "as if it was written by human experts."

Using AI to help write is a separate question. The "How" section of the same page asks: "Is the use of automation, including AI-generation, self-evident to visitors through disclosures or in other ways?" It suggests AI disclosures for content where readers might ask how it was created. "Consider adding these when it would be reasonably expected."

Google’s guidance on using generative AI content adds one rule: "It is critical to manually factcheck and review all AI-generated content for accuracy and trustworthiness before publishing." It warns that mass-produced AI pages may fall under the scaled content abuse spam policy.

The fake author paragraph is about invented writers. A real staff member who drafts with AI, then reviews and signs the post, is still the author.

Fake author risk by byline type

Most nonprofits, associations and universities have a mix of byline habits. Here is how they line up against Google’s text.

Google’s examples do not mention stock photos. A stock photo on a made-up name is still a fabricated profile, so treat it the same way.

Ghostwritten posts and staff work under an org byline

Ghostwriting is the hardest case, because Google’s text does not mention it. Staff often draft posts for executive directors and presidents, who review, edit and sign them.

Google’s concern is content made "to appear as if it was written by human experts" when no such expert exists. An executive who approves a post is a real person who answers for it. The risk rises when the byline makes a claim the executive cannot back up, such as clinical or legal expertise.

Two habits keep ghostwritten posts on safe ground:

• Keep the bio honest. List the executive’s real role. Skip implied expertise in topics they did not work on.
• Credit contributors when readers would care. A line such as “With research by the policy team” is accurate and costs nothing.

Organization bylines are simpler. A "Staff" byline is accurate when several people produce the work. A byline that links to a page naming the team and its role answers Google’s question: "Is it self-evident to your visitors who authored your content?"

Setting up author pages in WordPress

WordPress builds a byline from each user account. Under Users, then Profile, the "Display name publicly as" setting controls the name readers see. The Biographical Info field holds the bio, and the profile picture comes from Gravatar, according to the WordPress profile screen documentation.

1. Use real names. Change any display name that shows a login name or a persona.
2. Fill in the bio. One or two sentences: role, focus areas, real credentials.
3. Show the bio on posts. In block themes, the Author Name, Author Biography and Avatar blocks replace the older Author block.
4. Create a shared account for org bylines. Give it a bio that names the team.
5. Handle outside writers. The Co-Authors Plus plugin lets you “Add writers as bylines without creating WordPress user accounts.” It also supports more than one byline per post.

If you use Yoast SEO, check Settings, then Advanced, then Author archives. Yoast’s help page says that when archives are off, Yoast "will redirect the author archive pages to the homepage." On a multi-author site, that leaves bylines with nowhere useful to go. Keep archives on, and add bios so each archive is a real author page.

Setting up author pages in Drupal

Drupal decides per content type whether bylines show at all. Under Structure, then Content types, edit the type. On the Display settings tab, the "Display author and date information" box turns the byline on or off, as the Drupal user guide shows.

By default, that byline shows the author’s username. For a real author page, there are two common approaches:

• Extend the user profile. Add fields for display name, role, bio and photo, and theme the profile page.
• Build a Person content type. Reference it from articles with an entity reference field. This works for guest writers and staff without logins.

Either way, show the real name, not the login name. The Schema.org Metatag module can then output author markup.

Author markup that matches the byline

Structured data should say what the page says. Google’s Article structured data documentation sets a few rules:

• “Use the Person type for people, and the Organization type for organizations.”
• “In the author.name property, only specify the name of the author.” Job titles go in jobTitle.
• List each author in their own author field, and include every author shown on the page.
• Give author.url a page that identifies the author, such as the author page above.

An org byline should be marked up as an Organization, not as a fake Person. Our Schema.org guide and on-page SEO checklist cover the rest of the Article markup.

A fake author audit for this month

1. List every byline in use. Export authors from WordPress or Drupal and check each against a real person or team.
2. Retire personas. Reassign their posts to the real writer or to the organization byline.
3. Check photos. Replace stock or AI-generated headshots with real photos, or use no photo.
4. Check credentials. Remove any degree, license or title the person does not hold.
5. Fix dead-end bylines. Every byline should lead to a page about that person or team.
6. Match the markup. Person for people, Organization for org bylines.

If search traffic has already moved, our Search Console walkthrough for traffic drops helps sort out the cause before you change anything.

Frequently Asked Questions