Entity authority starts with structured data: one clean identity, machine-readable, linked to your real profiles. Fill in the company and copy out valid JSON-LD — the Organization block for your homepage, the FAQ block for your answer pages.
The organization
LinkedIn, Crunchbase, G2, Wikipedia — the records that corroborate you exist.
The founder (AI trusts people first)
The FAQ — your answer pages
Organization · paste in your homepage <head>
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://acme.com/#org",
"name": "Acme",
"url": "https://acme.com",
"description": "Acme is the revenue platform for B2B teams that want pipeline without the busywork.",
"sameAs": [
"https://www.linkedin.com/company/acme",
"https://www.crunchbase.com/organization/acme"
],
"founder": {
"@type": "Person",
"name": "Jane Smith",
"jobTitle": "CEO & co-founder"
}
}
Validate at validator.schema.org or Google's Rich Results test.
FAQPage · paste in the page that shows these Q&As
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Acme?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Acme is a revenue platform that helps B2B teams build pipeline without manual busywork."
}
}
]
}
The visible page content must match the schema — engines check.
The rest of the kit
The GEO Templates Pack
The canonical-description template, entity consistency checklist, FAQ page skeleton, content chunking template, and an llms.txt starter. One markdown file, free.
The monthly monitoring workbook from playbook chapter 07: a fixed question panel, a run log, and a dashboard that computes your mention rate per engine over time.