No Author Pages: How to Build Author Profiles for E-E-A-T

What this check flags

This issue fires when your content carries author names but those names do not resolve to a dedicated page. A byline that is plain text, or that links to nothing, leaves a search engine guessing about who wrote the piece. The check is looking for an author archive or profile URL, usually something like yoursite.com/author/jane-doe, where a reader can see who the writer is and what else they have published.

It is a real signal, not a vanity item. Google's quality raters are told to look for information about who created the content. When that information is thin or missing, the page can be rated low or lowest quality. A floating name with no destination is exactly the kind of thin signal that hurts you.

Why author pages help

An author page does several jobs at once. It creates an entity for the writer. Search engines and AI models think in terms of entities, real people and things they can identify and describe. A single canonical page for each author gives the algorithm a stable anchor to attach facts to.

It also gives Person schema a home. The author page is where you place the full structured data for that individual: name, job title, who they work for, what they know about, and a sameAs array linking to their LinkedIn, their professional profiles, and any other place the same person appears online. Those sameAs links are how Google corroborates that the person is real and is who you say they are. Without that confirming evidence from outside your own site, the claim of expertise rests on your word alone.

A dedicated page consolidates authority too. Every article a writer publishes points back to one profile, so the topical track record stacks up in a single place instead of scattering across loose bylines. That accumulation is what builds a recognizable expert over time. And it helps AI systems that summarize and cite content connect a piece to a real person with a verifiable background, which matters more each month as answer engines decide whom to trust.

What a strong author page includes

A useful author page is more than a headshot and one sentence. Include the writer's full name, a real photo, and a bio that states their actual experience and credentials in plain terms. Spell out why this person is qualified to write on the topic. Add their role and the organization they work for. List the areas they cover. Show a feed of their published articles so the page demonstrates a body of work. Link out to their verified profiles, and where it fits, link to your About page so the site's own structure connects writer to publisher.

How to build them

Most content systems already generate author archives. In WordPress, every user with published posts has an archive at /author/username; the work is making those pages exist as real templates, filling out each profile, and making sure they are indexable rather than hidden or thin. Give the author template a proper bio block, photo, and post list, then make your byline link to it.

Then add the structured data. Put full Person schema on the author page, and reference the same author from each article using a matching @id so the two connect. Here is the shape of the Person markup for the author page:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://example.com/author/jane-doe/#person",
  "name": "Jane Doe",
  "url": "https://example.com/author/jane-doe/",
  "jobTitle": "Senior SEO Analyst",
  "worksFor": { "@type": "Organization", "name": "Example Co" },
  "knowsAbout": ["Technical SEO", "Structured Data"],
  "sameAs": [
    "https://www.linkedin.com/in/janedoe",
    "https://example.com/about/"
  ]
}

On the article, keep the author reference lean and point its @id and url at that same author page. The two pieces of markup share one identifier, so the engine reads them as one person.

When you do not need them

If you run a single-author site, a separate per-author archive can be overkill. In that case your About page does the same work: it carries the Person schema, the credentials, and the sameAs links, and your bylines point there. The goal is a real entity behind the content, not a particular URL pattern. One owner, one strong About page, done.

Common mistakes

The frequent slip is a thin author page with a stock photo and a generic line that says nothing about real expertise. That checks a box without adding trust. Another is an empty sameAs array, or one stuffed with links that do not actually feature the same person; those links are meant to verify, so they have to be genuine. Watch for mismatched identifiers, where the article schema and the author page use different @id values and never connect. Avoid noindexing your author archives by reflex, and do not let bylines stay as plain text once the pages exist. Fix the link so it points home.

FAQ