How to Create an Author Page: Bylines, Bio, ProfilePage Markup and Article Author Links

What Is an Author Page?

An author page is a page on your own site about one person who creates content there, which every byline by that person links to.

It answers the “Who” in Google's “Who, How, and Why” framework. Google's guidance asks whether it is “self-evident to your visitors who authored your content”, whether pages carry a byline where one might be expected, and whether bylines lead to background about the author and “the areas they write about” (Google). An author page is different from an executive bio sent to journalists (see how to write an executive bio for media), though the facts should match, and different from Person markup, which is the code layer on top of the page (covered in depth in how to add Person schema).

What it does not do: Google has not said author pages are a ranking factor, and our report on bylines and credibility signals sets out what Google does and does not claim. For the underlying concept, see what E-E-A-T is.

How to Create an Author Page at a Glance

Time: one to two hours per author for content, plus template work once for the site (our estimate). Tools: your CMS, Google's Rich Results Test, Search Console. Cost: none. Skill level: beginner for the page; intermediate for templates and markup.

What You Need Before Starting

• A list of everyone who has a byline on the site, including past staff and guest contributors.
• Each author's agreement to a public page, a real photo they approve, and their verified role, credentials and experience.
• The URLs of each author's official profiles elsewhere (for example LinkedIn, a university page, a professional register).
• Access to the CMS template that renders bylines and article markup, or a developer who has it.
• Access to Google Search Console for the site.

Step 1: Decide Who Gets a Page and How to Handle Unsigned Content

List every real person who is shown as an author, and decide which content is published under the organisation instead.

Why: Google's author markup guidance says to use “the Person type for people, and the Organization type for organizations”, and that if the author is an organization you could link to its home page (Google, author markup best practices). Unsigned company content does not need an invented person. Expected result: a list of named authors and a rule for organisation-authored pages. Common mistake: creating a persona to make corporate content look personal. Google says fabricating creator profiles “is a form of deception” (Google).

Step 2: Choose One Stable URL per Author

Create one URL pattern for author pages, such as /authors/jane-doe or /team/jane-doe, and use only that URL for each person everywhere.

Why: Google's Article documentation describes author.url as a page that “uniquely identifies the author” (Google). Two pages for one person (a team page and a separate CMS author archive, say) dilute that. If your CMS generates an author archive automatically, either make that archive the author page by adding the bio to it, or point bylines and markup to one chosen page and treat the other as a duplicate (see what a canonical URL is). Expected result: one indexable URL per person. How to verify: search your site for the author's name and confirm only one profile page exists. Common mistake: changing the URL when a CMS theme changes, which breaks every byline link and author.url value.

Step 3: Write the Visible Content

Write the page for a reader who wants to know whether to trust this person on this topic. Include:

• Name and current role, exactly as used in bylines.
• A real photo the author approved. Google's ProfilePage guidance says that if there are no images, “don't include a default image, icon, or placeholder image” in the markup (Google).
• A short factual bio in the third person: experience, credentials you can verify, and the areas they write about.
• Topics covered, so a reader can see the match between the person and the article.
• Links to official profiles elsewhere, which you will also use as sameAs.
• A list of their articles, newest first, so the page shows what they have actually written.
• A way to reach the editorial team or a link to your editorial or corrections policy.

Expected result: a page a stranger could use to check who the author is. Common mistake: credentials that cannot be verified, or a bio that is marketing copy for the company.

Step 4: Link Every Byline to the Author Page

Change the article template so each byline is a visible link to that author's page, and show the publication date next to it.

Why: Google's question is literal: do bylines “lead to further information about the author”? Discover's transparency policy also asks news sources for “clear dates and bylines” (Google Discover policies). With several authors, link each name separately. Expected result: every byline on the site resolves to the right author page. How to verify: crawl or sample articles and check each byline link returns HTTP 200 and the correct person. Common mistake: a byline in plain text with the author page reachable only from a staff list.

Step 5: Add ProfilePage Markup With a Person as mainEntity

Add ProfilePage JSON-LD to the author page with a Person as mainEntity, using values that appear on the visible page.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "dateModified": "2026-10-09",
  "mainEntity": {
    "@type": "Person",
    "@id": "https://example.com/authors/jane-doe#person",
    "name": "Jane Doe",
    "jobTitle": "Senior Editor",
    "description": "Writes about logistics and supply chains.",
    "image": "https://example.com/images/jane-doe.jpg",
    "sameAs": [
      "https://www.linkedin.com/in/example-jane-doe"
    ]
  }
}
</script>

