Person markup should describe the real person featured on a biography page. On Squarespace, first inspect existing markup and confirm that your plan supports the required code-injection feature. Add only accurate facts that the visible biography supports.
01
Prepare the biography and identity fields
Confirm the person's name, role, biography URL, authorized image, and genuine profile links. Use Schema.org's Person vocabulary for relevant properties. Do not add awards, qualifications, or employer relationships merely because a template includes a field. If the page is a profile, review Google's ProfilePage requirements separately; a valid Person object alone does not guarantee a special search appearance.
02
Place the code on the intended page
Squarespace's current help explains page-specific header injection through the page settings' Advanced area. This differs from the sitewide Header field, which inserts code across the site. A single person's biography generally should not be declared as the main subject of every service page. Save a copy of the original settings before adding a JSON-LD script so you can reverse an error.
- Check whether Squarespace or another integration already outputs similar markup.
- Use the biography's actual canonical URL and consistent identifiers.
- Avoid copying real personal details from a sample snippet.
03
Validate the live page
After saving, inspect the published page rather than relying only on the editor preview. Check JSON syntax, the structured-data interpretation, and any Google feature-specific requirements. Compare every substantive claim with the visible biography. Test mobile appearance and basic navigation because custom code can cause unexpected problems. Record the change and review it when the person's role or profile links change.
Frequently asked questions
Should I put Person markup in the global footer?
Only if it accurately belongs sitewide and does not conflict with page-specific facts. For one biography, page-level placement is usually easier to maintain correctly.
Why does valid markup not appear in search?
Validation confirms only part of eligibility. Google decides whether to show supported features; indexing, content requirements, and other factors still apply, with no guaranteed display.
Continue with your next step
Related guides on this topic
Sources and policies
Check the current policy before submitting a request.
You do not have to figure out the next step alone.
Share the URLs and explain your concern. We will review the context and explain which options are worth assessing.
Request a confidential reviewOr call (307) 429-2531Educational information, not legal advice. Outcomes depend on the facts and decisions made by third parties.