Authors people can verify: how to check your site’s authorship before the Google update

Fake authors and E-E-A-T: what Google now calls deception

The helpful content guide now has a paragraph on deceptive authorship information. Its example: fabricated creator profiles with AI-generated headshots, made-up names or false credentials. Google calls this deception that undermines trust with both users and search systems.

Lily Ray has observed fake or AI-generated authors, including on money and health topics, among sites hit by 2026 updates. That’s a practitioner’s observation, not Google data.

Google doesn’t require a named author on every page, but it strongly encourages accurate authorship information, such as bylines where readers expect them. Above all, don’t deceive: an “Editorial team” byline is more honest than a made-up expert.

Sources: Google: helpful content, Relevant Audience: authors, Lily Ray

The verifiability ladder

We rate authors by how easy it is to confirm each rung. The first three, name and photo, bio and an author page, are easy to generate, so on their own they prove little. Trust comes from the upper rungs: experience you can find, a footprint off the site and accountability for the text. Switch the ladder at the top to “fake author” to see where the fake breaks.

A note on the common advice that “the author must be in Google’s Knowledge Graph”: Google’s documentation has no such requirement. Outside confirmation matters, but it isn’t the same as a Knowledge Graph entry.

Source: Google: helpful content

Checking your site’s authors

Eight questions; answer them for each author. The heaviest weight goes to whether the person actually exists.

Author page and markup

Google’s article structured data documentation sets specific rules for authors:

• author.name holds only the name, without job title, publication or words like “By”. Use jobTitle for the role.
• author.url links to a page that uniquely identifies the author: a profile on the site, an “about me” page, a social profile. sameAs is an alternative.
• If the author has a page on your site, mark it up as ProfilePage.
• List each author separately. Don’t merge several people in one field.
• Use Person for people and Organization for organizations.

<!-- On the article page -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article headline",
  "datePublished": "2026-10-17",
  "author": [{
    "@type": "Person",
    "name": "First Last",
    "url": "https://example.com/authors/first-last"
  }]
}
</script>

<!-- On the author page /authors/first-last -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "name": "First Last",
    "jobTitle": "Job title",
    "sameAs": ["https://www.linkedin.com/in/…"]
  }
}
</script>

jobTitle is a schema.org property; Google’s ProfilePage documentation doesn’t list it, but it does no harm.

Markup doesn’t make an author real. It helps Google connect content to a person; the person is still verified by the author page and their footprint off the site.

Sources: Google: Article markup, Google: ProfilePage markup

When a team or AI writes the content

There are several honest ways to sign content, and none of them needs a made-up expert:

• Editorial byline

  The author is the organization. Use Organization in markup and link to a page about the team and how content is made.

• Author and reviewer

  The team or AI drafts, a named specialist reviews. Byline: “Reviewed by: name, role”, linked to their page.

• Being open about AI

  Google recommends explaining how content was made where readers would care. A short line at the end usually does it (our practice).

• One person, their own topics

  If someone signs articles, they should be within that person’s experience.

Sources: Google: helpful content, Google: generative AI

What to do with fake authors

Authorship is part of the overall quality picture. If fake authors come with lots of similar AI texts, start with the content self-audit.

FAQ

Sources

Authorship and markup requirements are from Google Search Central documents checked on October 17, 2026. Observations on affected sites are Lily Ray’s. The verifiability ladder and the checklist are our method; the checklist is pre-filled with an example.

How this piece was made: written by the SurfUp editorial team with AI assistance; every fact and number was checked by hand against the sources listed above.

1. Google Search Central — Creating helpful, reliable, people-first content (updated October 5, 2026)
2. Relevant Audience — Google adds fake-author warning to helpful content page
3. Lily Ray — Prediction: the next massive Google update is around the corner, October 4, 2026
4. Google Search Central — Article structured data
5. Google Search Central — Profile page structured data
6. Google Search Central — Guidance on using generative AI content (updated October 1, 2026)