Structured identity is not the creation of another public identity system. It is the practice of making existing relationships understandable to software as well as people.
A website already communicates identity through visible elements such as:
- name - logo - author or organization - domain - profile page - contact information - links to official external profiles
Structured data can describe some of those same facts in machine-readable form.
PROFILEPAGE
Google documents ProfilePage structured data for pages whose primary focus is a single person or organization associated with the site. The mainEntity of a ProfilePage is a Person or Organization.
This makes ProfilePage appropriate for pages such as:
- creator profiles - author profiles - organization profiles - employee profiles - "About Me" pages centered on one person
It is not a generic marker to place on every page of a network.
PERSON AND ORGANIZATION
Person and Organization describe different kinds of entities. A network should use the type that matches the real subject of the page rather than treating every branded property as a Person or every creator as an Organization.
SAMEAS
Schema.org provides sameAs for a URL that unambiguously indicates the identity of the item being described. In practice, it can be used to point from an entity on an owned website to an official external profile or another authoritative identity URL.
Example concept:
Creator profile on owned site -> official YouTube channel -> official social profile -> another authoritative profile for the same creator
The important word is SAME.
Do not use sameAs merely because two properties are related.
A parent network and one of its projects are related, but they are not necessarily the same entity. A creator and a company they operate are related, but they are not necessarily the same entity. A publication and its parent organization are related, but they are not necessarily the same entity.
Those distinctions matter more as a network grows.
STRUCTURED DATA DOES NOT REPLACE THE VISIBLE PAGE
Google states that structured data is a standardized format for classifying page information. It should describe the content that actually exists on the page rather than inventing relationships that users cannot verify from the page itself.
A useful operating rule is:
Visible relationship first. Machine-readable relationship second.
STRUCTURED IDENTITY IN A NETWORK
The practical value of structured identity increases when many properties exist because names alone become insufficient.
A network may need to distinguish:
- same entity - owned by - operated by - author of - publisher of - member of - project of - official channel for - related to
Not all of those relationships should be forced into sameAs.
For WRUnity education, the important lesson is therefore not "create another identity." It is "describe the identity and relationships that already exist accurately."
Source references: Google Search Central — ProfilePage structured data https://developers.google.com/search/docs/appearance/structured-data/profile-page
Schema.org — sameAs https://schema.org/sameAs
Put This Lesson to Work
Review the corresponding part of one channel: its identity, images, links, layout, or relationship to its website. Compare the current state with the guidance and write the change you would make.
Worked example
If a channel teaches repairs, its description can identify the intended viewer, the repair subjects, and the official guide website. An unrelated network directory does not help that viewer.
Your finished result
A documented channel improvement, a reason for it, and a check from the viewpoint of a new visitor.
Check your understanding
- Can you explain the main idea without repeating a slogan?
- What evidence or example supports your explanation?
- Which decision will you make differently, and why?