Author and Publisher Identity Audit
Who wrote a piece of content is the foundation of how much anyone trusts it. Search engines read that not only from the visible byline but from the page's structured data: the author's name, their own page, and the chain of links out to their external profiles. This tool audits your page's author and publisher markup end to end, covering the meta tag, Open Graph, the JSON-LD Person schema, the sameAs chain, and whether they all agree with each other.
The meta tag no longer does the job on its own
For many years the way to declare an author was the <meta name="author"> tag. It's still harmless, but on its own it produces no identity signal: it hands the search engine a text string and nothing more, saying nothing about who that name belongs to, where else they write, or what organization they work for. The structure that carries author identity today is the Person schema inside JSON-LD. An author field added to the page's Article schema turns the name into an ENTITY, and that entity can then be connected to other publications, organizations and external profiles.
sameAs: where identity becomes verifiable
The sameAs field in a Person schema lists the author's profiles beyond your site: LinkedIn, author pages on industry publications, academic profiles, professional directories. The field isn't decoration; it's what lets a search engine verify the identity INDEPENDENTLY. A name that appears only on your own site is an expertise you assert. The same name appearing with the same expertise across three separate independent sources is an expertise that has been verified. The links have to be real and reachable: broken links, or links belonging to a different person, weaken the chain rather than strengthening it.
Generic author names
Content management systems fill the author field with "admin", "editor" or similar by default, and the value is very often never changed. Such a name identifies nobody; to a search engine it produces almost the same result as declaring no author, and it can even read as carelessness. If no single person is responsible for a piece of corporate content, declaring the organization as the author is a better answer than leaving a generic username in place.
Publisher: the organization behind the individual author
The publisher is as much a trust signal as the author. In JSON-LD, the publisher field declares the organization publishing the content as an Organization type, along with its name and logo. In sensitive fields such as news, health and finance in particular, a search engine looks at the reputation of the organization behind the writer as well as the writer's own expertise. The publisher declaration also affects how the content is represented in search results and on news surfaces.
Consistency: same person, same name
An author's name can appear in three separate places on a page: the visible byline, the meta tag and the JSON-LD schema. All three should be written identically. Different spellings, one abbreviated, one with a title, one with a nickname, make it harder for a search engine to see that the same person is meant, and they fragment the entity link. The same discipline applies across the author's other articles: identity is built over time through repeated, consistent declarations.
Your Questions
Frequently Asked Questions
Does author information directly affect rankings?
It hasn't been defined as a direct ranking factor. But author identity carries the experience–expertise–authoritativeness–trust (E-E-A-T) framework Google uses in its quality assessment, and it's a decisive part of that assessment in sensitive fields such as health, finance and law. Content with no named author is also noticeably less likely to be cited in AI answers.
Should I remove the meta author tag?
No, it's harmless and some tools read it. It isn't sufficient on its own, though; the real identity is established with the JSON-LD Person schema. If you use both, make sure the names match exactly.
Which links should go in sameAs?
Profiles the author genuinely owns, that confirm their identity and are reachable: LinkedIn, professional directory entries, author pages on industry publications, academic profiles. Irrelevant or broken links added to pad the list produce no benefit; what matters is verifiability, not quantity.
Can I declare the organization as the author on corporate blog posts?
Yes. If no single person is responsible, using the Organization type in the author field is far better than leaving a generic username like "admin". But for content that makes a claim to expertise, naming a real person as the author and backing that person's identity with sameAs is a much stronger signal.
Is an author page required?
Not required, but strongly recommended. A page gathering the author's biography, job title, field of expertise and list of publications makes it clear that bylines across different articles belong to the same person, and it becomes the hub of the sameAs chain. The url field in the Person schema should point at that page.
Should I update dateModified on every publish?
Only when the content genuinely changes in a meaningful way. Refreshing the date while nothing has changed comes from wanting to look current in the short term, but it destroys the signal's credibility, and over time the search engine stops paying attention to the field.