How to use an author page and a blog byline

An author page is where a reader can see who stands behind a set of articles. A blog byline is the credit on the article itself, next to the date, linking to that page. The job of both is identification. They are not a badge you add because a checklist said E-E-A-T wants a face.

What is an author page?

Readers use an author page to decide whether to trust the next article. They look for a name they can recognize, a role that explains why this person or this company would know, and links to other pages that person signed. A page that is only a keyword paragraph (“Jane writes about async standup SEO, sprint retro SEO, and kanban SEO”) tells them nothing they can check.

Many author-page SEO guides treat the URL as a ranking object: add a photo, add social profiles, add Person schema, repeat the head term in the bio. The photo and the schema are fine when they describe someone real. The head term in the bio is the same stuffing problem as a keyword in alt text. The page’s purpose is the person or the company, which is why it belongs in the same family as an SEO content audit label. If the URL does not help a reader who arrives directly, it should not be dressed up to collect queries.

A byline is the short version of that page, placed where the article’s date already is. “By Northwind” or “By Priya Shah” is enough on the article. The explanation lives one click away. A byline that is an image of a signature, with no text, fails the same way a steps-only JPEG fails: the name is not in the HTML.

What E-E-A-T actually asks

E-E-A-T is Google’s shorthand for experience, expertise, authoritativeness, and trustworthiness. In the helpful-content guidance, trust is the important part. The others contribute to it. A page does not have to perform all four. Some pages are useful because the writer did the thing. Some are useful because they explain a method carefully. Google also says E-E-A-T is not itself a single ranking factor. Systems use a mix of signals that can identify helpful content. You cannot paste “E-E-A-T” onto a template and call the work done.

The “who” questions on that page are practical. Is it obvious who created the content? Does the article carry a byline where a reader would expect one? Does the byline lead to more about that author, including what they know? Accurate authorship information is what they encourage. The answer engine guide talks about being quotable. This page is about being identifiable. An answer engine that names a source is naming someone. If that someone is fictional, the citation inherits the fiction.

Main content still does the job of the article. An author box in the sidebar does not repair a procedure that is wrong. Google’s quality discussion treats the main content, the part that fulfills the page’s purpose, as central. Effort, originality, skill, and accuracy are the helpful content attributes for that main content. The byline supports trust. It does not substitute for the steps, the sources, or the scope you already set in the content brief.

Invented experts are a trust failure

The same helpful-content page tells site owners to avoid deceptive authorship. Fabricating a creator profile, including with an AI-generated headshot, a made-up name, or false credentials, so the content looks as if a human expert wrote it, is described there as deception. Deception makes a page untrustworthy to people and to Google’s automated quality systems, and it is called a signal of a low-quality page.

This shows up on sites that publish faster than they have editors. A model drafts a standup guide. Someone adds “By Maya Ellison, certified agile coach” and a portrait that was generated for the purpose. Maya is not on the team. The certificate is not real. The author page repeats the story and links to the same articles, which makes the fiction look consistent. Consistency is not evidence. A reader who emails Maya gets nothing back. An answer engine that says “according to Maya Ellison” is quoting a mask.

A photo of a real colleague, used with their agreement, is ordinary. A company logo next to the company name is ordinary. An empty byline on a page where readers do not expect one, such as a changelog, can be ordinary. The failure is the invented person. If you do not have a named expert, publish as the organization. That is more trustworthy than a costume. A real byline also does not make a set of near-duplicate pages helpful. That set is scaled content abuse when it exists to catch queries.

When the author is a person, and when it is the company

Use a person when that person will actually answer for the article. They reviewed the facts, they can correct a step, and they are willing to have their name on it. The author page then says what they do at the company, which topics they handle, and which articles carry their byline. First-hand experience, if they have it, belongs here as a concrete note: “Priya has run this standup with a six-person team since 2023,” if that is true. A sentence you cannot support does not become experience because it sits in a bio. If it depends on someone else’s document, cite that document beside the sentence.

Use the organization when the article is the company’s explanation and no single employee is the public author. “By Northwind” is a clear byline. The author page is then about Northwind: what the product does, who edits the guides, and how a draft is checked. Many product blogs should work this way. Forcing every URL into a personal brand creates pressure to invent the person you do not have.

