Before you start
- A way to add code to your page: direct HTML, or a “code injection” or “header scripts” box in your site builder.
- The page addresses, a logo address (at least 112×112 pixels) and a headshot address.
- The addresses of your official profiles.
- A verified Search Console property. See the personal site guide.
How markup maps to your page
Every value in the markup should match something a visitor can see on the page. Google’s rule is plain: don’t mark up content that isn’t visible to readers.
"@type": "Person",
"name": "Jane Example", 1
"jobTitle": "Chief Operating Officer", 2
"worksFor": { "name": "Example Corp" }, 3
"image": ".../jane-example.jpg", 4
"sameAs": [ linkedin, company bio ] 5
Step by step
-
Step 1: Pick the right page and type
-
A person: use
ProfilePagewithmainEntityset to aPerson, on your About page. Google says the page’s main focus must be a single person or organisation connected to the site. -
A company: use
Organization(or a more specific type such asLocalBusiness) on the home page or one About page. It doesn’t need to be on every page.
-
A person: use
-
Step 2: Use the documented properties
For a person in
ProfilePage, Google requiresnameand recommendsalternateName,description,imageandsameAs. For anOrganization, nothing is required; Google recommendsname,url,logo,sameAs, address and contact details, among others.sameAslists pages that unambiguously identify the same person or company, such as your LinkedIn profile.jobTitleandworksForare valid schema.org properties for a Person, though Google doesn’t list them for any rich result. -
Step 3: Paste the block into your page
Copy a template below, replace every example value, and delete any line you can’t show on the page. Paste it inside a
<script type="application/ld+json">tag, in the page’s head or body. Google recommends this JSON-LD format and can also read it when a site builder adds it with JavaScript. -
Step 4: Test it with Google’s Rich Results Test
Open the Rich Results Test, enter your page address (or paste the code with “Code instead of URL”), and run it. Look for “Profile page” or “Organization” under detected structured data, with no errors.
Illustration. A passing test: the type is detected (1) and marked valid (2). -
Step 5: Check the full vocabulary
The Rich Results Test only checks types Google uses. Run the same page through the Schema Markup Validator at validator.schema.org to catch mistakes in properties like
jobTitle. Remove any comments from the code first; they make JSON-LD invalid. -
Step 6: Publish and ask Google to recrawl
In Search Console, inspect the page and click Request indexing. Google says to allow several days for it to pick up the change.
Copy-and-paste templates
A. Personal site (your About page)
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"url": "https://www.example.com/about",
"dateCreated": "2026-11-16T09:00:00+00:00",
"dateModified": "2026-11-16T09:00:00+00:00",
"mainEntity": {
"@type": "Person",
"@id": "https://www.example.com/#person",
"name": "Jane Example",
"alternateName": "Jane Q. Example",
"description": "Chief Operating Officer at Example Corp",
"jobTitle": "Chief Operating Officer",
"worksFor": {
"@type": "Organization",
"name": "Example Corp",
"url": "https://www.example-corp.com/"
},
"image": "https://www.example.com/images/jane-example.jpg",
"url": "https://www.example.com/",
"sameAs": [
"https://www.linkedin.com/in/jane-example",
"https://www.example-corp.com/leadership/jane-example"
]
}
}
</script>
B. Company site (home or About page)
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/#organization",
"name": "Example Corp",
"alternateName": "ExampleCo",
"legalName": "Example Corporation Inc.",
"url": "https://www.example.com/",
"logo": "https://www.example.com/images/logo.png",
"description": "Example Corp makes accounting software for small manufacturers.",
"foundingDate": "2012-03-01",
"email": "contact@example.com",
"telephone": "+1-555-010-0100",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Example Street",
"addressLocality": "Springfield",
"addressRegion": "IL",
"postalCode": "62701",
"addressCountry": "US"
},
"sameAs": [
"https://www.linkedin.com/company/example-corp",
"https://www.youtube.com/@examplecorp"
]
}
</script>
C. Optional: preferred site name (home page only)
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Example Corp",
"alternateName": ["ExampleCo", "example.com"],
"url": "https://www.example.com/"
}
</script>
Template C tells Google the site name you prefer; it isn’t supported for subfolders.
What to expect
The test tools answer instantly. Google says to allow several days for a recrawl. Whether a logo, knowledge panel or AI answer then changes is up to Google’s systems; nothing is promised.
What this can’t do
- Valid markup doesn’t guarantee any rich result or knowledge panel.
- Google says there is no special markup for its AI features, and structured data isn’t required to appear in them.
- Breaking the guidelines can bring a manual action that removes rich result eligibility.
Common mistakes
-
Marking up facts not on the pageEvery value should be visible to readers.
-
Conflicting factsA title in the markup that differs from the page or LinkedIn.
-
Review stars about yourselfSelf-serving reviews on your own LocalBusiness or Organization page aren’t eligible for stars.
-
Broken JSONComments, trailing commas or smart quotes stop it parsing.
-
Placeholder imagesUse a real headshot or logo; logos need at least 112×112 pixels.
-
ProfilePage on the wrong pageIt belongs on a page mainly about one person, not a shop’s home page.
Sources
Checked against the official pages on 16 November 2026. Platforms change their screens and rules often; if something looks different, follow the official page.
- Google Search Central: Profile page (ProfilePage) structured data — which pages qualify; required and recommended properties
- Google Search Central: Organization structured data — recommended properties, logo rules, placement, recrawl
- Search Console Help: Rich Results Test — testing a URL or code; what the tool can’t test