How to Add Author Bios and Expert Profile Pages to Your Site

Your site publishes articles, but none of its pages link to an author or team profile, so readers and search engines can't see who wrote the content or why they're qualified. By the end of this guide you'll have author profile pages at a recognizable URL such as /author/jane-doe or /team, with credentials and social links, linked from every article byline and marked up with Person schema.

By Updated ⏱ 30-60 minutes🎯 Beginner● Medium impactContent
Illustration: Author expertise and bios fix guide
CONTENT · FIX GUIDE Author expertise and bios IMPACTEFFORT TIME30-60 minutes LEVELBeginner

Why it matters

Google's quality rater guidelines ask who created a page and what makes them qualified to write it. That weighs most on health, finance, legal and other YMYL topics. AI answer engines also attach author names and credentials when they cite sources.

An article with a linked author who has a verifiable bio, a job title and sameAs profiles is easier to trust and to attribute than an anonymous post. Readers use bylines the same way: a named expert with a LinkedIn profile makes a guide more credible and more shareable.

✕BeforeArticles show "By Jane" as plain text(or no byline at all), and no page onthe site links to /author/, /authors/,✓AfterEvery article has a byline linking tohttps://example.com/author/jane-doe,which shows Jane's credentials,

What you need

Admin access to your CMS or site code
A short bio, headshot, job title and credentials for each writer
Public profile URLs for each writer (LinkedIn, X, GitHub, ORCID, etc.)
Access to your article template or theme settings

Step-by-step fix

1

Choose a URL pattern for author pages

Pick one consistent path for writer profiles. The audit recognizes links to these patterns:

  • /author/jane-doe or /authors/jane-doe (best for blogs with several writers)
  • /team or /people (a single page listing everyone)
  • /about/jane-doe (an individual page under About)

Paths like /about-us, /contributors or /writers are not recognized. If you already use one of those, add a page at a matching path or rename the slug and set up a 301 redirect.

text
https://example.com/author/jane-doe
https://example.com/authors/
https://example.com/team
https://example.com/about/jane-doe
Pro tip: For more than three regular writers, use individual /author/ pages plus an /authors/ index. A single /team page is fine for small sites.
2

Collect the expertise details for each writer

For every person who writes or reviews articles, gather:

  • Full name and a professional headshot (at least 400x400px)
  • Job title and employer
  • Credentials: degrees, licenses or certifications, with the issuing body
  • Years of relevant experience and notable work
  • Topics they cover
  • Profile links a reader can check (LinkedIn, X, GitHub, ORCID, a speaker page)

Use specific facts. "Certified Financial Planner since 2014, 9 years at Example Co" carries more weight than "passionate finance writer".

Pro tip: If articles are medically, legally or financially reviewed, collect bios for the reviewers too and show a "Reviewed by" line.
3

Build the author profile page

Create the page at the path you chose. Include an H1 with the person's name, the headshot with descriptive alt text, a 100-250 word bio, the credentials list, the social links, and a list of their articles. Add Person JSON-LD in the page <head>.

Use the sameAs property for the social profiles, jobTitle for the role, hasCredential or knowsAbout for expertise, and worksFor for the organization.

html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://example.com/author/jane-doe#person",
  "name": "Jane Doe",
  "url": "https://example.com/author/jane-doe",
  "image": "https://example.com/images/jane-doe.jpg",
  "jobTitle": "Head of Security Research",
  "worksFor": {"@type": "Organization", "name": "Example Co", "url": "https://example.com"},
  "knowsAbout": ["Web application security", "OWASP Top 10"],
  "hasCredential": {"@type": "EducationalOccupationalCredential", "name": "OSCP", "recognizedBy": {"@type": "Organization", "name": "OffSec"}},
  "sameAs": ["https://www.linkedin.com/in/janedoe-example", "https://github.com/janedoe-example"]
}
</script>
Pro tip: Keep the @id stable. You'll reference it from article schema so search engines connect each article to the same person.
4

Link the byline on every article to the author page

Edit your article template so the byline is a real <a href> link to the author page, not plain text. Place it near the title, and optionally add a short author box with a 1-2 sentence bio at the end of the article. The link must be in the server-rendered HTML.

A link injected later by JavaScript may not be seen by crawlers.

html
<p class="byline">By <a href="/author/jane-doe" rel="author">Jane Doe</a>, Head of Security Research · Updated <time datetime="2026-01-15">15 Jan 2026</time></p>

<aside class="author-box">
  <img src="/images/jane-doe.jpg" alt="Jane Doe" width="80" height="80">
  <p><a href="/author/jane-doe">Jane Doe</a> is an OSCP-certified security researcher with 10 years of penetration-testing experience at Example Co.</p>
</aside>
Pro tip: Also link /authors/ or /team from your footer or About page so the profiles are reachable from anywhere on the site.
5

Reference the author in your Article schema

