Should a blog byline use Person or Organization?
Use Person when a named individual wrote the article and Organization when the editorial organization owns the byline. Keep visible and structured authors identical.
Written for a small company or solo publisher choosing accurate visible bylines and Article author markup for a maintained technical blog.
Key facts
- Google recommends using Person for individual authors and Organization for organizational authors.
- Every visible author should appear as a separate author in Article markup.
- The publisher belongs in the publisher property rather than inside author.name.
A useful rule: make each important claim understandable and verifiable without requiring the reader to reconstruct your meaning from the rest of the page.
Choose the author readers can actually identify
Use a Person byline when a named individual researched, wrote, and owns the article's claims. Use an Organization byline when a maintained editorial team publishes under a shared identity and no individual is presented as the writer. Do not invent a staff persona to make a page look personal. The visible byline should match the Article markup exactly. A reviewer can appear separately when the site has a real review process, but review does not replace authorship. The choice is an accountability decision, not an SEO tactic. Readers should know who can correct the page and what expertise supports the work.
- Document who wrote, fact-checked, reviewed, and published the article.
- Use the real public editorial identity rather than a keyword-rich author label.
- Provide a corrections or contact path from the author or organization page.
Keep author.name clean
Google advises placing only the author's name in `author.name`. Do not include “Posted by,” the publisher, a credential, or a job title in that field. Use `jobTitle` for the role and `publisher` for the publishing organization. If several people are visible co-authors, create a separate author object for each instead of joining their names into one string. Use a stable URL for a public profile that explains the author's background and lists relevant work. When the author is the organization, link to the organization's accurate about page or home identity.
- Separate name, job title, profile URL, and publisher into their proper properties.
- Keep spelling and capitalization consistent across the byline, profile, and JSON-LD.
- Remove honorifics and promotional descriptors from the name field.
Sources: 1
Make the visible byline useful
Show the author near the title with publication and update dates. Link the name to a page that tells the reader who is responsible, which subjects the author covers, and how sources are checked. A generic “Admin” profile or empty author archive provides little accountability. For an organization byline, explain the editorial process and ownership without pretending that a committee personally tested something it did not. Add a reviewer only when a named person performed a real review. High-stakes claims need the appropriate qualified source or professional review regardless of how polished the author schema looks.
- Include a short role that describes editorial responsibility, not a marketing slogan.
- List relevant authored work and correction contact information on the profile.
- Keep first-person claims out of organizational articles unless the underlying test and actor are named.
Separate author from publisher identity
The publisher is the organization responsible for the site or publication. A person can author the article while the organization publishes it. Connect both to stable IDs in the JSON-LD graph so the Article refers to the same organization used by the site-wide Organization node. Do not duplicate the brand as part of every author name. When a solo publisher is both author and business owner, the Person and Organization can still be distinct entities with a real relationship. Clear identity prevents markup from implying that a person is a company or that a company is a person.
- Reuse one organization `@id` across the website and article graph.
- Use a Person profile URL for the author and the canonical organization URL for the publisher.
- Keep logos and social identities on the organization rather than the person unless they truly belong there.
Audit bylines across the archive
Export every public article with its visible author, structured author type, author URL, and publisher. Flag missing profiles, joined co-author names, inconsistent spellings, and pages where markup lists someone not visible. Review whether an old employee or contractor should remain credited and whether the profile still provides accurate context. Preserve truthful authorship after staff changes. Update the modification date only when the page's visible provenance or substantive review changes materially. The audit should make ownership clearer for readers; it should not erase contributors to make the archive look uniform.
- Require visible authors and structured authors to match in automated tests.
- Check that every profile and organization URL returns a successful canonical page.
- Keep a record of authorship corrections and editorial review changes.
Put it to work
Find the highest-impact fix on your site.
Compare the visible byline with Article author type, name, profile URL, publisher, and page dates.
Audit article authorshipSources
- 1.Google Search Central: Article structured dataChecked 2026-07-26
- 2.Google Search Central: Organization structured dataChecked 2026-07-26