Skip to content
SilktideHelp

Author pages and bylines

For editorial and advisory content - guides, analysis, how-tos, research - make it obvious who wrote it, and give that person a stable page that proves they exist. A byline alone is a name. An author page with credentials, a photo of a real person, and links to their public profiles is evidence an assistant (and a skeptical reader) can check.

Throughout this page, suppose Fernwood publishes a guide "How to reconcile corporate card statements," written by Maria Chen, Fernwood's head of accounting products.

This technique applies where a reader would reasonably ask "who wrote this?" Product pages, pricing, and pure navigation do not need bylines; forcing them there looks like theater. Google's own guidance says the same: add accurate authorship where readers would expect it.

Why it works

When several sources say roughly the same thing, answer engines prefer the one they can attribute to a verifiable human - and search quality systems have long weighted the same signals under the name E-E-A-T (experience, expertise, authoritativeness, trustworthiness). Google's helpful-content guidance asks creators directly: is it self-evident who authored this? Do bylines lead to further information about the author?

Authorship helps three audiences at once:

  • AI assistants attribute what they cite. A page whose only voice is an unnamed organization gives them nothing to attribute, and content that cannot be attributed is cited less and trusted less. Silktide's AEO reports judge this directly as Credible expertise shown and Clear who and what this is.
  • Readers decide whether to believe you. A named expert with a track record beats "the Fernwood team" for anything advisory - especially topics that affect money, health, or safety.
  • Engines can resolve identity. links from a Person entity to LinkedIn, a personal site, ORCID, or similar let machines confirm this Maria Chen is the same Maria Chen elsewhere - the same job identity resolution does for organizations in Structured data markup.

Be clear about what this is not: a byline is not a ranking magic word. Google has said bylines are for readers, not a direct ranking factor. The durable value is trust and attribution - which is exactly what answer engines need when choosing whom to quote.

What to build

1. A real byline on every editorial page

Near the top of the article, not buried in the footer:

<p class="byline">
  By <a href="/authors/maria-chen">Maria Chen</a>,
  Head of Accounting Products at Fernwood
  · <time datetime="2026-07-10">Updated July 10, 2026</time>
</p>

Include the role or credential that makes this person the right author for this piece - not a generic job title copied onto every article. The byline links to their author page. Pair it with an honest update date; see Machine-readable dates.

2. A stable author page per person

Give each regular author a URL that will not change: fernwood.example/authors/maria-chen. The page should contain, at minimum:

  • Full name and current role, matching the byline exactly.
  • A short bio that states relevant experience in plain language - years in the domain, what they have built or studied, what they are responsible for at Fernwood. First-hand markers ("I led Fernwood's multi-entity approval redesign") beat resume padding.
  • A real photograph of the person. Stock photos and illustrations read as fabricated authorship - and fabricated authorship is worse than none.
  • Links to verifiable public profiles - LinkedIn, a personal site, conference talks, ORCID for research-heavy authors. These become the sameAs values below.
  • A list of their articles on your site, so the page accumulates evidence over time.

One author page per person, reused everywhere they publish. Do not create a fresh "about the author" block that diverges from the canonical page.

3. Person structured data, connected to the article

Declare the author in on both the article and the author page, and link them. On the article:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to reconcile corporate card statements",
  "datePublished": "2026-05-01T09:00:00Z",
  "dateModified": "2026-07-10T14:30:00Z",
  "author": {
    "@type": "Person",
    "@id": "https://fernwood.example/authors/maria-chen#person",
    "name": "Maria Chen",
    "url": "https://fernwood.example/authors/maria-chen",
    "jobTitle": "Head of Accounting Products",
    "sameAs": [
      "https://www.linkedin.com/in/maria-chen-example"
    ]
  },
  "publisher": { "@id": "https://fernwood.example/#org" }
}
</script>

On the author page, publish a fuller Person (or ProfilePage) that owns the same @id, so every article points at one canonical entity rather than a slightly different copy of Maria on each post. Give that Person a non-empty sameAs wherever the author has public profiles - it is the field that makes identity checkable.

Wire this through your : authors should be records with a bio, photo, and profile URLs, and every article template should pull the byline and JSON-LD from that record. Hand-maintained author blocks drift within a month.

Writing rules that make authorship believable

  • Match the voice to the byline. A piece signed by a practitioner should read like one - concrete, first-hand where true, willing to say what does not work. Ghostwritten executive bylines with no connection to the named person are detectable and discounted.
  • Credentials must be relevant and checkable. "Maria Chen, MBA" on a card-reconciliation guide is weaker than "Maria Chen, who built Fernwood's reconciliation workflow used by 4,000 companies." Link claims you make about the author to evidence on the author page.
  • Disclose AI assistance when a reader would wonder how the piece was made. Google's guidance on AI-generated content asks creators to make the "how" clear; listing "AI" as the author is the wrong answer - name the human responsible, and disclose automation where it substantially produced the draft.
  • Do not invent authors. Fake names, stock-photo "staff writers," and author farms are the authorship equivalent of astroturf review sites. If no suitable human exists for a piece, publish it under the organization and say so - honesty beats a fabricated byline.

Where this technique stops

  • Product and marketing pages rarely need a personal byline; Clear who and what this is is usually satisfied by a consistent organization name.
  • News-style content that appears in Google News has stricter byline expectations - follow Google News policies if that is your channel.
  • Safety-sensitive authorship. Where naming an author creates a real risk, prioritize safety; Google's helpful-content guidance acknowledges this. An organization byline with an About page is better than endangering a person.

How Silktide helps

Last updated

Was this page helpful?