Separate the roles before choosing field values
Start with the credit line and the editorial record for this particular post. A company domain, a reviewer’s approval or a writing contract does not by itself establish authorship. Decide who wrote the answer and who publishes it, then compare the decision with the visible page. If the two disagree, resolve the credit before completing the fields.
| Role or field | What to match | Decision to make |
|---|---|---|
| Visible byline | The credited writer or writing organization | Does it accurately describe who wrote this post? |
author | The author named in that byline | Use a person, an organization or separate authors as appropriate |
| Author identity link | A page identifying that same author | Does the destination distinguish the credited author? |
publisher | The organization publishing the post | Keep this role separate from writing credit |
| Reviewer or contractor | Their actual contribution | Include as an author only when they really are a credited author |
Google's Article guide permits “Person” or “Organization” for author. Its author.url description calls for a page that “uniquely identifies the author of the article.” It also accepts url and sameAs “when disambiguating authors.” Google's Article author guidance
An identity page should support the name actually used in the credit. Do not fill an empty profile with invented qualifications, job history or expertise. If responsibility has been assigned to an editorial organization, confirm that the organization really exists and can be identified; a convenient label is insufficient. The content and evidence responsibilities can be recorded alongside a technical answer evidence brief.
Schema.org defines publisher as “The publisher of the article in question.” For a post published by a company, use that publishing organization. This does not make the company the author of every post on its website. Schema.org publisher definition
The current Google Article guide states “There are no required properties”; publisher is a Schema.org property, not a Google Article required field. Google's Article property definitions
Read a placeholder example as a role map
Suppose a technical answer is written collectively by Example Co. Technical Editorial Team and published by Example Co. All names and URLs below are placeholders, not real entities or author profiles. The field snapshot shows roles only, not a complete Article object.
Visible credit: Written by Example Co. Technical Editorial Team. Published by Example Co.
| Field path | Placeholder value |
|---|---|
author.@type | Organization |
author.name | Example Co. Technical Editorial Team |
author.url | https://example.com/technical-editorial-team/ |
publisher.@type | Organization |
publisher.name | Example Co. |
publisher.url | https://example.com/ |
The two organizations can have different names and identity pages because they carry different responsibilities. The team page identifies the credited writing organization; the company page identifies the publishing organization. Neither destination needs an invented biography to justify the distinction.
Now change the hypothetical credit to “Written by Author A and Author B.” If these are the credited individual writers, create separate Person entries with their respective names and genuine identity links. Do not retain the team as sole author merely because it is a familiar label. For coauthored posts, Google says to “list each author in their own” author field. Google's guidance on multiple authors
A reviewer who checks calculations can receive a visible review credit without automatically becoming an author. Likewise, an outside writer can be an author when that reflects the actual contribution and agreed credit; purchasing the work does not settle the field by itself. Ask what role each participant performed and what credit readers will see.
Check the visible page against the fields
Review one post at a time, retaining the rendered credit and the corresponding field values together. A reusable acceptance checklist is:
- Confirm the byline reflects the actual credited writer or writing organization. Record unresolved credit questions rather than inventing a name.
- Compare every author name and type with the visible credit. Check that every credited coauthor has a separate entry.
- Open each identity link. Confirm that it identifies the same author, and that an organization’s link has not been substituted for a person’s profile.
- Confirm the publisher is the publishing organization. Check whether any publisher name has slipped into an author’s name as extra text.
- Keep review credit and other contributions accurate. Recheck authorship if the visible credit changes, using a source verification and update record.
A parser can check whether fields are readable; the editorial comparison checks whether their roles are true. Treat successful validation as a technical finding, not a prediction of indexing, search appearance, AI citations or rankings.
Want to see how AI engines describe your brand today?
Get a free growth audit