identified and prioritised
- ✗No llms.txt file: AI crawlers had no structured guidance on what content to prioritise
- ✗No FAQ or HowTo schema: key service pages had zero structured data for AI consumption
- ✗Keyword-optimised, not question-optimised: content answered no direct question a prospective client would ask an AI
- ✗No entity definition page: AI systems could not confidently identify who the firm was, what they specialised in, or where they operated
- ✗Zero AI citations: tested across ChatGPT, Perplexity, and Gemini for 12 relevant queries. Zero citations across all three.
- ✗Features, not outcomes: all copy described services, not the results clients experience. AI systems cite outcome language, not feature lists.
- ✓Prioritised fix list: 6 issues ranked by AI visibility impact, with exact implementation steps for each
- ✓llms.txt file specification: custom-written and ready to deploy, structured to guide AI crawler behaviour
- ✓FAQ schema template: for the firm's top 5 service pages, pre-written with AI-optimised question-answer pairs
- ✓Entity page blueprint: structure and copy guidance for an About page that AI systems can use to identify and recommend the firm
- ✓Content rewrite brief: for their three highest-priority pages, shifting from feature language to outcome language
- ✓Query cluster map: 15 questions their ideal clients are asking AI platforms right now, with gap analysis showing where the firm had no answer on record
The Insight
"This firm had done everything right for Google and it had worked. But Google's algorithm and AI's retrieval logic are fundamentally different. Google rewards domain authority and keyword density. AI rewards entity clarity, question-format content, and structured data. This firm was invisible to AI not because of poor content but because their content was built for the wrong reader entirely."
Jason Morris, Sticky Frog