Technical SEO and GEO — Generative Engine Optimization, writing a site so ChatGPT, Perplexity, Gemini and Google's AI Overviews can cite it in their answers — aren't two separate jobs. They're the same structure, read by two different kinds of reader: a traditional crawler and a model pulling out verifiable facts.
I plan these with the pages, not on a site that's already finished: heading hierarchy with no skipped levels, one H1 per page, meta descriptions written to be read in full, structured data that states who you are, what you do and where you work.
For the generative side, one thing matters most: answering specific questions in sentences that stand on their own, out of context — that's exactly how a model quotes them. This page follows that rule too: it defines "GEO" the first time it comes up instead of assuming you know it.
{
"@type": "ProfessionalService",
"name": "Andrea Catapano",
"areaServed": ["Naples", "Portici", "Ercolano"],
"email": "hello@andreacatapano.com"
}what it includes
- Title, meta description, heading hierarchy and canonical checked on every page
- Person, ProfessionalService, BreadcrumbList and FAQPage structured data where it applies
- Content written to answer specific questions, quotable out of context
- Core Web Vitals and load-speed review
related case studies
faq
What is GEO, and why should I care?
GEO stands for Generative Engine Optimization: making a site quotable in the answers of ChatGPT, Perplexity, Gemini and Google's AI Overviews. People increasingly read the answer without clicking a result; if a site isn't written so a model can pull verifiable facts out of it, it doesn't get cited. The work is on page structure, structured data, and content that answers specific questions.