meta author Tag

The meta author tag: authorship signals beyond a single HTML line

The classic <meta name="author" content="..."> tag declares who wrote the document. It is trivial to add and supports a comma-separated list when several people collaborated. Its direct SEO impact is small — Google has confirmed that it ignores most generic meta tags as ranking signals — but it remains useful for RSS feed readers, content management systems, archival systems, intranet search and as a fallback for tools that have not migrated to JSON-LD yet. The real authorship layer for the modern web lives in structured data, not in this tag, but having both costs nothing and covers more crawlers.

<meta name="author" content="Ada Lovelace">
<meta name="author" content="Ada Lovelace, Charles Babbage">
<meta name="author" content="Editorial Team">

JSON-LD, Schema.org Person and the modern E-E-A-T layer

Google's quality framework E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) places heavy weight on identifiable authors with topical credentials. The recommended way to signal this is via a JSON-LD Article block whose author property points to a Person object with name, url (a real author bio page on your domain) and ideally sameAs pointing to LinkedIn, ORCID, Google Scholar or another canonical identity. For multi-author pieces, use an array.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Quantum sorting algorithms",
  "author": [
    { "@type": "Person", "name": "Ada Lovelace", "url": "/authors/ada" },
    { "@type": "Person", "name": "Charles Babbage", "url": "/authors/charles" }
  ]
}

Open Graph article:author and Dublin Core

Open Graph offers article:author for news and blog content; Facebook, LinkedIn and most preview cards read it. Dublin Core (DC.creator, DC.contributor) is still standard in academic publishing and many institutional repositories. Combining all four layers — meta author, OG article:author, DC.creator and JSON-LD Person — gives you maximum compatibility with crawlers, social networks, RSS readers and library systems.

<meta property="article:author" content="https://example.com/authors/ada">
<meta name="DC.creator" content="Lovelace, Ada">
<meta name="DC.contributor" content="Babbage, Charles">

Historical context: Google Authorship and what replaced it

Between 2011 and 2014, Google ran the Authorship project, where verified writers had their Google+ portrait shown next to their results in the SERP. The feature was deprecated in 2014 and the visual rel="author" link to profile pages disappeared in 2016. Modern equivalents are richer: detailed author bio pages on your own domain, structured Person markup, Knowledge Graph entities for prominent writers, and About/Author pages referenced by sameAs. Some niches (medical, finance, news) still get an author byline in the SERP card when this structured data is solid.

Where the meta author tag still matters in 2026

• RSS and Atom generators often read <meta name="author"> when the feed item lacks an explicit author field.
• WordPress, Ghost and most CMSs emit the tag automatically — losing it during a theme rewrite is a subtle regression.
• Academic preservation services (Internet Archive Scholar, Zotero, Mendeley) parse it to attribute references.
• Plagiarism detection tools (Copyscape, Turnitin) match author metadata to flag content reuse.
• Internal enterprise search indexes the tag for compliance audits and document attribution.

FAQ

Does the meta author tag help Google ranking? Marginally at best. Google does not use it as a direct ranking factor, but a coherent authorship strategy across meta, OG and JSON-LD reinforces E-E-A-T signals which do influence ranking in YMYL niches.

Should I use meta author or JSON-LD Person? Both. JSON-LD is the modern standard and the one Google explicitly documents for rich results, but the meta tag is so cheap that there is no reason to drop it.

How do I declare multiple authors? Comma-separated inside a single content attribute, or — better — multiple <meta name="author"> tags in series. For JSON-LD, use an array of Person objects under the author property.

What about anonymous or staff content? Use a generic value like "Editorial Team" with a corresponding Organization in JSON-LD. Never invent a fake person — Google can penalize fabricated author personas.