Short answer: a mature dashboard tracks byline coverage, profile integrity, identity mismatch, role clarity, reviewer coverage, stale-profile rate, reciprocity, local consistency, lifecycle lag and provenance completeness. Google documents Article and ProfilePage structured data, but does not publish a universal author-authority score.
Baselines
Define the eligible corpus: articles, research and explainers where the author identity is legitimate. Excludes service pages or corporate pages where an individual author would be artificial.
Indicator 1: byline coverage
Eligible articles with legitimate author from the total of eligible articles.
Indicator 2: profile integrity
Profiles that respond correctly, have coherent canonical and do not go through unnecessary redirects.
Indicator 3: identity mismatch rate
Byline, profile and structured data that do not identify the same person.
Indicator 4: role clarity
Profiles with current role and clear relationship with the company. Do not treat localized titles as an automatic mismatch.
Indicator 5: reviewer coverage
Content defined by editorial policy as requiring a reviewer has an actual and distinct reviewer.
Indicator 6: stale-profile rates
Profiles with role, bio or status not updated after a lifecycle event.
Indicator 7: article-profile reciprocity
The article goes to the profile, and the profile allows the discovery of related articles.
Indicator 8: local consistency
Localized profiles identify the same person and the mapping between locales is correct.
Indicator 9: lifecycle lag
Time between role change/departure and update of relevant surfaces.
Indicator 10: provenance completeness
Biographical and credential claims that can be supported and have an internal owner.
The denominators
Byline coverage uses eligible articles. Profile integrity uses active profiles. Reviewer coverage uses articles that require review. Do not combine populations.
Observation window
Runs after reorganizations and migrations; for stable teams, monthly or quarterly may be sufficient. Lifecycle lag must be measured continuously at events.
False-attribution risks
Traffic, ranking or citations can be affected by rewrites, PR, backlinks, demand and Search/model updates. Don't author the cleanup without a separate design.
How do you treat former authors
A historical author is not a mismatch just because he no longer works for the firm. Profiles should clarify status without rewriting legitimate attribution.
How do you treat organization author
Some items are collectively produced. Use organization author when the actual process warrants it, not fictitious persons.
Dashboard layout
It separates coverage',integrity', lifecycle',provenance' and external observations. Show actionable findings, not just scores.
How do you treat external observations
You can monitor author mentions or source citations in a fixed query set. These are external outcomes, not quality gates.
Acceptance criteria
The dashboard is auditable when:
- the eligible corpus is versioned;
- the denominators are clear;
- profile IDs are stable;
- lifecycle events are logged;
- claims have provenance;
- local mapping is preserved;
- raw findings are accessible;
- severity is defined;
- external outcomes are separate;
- a reviewer can reproduce the percentage.
How do you define the denominators before the dashboard
Byline coverage' uses eligible articles,profile integrity' existing profiles, and `reviewer coverage' only the content for which the policy requires review. If all percentages use total pages, the dashboard produces meaningless comparisons. Show the numerator and denominator next to the percentage, not just an aggregate grade.
Lifecycle events that must be logged
Promotion, change of practice, departure, return, team merger and CMS migration can affect the identity layer. For each event, it keeps the date, affected profiles and expected action. Thus, `lifecycle lag' becomes verifiable and does not depend on an audit done much later.
Provenance for credentials
In regulated professions, qualification, membership and professional titles must have a current source and status. Don't turn the dashboard into a credential catalog; follow only public claims that may change the trust or interpretation of expertise.
Prioritization of findings
P0: Wrong person, fake byline or misleading role. P1: broken profile, stale credential or missing reviewer where required by policy. P2: local mismatch and reciprocity. P3: cosmetic differences. This severity helps the team not treat all deviations as emergencies.
Drill-down required
Each percentage must lead to URL, person, issue type and timestamp. If the dashboard shows 7% mismatch, the reviewer must be able to see exactly seven cases out of a hundred and reproduce the classification rule.
How do you report external observations
Author mentions in Search or AI can be displayed separately with query, language and date. Do not combine them with `identity integrity'. A person can be perfectly editorially attributed and still not be mentioned in a particular external output.
Maturity criterion
The dashboard becomes operable when lifecycle events automatically generate review tasks, denominators are stable and P0/P1 have owners. From that point, the indicators must prevent drift, not justify the continuous increase in the number of profiles.
How do you treat archived profiles
A former author profile may remain necessary for historical attribution. Mark it former' orarchived', keep associated articles and avoid including it in the denominator of active profiles. Automatic homepage redirection can destroy context and turn a historically valid profile into a false positive.
How do you deal with a KPI that is improving too quickly
If the mismatch rate suddenly drops after changing the rubric, check if the denominator or definition of eligibility has changed. The dashboard must keep revision history for formulas, otherwise a trend can only reflect new methodology, not better quality.
Claim ledger
- FACT/EVIDENCE: Google recommends author identification for Article and documents ProfilePage.
- PRACTITIONER GUIDANCE: author dashboards must separate coverage, integrity and lifecycle.
- INFERENCE: coherent profiles reduce ambiguity of attribution.
- NOT PROVEN: a universal author-authority score or direct effect on AI citations.
Conclusion
The author identity dashboard should tell where attribution is broken and who is fixing it. In professional services, transparency and lifecycle are more useful than a generic authority score.
Sources reviewed
- Google Search Central, Article structured data: https://developers.google.com/search/docs/appearance/structured-data/article
- Google Search Central, ProfilePage structured data: https://developers.google.com/search/docs/appearance/structured-data/profile-page
- Google Search Central, Organization structured data: https://developers.google.com/search/docs/appearance/structured-data/organization
