Understanding the ins and outs of website growth, we help ensure that your site grows over time with ever-increasing reach and accessibility. Not only do we employ the latest digital marketing techniques for driving traffic directly to your website, but our strategies also focus on gaining loyalty from those visitors so they come back again and again.
Leave your contacts to get a comprehensive and aggressive digital marketing plan taking your business to new heights.
EEAT Author Profile Audit: 11 Fields to Check in 2026
An author profile built for experience, expertise, authoritativeness and trustworthiness (EEAT) is a page that shows a real person wrote the article: real name, stated role, original photo, checkable credentials, outside profiles and Person markup. Google says E-E-A-T is not a specific ranking factor, so use these eleven fields to verify authors, not to boost rankings.
I lead search engine optimization (SEO) and content at Mettevo, and I audit EEAT author profiles the way I audit markup: field by field, with a pass line for each. This article publishes the rubric itself, built from Google Search Central guidance and from auditing our own author page on mettevo.com, not an aggregate study of other sites.
Key Takeaways
Google's people-first content guidance says E-E-A-T "isn't a specific ranking factor" and calls fabricated creator profiles, including headshots generated by artificial intelligence (AI), a form of deception. I treat author fields as verification, not ranking inputs.
The rubric has eleven fields. Nine rest on Google's documentation. Fields 8 and 9 rest on our own reasoning.
According to our 16 November 2026 scoring, our own author page has seven passes, two partials, one fail and one unverified field.
According to our 28 September 2026 crawl, Person markup appears on 54 of 58 indexable pages (the 54 article pages), and the crawl records 245 internal links pointing to the author page.
A house byline such as "Team" fails fields 1, 2, 4 and 6 by construction. Name the person who stands behind each piece.
What does E-E-A-T mean on a byline in 2026?
Google says trust is the most important of the four qualities, and that content does not have to demonstrate all of them. On a byline, trust becomes a concrete test: can a reader identify the person, read their background and confirm it somewhere else? Google's "Who" section asks whether pages carry bylines and whether bylines lead to further information about the author.
How does Google detect an author's expertise?
Google does not publish an author-expertise detector. Google's documentation refers to "a mix of factors that can identify content with good E-E-A-T" and gives creators questions to ask, not a scoring method. For markup, the Article structured data documentation says Google can understand both sameAs and url when disambiguating authors. My working inference is reconciliation: if name, role, photo and links agree across page, markup and outside profiles, a person or a machine can confirm who wrote the piece.
What should an author bio page actually contain in 2026?
The rubric has eleven fields, each with a pass line you can check from the public page. Nine fields rest on text in Google's documentation. Fields 8 and 9, and the two-profile line in field 7, rest on our own reasoning. The schema.org Person vocabulary marks no property as required, so I use it for property names only. The last column is our testbed: the reference author page, scored on 16 November 2026.
#
Field and pass line
Basis
Our page, 16 Nov 2026
1
Real full name. One real name, spelled the same on byline, page and markup.
Google strongly encourages "accurate authorship information" and lists made-up names as deception.
Pass. "Oleg Silin" in the page heading.
2
Named job title. A role that fits the topic, shown on the author page.
Article docs: the title goes in jobTitle, not in author.name.
Pass. "Co-founder of Mettevo Digital Agency". The article byline shows no role.
3
Byline link. Each byline links to a page about that one person.
Google asks whether bylines lead to author background. Article docs: author.url "uniquely identifies the author".
Pass. The byline we read links to the author page; the 28 September 2026 crawl records 245 internal links to that URL.
4
Original portrait. A real photograph, not stock and not generated.
Google lists AI-generated headshots as deception.
Pass. Portrait in Mettevo-branded clothing, alt text names the person.
5
Specialization statement. One or two sentences on the subjects covered and why.
Google asks for background on "the areas they write about".
Partial. The bio lists work areas without a one-line statement.
6
Checkable credentials. Each credential names its issuer or register.
Google lists false credentials as deception. schema.org: alumniOf, award, hasCredential.
Fail. No education, certification or award tied to the work.
7
Outside profiles. Two or more on other domains, linked from the page.
Article docs: sameAs helps disambiguate authors. The number two is our reasoning.
Pass. LinkedIn and YouTube.
8
Affiliation and contact. Employer named, plus a way to reach the author or the organization.
Pass. Employer in the role line, contact only through the company contact page.
9
List of work. The author's articles, with a visible total.
Our reasoning: the list shows a record on the topic.
Partial. Ten titles listed, no total.
10
First-person evidence. A first-person bio and a piece that shows first-hand work.
Google: content can help through "the experience it demonstrates".
Pass. First-person bio on why the agency started and what the author does now.
11
Matching Person markup. Structured data with name, title, address, image and profiles that match the visible page.
Article docs list author, author.name and author.url as recommended.
Unverified. Person markup on all 54 article pages in the crawl, but the author page was not crawled.
Besides the page, we read the byline and author box on one article, the Core Web Vitals guide, and used our 28 September 2026 crawl: 60 addresses fetched, 58 indexable, JavaScript rendering off, schema types counted but not validated. Seven fields pass, two are partial, one fails and one is unverified. Field 11 stays open because the crawl did not include the author page. The posture I take is to score the page as it renders on the audit date, never the page we plan to publish.
What are the red flags of a stock-photo author bio?
Google's guidance describes fabricated creator profiles, such as "AI-generated headshots, made-up names, or false credentials", as "a form of deception", and says any deception is a signal of a low-quality page. Three red flags come from that list. The fourth is a test I recommend for any bio.
A headshot that is stock or generated. Run a reverse image search. The same face under several names is stock. A portrait found nowhere else is not proof of a fake, so run the name check next. This fails field 4.
A name with no footprint. Search the exact name with the employer. A real author leaves traces outside the site, such as a profile, a talk or a register entry. If the byline is the only trace, field 7 fails.
Credentials nobody can check. "Award-winning expert" with no award. "15 years of experience" with no employer. A degree with no institution. Each credential should name its issuer. This fails field 6.
A bio that survives a name swap. Put another author's name on the bio. If it still reads true, it is interchangeable copy. This is the fastest test I know, and I would rewrite a failing bio before touching any markup. It fails fields 5 and 10.
Does Person schema on the byline help rankings?
Google's Article documentation presents author markup as a way to identify authors: it lists author, author.name and author.url as recommended and says no property is required. We have no data showing a ranking effect, and Google says E-E-A-T is not a specific ranking factor. We ship Person markup because it makes the byline machine-checkable and forces page and markup to agree.
In the fragment below, the Person object sits inside Article.author, and its values follow what the author page shows on 16 November 2026. Google says to put only the name in author.name and the title in jobTitle. It also says to validate with the Rich Results Test and fix critical errors.
I would not add alumniOf, award or hasCredential until the author page names the institution, so the fragment leaves them out. Markup should never claim more than the visible page shows. I treat a clean Rich Results Test result as a validity check, not a credibility check.
How do you audit a byline in 30 minutes?
Run this routine on your own site or a client's. It needs a browser, a reverse image search and the Rich Results Test. For the brand behind the byline, our AI visibility audit walks seven checks that cover profile and markup on your pages plus how your brand appears in AI answers. Time-box each step:
Minutes 0 to 3. Copy the byline exactly as printed on three articles.
Minutes 3 to 8. Click each byline and note where it lands: an author page, a team page or nowhere.
Minutes 8 to 15. Score the author page against the eleven fields.
Minutes 15 to 20. Reverse image search the photo and search the name with the employer.
Minutes 20 to 25. Open an article in the Rich Results Test and compare the author markup with the visible byline.
Minutes 25 to 28. Check that the role text agrees across byline, page and markup.
Minutes 28 to 30. Log the score, the date and the page addresses so a second person can repeat it.
What changes for agencies writing under house author pages?
A house byline such as "Team" or "Admin" fails fields 1, 2, 4 and 6 by construction, because a group has no single name, title, face or credential. In my view the fix is attribution to the person who stands behind the claims.
Three practices follow. Keep one author record per person and generate the byline, the page and the markup from it, so they cannot drift. Name a reviewer when a writer drafts for an expert, because Google asks whether content is written or reviewed by an expert or enthusiast who demonstrably knows the topic. Never invent a persona: Google lists made-up names and false credentials as deception.
Google describes E-E-A-T as qualities its systems look for and says it is not a specific ranking factor, so the fields on this list are a verification standard. Any link between them and rankings is a correlation we have not isolated. We quote Google's pages as read on 16 November 2026.
This article publishes a rubric and a single-site self-audit, not an aggregate study. We did not audit a cross-site sample in a way we would publish per-field percentages from, so we publish none. Each of the eleven fields names a Google source or labels itself as our own reasoning, and the self-audit on mettevo.com is the only dataset we attach outcomes to.
According to our Search Console data for the mettevo.com domain property (monthly totals, pulled 10 September 2026), impressions fell from 390,704 in February 2026 to 146,119 in August, a drop of 63%. Click-through rate (CTR) rose from 7.78% to 14.37% and average position improved from 26.75 to 23.41, yet implied clicks fell about 31%. A CTR of 7.78% at position 26.75 looks inconsistent with a normal click curve. One possible cause is a few high-CTR queries blended with a long tail of deep rankings, but monthly totals cannot test it. We assign none of this movement to author pages.
Frequently asked questions (FAQ)
What is an E-E-A-T author profile?
An E-E-A-T author profile is a page for one named author that lets a reader verify who wrote an article. It shows a real name, role, original photo, checkable credentials, outside profiles and matching Person markup. Google says E-E-A-T is not a specific ranking factor, so treat the profile as a trust standard, not a ranking lever.
How does Google detect an author's expertise?
Google does not publish an author-expertise detector. Its documentation refers to a mix of factors that can identify content with good E-E-A-T, and its Who section asks whether bylines lead to background about the author. For markup, Google says it can use sameAs and url to disambiguate authors. Anything beyond that is inference.
What should an author bio page actually contain in 2026?
Eleven fields: real full name, named job title, byline link, original portrait, specialization statement, checkable credentials, two or more outside profiles, affiliation and contact, list of work, first-person evidence and matching Person markup. Nine rest on Google's documentation. Fields 8 and 9 rest on our reasoning.
Does Person schema on the byline help rankings?
Google's Article documentation presents author markup as a way to identify authors and lists author, author.name and author.url as recommended, with no required properties. We have no data showing a ranking effect. We ship Person markup because it makes the byline machine-checkable and forces the visible page and the markup to agree.
How do you audit an author profile for E-E-A-T?
Spend 30 minutes. Click three bylines, score the author page against the eleven fields, reverse image search the photo, search the name with the employer, compare the markup with the visible page in the Rich Results Test, check the role text agrees everywhere and log the result with the date.
What are the red flags of a stock-photo author bio?
Four: a headshot that is stock or AI-generated, a name with no footprint outside the site, credentials nobody can check, and a bio that survives a name swap. Google names AI-generated headshots, made-up names and false credentials as fabricated creator profiles and calls them a form of deception.