When a company page hides the person buyers want
Make an individual’s role clear without treating an organization as a person.
On this page
A company website can explain the service well and still leave a buyer unsure who will do the work. That gap matters when the buyer wants to assess an individual’s experience, authorship, or role before getting in touch.
Give the organisation page and the person page different jobs, then make their shared facts agree.
Notice the kind of ambiguity on the page
Read the site as someone who has not met you. Can they tell whether a named person is the founder, an employee, a contractor, an author, or simply someone quoted in an article? Can they tell whether that person currently delivers the service the company describes?
Common problems are small but consequential. A company page might say “our research team” without naming the person leading a project. A page may show a founder’s name only in the footer. An article may carry a company byline even though a specific person wrote it. None of these details are proof of a problem by themselves. They are prompts to make the relationship clear where a client needs it.
Start with the decision a reader is trying to make. A company page should help them understand the organisation’s offer. A personal page should help them understand the individual’s role, relevant background, and public work. They can link to each other without repeating every paragraph.
Give each page a clear role
Use this division as a starting point:
| Page | Main question it answers | Information to include |
|---|---|---|
| Company page | What does this organisation offer, and how does a client engage it? | Services, team context, sectors, process, contact route, and permitted company evidence |
| Person page | Who is this individual, and what is their role in the work? | Current role, relevant background, authored work, areas of responsibility, and links to the company page |
The company page should not claim that every employee has a founder’s experience. The person page should not present the organisation’s whole track record as a personal achievement. State the relationship directly: “Maya Chen is the research director at Northstar” is clearer than a generic team list. If Maya left the organisation, state the dates or use past tense.
An illustrative company page could say, “Northstar provides service-research and planning support for public-interest organisations.” Maya’s page could say, “Maya Chen is Northstar’s research director and leads discovery projects.” If the site lists a report by Maya, the report should identify the author and make clear whether it represents Maya’s view, the organisation’s work, or both.
Build a useful personal page
For a person whose work is central to a sale, a speaking engagement, or published work, a personal page can be short. It needs enough detail for a reader to confirm that the individual is the right person.
Include the person’s name as they use it professionally, their current role, a plain description of responsibilities, and links to relevant articles, talks, reports, or public profiles. Add only facts that are current, permitted, and supportable. A headshot or contact route can help distinguish a common name when it is appropriate for the work.
Do not fill the page with a generic career timeline. A buyer needs the parts of the background that explain current fit. “Leads qualitative research for Northstar’s service-design projects” tells a reader more than “passionate about innovation.” A dated prior role can be useful if it relates to the work. A confidential client list, a private result, or an expired credential does not become safe to publish because it appears on an individual page.
Keep shared facts aligned
Choose a small set of facts that should agree everywhere: the person’s professional name, current role, organisation, service relationship, current location where it affects fit, and main contact route. The wording can vary, but the underlying facts should not conflict.
Review each new or updated page against the other one. A company team page may identify an employee while the employee’s personal site describes an independent practice. Either could be accurate, but the reader needs dates or context. A current employment relationship, a former role, an advisory relationship, and a published guest contribution are different facts.
Keep a short source record with the URL, owner, statement, and review date. The source consistency checklist provides a simple format. If a returned AI answer links to either page, trace the claim to the cited passage before deciding what the page supports.
Link the pages in both directions
The company page can link to the person’s profile from a team section, a report byline, or a named project lead. The personal page can link to the company from the current-role description. Use descriptive link text so readers know what they will find.
Do not create a link solely to imply an affiliation that the page does not explain. A personal site that links to a company logo without saying whether the person is an employee, founder, adviser, or alumnus leaves the ambiguity in place. Add a short factual sentence beside the link.
Google’s ProfilePage guidance supports this division: a profile page must focus on one affiliated person or organisation, and employee, author, and About pages are valid examples. Use the correct Person or Organization type when it is known. Google’s ProfilePage documentation
Make the pages clear before adding markup. Google requires structured data to represent visible content and not mislead readers. It can enable a search feature, but Google does not guarantee display. Google’s structured data guidelines
Maintain the distinction after a change
When someone joins, leaves, changes role, or starts an independent practice, review both pages on the same day. Update the facts you control and ask external publishers to correct current-role bios where needed. Preserve historical articles and reports with a date or an accurate former-role description.
Record the two URLs, the facts you changed, and the review date. Next time the role changes, review those same two pages before publishing a new byline or team listing.