Schema markup, entity density, citation anchors, and the structural signals AI models actually read. A component-by-component teardown of the ideal GEO page.
If you've read our piece on GEO basics, you understand why AI visibility matters. Now let's get specific: what does an AI-optimised page actually look like, component by component? Not in theory — in practice. We're going to walk through every structural element that matters, explain what AI models do with each one, and give you a checklist you can use to audit any page on your site today.
Think of this as a teardown. We're disassembling the ideal GEO page and laying out every part on the workbench. By the end, you'll know exactly what's missing from your own pages and what to fix first.
Component 1: The title tag and H1
The title tag is the first thing an AI model reads when it encounters your page. It's used for entity classification — the process by which LLMs determine what this page is fundamentally about, and which entities it involves.
The most common mistake is being clever instead of clear. A title like "The Future of Work Is Here" tells an AI model almost nothing. A title like "Notion: Project Management and Documentation Software for Teams" gives it entity name, category, primary function, and target audience in one line.
The formula that works: [Entity Name]: [Category] + [Primary Value Proposition or Audience]. Some examples:
- "HubSpot: CRM Software for Marketing and Sales Teams" (beats "The Best CRM")
- "Figma: Collaborative Interface Design Tool for Product Teams" (beats "Design Better Together")
- "Arclign: Generative Engine Optimisation Agency for B2B Brands" (beats "We Grow Brands")
Your H1 should mirror or closely match the title tag. Divergence between H1 and title tag can create ambiguity about what the page is authoritative on. Consistency signals confidence to AI classifiers.
Component 2: JSON-LD schema markup
Schema markup is the most direct communication channel you have with AI systems. While everything else on a page is written for humans and interpreted by machines, JSON-LD schema is written explicitly for machines. It's the part of your page that says: "Here is precisely structured, unambiguous data about this entity."
For most B2B websites, the priority schema types are:
- Organization schema — Name, URL, logo, founding date, description, contact info, social profiles. This anchors your brand as a defined entity in the knowledge graph.
- FAQPage schema — Wraps your FAQ section and makes each Q&A pair machine-readable as a structured answer. Extremely high leverage for citation rate.
- Article schema — Author, publication date, publisher. Establishes content credibility and attribution.
- HowTo schema — For instructional content. Tells AI the content has procedural structure and established steps.
- BreadcrumbList schema — Clarifies content hierarchy and site structure.
Here's what a well-formed Organization schema looks like:
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Organization", "name": "Arclign", "url": "https://arclign.ai", "logo": "https://arclign.ai/logo.png", "description": "Arclign is a generative engine optimisation agency that helps B2B brands earn citations in AI search tools including ChatGPT, Perplexity, and Gemini.", "foundingDate": "2024", "sameAs": [ "https://linkedin.com/company/arclign", "https://twitter.com/arclign" ], "contactPoint": { "@type": "ContactPoint", "contactType": "sales", "email": "hello@arclign.ai" } } </script>
"Schema is how you speak directly to the machine. It's the one part of the page written entirely for AI consumption."
Component 3: The entity definition paragraph
Every page should have one paragraph, positioned near the top of the body content, that unambiguously defines the central entity. This is the paragraph that answers, in plain language: what is this? Who is it for? What does it do? What problem does it solve?
For a product page, this might read: "Notion is a connected workspace platform for teams and individuals. It combines notes, databases, wikis, and project management into a single application, enabling teams to replace multiple productivity tools with one unified environment. It is used by over 30 million people globally, from individual freelancers to enterprise teams at companies including Figma, Pixar, and Nike."
That one paragraph gives an AI model everything it needs to accurately describe your product in a summary. Without it, the model is forced to infer — and inference creates inaccuracy. The entity definition paragraph is essentially the "first citation" you're providing for yourself.
Keep it to 3–5 sentences. Be factual, not promotional. Avoid superlatives and claims that can't be verified. The goal is accuracy and completeness, not salesmanship.
Component 4: Heading hierarchy
AI models parse your heading tree to understand the scope and organisation of your content. A logical, hierarchical heading structure communicates not just what topics you cover, but how they relate to each other and to the central entity.
- H1: Entity name + primary topic. Should be unique per page.
- H2: Major subtopics that function as natural question-answer pairs. "How does X work?" "What are the benefits of X?" "How does X compare to Y?"
- H3: Supporting detail under each H2. Specific features, sub-topics, caveats.
The key insight: AI models treat H2 headings as potential query matches. When someone asks Perplexity "How does [your product] work?" — if you have an H2 that says "How [Your Product] Works" followed by a clear, direct explanation, you've created a perfect citation target. Your heading is the question; the content beneath it is the answer.
Avoid heading structures that are purely promotional ("Why We're the Best"), vague ("Our Approach"), or non-hierarchical (jumping from H1 to H4). These patterns suggest disorganised thinking and reduce citation probability.
Component 5: FAQ sections with schema
FAQ sections are arguably the highest-leverage component on an AI-optimised page. Each question-answer pair is a pre-formatted citation target. If someone asks an AI tool a question that matches one of your FAQ items, and your page has FAQPage schema correctly applied, you are perfectly positioned to be the source.
The rules for effective GEO FAQ sections:
- Write each answer in 2–4 sentences. Direct, declarative, complete.
- Use the question itself as the heading (H3 under an H2 "Frequently Asked Questions").
- Answer the question in the first sentence — don't build to the answer.
- Cover at minimum: what, how, why, who for, how much, how does it compare.
- Wrap the entire section in FAQPage schema with each Q&A as a Question and Answer entity.
A page with 8–12 well-written FAQ items and proper FAQPage schema will generate significantly more AI citations than the same page without the schema. In our client work, we've seen 3–5x citation rate increases from FAQ schema implementation alone.
Component 6: Citation anchors
Citation anchors are the signals that tell AI models your content is credible enough to cite in its own outputs. The primary technique is simple: when you mention a statistic or claim, name the source explicitly and in a way the AI can parse.
Instead of: "Studies show that AI search queries are growing rapidly." Write: "According to a 2025 Gartner report, AI-powered search interactions grew 340% year-over-year among enterprise knowledge workers." The named source, the year, and the specific data point together create a citation anchor. AI models learn to treat content that references named sources as more authoritative — and more worthy of being cited themselves.
Additional citation anchor techniques:
- Link to authoritative external sources (Gartner, HBR, McKinsey, industry associations)
- Reference well-known researchers or practitioners by name and title
- Cite your own original research ("In our 2025 analysis of 200 B2B brands...")
- Include publication dates on all content — undated content signals lower reliability
Component 7: Author credibility signals
AI models assess content trustworthiness through several author-related signals. Anonymous content — posts with no byline, or a generic "Team" attribution — scores lower on credibility heuristics. Named, verifiable authors with clear credentials score higher.
The author credibility stack for GEO:
- Byline with full name and title. "Sarah Chen, Head of Technical SEO at Arclign" is a credibility signal. "Staff Writer" is not.
- Author bio section. A paragraph about the author's background, expertise, and relevant experience. Link to their LinkedIn profile.
- Author schema. Person schema linking the author entity to your Organisation schema. This creates a verifiable knowledge graph relationship.
- Publication date + last updated date. Both dates matter. "Last updated: January 2026" signals that the content is maintained and current.
- Author elsewhere on the web. If your authors also publish on industry sites, contribute to LinkedIn, or appear in podcasts, those external signals reinforce their authority in AI training data.
Full Component Checklist — AI-Optimised Page
- Title tag: Entity name + category + audience (clear and explicit)
- H1 mirrors or closely matches title tag
- Organization schema (JSON-LD) present and complete
- Article or WebPage schema with author, date, publisher
- Entity definition paragraph in first 200 words of body content
- Logical H1 → H2 → H3 heading hierarchy
- H2 headings written as natural question-answer pairs
- FAQ section with 8+ items and FAQPage schema
- Each FAQ answer is 2–4 sentences, direct, complete
- Named source citations for statistics and claims
- External links to authoritative publications
- Author byline with full name, title, and LinkedIn
- Author bio section with credentials
- Person schema for author entity
- Publication date + last updated date visible
- Page load time under 2.5 seconds
- BreadcrumbList schema for navigation context
- HowTo schema for any instructional content
- Meta description: 140–160 chars, includes entity name and primary topic
- Internal links to related authoritative pages on your domain
What to avoid
Just as important as what to include is what to remove. Several common content patterns actively suppress your AI citation rate:
- Keyword stuffing — AI models recognise unnatural keyword density and treat it as a credibility signal against the page
- Thin content — pages under 600 words with no structure rarely appear in AI-generated answers for competitive topics
- Missing entity definition — without a clear "what is this" paragraph, AI models must guess, and guesses create inaccuracies
- No schema markup — the page is entirely dependent on natural language parsing, which is less reliable than structured data
- Anonymous authorship — no byline or generic team attribution reduces credibility scoring
- Outdated content — pages that haven't been updated in 2+ years signal unreliability; include "last updated" dates and refresh key pages annually
GEO is not about gaming AI systems — it's about communicating clearly with them. Every component described in this article is about reducing ambiguity, establishing credibility, and making your expertise legible to a machine reader. The pages that win AI citations aren't the ones trying to trick the algorithm. They're the ones that are genuinely the best, clearest, most credible answers to the questions they're optimised for.
Start with your highest-traffic pages. Run them through this checklist. Fix the gaps. Then move to your category definition pages and your FAQ content. Within 6–8 weeks, you'll start seeing a measurable shift in how AI tools represent your brand.