Author Pages and Bylines: 2026 SEO Guide
Google's page "Creating helpful, reliable, people-first content" asks three short questions about who made your content:
- "Is it self-evident to your visitors who authored your content?"
- "Do pages carry a byline, where one might be expected?"
- "Do bylines lead to further information about the author or authors involved, giving background about them and the areas they write about?"
My view: most sites pass the first question and fail the third. The name sits at the top of the post, but it often leads nowhere useful, and the real work is the author page that name should link to. That page is where a byline keeps its promise.
This matters most for anyone who publishes advice under a company name, and for publishers, clinics and law or finance firms with named experts. Our E-E-A-T and helpful content guide covers the wider trust framework.
Do bylines and bio pages affect SEO?
Not as a switch you can flip: Google's helpful content page "strongly" encourages accurate authorship, such as bylines where readers expect them, but it also says E-E-A-T is not a ranking factor on its own. Treat bylines and the bio page behind them as trust assets, built for readers who check who wrote the advice.
Google writes: "We strongly encourage adding accurate authorship information, such as bylines to content where readers might expect it." The same page adds, "While E-E-A-T itself isn't a specific ranking factor," using a mix of factors that spot good E-E-A-T is useful. Our take: never promise a ranking lift from a byline, and read our guide to building real, verifiable author identity.
What should a byline say, and where should it link?
Show the real name of the person who wrote the post, near the title, and make the name a link. Google's Article markup page lists a social media page, an about me page or a bio page as fair targets, and our advice is to point it at a page on your own site.
Google's Article page, last updated September 8, 2026, adds: "If the URL is an internal profile page, we recommend marking up that author using profile page structured data." Our take: point the name at the author page on your own site, because you do not control a social profile and it rarely explains why the person knows your topic. Our Google News guide lists the extra trust pages news sites need.
What belongs on an author page?
In our view, a good bio page answers the three "Who" questions in a few lines. It shows the real name, the role, the topics the person covers and why they know them, and it adds credentials a reader can check, real outside profiles, a real photo or none, their posts and a way to reach them.
Google's expertise questions mention "background about the author or the site that publishes it, such as through links to an author page or a site's About page". The third "Who" question also asks about "the areas they write about", and in our view most bio pages skip that part. Our minimum list, as opinion:
- The role, the employer and the topics they cover.
- Credentials or licenses with enough detail to check.
- Links to real outside profiles, for example a LinkedIn profile tuned with our people search guide.
- A list of their posts and a way to contact them or the editor.
Lawyers also face bar advertising rules on what a bio may claim, covered in our law firm SEO guide.
Is an author archive the same as an author page?
No, in our view: an archive that lists post titles under a name answers none of the three "Who" questions, because it shows what someone published, not who they are or why to trust them. The fix is simple: put the bio at the top of the archive and keep the posts below it.
Google's ProfilePage page covers that case: if a profile page also shows recent activity, its markup can point to each article by its URL. Every byline is also an internal link repeated on every post, and our internal linking strategy guide explains how internal links pass value, and why links in the body count for more than repeated ones.
How do you mark up authors in Article structured data?
Google's Article page says to list every author shown on the page, each in their own author field, and to put only the name in the name field. Use the Person type for people and Organization for companies, never Thing, and add a url or sameAs link. Keep the job title and any prefix like Dr out of the name.
Google's Article page accepts three schema.org types, Article, NewsArticle and BlogPosting. It lists no required properties, but for authors it strongly recommends the type and url or sameAs properties. Its other rules:
- Leave "posted by" and the publisher name out of author.name.
- Put the job title in jobTitle and a prefix in honorificPrefix.
- Put the publisher's name in the publisher field.
Google adds that it "can understand both sameAs and url when disambiguating authors." Our advice: use url for your own bio page and sameAs for the outside profiles it lists. Our entity SEO guide explains how sameAs links tie one identity to its verified profiles, and our JSON-LD guide shows how to add markup.
What is ProfilePage markup, and when should you use it?
ProfilePage is markup for a page about one person or organization, and Google says it helps Google Search "understand the creators that post in an online community". Use it on the bio page your bylines point to. It needs one main entity, a Person or an Organization, with a name, and dates, an image and outside links are recommended.
Google's ProfilePage page, also last updated September 8, 2026, sets one firm rule: "The primary focus of the page must be a single person or organization that is affiliated with the overall website." Its valid examples include "An author page on a news site" and an employee page on a company website. A store's main home page does not qualify.
Google also says dateModified should ideally reflect only human edits, and interactionStatistic should only count activity on the site that hosts the page. Google suggests checking the markup with the Rich Results Test and then watching for issues in Search Console. Our guide to debugging structured data errors covers testing.
Which author fields should you get right first?
Start with the author field in your Article markup, because it carries the name, type and link for every writer. Keep the publisher name in the publisher field, as Google's Article page asks, not in the author name. On the author page, mainEntity is the field Google requires, and the table shows what Google says and what we would do.
The third column paraphrases Google's Article and ProfilePage pages, both saved on October 6, 2026. The fourth is our opinion.
| Field | Where it goes | What Google says | Our advice |
|---|---|---|---|
| author | Article markup | Person or Organization, following the author markup best practices | List every visible author, one field each. |
| author.name | Article markup | Only the author's name, with no other details | Match the visible byline name exactly. |
| author.url | Article markup | A page that uniquely identifies the author | Point it at your own bio page. |
| sameAs | ProfilePage or Article markup | Other external profiles or home pages, and an alternative to author.url | List only real profiles that match the name. |
| mainEntity | ProfilePage markup | Required, a Person or Organization, Person if unknown | Set it to the person the page is about. |
| image | ProfilePage markup | No default, icon or placeholder image when none exists | Use a real photo or leave it out. |
How should you show the date on a post?
Show a visible, labeled date near the byline, such as "Published" or "Last updated", and make the datePublished and dateModified fields in your Article markup match it. Google's date guidance also rules out future dates and the date of an event the page describes. Change the updated date only after a real edit.
Google's page on byline dates, last updated December 10, 2025, says: "A byline date is the date that Google estimates that the web page was updated or published." The helpful content page lists this warning sign: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" Our content refresh guide covers when an old post has earned a new date.
How should you handle guest writers, teams and posts with several authors?
Treat a guest writer like staff: a real name, a bio page on your site and a place in the author markup. If several people wrote a post, Google asks for each in their own author field. If a company truly wrote it, Google's Article page suggests the Organization type and a link to its home page.
Our view: a byline like "Admin" or "Staff" answers none of the "Who" questions, and a guest byline that links nowhere is a common weak spot. If you cannot give a guest a bio page, name the editor who reviewed the post. Our guide to Google's site reputation policy explains the rules for third-party pages on a host site.
Should you disclose AI help on the byline?
Disclose it where readers would expect to know. Google's helpful content page says AI or automation disclosures are useful where someone might wonder how the content was made. What you must never do is invent a human author for AI text, because Google treats fabricated creator profiles as a form of deception.
Google's page says "Fabricating creator profiles" is "a form of deception", and that deception "is a signal of a low-quality page." Our take: if a person used AI for a draft, then checked, rewrote and stands behind it, that person signs it, with a short note on how it was made. If no person checked it, no person should sign it. Our roundup of AI tools for SEO content also insists on a human editing pass.
What does this look like for businesses in the US, Europe and Korea?
The rules are the same everywhere, and only the details shift. A US tax firm leads with licenses, a European software company handles guest writers and a Korean clinic has doctors sign their articles. In each case, the byline names a real person and links to a page that shows who they are.
For example, a Denver tax preparation firm has articles written by named CPAs. Each CPA's bio page states the license, the issuing state of Colorado and their tax topics, and the Article markup lists each CPA as a Person with the role in jobTitle.
For example, an Amsterdam software company in the Netherlands runs a blog with guest posts from partner engineers, and each guest gets a short bio page in English and Dutch, with a named company editor shown as reviewer.
For example, a Seoul dermatology clinic in South Korea publishes skin care articles signed by its doctors, and each doctor's page lists their specialty and training. Our healthcare SEO guide argues that clinicians should write or review clinical pages. If Naver matters to you too, our Naver guide covers Korean search.
Where should you start with your author pages?
Start with a list: export every byline name on the site, merge duplicates and retire any name that is not a real person. Then give each person an author page that answers the three "Who" questions. Point every byline at it, fix the author field in your Article markup and add ProfilePage markup to the bio page.
Make each fix in the byline template, which reaches every post at once, and our technical SEO audit guide explains why fixes grouped by template are the ones that ship. Then click the byline on your most read posts and confirm each lands on a bio page that answers all three questions.
Frequently asked questions about bylines
Can a writer use a pen name on a byline?
Be careful here: Google's helpful content page lists "made-up names" among the ways to fabricate creator profiles that make content look written by human experts. A pen name used by a real person who wrote the post is a different case, but it weakens the "Who" answer. Our view: if you use one, state that on the bio page, describe the real background honestly and never attach credentials no one holds, and for advice on health, money or law, use the real name.
Does every page on a site need a byline?
No: Google's question asks whether pages carry a byline "where one might be expected". In our view, readers expect one on articles, guides, reviews and news, but not on a product page, a contact page or a pricing table. Our rule of thumb: if the page gives advice or opinion that a person wrote, it should name that person. If the page is plain company information, such as a returns policy, the company stands behind it, and your About page already answers who that is.
Does an author page need a photo?
The Google pages cited here do not require one. Google's ProfilePage page lists image as a recommended field, and it says to leave out a default image, icon or placeholder when there is no real photo. The helpful content page also names AI-generated headshots as one way to fabricate a creator profile. Our view: a real, recent photo helps readers trust the page, and a stock photo does the opposite, but if the writer does not want a photo, leave it out.
What should happen to a bio page when a writer leaves?
Our view: keep it live, because their posts still carry their name and readers who click the byline should still learn who wrote them. Update the page to say the person no longer works there, but never swap their name for a current employee on old posts, because that makes the byline false. If a current expert reviews and updates an old post, add them as a reviewer, keep the original author named and change the updated date only if the content changed.
Can a writer have a bio page on several sites?
Yes: a writer who contributes to several sites can have a bio page on each. Google's ProfilePage page says the page must focus on a single person or organization affiliated with the site, and in our view a regular contributor can fit that. Our advice: keep the name the same everywhere and connect the pages through the sameAs field, which Google describes as the URL to other external profiles or home pages. Write a fresh bio for each site rather than pasting the same text.
How many authors can one post list in the markup?
Google's Article page sets no number, but it says all the authors presented as authors on the page should also be in the markup, each in their own author field. What matters is that the markup and the visible byline agree. Our view: list the people who did real work on the post, such as the writer and an expert who shaped it. A long list of names that readers cannot connect to the content helps no one. Match their order too.
Does a "reviewed by" line count as authorship?
Not by itself, in our view: Google's author rules cover the people a page presents as authors, and a reviewer plays a different role. A "reviewed by" line is still worth adding on health, legal and money topics, as long as the reviewer actually read and checked the post. Give the reviewer a bio page too and link their name to it, but do not list a reviewer as an author in the Article markup unless the page shows them as one.
Should author archive pages be indexed?
None of the Google pages cited here takes a position. Our view: index the archive only if it carries a real bio at the top and the person has written enough to make the page useful. A bare list of titles adds little that the posts do not already show. If you merge the bio and the archive into one page, that page is usually worth indexing. Thin archives for guest writers with one post can stay out of the index.
Will ProfilePage markup show anything special in search results?
Google does not promise it will: both the Article and ProfilePage pages say "Google does not guarantee that features that consume structured data will show up in search results." The ProfilePage page describes the markup as a way to help Google Search understand creators. Our view: add it because it helps Google understand the bio page and costs little, not because you expect a new feature. Judge the work by whether the markup is valid and every byline links to the right page.
Should the byline show a degree or job title next to the name?
On the visible page, yes, if it helps the reader: a name followed by "CPA" or "Dermatologist" tells readers why to trust the post. In the Article markup, though, keep the name field to the name alone. Google's Article page says to put the job title in jobTitle and an honorific in honorificPrefix or honorificSuffix. Our view: keep the visible title and those fields in step when the person changes roles, and never add a title to the name field to look more expert.