A shared desk is allowed. Two people can sign one article if both did the work. List both, and link both pages. A byline that names a committee no reader can find (“The Northwind Insights Team” with no page and no members) is only slightly better than a fictional coach. Either name the company, or name the people.

What to put on the author page

Five fields cover a page a reader can use. Extra fields are worthwhile when they are true. A wall of social icons that lead to empty profiles is not a field.

• Name. The person or the organization, spelled as it appears in the byline.
• Role. The job they have. “Writes the product guides” is a role. “Visionary thought leader” is not.
• Work. A few sentences on what they have done that relates to the articles. Skip the origin story unless it explains the expertise.
• Articles. Links to the live URLs they signed. This is the author archive that matters. A tag page full of drafts and quotes does not help.
• How the drafts are made. If automation writes the first version, say that a person checks the claims before publication. Google’s guidance on the “how” of content says disclosures are useful when a reader might wonder how the page was produced. Put the note where that question arises, on the author page or at the end of the article, in plain language.

Leave the page out of any scheme that assigns it a commercial query. An author page can be indexed. Its title should be the person’s name or the organization’s name, plus a few words of role if that helps. “Priya Shah, product editor at Northwind” is a title. “Best async standup expert 2026” is a query the author page should not chase. Author page SEO, done as identification, is a clear URL, a byline that links to it, and a bio that matches the articles. Done as a ranking project, it becomes another thin page in the topic cluster you did not mean to create.

Photos need the same honesty, and the same image SEO. Alt text for a real headshot can be the person’s name. Alt text for a logo can be the company name. A decorative background gets an empty alt attribute. Do not generate a face to fill the circle in the template.

Make the schema name the same author

Article structured data can name an author as a person or an organization. Google’s article structured data documentation is about describing the article, including who wrote it, when you use that markup. The visible byline and the author value should be the same party. If the page says “By Northwind,” the JSON-LD should not say a person you created for the schema. If the page says “By Priya Shah,” the schema should use that name and can point at her author page URL.

Dates follow the same match. datePublished and dateModified should agree with the dates a reader can see. The content refresh guide is where those dates change, and only after the article itself changed. An author page does not get a fresh date because you swapped the portrait.

Person schema on the author page can include name, jobTitle, and url when those are visible. Adding alumniOf, awards, or a medical credential the person does not have is the false-credential problem in JSON. Markup does not create expertise. It repeats what the HTML already says. FAQ schema does not belong on an author page unless the page shows real questions and answers. FAQ rich results stopped appearing in Google Search on 7 May 2026, so the markup is not an accordion. The rest of the article object, including the headline and the dates, is the article schema guide. Describe the page you published.

An author page example

Northwind publishes the product-team rituals cluster. They have one editor, Priya, who runs the team’s own meetings and reviews every guide before it goes out. A model can draft from their notes. Priya deletes claims they did not measure. Here is a byline that fits, and here is one that does not.

• On the article. “By Priya Shah. Updated 6 October 2026.” The name links to /authors/priya-shah.
• On her page. She is the product editor. She has run the six-person standup since 2023. The page lists the procedure, the retro questions, and the comparison she signed. A line says drafts may start from a model and she checks the steps against how the team works.
• Schema. Article author is a Person named Priya Shah, with the same URL. It does not add a certification.
• The version to reject. “By Maya Ellison, certified agile coach,” with a generated headshot and an author page that has never met a reader. Northwind does not employ Maya. The certificate is decoration. Publish as Priya, or publish as Northwind. Do not publish as Maya.

If Priya leaves and nobody replaces her as the public author, change the byline to Northwind and say the guides are maintained by the product team. Keep her name on the articles she wrote only while that credit is still accurate, and update the author page so it does not imply she still edits. A stale byline is a fact, like a stale product name. It belongs in the refresh when it stops being true.

How this shows up in a BloGoose draft

BloGoose writes from your site and your voice. The draft still needs an owner. Set the byline to a person on your team or to your organization before you publish, and use that same name in the article schema. The product should not be asked to invent a coach. A disclosure that a model assisted the draft can live on the author page you already maintain, so you are not adding a new fictional editor to carry the blame or the credit.

The pipeline can ship the article on a schedule. The schedule does not choose the human or the company that will stand behind it. That choice is the byline. Make it before the first URL in the cluster goes live, and keep it stable enough that a reader recognizes it on the second article.

Questions about author pages