If you lead revenue or marketing at a growing B2B company, author schema is the schema markup that tells search engines who wrote a page and where to learn more about them. You add it to the article and to a bio page for each writer, and keep both in step with what readers see.
This guide is for CEOs, founders, CROs and the marketing lead who ships the page. You get what Google asks for, a six-step method for adding Person markup and an author bio page in HubSpot, and an honest view of what it does for AI search. It makes authorship clear. It does not buy rankings.
|
Author Schema Author schema is structured data, usually JSON-LD, that defines the person who wrote an article and links that name to a bio page and other profiles that confirm who they are. |
Most B2B blogs show a name and a small photo, then stop. A buyer cannot tell who the writer is, and a search engine has only a string of text to go on. Author schema fixes that without changing how the page looks.
Check these four things first. Markup cannot make an anonymous page credible.
If you have not yet mapped the wider set of on-page signals, the AEO checklist with an annotated page shows where authorship sits among them.
Structured data is code on a page that labels what the page contains, so a machine reads the structure of your content without guessing. Schema markup is the shared vocabulary for that code, published at schema.org. Rich results are the enhanced listings some schema markup can earn in search results.
Author markup is mostly about understanding. It gives search engines a reference they can match to a real person, which is why your website, the bio page and the profiles must agree. Think of it as an example of structured data doing a small, honest job: connecting a name to a person.
In publishing, an author bio means something different. Book writers shape a bio around a genre, a debut or an award, whether they write fiction, non fiction or novels.
A business author bio has a different job: it tells a buyer, in a few words, why this person can be trusted on this subject. Keep the focus on expertise, not personality, and leave out the family story and hobby background. The same idea applies to the markup, which describes a professional, not a persona.
Google's guidance on helpful content for Google Search asks who created a page and whether the byline leads to more about the author. It encourages accurate authorship information, such as bylines where readers would expect them, and warns against fabricated creator profiles, made-up names and false credentials.
So the honest approach is also the safe one. Use real people with real credentials, and say only what is true about them.
Google does not list author markup as a ranking factor, and nothing in its documentation promises better search results from it. Its article documentation describes the author property as recommended, and says the markup helps Google understand authors across its features.
Other engines and AI tools that read pages also gain a clearer signal about who is speaking, though none of them promise a result.
Treat the structured data as clean labeling that backs up a visible byline, and follow Google's best practices for author markup so the format stays valid. The bio, the credentials and the quality of the writing carry the weight.
Clear author information lets a reader verify qualifications and expertise, which fits what Google calls experience, expertise, authoritativeness and trustworthiness, or E-E-A-T. Structured data also helps systems interpret a page and identify the entities on it. A consistent profile strengthens a writer's digital footprint by linking their work across the web.
Each step ends with what done looks like, so you know when to move on.
List every person who should be credited, including reviewers if you use them. A page credited to "the team" or to a company name gives readers and users of AI tools nothing relevant to check.
Write each author bio in the third person, in two to four sentences: who they are, what they work on and why they know it.
Mention real roles, real projects and real expertise, so the author bio gives a reference a reader can check. Keep the author bio plain and specific, and skip superlatives.
Add a clear photo too; the avatar becomes the profile image on the author page. Write the bio so it is relevant to the topics the author covers on your site.
You are done when each writer has a bio they have read and approved.
HubSpot generates an author page for each blog, listing every post credited to that author. Its knowledge base article on managing blog authors explains that each author profile holds a display name, bio and avatar, and that the page title and meta description pull from the author name and bio.
In the blog tool, open the authors dashboard, create or edit the author, and fill the optional fields: bio, avatar, website and social profiles. Use the same name everywhere so the page and the markup agree.
You are done when each author page loads on your blog and shows the right name, photo, bio and links.
Google recommends JSON-LD as the easiest structured data format to maintain, as its introduction to structured data explains. For a bio page, Google's profile page documentation lists an author page as a valid use and asks for a mainEntity that is a Person or Organization with a name.
The vocabulary comes from schema.org's Person type, which includes jobTitle, worksFor, knowsAbout and the sameAs property. This example uses placeholder details, so replace every value with your own:
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"mainEntity": {
"@type": "Person",
"name": "Jordan Reyes",
"image": "https://www.example.com/images/jordan-reyes.jpg",
"jobTitle": "Head of Revenue Operations",
"url": "https://www.example.com/blog/author/jordan-reyes",
"worksFor": {
"@type": "Organization",
"name": "Example Company",
"url": "https://www.example.com"
},
"sameAs": [
"https://www.linkedin.com/in/example-profile",
"https://www.example.com/team/jordan-reyes"
]
}
}Use one consistent format for names, titles and links across the site, and make sure the sameAs links point to real pages that are about the same person. The structure above also works as a template for every future writer. Google says it can use either sameAs or url when it disambiguates authors.
You are done when the code parses and every value on it matches the visible bio page.
Each post, like any webpage that credits a writer, needs its own markup that points to the writer.
Google's article structured data documentation lists author as a recommended property and gives best practices for it: include every author shown on the page, list each author as a separate entry, use the Person type, and add a url or sameAs link that points to a page about the person.
Credit several writers as separate author entries, never as one merged name. Use the recommended properties for Article structured data, such as author, headline, image, date published and date modified.
Use the same data you used on the bio page, and put only the name in the name field. Job titles belong in jobTitle, and the publisher belongs in the publisher property. Point the url at the bio page from step 2, and keep both dates accurate.
You are done when each post names its author, the url leads to the bio page, and the name matches the byline.
Paste the profile page script into the head of the author page template, and the article script into the post.
Users who edit the page later need to know where the code lives, so note it on your site checklist.
HubSpot's page on using code snippets with HubSpot content describes the Head HTML field and notes that footer HTML is not available for blog posts.
HubSpot's blog settings guidance says its Structured Data setting turns on BlogPosting schema, and to avoid enabling it when custom schema already exists. View the page source first, so you know which block is already there and keep one source per schema type.
You are done when each page shows one article block and one author block in the source.
Validate schema markup with the Schema Markup Validator or Google's Rich Results Test tool to check syntax. Run the structure of the page through it again after every template change.
Then open the live page and compare the code with what a reader sees, and check how the page shows in Google Search results after it is recrawled. Search Console reports show whether Google reads the structured data without errors, and where rich results apply.
Add a review date to your calendar. When a writer changes role or adds a profile, update the bio and the code in the same sitting. The organization schema maintenance guide covers a quarterly routine that also suits Person markup.
You are done when the validator shows no errors and one person owns the review date.
Check your pages against this list before you publish.
Clear authorship helps readers and site visitors judge your content and gives search engines and AI tools a consistent entity to connect to each post. The data you add stays small and the gains show up differently for each team.
Prospects can see who wrote the advice they are reading, and what that person has done. Reps can send a link to a writer's bio and article instead of explaining who the expert is.
Marketing owns one tidy pattern for every article: bio page, Person markup and Article markup. New writers slot into it, and it ties into your wider plan for optimizing content for AI search.
Customers meet the same named people in guides, webinars and support. When an article carries a real author, customer success can point to it and know the person behind it will stand by it.
Author schema will not rank a thin page, and it is no shortcut to AI citations. What it gives you is a habit that serves readers and machines alike: real writers, honest bios and markup that matches the page. Pair it with entity work such as knowledge graph and entity authority.
Propello is a HubSpot partner and designs and builds connected go-to-market systems on HubSpot. If your content, data and reporting do not yet agree with one another, an audit is the place to start.