Article and ProfilePage Markup: Build One Verifiable Author Identity Chain
Connect visible bylines, Article author entities, ProfilePage markup, and external identity links without creating conflicting author records.
Direct answer: Use the visible author page as the identity hub. The article byline should link to that page, Article structured data should represent every real author with the correct type and author URL, and the profile page can use ProfilePage markup whose mainEntity is the same Person.
Structured data does not create expertise. It makes an existing, visible identity easier to interpret. The name, biography, role, credentials, profile image, disclosures, published work, and external identity links must remain accurate for readers before they are expressed in JSON-LD.
Define the visible source of truth
Choose one canonical public name for the person. On SearchEngineAnswer, that is Abdessalam Alaoui. Use it in the article byline, author archive heading, profile biography, structured data, image metadata where relevant, and editorial credits. Avoid shortening it to “Abdessalam” in one layer while another layer presents a different entity name.
The author page should explain the person’s role, areas of expertise, relevant experience, editorial responsibilities, and relationship to the publication. Link to articles the person actually wrote and to policy pages that explain corrections, AI assistance, and commercial relationships.
Connect Article and ProfilePage entities
| Surface | Required identity | Common failure |
|---|---|---|
| Byline | Visible full name linked to profile | Plain text or wrong profile |
| Article author | Person with name and URL | Publisher used as person |
| ProfilePage | mainEntity Person | Page entity confused with person |
| sameAs | Accounts that identify the same person | Unrelated brand or directory links |
Google’s Article documentation says to include all authors and use the correct Person or Organization type. Its ProfilePage documentation describes a page whose main focus is a person or organization. Keep the page URL and person identifier stable where practical.
Use author URL and sameAs carefully
The author URL should lead to a page that identifies the author, not to a generic About page or social profile chosen only because it is authoritative. An internal author page gives the publication control over the visible biography, article list, disclosures, and corrections.
Use sameAs for external pages that clearly identify the same person, such as a controlled professional profile or personal site. Do not add every citation, employer page, directory entry, or brand the person founded. A relationship to a company is not the same as identity equivalence.
When a name or role changes, update visible content and structured data together. Preserve redirects from retired profile URLs and check that old article markup does not keep a stale author identity.
Validate the complete chain
- Open the article without JavaScript and confirm the visible byline and profile link.
- Extract the Article JSON-LD and list every author entity, type, name, and URL.
- Open the profile page and verify the visible name, biography, image, and article relationship.
- Extract ProfilePage markup and confirm that
mainEntityis the same real person. - Open every identity link and remove unsupported or conflicting references.
- Test representative articles in validation tools, then inspect the rendered graph manually.
Syntax validation is necessary but insufficient. A graph can pass a parser while connecting the wrong person, omitting a co-author, or asserting a social identity the author does not control.
Audit authorship over time
Run the identity audit when an author name, biography, role, profile URL, social account, or publishing workflow changes. Check imported and syndicated articles separately. For reviewed material, distinguish author, reviewer, editor, and publisher roles rather than assigning every contribution to one person.
See the Abdessalam Alaoui author page, editorial policy, and corrections policy for the visible trust layer that the markup should describe.
Ask a question or join the discussion