Rules from Google's ProfilePage documentation: the page's “primary focus” must be a single person or organisation “affiliated with the overall website”; mainEntity is required; name should be the real name; description is for “the user's byline or applicable credential”; and dateModified should ideally represent only human-edited changes to the profile. Google describes ProfilePage as helping it understand creators; it does not promise a special search appearance for company author pages. For full Person properties and how to link a person to your organisation, follow our Person schema guide. Common mistake: marking up facts that are not on the visible page.

Step 6: Point Article Author Markup at the Page

Update the Article, NewsArticle or BlogPosting markup on every article so author is a Person with the author's name and url set to their author page.

"author": [{
  "@type": "Person",
  "name": "Jane Doe",
  "url": "https://example.com/authors/jane-doe"
}]

Rules from Google's author markup best practices: include every author shown on the page; list each author in their own entry rather than “Willow Lane, Regula Felix” in one field; put only the name in author.name, not a job title, publisher name, honorific or “posted by”; and use valid URLs. Google adds that it “can understand both sameAs and url when disambiguating authors.” See how to add Article structured data for the rest of the markup. Expected result: author.url on every article matches the author page URL exactly. Common mistake: a template that outputs the author's display name with a title, such as “Dr Jane Doe, Senior Editor”, in name.

Step 7: Test, Deploy and Keep It Current

Run the author page and one article through Google's Rich Results Test, fix any critical errors, deploy, then inspect the live URLs in the URL Inspection tool.

Why: Google's ProfilePage steps are to validate, deploy a few pages, and make sure the page is not blocked by robots.txt, noindex or a login (Google). Keep it current: update role and bio when they change; when an author leaves, keep the page and their article list and mark the role as past (our recommendation), so old bylines still lead somewhere true. Expected result: the test detects a ProfilePage item, and URL Inspection shows the page can be indexed. Common mistake: deleting author pages for departed staff, which leaves every one of their bylines pointing at a 404.

How to Verify It Worked

• Rich Results Test: detects a valid ProfilePage on the author page and an Article with an author that has a url on an article.
• URL Inspection: the author page is indexable and Google can fetch it.
• Byline links: a sample of articles shows each byline linking to the correct author page with HTTP 200.
• Consistency: the name in the byline, on the author page, in author.name and in mainEntity.name is identical.

How to Choose the Right Author Setup

Common Problems and Fixes

What Not to Do

• Do not invent authors, use AI-generated headshots or claim credentials that are not real. Consequence: Google says this is “a form of deception” that makes a page untrustworthy. Correction: real people, real photos, verifiable facts.
• Do not merge authors into one name field. Consequence: Google's guidance says to list each author separately. Correction: one entry per author.
• Do not use the wrong type. Consequence: Google says not to use Thing, or Organization for a person. Correction: Person for people.
• Do not use a logo as a person's profile image. Consequence: Google says not to include a placeholder or icon. Correction: a real photo or no image.
• Do not expect a ranking change. Consequence: misplaced expectations. Correction: treat the page as transparency for readers and clarity for search engines.

Frequently Asked Questions

Sources and Methodology

This guide is built from Google Search Central documentation read on October 9, 2026: the helpful content guidance (last updated October 5, 2026), the Article structured data page and its author markup best practices, and the ProfilePage structured data page (both last updated September 8, 2026), plus Google's Discover content policies. We did not build or test an author page for this guide, and we make no claim about ranking effects; Google does not publish one. The time estimate and the advice on departed authors are ours. Markup examples use example.com placeholders.

1. official Google Search Central, Creating helpful, reliable, people-first content. Who/How/Why; bylines; fabricated creator profiles. Read October 9, 2026.
2. official Google Search Central, Article (Article, NewsArticle, BlogPosting) structured data, including author markup best practices. Read October 9, 2026.
3. official Google Search Central, Profile page (ProfilePage) structured data. Read October 9, 2026.
4. official Google Search Help, Discover content policies. Transparency policy. Read October 9, 2026.
5. official Google, Rich Results Test and Search Console Help, URL Inspection tool. Read October 9, 2026.