# Article and Author Schema for Expertise

> How to mark up Article authors so search engines and AI tools can tell who wrote a page: Google's author rules, Person markup, bylines and author pages.

Source: https://mentionx.ai/learn/technical/article-author-schema-expertise  
Author: Dipuck Jones, founder of MentionX  
Updated: 30 October 2026  
Level: Practitioner

**Author schema tells search engines who wrote an article: use Article markup with an `author` that has `@type` Person, the name only in `name`, and a `url` or `sameAs` pointing to an author page.** Google strongly recommends type and url properties, and asks for accurate bylines where readers expect them ([Google](https://developers.google.com/search/docs/appearance/structured-data/article), [Google](https://developers.google.com/search/docs/fundamentals/creating-helpful-content)). It's a clarity signal, not a ranking switch: Google says E-E-A-T itself isn't a specific ranking factor.

*Facts are from Google Search Central and schema.org, accessed 30 Oct 2026. Points marked "Our view" are interpretation.*

> **Key takeaways**
>
> - Article and author markup helps search engines understand who wrote a page and when.
> - Google recommends author properties with a name and a URL that identifies the person.
> - Markup must match the visible byline and dates; never mark up authors who didn't write the content.
> - Test with Google's Rich Results Test and roll out through templates, not page by page.

*Checked on 31 October 2026. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.*

## Why does authorship matter for AI visibility?

Google's people-first guidance asks whether it's self-evident who authored your content, whether pages carry a byline where one might be expected, and whether bylines lead to more information about the authors and the areas they write about ([Google](https://developers.google.com/search/docs/fundamentals/creating-helpful-content)). It says that clearly indicating who created content aligns with E-E-A-T, and that its systems give even more weight to content with strong E-E-A-T on topics that could significantly affect health, financial stability or safety.

*Our view:* AI answers on high-stakes topics tend to lean on sources with clear expertise. Visible authorship plus consistent markup makes that expertise easier to recognise.

## What are Google's author markup rules?

Google's Article documentation lists best practices ([Google](https://developers.google.com/search/docs/appearance/structured-data/article)):

| Rule | Do | Don't |
|---|---|---|
| Include all authors | Mark up every author shown on the page | Leave co-authors out |
| Multiple authors | One `author` entry per person | `"name": "Willow Lane, Regula Felix"` |
| Use type and url | `@type` Person or Organization, plus `url` or `sameAs` | Use `Thing` |
| Name only | `"name": "Echidna Jones"` | Job titles, honorifics, publisher or "posted by" in the name |
| Extra details | `jobTitle`, `honorificPrefix` | Stuffing them into `name` |

Google says there are no required Article properties; add the ones that apply ([Google](https://developers.google.com/search/docs/appearance/structured-data/article)).

## What does a good template look like?

An fictional example with hypothetical names:

```json
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How VAT works for UK sole traders",
  "datePublished": "2026-10-01T09:00:00+01:00",
  "dateModified": "2026-10-28T14:30:00+01:00",
  "author": [{
    "@type": "Person",
    "name": "Priya Shah",
    "jobTitle": "Chartered Accountant",
    "url": "https://www.example.com/authors/priya-shah",
    "sameAs": ["https://www.linkedin.com/in/example"]
  }],
  "publisher": {"@id": "https://www.example.com/#organization"}
}
</script>
```

Google recommends timezone information for `datePublished` and `dateModified`; otherwise it defaults to Googlebot's timezone ([Google](https://developers.google.com/search/docs/appearance/structured-data/article)). The `publisher` reference reuses your Organization markup; see [Organization schema for brand entities](https://mentionx.ai/learn/technical/organization-schema-brand-entities).

## What should an author page include?

*Our view:* the `url` should lead to a real page with:

- Full name and photo of the actual person
- Role and relevant qualifications, with verifiable details such as professional registrations
- Topics they cover and a list of their articles
- Links to profiles they control, matching the `sameAs` list
- Person markup on the page itself ([schema.org](https://schema.org/Person))

## What must you avoid?

Google says fabricating creator profiles, such as AI-generated headshots, made-up names or false credentials used to make content look written by human experts, is deception that makes a page untrustworthy to users and its systems ([Google](https://developers.google.com/search/docs/fundamentals/creating-helpful-content)). Also avoid:

- Listing a well-known expert as author when they only reviewed the piece. Use a separate "reviewed by" line in the visible content instead.
- Byline in markup but not on the page. Google's guidelines say markup must reflect visible content ([Google](https://developers.google.com/search/docs/appearance/structured-data/sd-policies)).
- One generic "Admin" or "Team" author across everything, when individuals wrote the pieces.

## What about AI-assisted content?

Google's guidance on AI content focuses on whether it's helpful and accurate, and suggests explaining how automation was used where readers might reasonably wonder ([Google](https://developers.google.com/search/docs/fundamentals/using-gen-ai-content), [Google](https://developers.google.com/search/docs/fundamentals/creating-helpful-content)). *Our view:* name the human who's accountable for the piece and describe the process honestly, for example "Drafted with AI assistance, edited and fact-checked by Priya Shah".

## How do you test it?

1. Run an article through the [Rich Results Test](https://search.google.com/test/rich-results) and the [Schema Markup Validator](https://validator.schema.org/).
2. Check every author is a separate entry with `@type`.
3. Open each author `url` and confirm it works and describes the person.
4. Compare names across byline, markup and author page.

## How do you roll this out across a site?

*Our view:* fix it in templates, not page by page. Create an author record in your CMS for each real writer with name, role, bio and profile links, then generate the byline, author page and markup from that one record. That keeps all three consistent. For legacy content with no named author, either attribute it accurately to the person who wrote or now maintains it, or use your Organization as author rather than inventing a name. Review author records when people change roles or leave.

## Exercise

Audit five articles. For each, record the visible byline, the markup author, the author URL and whether the details match. Fix the template that causes any mismatch.

## Checklist

- Visible byline on articles
- One author entry per person, @type Person
- Name only in author.name
- url or sameAs to a real author page
- Dates with timezone
- No fabricated personas

## From MentionX data: which pages engines cite

**Method.** Read-only aggregate queries over MentionX scans from 22 August to 29 October 2026 (UTC): 2,217 engine runs (2,154 completed) across 18 anonymised projects and six engines.

Article markup applies to the largest cited URL type in the MentionX sample:

| Cited URL type | Share of 9,750 citations |
| --- | --- |
| Blog or article | 19.6% |
| Homepage | 10.0% |
| Review page | 2.7% |
| Docs | 2.6% |
| Pricing | 1.9% |
| Wikipedia | 1.6% |

Engines differ widely in how often they cite pages at all:

| Engine | Brand mentioned | Answers with no citations |
| --- | --- | --- |
| Gemini | 47.3% | 50.7% |
| OpenAI | 42.9% | 30.2% |
| Perplexity | 31.5% | 4.1% |
| AI Mode | 31.3% | 12.6% |
| Copilot | 26.0% | 47.0% |
| DeepSeek | 24.0% | 99.0% |

*Our view:* markup doesn't guarantee citations, but articles are the page type engines cite most, and accurate authorship and date markup helps make clear what each article is and who stands behind it.

**Limits.** A convenience sample of mostly B2B software projects, run through engine APIs, which can behave differently from the consumer apps. Perplexity, Copilot and DeepSeek figures come from a single day (26 October 2026), so treat them as a snapshot, not a trend.

## Worked example: Ledgerline adds author markup to its article template

*Ledgerline is a fictional accounts-payable tool. Figures are illustrative.*

Ledgerline's articles show bylines, but the markup only includes the headline. The developer adds Article markup to the template with the headline, the published and modified dates, an image and an author property.

Each author is a Person with a name and a url pointing to their author page on the Ledgerline site. The author page itself has Person markup with the job title and sameAs links to the author's LinkedIn profile. For articles written by the company, the author is the Organization.

The team tests ten articles with the Rich Results Test and the Schema Markup Validator, fixes a template bug that output the published date as the modified date, and checks that each date matches the visible date on the page.

> **Pro move:** Generate author markup from the same database field as the visible byline. If the two come from different places, they'll drift apart.

## How should you handle multiple authors?

List each author as a separate item in the author property, in the same order as the visible byline. Don't combine names into one string. If a reviewer isn't an author, don't put them in the author property; mention them in the visible text instead.

## How should dates be marked up?

Use the published date for datePublished and the date of the last meaningful change for dateModified. Include time zones where you can. Don't change dateModified for small edits like fixing a typo, and don't set it automatically on every page load. The dates in the markup should match the dates readers see.

## What about organisation authors?

When content is genuinely written by the company, use the Organization type for the author, with its name and url. *Our view:* for advice content, a named person with relevant experience is more useful to readers, so use organisation authors mainly for news and announcements.

## How do you keep author markup accurate?

Review author markup when someone joins, leaves or changes role. Keep author page URLs stable, and redirect them if they change. Re-test a sample of pages after any template change. Check Search Console for structured data errors monthly.

## Where should author markup go?

Put Article markup on each article page, with the author property pointing to the author's page. Put Person markup on the author page itself. Don't add full Person markup for every author on every article; a name and url in the author property are enough there. Keep markup in the page's HTML, ideally as JSON-LD.

## How do you mark up a reviewer?

schema.org has a reviewedBy property for web pages, but Google doesn't document it for author features. *Our view:* name the reviewer in the visible text and, if you use reviewedBy, make sure it matches. Don't list reviewers as authors.

## How do you handle guest authors?

Give guest authors their own author page, or link the author url to a profile that clearly belongs to them. Include their name and a short bio. Make clear in the visible text that they're a guest contributor if that's the case.

## How do you check markup at scale?

Crawl the site with a tool that extracts structured data, and check that every article has an author with a name and url. Flag articles where the author name in the markup doesn't match the visible byline.

## What does a minimal working example contain?

A minimal Article block includes the headline, an image, datePublished, dateModified and an author with a name and url. The author page carries a Person block with the name, jobTitle, url and sameAs links. Start with this, test it and add optional properties only when they're accurate and maintained. *Our view:* a small set of correct properties is better than a long list that drifts out of date.

## How do you avoid common template errors?

Check that dates are output in ISO 8601 format, that author urls are absolute and that the same author isn't listed twice. Make sure markup isn't output on pages where the visible byline is missing.

## How do you roll out changes safely?

Change the template on a small set of articles first, test them and check Search Console for errors over a week or two. Then apply the change across the site. Keep a record of the template version so you can roll back if something breaks. *Our view:* staged rollouts catch errors that tools miss, such as wrong authors on older articles.

## Common questions

**Is author markup required?** No. It's recommended, and it helps search engines understand authorship.

**Should we use sameAs for authors?** Our view: yes, on the author's own page, linking to profiles that clearly belong to them.

**Does author markup help AI answers?** There's no published evidence of a direct effect. It helps make authorship clear, which supports trust.

## Related

- [Schema markup for AI search](https://mentionx.ai/learn/technical/schema-markup-ai-search)
- sameAs links and the knowledge graph

## Sources

- Google, [Article structured data](https://developers.google.com/search/docs/appearance/structured-data/article); [creating helpful content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content); [using generative AI content](https://developers.google.com/search/docs/fundamentals/using-gen-ai-content); [structured data guidelines](https://developers.google.com/search/docs/appearance/structured-data/sd-policies); [Rich Results Test](https://search.google.com/test/rich-results)
- schema.org, [Person](https://schema.org/Person); [Schema Markup Validator](https://validator.schema.org/)
All accessed 30 Oct 2026.

## Frequently asked questions

### Is author markup a ranking factor?

Google says E-E-A-T itself isn't a specific ranking factor. Author markup helps Google understand and represent the author; it doesn't guarantee rankings or citations.

### What should go in author.name?

Only the person's or organization's name. Google says not to include job titles, honorifics, publisher names or words like "posted by".

### Can I use AI-generated author personas?

No. Google calls fabricated creator profiles, such as made-up names or AI-generated headshots, a form of deception.

---

Written and reviewed by Dipuck Jones for MentionX Learn. The HTML version of this page: https://mentionx.ai/learn/technical/article-author-schema-expertise