Build an expert source inventory before changing your content
List the pages that shape a reader’s understanding before deciding what to improve.
On this page
Before changing an About page or correcting an AI answer, record the public pages that describe your work. An inventory does not make an engine recommend you. It shows which pages exist, who controls them, what each says, and when someone last checked them.
This is different from a source-consistency checklist. A consistency check compares facts across pages. An inventory comes first. It tells you which pages belong in that comparison and who can update each one.
Start with pages that a reader can reach
List public pages that could shape a prospective client’s understanding of you. Begin with your own site, then add independent pages where your work is identified. Do not add private profiles, confidential case studies, or pages that require a login.
| Page | Owner | Why it belongs | Reviewed |
|---|---|---|---|
| Personal site or About page | You | Name, role, services, contact route | [date] |
| Service page | You | Scope of a specific offer | [date] |
| Publisher author page | Publisher | Byline and subject matter | [date] |
| Employer or association profile | Organisation | Current or past role, where relevant | [date] |
| Event, podcast, or report page | Host or publisher | Public contribution and date | [date] |
These are illustrative rows. Replace them with pages you can open and review.
Add a page because it gives a reader a useful fact, not because it has a prestigious domain. An old directory job title may need review. A current article byline can connect a piece of work to its author.
If a returned AI answer shows a citation, put that page in the inventory with the answer date and question. The citation is a reason to inspect the page. It is not proof that the page caused the answer or that every statement in the answer is correct.
Separate pages you control from pages you do not
Ownership determines the next action. You can correct a factual error on your own site. You may be able to request a correction from an association, publisher, or former employer. You cannot silently rewrite a third-party page, and a third-party page may be historical rather than wrong.
Use an owner field that names a person or organisation, not a vague label such as “external.” Add a contact route or an internal note about who can update the page if that is useful to your team.
| Ownership | Useful next action |
|---|---|
| You or your team | Check the fact, update visible copy, then record the date. |
| Current employer or partner | Confirm the wording and use its normal correction process. |
| Publisher or event host | Ask for a factual correction, preserving a dated historical record where appropriate. |
| Directory or database | Check the listing policy and submit a correction if one is supported. |
| Unknown | Record the page, but do not treat it as a source you can maintain. |
An old conference biography may accurately describe a role at the time of the event. Mark it as dated and give current context on your own site.
Record what each page actually says
Do not summarize with “good profile” or “strong evidence.” Capture the small facts a reader could use to decide whether you are the right person to contact.
- The exact professional name used on the page
- Role, organisation, or independent status
- Service or subject area described
- Location, language, or sector if it affects fit
- Byline, date, or named contribution
- Link to a relevant profile, work sample, or contact route
- Any claim that needs separate approval or evidence
For example, an author page might identify Priya Shah as a “research consultant writing about public-service design.” That supports an authorship and subject statement. It does not establish that Priya currently runs workshops, has worked for a named client, or achieved a particular result. Keep the record narrow enough that someone else can check it.
Google encourages accurate authorship information where readers would expect it. It does not promise rankings, citations, or AI-answer outcomes. Google’s guidance
Flag conflicts and gaps before writing
Once the list exists, compare only the facts that matter. A page can be incomplete without being contradictory. A guest-post byline that omits your current service is normal. A personal site that lists a role you left years ago is a factual conflict worth fixing or dating.
| Finding | Record it as | Next step |
|---|---|---|
| Same role described in different words | Possible variation | Check that both descriptions remain accurate. |
| Former title presented as current | Conflict | Correct or add the relevant dates. |
| No public page links a byline to you | Gap | Consider adding an accurate author page or profile link. |
| A result cannot be publicly supported | Claim risk | Remove it, qualify it, or obtain permission before publication. |
Do not fill a gap by inventing a credential, adding a client name, or turning team work into an individual result.
Give every page a realistic review date
“Review regularly” is too easy to ignore. Assign a date or a trigger that fits the page. A service page should be checked after an offer changes. A directory profile may need a quarterly check. A stable article needs less attention unless its links fail or its author bio becomes misleading.
| Trigger | Review action |
|---|---|
| New role, offer, location, or contact route | Check owned pages and current profiles. |
| Returned answer contains an old detail | Save the answer, inspect the cited page, and note whether it is current or historical. |
| New public work goes live | Add its byline or contribution page if it helps readers verify your work. |
| Former employer or event page is inaccurate | Request a correction and retain the request date. |
ProfilePage structured data is designed for pages primarily about a person or organisation, but markup should match visible, accurate page content. Google does not guarantee that structured data will appear in a search feature. Treat it as page-description markup, not a substitute for clear public copy. Google’s ProfilePage documentation
Before changing a page, add its owner, its last review date, and the exact fact you need to verify. Then use the source consistency checklist to compare the facts across the inventory.