Author attribution: what the check tests and how to fix it

Weight 0.5. Counts crawled pages with a top-level JSON-LD author, a meta name=author tag, or a rel=author element. 50% passes. Names are not checked.

Content Quality · Weight 0.5 in the w2agent Score

How common is it?

13% of 1223 measured sites where this check applied pass.

Latest audit of each site under rubric v3.1. Sites where the check did not apply or could not be measured (for example, no llms.txt for the llms.txt checks) are left out. A partial result does not count as a pass.

What this check tests

A crawled page (the homepage plus up to nine more) counts as attributed if it has at least one of:

  • A parsed JSON-LD block whose top-level object has an author member that is not undefined. Its value is not inspected, so an empty author counts. A block that is an array, or an object inside @graph, is not read.
  • A <meta name="author"> tag, whatever its content.
  • Any element with rel="author", such as <a rel="author" href="/team/jo">.

The score is the share of attributed pages, rounded. 50 or more passes, 1 to 49 is partial, 0 fails. The message reads "3/10 pages have author attribution".

It does not read the visible byline text. A page that says "By Jo Chen" in a paragraph, with none of the three markers, does not count. It does not check that the author is a real Person or Organization, that a name is present or that a link resolves. It also cannot tell an article from a pricing page, so a site that is mostly product, landing and utility pages will score low, correctly in a technical sense and unhelpfully in an editorial one.

Why it matters to agents

Google's helpful-content guidance poses "who created the content" as a question: is it self-evident to visitors who wrote it, do pages carry a byline where one is expected, and do the bylines lead to background on the author. Google says clear authorship aligns with the E-E-A-T concepts it describes and that it encourages accurate authorship information. The Article structured data page lists author with author.name and author.url, where the URL points to a page that identifies the author, such as a profile or bio page.

The fetched sources stop at that. None says an AI assistant weighs authorship when choosing sources. Treat the markup as a statement of who is responsible for the content, useful to readers and to any system that wants to attribute it. This is why the check weighs 0.5.

How to fix it

For articles, guides, reviews and documentation with identifiable authors:

  1. Show a byline, and link it to an author page where the person's background is explained.
  2. Mark the link so machines can follow it:
<a rel="author" href="/team/jo-chen">Jo Chen</a>
  1. Add author data to the page's top-level JSON-LD, with a name and a URL. Google's guidance says to list each author as a separate entry and not to merge several names into one field:
"author": [
  { "@type": "Person", "name": "Jo Chen", "url": "https://example.com/team/jo-chen" },
  { "@type": "Person", "name": "Sam Ortiz", "url": "https://example.com/team/sam-ortiz" }
]
  1. Optionally add <meta name="author" content="Jo Chen">. MDN defines the value as the document author's name.
  2. Do not invent authors for pages that have none. A company page can name the organization instead, and a lower score on non-editorial pages is expected.

Related: freshness signals covers the date beside the byline, schema.org completeness lists author among the fields it counts for creative works, and citation readiness has a looser author-word signal.

Examples from measured sites

Up to 10 of the highest-scoring sites in each group, from recent audits. Failing includes partial results.

Passing

Failing or partial

Sources

Verified against these sources on

Does your site pass this check?

Check your own site →