Structured data is the machine-readable code on your website that tells search engines and AI models exactly who you are. For a person, it means Person schema written in JSON-LD, plus sameAs links that connect every profile you own into a single entity. Get it right and a machine reads your name, job, employer, and social accounts as facts rather than guesses.
This component is worth 10 points on the BlitzMetrics Personal Brand Score. It is the smallest line item by points, but it does the heavy lifting that the rest of the score depends on.
Why structured data matters
Search engines and language models do not read a page the way you do. They look for explicit signals. A headline that says “Award-winning founder and speaker” means nothing to a machine. A line of Person schema that names you, lists your job title, and points to your verified LinkedIn means everything.
Structured data resolves the identity problem. Most people share a name with dozens of others, so a crawler has to decide which Jane Smith wrote the article, which one runs the company, and which one spoke at the event. Person schema removes the ambiguity by tying one set of facts to one set of URLs.
It also feeds the next two stages of the method. Clean schema strengthens your single entity home page and gives Google the structured facts it needs to build your verified Knowledge Panel. Skip the schema and both stages stall, because the machine never confirms who the page is about.
How we score structured data
We check three things. First, valid Person schema in JSON-LD on your entity home page, with name, job title, employer, and image. Second, a complete sameAs array that lists every profile you control, so the machine merges them into one entity. Third, schema that validates cleanly with no errors in a structured-data testing tool.
Structured Data — max 10 points
| Score | What we see |
|---|---|
| 0 points | No Person schema. A machine has to infer who you are from plain text. |
| 1–6 points | Partial schema. Person markup exists but skips job title, image, or sameAs, or it throws validation errors. |
| 7–10 points | Complete, valid Person schema with a full sameAs array linking every owned profile into one entity. |
The bands reward completeness, not effort. A page either hands a machine clean facts or it does not, and the score reflects exactly which.
How to raise your structured data score
Work through these steps in order. Each one moves you up a band.
- Add a Person JSON-LD block to your entity home page with the @type, name, jobTitle, worksFor, and image properties filled in.
- Build the sameAs array next. List the canonical URL for every profile you own — LinkedIn, your company bio, your verified social accounts, your speaker pages, and any author archive.
- Match the facts to the visible page. The job title and employer in the schema should read the same as the text a human sees, so the machine and the reader agree.
- Validate the markup in a structured-data testing tool and clear every error and warning before you ship.
- Keep it current. When you change roles or launch a new profile, update the schema the same day so the entity never drifts out of date.
Done right, those few lines of code turn a web page into a fact a machine can trust, and that trust carries straight into your entity home and Knowledge Panel work.
Make yourself machine-readable. Start with the full Personal Brand Score framework to see how structured data feeds every other component, then fix your schema first — it is the fastest 10 points on the board.