Teams that have nailed technical SEO are often surprised when they audit their AI visibility.
On paper everything looks great:
- Next.js or similar modern framework
- Clean semantic HTML
- Multiple schema.org types wired correctly
- Sitemaps, robots.txt, llms.txt all present
- Fast, mobile-optimised pages
Then they ask a few LLMs:
> "What are the best tools for [our category]?"
…and their brand is either missing or described in a way no one on the team would sign off.
As a developer, this is frustrating because you’ve done the hard technical work. The missing pieces usually aren’t more markup — they’re about how the system understands your entity:
- Is it unambiguous who you are and what you sell?
- Do you explicitly connect your product and category in copy, schema and FAQs?
- Do your docs, blog and marketing pages tell a coherent story, or three different ones?
GEO (Generative Engine Optimization) sits on top of SEO and technical hygiene. The opportunity for dev teams is to treat “How will an LLM interpret this page, this component, this FAQ?” as a first-class concern alongside performance and accessibility.
If you’ve started to think about this layer in your stack, what checks or linters have you experimented with?
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.