In each article's Article or BlogPosting JSON-LD, set author to a Person object with the same name, a url pointing to the author page, and the matching @id. Google uses author.url to tell authors with the same name apart.

html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Harden Your Login Form",
  "datePublished": "2026-01-10",
  "dateModified": "2026-01-15",
  "author": {
    "@type": "Person",
    "@id": "https://example.com/author/jane-doe#person",
    "name": "Jane Doe",
    "url": "https://example.com/author/jane-doe"
  },
  "publisher": {"@type": "Organization", "name": "Example Co"}
}
</script>
6

Check the result

Open a published article and view the page source (Ctrl+U or Cmd+Option+U). Search for href="/author (or /team, /people, /about/) to confirm the link is in the raw HTML. Click through to make sure the author page returns 200, isn't redirected to the homepage and isn't set to noindex.

Then run the article URL through Google's Rich Results Test, confirm the author is detected, and re-run the audit.

text
curl -s https://example.com/blog/harden-login-form | grep -Eo 'href="[^"]*/(author|authors|team|people|about/[a-z-]+)[^"]*"'
Pro tip: Use curl or view source, not DevTools Elements. DevTools shows the DOM after JavaScript runs, which can hide a missing server-side link.

Platform-specific notes

WordPress

Author archives are built in at /author/username. Fill in Users > Profile > Biographical Info and set a display name. In Yoast SEO, check Yoast SEO > Settings > Advanced > Author archives and make sure they aren't disabled, because disabling them redirects author links to the homepage. In Rank Math, check Rank Math > Titles & Meta > Authors. Change ugly usernames by editing the user's nicename or with a plugin, since the slug comes from the login name. Add social URLs in the Yoast or Rank Math contact fields on the user profile so they're output as sameAs.

Shopify

Blog articles show the author name as plain text, and Shopify has no author pages. Go to Online Store > Pages > Add page, create a page with the URL handle "team" (it lives at /pages/team, which the audit recognizes), then edit the article template (sections/main-article.liquid in Dawn) and wrap the author in a link, e.g. <a href="/pages/team#{{ article.author | handleize }}">{{ article.author }}</a>.

Wix

Wix Blog writer profiles live under /profile/..., which isn't recognized as an author page. Create a regular page (Pages & Menu > Add Page) and set its URL slug to "team" or "authors" under Page Settings > SEO basics. Link to it from the blog post page layout or from each post's intro, and from the site footer.

Webflow

Create a CMS Collection named "Authors" with the slug "author" and fields for name, photo, job title, bio, credentials and social links. Add a Reference field "Author" to Blog Posts, then on the Blog Post template bind a link block to the referenced author's page. Paste Person JSON-LD into the Authors template's custom code (Before </head>) using CMS field embeds.

Next.js

Add a dynamic route such as app/author/[slug]/page.tsx with generateStaticParams for each author, and render the byline with next/link, e.g. <Link href={`/author/${post.author.slug}`}>. Next/link outputs a real <a href> in server-rendered HTML. Inject Person and BlogPosting JSON-LD with a <script type="application/ld+json"> tag in the page component.

Check that it worked

✅ How to verify

  • View the source of any article and confirm a link to /author/, /authors/, /team, /people or /about/name is present in the raw HTML.
  • Open the linked author page and confirm it returns HTTP 200, isn't noindexed, and shows the name, credentials, experience and working social links.
  • Paste an article URL into Google's Rich Results Test or validator.schema.org and confirm the author Person has the correct name and url.
  • Re-run the site audit and confirm the check reports that author or team profile pages are linked.

⚠️ Common mistakes

  • Using an unrecognized path such as /about-us, /contributors or /writers. Use /author/, /authors/, /team, /people or /about/name instead.
  • Showing the byline as plain text, or adding the author link with client-side JavaScript so it's missing from the HTML crawlers fetch.
  • Disabling WordPress author archives in an SEO plugin, which redirects every author link to the homepage.
  • Writing vague bios ("loves marketing") with no checkable credentials, job titles or external profile links.

Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.

Check my site free

FAQ

Do author bios actually help SEO?

Author bios aren't a direct ranking factor. They do support the experience, expertise and trust signals Google's quality raters look for, especially on YMYL topics. They also give search engines and AI assistants a clear, linkable entity to attribute content to.

Should I use individual author pages or a single team page?

With several regular writers, give each one a page at /author/name so their articles are grouped and each Person has its own URL. A small site with one or two writers can link bylines to anchors on a single /team page.

What should an author bio include?

Include the full name, a headshot, the job title and employer, relevant credentials with the issuing body, years of experience, the topics covered, and links to public profiles such as LinkedIn. Keep it factual and around 100-250 words on the profile page, with a 1-2 sentence version under each article.

What if my articles are written by the company, not a person?

Name a real person where you can, such as the writer or a subject-matter expert who reviewed the article, and link to their profile. If content is genuinely team-produced, link the byline to a /team page that lists the people involved and their qualifications.