An expert source page lists the people at your organization whom a journalist can quote, says what each person can speak about, and shows how to reach them. The short answer: put people ahead of the brand, give every expert one narrow topic with evidence behind it, publish a contact route that works, and keep a few ready quotes on the page. Small business owners, founders and lean PR teams can use it to become findable by reporters who are looking for a source instead of waiting to be noticed. Each part of the build follows the order a reporter would judge it: who is on the page, what they know, how to reach them, and how markup and upkeep support that.
What the page is for, and how it differs from a newsroom
A page organized around people and topics
A reporter working on a story needs a person who knows the subject. A company overview does not help with that. The expert source page answers three questions in one place: who can speak to this topic, why that person is credible, and how to get a reply. Each expert gets a card with a name, a job title, topic areas, a short background, links to earlier published comments and a contact route. Brand messaging comes second.
Google’s helpful content guide (Opens in a new tab) puts the reader’s view of authorship into questions that fit this page well. It asks, “Do pages carry a byline, where one might be expected?” and it says, “We strongly encourage adding accurate authorship information, such as bylines to content where readers might expect it.” An expert source page extends that idea. When a byline on an article or a name in a quote points to a profile, the reader can check who the person is.
Where a newsroom page still fits
A newsroom page is the company’s own announcement desk: releases, logos, boilerplate text, a media kit and a general press contact. Experts do not replace it and it does not replace them. A brand with both pages gives reporters a way to find the company news and a separate way to find the person who can comment. For the newsroom side, see the online newsroom page guide. For the reverse direction, where a reporter has already posted a request and you answer it, see earning links from journalist requests.
| Question a reporter asks | Where it is answered |
|---|---|
| What did the company announce? | Newsroom page |
| Where is the logo or a product photo? | Newsroom page or media kit |
| Who can explain this topic to our readers? | Expert source page |
| What has this person said before? | Expert card with linked earlier comments |
| How fast will they answer? | Response time statement on the expert page |
| Who handles a general press question? | Newsroom page, with its own contact |
Who the page serves besides reporters
Editors, podcast producers, conference organizers and bloggers also look for a person to quote or invite. The page works for them without extra effort, because it already carries topic areas and a contact route. Practical suggestion: write the introduction as if the reader were an editor with only a few minutes, not as a promotional text for the brand.
Choosing experts: topic area, experience and availability
Test one: the topic fits in a headline
A good topic area is narrow enough to appear in a story headline. A label such as “marketing” or “technology” matches nothing a reporter is writing about. Ask each candidate to list the questions customers or colleagues bring to them again and again, then group those questions into one theme. The theme becomes the topic line on the card. A second and third topic can follow, but the card leads with the strongest one.
Test two: the evidence can be shown
The same Google guidance asks, “Does your content clearly demonstrate first-hand expertise and a depth of knowledge”, and it asks whether content is “written or reviewed by an expert or enthusiast who demonstrably knows the topic well”. Evidence on a card can be the number of years in the field, the kind of work the person does, a talk they gave, a piece they published or a course they teach. Each item must be checkable outside the page. A title, award or publication that cannot be confirmed stays off the card.
Test three: the person can actually respond
Availability decides whether a card is useful. An expert who is away from the desk for weeks cannot answer a reporter with a same-week deadline. Before adding a person, agree on the answer window, the hours when replies are possible and the channel. Practical suggestion: promise a window slightly longer than your team can really meet, then beat it. A promise that is kept builds more trust than a fast promise that slips.
Decision rule: when the answer is no
Decision rule: an expert joins the page only if all three tests pass. If the topic is vague, ask the person to narrow it. If the evidence is missing, wait until there is a talk, an article or a documented project to point to. If availability is uncertain, leave the person off and revisit at the next review. A shorter page with reliable people is more useful than a long page with silent names.
Contact details: shared inbox, form or direct line
Why a form and a shared inbox come first
Putting an expert’s personal mobile number on a public page looks fast, yet anyone can copy it. Practical suggestion: publish a corporate email address and a contact form with a topic selector. Make the form ask for the outlet, the topic and the deadline so the message reaches the expert in a usable shape. A shared inbox lets a colleague reply when the expert is away.
Consent and removal
Practical suggestion: before a name, photograph or contact route goes live, get the expert’s written approval and keep the record. Agree in advance that the card will be removed on the day the person leaves the company or changes role. A direct line can be offered only at the person’s own request and through a company number that someone answers.
Weighing the routes against each other
| Route | What it gives the reporter | What can go wrong | Suggestion |
|---|---|---|---|
| Shared corporate inbox | A reply even when the expert is away | Nobody owns it, so replies slip | Use, and name an owner |
| Contact form with topic selector | Outlet, topic and deadline arrive together | Takes longer to fill in | Use, keep it short |
| Personal mobile number | Quick access | Personal data on a public page | Do not publish |
| Company media phone number | Quick access in urgent cases | Needs someone to pick up | Use only if answered |
| Direct message on a social account | Easy for a reporter who already follows the expert | No record on the company side, and easy to miss | Do not rely on it as the listed route |
Fields the page should carry
Required, recommended and skipped fields
Not every detail deserves space on a card. The table splits fields into three groups, based on what a reporter needs to decide and to write a correct attribution. For a fuller treatment of author profile pages for readers rather than reporters, see building an author page for E-E-A-T.
| Field | Group | Reason |
|---|---|---|
| Full name as it should appear in print | Required | Prevents misspelled or shortened names in a published quote |
| Job title | Required | Lets the reporter describe the source correctly |
| Topic areas | Required | Allows matching a person to a story |
| Contact route and response window | Required | Turns interest into an actual exchange |
| Short background with checkable facts | Recommended | Shows first-hand experience |
| Links to earlier comments, talks or articles | Recommended | Shows the person has spoken publicly before |
| Languages | Recommended | Matters for outlets in other markets |
| Portrait the company owns | Recommended | Gives editors a usable image |
| Personal mobile number | Skip | Sits on a public page for anyone to copy |
| Home address or family details | Skip | Has no editorial value |
Checklist: a complete expert card
- The name is exactly as it should be printed.
- The title is the real role, not an invented label.
- One lead topic is written in a single plain sentence.
- At least two checkable facts back the topic.
- Earlier public comments open correctly.
- The contact route is monitored and the response window is stated.
- The card shows when it was last reviewed.
Layout for a quick scan
Place name, title and lead topic at the top of each card. The background paragraph follows, then the contact route, then a small block of ready quotes. A reporter should be able to recognize the person from the first two lines. Group cards under topic headings so that a reporter searching for a subject lands on the right cluster. If an expert fits two topics, keep a single card and link to it from the second cluster instead of duplicating the text.
Person markup: jobTitle, knowsAbout, sameAs
What schema.org defines for a person
On Person - schema.org (Opens in a new tab), the type is described as “A person (alive, dead, undead, or fictional)”. The page defines jobTitle as “The job title of the person (for example, Financial Manager)”, worksFor as “Organizations that the person works for”, and email as “Email address”. The sameAs property is described as a “URL of a reference Web page that unambiguously indicates the item’s identity”. The knowsAbout property lets the markup name a topic the person knows about.
| Property | What it carries on an expert card | Practical note |
|---|---|---|
| name | Printed name | Same spelling as the visible card |
| jobTitle | Role | Matches the visible title exactly |
| knowsAbout | Narrow topics | Only topics that the card text also shows |
| sameAs | Profile pages that identify the person | Only pages that truly belong to that individual |
| worksFor | The organization | Consistent with the organization markup |
| Published contact address | Only a route that is shown on the card |
How it connects to author markup on articles
When the expert also writes articles, the article markup should point to the same person. Article structured data - Google Search Central (Opens in a new tab) states that “There are no required properties; instead, add the properties that apply to your content.” Its author guidance asks you to include every author who appears on the page, to give each author a separate field and to use Person for people and Organization for organizations. It also says to specify only the author’s name in the name field, and to move job titles and similar details into other properties such as jobTitle. The author url, according to the same page, should lead to a page that uniquely identifies the author, and Google can understand both sameAs and url when disambiguating authors.
The practical result is a clean chain: the article byline links to the expert’s card or profile, the card carries a Person definition, and the Person definition points to outside profiles through sameAs. For the organization side of that chain, see organization markup and sameAs.
Markup stays a mirror of the page
Every value in the markup has to be visible on the page. Putting a title or a topic only in markup tells the search system something different from what the reader sees. The documentation has no statement on a dedicated search result feature for Person, so the markup should not be sold internally as a ranking move. Treat it as a machine-readable copy of the card, and update it the same day the card changes.
Preparing quotable lines and response times
What makes a ready quote useful
A ready quote is a short statement an expert is willing to stand behind. A reporter does not have to use it word for word, but seeing it shows how the expert thinks. A useful quote makes one claim, gives the reason in a sentence and ends with something the reader can do or understand. A figure goes in only with a link to its source. A personal observation is labeled as an observation. Attach each quote to a topic heading so reporters can filter.
| Quote type | Purpose | Label on the card |
|---|---|---|
| Definition | Explains a term in two sentences | Definition |
| Field observation | Describes what the expert has seen in daily work | Observation |
| Advice | Gives the reader one step to take | Advice |
| Sourced fact | States a fact with a link to the document | Sourced fact |
| Clarification | Corrects a common misunderstanding in one sentence | Clarification |
Experts can also offer comment in other forms. See ways to contribute to industry publications for quotes, data and event recaps as separate contribution types.
Setting the response window
State the response window in days, not in loose words such as “soon”. Separate channels if they differ: forms may be checked daily while a direct address may be checked on set days. A window that the team cannot meet damages the page more than a longer window that it can.
Handling a request step by step
- Log the request: who asked, which outlet, which topic and when the deadline falls.
- Match the topic to an expert on the page. If nobody fits, decline politely.
- Let the expert separate what they know first-hand from what lies outside their field.
- Send the reply in writing with sources for any figure or claim.
- Confirm the title and organization spelling with the reporter.
- When the piece is published, save the link and add it to the card.
Example scenario: a bird-watching gear shop
Why the shop needed a page
Example scenario: A shop sells binoculars, spotting scopes, field guides and feeders to bird watchers. A regional newspaper might ask for comment on choosing a first pair of binoculars, and the owner realizes that nobody has agreed who would answer. A reporter cannot contact a person whose name the shop has not published, so the owner decides to build a small expert page.
Applying the three tests
Three people could appear. The owner can speak about choosing optics for beginners. A guide who leads weekend walks can speak about reading a field guide and recording sightings. A part-time assistant knows the stock system. The owner and the guide each name a narrow topic, can point to a documented talk or a published note, and agree to reply within two working days. The assistant fails the evidence and availability tests for now and stays off the page. With only two people, the shop uses one page with cards.
Cards and quotes
The owner’s card carries the title as it appears on the shop’s documents, a lead topic of “first binoculars for beginners”, and a ready quote labeled as an observation about how new bird watchers describe their first purchases. The guide’s card lists “using a field guide on a first walk” and links to a walk description the shop already published. Contact goes through a shared inbox and a form that asks for the outlet and the deadline.
Keeping the cards current
The shop reviews the cards before each spring and autumn season. If the guide leaves, the card and its Person markup are removed the same day, so the page does not list someone who will not answer.
Keeping the page current and judging whether it works
Quarterly reviews and what triggers an edit
Practical suggestion: schedule a review every three months, and treat the timings in the table as suggestions to adjust. Ask three questions for every card: is the person still in the role, is the topic still accurate, and does the contact route still work. Add newly published comments to each card and remove links that no longer open.
| Event | Change on the page | Change in the markup | Suggested timing |
|---|---|---|---|
| Expert leaves | Remove the card | Delete the Person definition and the worksFor link | Same day |
| Title changes | Update the title line | Update jobTitle | Same day |
| New topic added | Add to the topic list | Add to knowsAbout | At the next review |
| Comment published in an outlet | Add the link to the card | Review sameAs | Within the week |
| Contact route or response window changes | Update route and window | Update email | Same day |
| Quarterly review | Check every card and remove dead links | Compare with the visible cards | Every three months |
Signals that the page is doing its job
Count inbound requests, the share that received a reply and the time the reply took. Note which replies turned into published comments and whether the expert was named with the correct title. Record whether the outlet linked to the card or the company, but treat the link as information, not as the aim. If no requests arrive, first check that the page can be reached from the contact and press areas of the site and that it can be indexed. Use what digital PR is and how to do it for the wider picture around outreach and measurement.
One owner for the page
Give the page to one person. Put a last-reviewed date at the bottom. A shared change log shows who edited which card and when, which helps when a reporter asks why a title differs from an older article.
Pre-launch checks and common mistakes
Before launch: the page and its cards
Page-level checks:
- The introduction speaks to an editor in one or two sentences.
- Experts are grouped by topic and each card reads on a single screen.
- Every card uses the same fields in the same order.
- The response window is stated in days.
- The contact route works and no personal mobile number appears.
- Each expert has approved publication in writing.
- A last-reviewed date is visible.
Mistakes with people and topics to catch while you check:
- Listing every employee to make the page look large.
- Using broad topic labels that match no story.
- Showing titles or awards that cannot be confirmed.
- Posting a ready quote with a figure that has no source.
- Letting the brand pitch replace the personal card.
Before launch: the markup
Markup checks:
- Every Person definition matches the visible card.
- jobTitle equals the visible title.
- knowsAbout lists only topics the card shows.
- sameAs points only to profiles of that individual.
- Article bylines link to the same card addresses.
Mistakes in markup and upkeep to catch while you check:
- Writing a title in markup that differs from the page.
- Adding a company profile to the sameAs list of a person.
- Leaving a card online after the expert has left.
- Promising a response window the team cannot keep.
- Allowing a wrong title to be printed because no one confirmed it with the reporter.
After the first request: process and purpose
Process checks:
- Someone is named to receive requests.
- A request log and a reply template exist.
- The three-month review is on the calendar.
- Someone saves the link after each published comment.
The page exists so a reporter can find the right person. Links may follow, but they are not guaranteed and cannot be demanded. Adding lines to quotes that ask for a link, or making a link a condition of an answer, turns a helpful page into a request. Google’s guidance says, “‘Why’ is perhaps the most important question to answer about your content”, and its answer is that content should be created primarily to help people.
Frequently Asked Questions
What if an expert changes jobs?
Remove the card the same day and delete the Person definition and the worksFor link. Earlier published quotes can stay in company records but should not appear as the person’s current details.
Is an expert source page the same as an About page?
No. An About page introduces the company. An expert source page lets a reporter pick a person by topic and shows how to reach that person. The two can link to each other.
Will Person markup earn links or rankings?
No promise of that kind can be made. The documentation has no statement on a dedicated search result feature for Person markup. The markup makes the card machine-readable and helps identify the person.
How many experts should the page list?
The documentation has no statement on a number. Practical suggestion: list every person who passes all three tests. One reliable expert helps a reporter more than ten who do not answer.
Does a ready quote commit the expert to a statement?
A ready quote only shows how the expert thinks. A reporter may ask new questions, and the expert answers each request afresh, stating the limits of what they know.
How do I connect an expert to the articles they write?
Use the Person type in the author field of the article markup, put only the name in the name field and point the url or sameAs value to a page that uniquely identifies the author. Titles belong in properties such as jobTitle.
Should the page show a photograph?
The documentation has no statement on photographs. Practical suggestion: add a current portrait the company owns, with the expert’s approval, because it helps editors.
Conclusion
An expert source page turns knowledge inside a company into something a reporter can use. The strongest versions carry a few carefully chosen people, each with one narrow topic, checkable experience, a working contact route and a response window the team can keep. Person markup copies those facts into a machine-readable form, though it replaces nothing on the visible page and promises neither links nor rankings. Upkeep matters as much as the first build, because a name that does not reply weakens the whole page.
Once the page is live, the rest of your outreach is a separate task. If you plan publisher partnerships or link-supported visibility work, you can compare options on the backlink packages page.
Post a comment
Please log in to leave a comment. Login