A.I Overviews

There is a new discipline sitting at the intersection of SEO and artificial intelligence that most UK marketing teams have not yet named, let alone mastered. It does not have a universally agreed label yet — some call it LLM SEO, others call it generative engine optimisation, others simply call it “writing for AI.” But the underlying concept is precise and learnable: if you understand how large language models process, evaluate, and recommend content, you can reverse-engineer that understanding into a content creation methodology that gets your brand cited, quoted, and recommended by AI systems at scale. This is not about tricking AI. It is not about keyword stuffing for robots or manufacturing artificial authority. It is about understanding the training logic and retrieval architecture of modern LLMs well enough to produce content that genuinely satisfies their evaluation criteria — which, as it turns out, closely mirrors what genuinely satisfies expert human readers. This guide breaks down exactly how to do it, with specific techniques applicable to UK businesses today. How LLMs Actually Evaluate Content: The Mechanics Behind the Recommendation Before you can create content that LLMs recommend, you need to understand what LLMs are actually doing when they process a query and select sources to cite or recommend. Large language models — the engines behind ChatGPT, Perplexity, Google’s Gemini, and the AI Overviews layer within Google Search — are trained on vast corpora of text from across the internet, weighted heavily toward content that was itself frequently cited, linked to, and referenced by other authoritative sources. This training process means LLMs have, baked into their parameters, a strong prior toward content patterns associated with credibility: clear attribution, specific factual claims, structured argumentation, consistent expertise signals, and accessible but precise language. When an LLM with retrieval augmentation (the ability to access live web content, as in ChatGPT Search or Perplexity) generates an answer, it follows a retrieval-then-synthesis process: it fetches candidate pages matching the query, evaluates their relevance and credibility signals, extracts the most pertinent passages, synthesises an answer, and cites its sources. The evaluation step is where prompt engineering for SEO intervenes. The signals that drive positive evaluation at this stage are not identical to traditional Google ranking signals — though they overlap significantly. They include: Semantic completeness — Does the content address the full scope of the query, including related subtopics and natural follow-up questions, or does it answer narrowly and stop? Claim specificity — Are assertions supported by specific numbers, named examples, referenced studies, or attributed quotes? Or are they vague generalisations that any source could have made? Entity density — Does the content contain clearly identified entities (people, companies, tools, locations, regulations, events) that allow the LLM to contextualise the information within its broader knowledge graph? Authoritativeness markers — Does the content demonstrate first-hand expertise through specific, experience-based observations that could not have been written without direct knowledge of the subject? Structural navigability — Can the LLM’s extraction system move through the content efficiently, identifying distinct claims and their supporting evidence without having to parse dense, undifferentiated prose? Prompt engineering for SEO is the discipline of deliberately optimising each of these signals within your content creation process — not as an afterthought, but as a core part of how the content is conceived, structured, and written. Write to the Full Semantic Scope of the Query, Not Just the Surface Question The most common mistake UK content teams make when creating blog posts and service pages is treating the target keyword as the full scope of what the content needs to cover. A post targeting “SEO for UK estate agents” that only discusses SEO in general terms — meta tags, backlinks, keyword research — is semantically incomplete relative to what an LLM would consider a comprehensive answer to that query. An LLM evaluating content for citation has been trained on thousands of documents about SEO for estate agents specifically. It knows that a genuinely authoritative piece on this topic would cover: Rightmove and Zoopla’s dominance in organic search and how estate agents compete around them, the role of local search and Google Business Profile for branch-level visibility, the specific schema types relevant to property listings, the seasonal keyword patterns in UK property search behaviour, and the regulatory content considerations imposed by the Property Ombudsman and Trading Standards. A post that covers all of this is semantically complete. An LLM encountering it has high confidence it is reading from a genuine subject matter expert. A post that covers only the generic points is semantically thin — and LLMs have a strong trained tendency to skip thin content in favour of comprehensive sources. How to apply this in practice: Before writing any piece of content, run the target query through ChatGPT, Perplexity, and Google’s AI Overview (from a UK IP address). Examine the subtopics, related questions, and specific entities mentioned in each AI-generated answer. These outputs are a direct window into what the LLM considers semantically necessary for a complete answer on this topic. Build your content structure to cover every subtopic the AI surfaces — and then go deeper on each one than the AI’s summary does. This process, done systematically, produces content that is both more useful to human readers and more citable by AI systems. The interests are aligned. Engineer Citable Sentences – The Atomic Unit of AI Recommendation In traditional content writing, the paragraph is the basic unit of composition. In prompt engineering for SEO, the citable sentence is the unit that matters most. A citable sentence is a single, self-contained assertion that is specific enough to be attributed, accurate enough to withstand scrutiny, and concise enough to be extracted without modification. LLMs cite at the sentence and passage level — they pull specific claims from source documents and incorporate them into synthesised answers. Content that is written as a series of citable, attributable claims gives AI systems far more raw material to work with than content written in flowing, essay-style prose where the

Most UK businesses treat structured data as a nice-to-have — something the developer adds at the end of a project, or something that gets half-implemented and forgotten about. That approach made sense when structured data was primarily about earning rich results: star ratings, FAQs, breadcrumbs, and product prices in the SERP. In 2026, the stakes are considerably higher. Structured data has become the primary language through which AI search systems — Google’s AI Overviews, ChatGPT Search, Perplexity, Gemini, and the generation of AI engines still in development — identify, verify, and cite sources. When an AI system is synthesising an answer and deciding which pages to attribute, it is not reading your content the way a human does. It is pattern-matching against structured signals: clearly defined entities, explicitly stated relationships, and machine-readable metadata that removes all ambiguity about what your page is, what it says, and who stands behind it. Put simply: without properly implemented structured data, your content is harder for AI systems to trust — and harder to cite. This is the complete guide to getting it right. Why Structured Data Matters More for AI Citation Than for Traditional SEO To understand the shift, you need to understand how AI search retrieval actually works. Traditional search engines rank pages by analysing links, content relevance, and hundreds of other signals — and then serve ranked URLs for the user to click through. The machine’s job ends at the SERP. The user decides what to read. AI search systems do something fundamentally different. They retrieve candidate pages, extract the most relevant information from those pages, synthesise it into a coherent answer, and then decide which sources to cite. The machine is now doing the reading, the summarising, and the attribution all at once. This changes what “optimised content” means. It is no longer sufficient to have content that ranks well in the traditional sense. The content must also be extractable — formatted and labelled in a way that allows an AI system to identify precisely what claim is being made, who is making it, and what context surrounds it. Structured data is the mechanism that enables extraction at machine speed and at scale. Pages with clear, comprehensive schema markup give AI systems a pre-processed map of their content. Pages without it force the AI to guess — and when the AI has to guess, it tends to default to the sources it can be most confident about. Usually, the large publishers, the government sites, and the established brands have years of entity corroboration behind them. For a UK small or medium-sized business competing for AI citations against larger, better-resourced competitors, structured data is the great equaliser. Implement it better than they do, and you signal a credibility that raw domain authority alone cannot manufacture. The Schema Types That Actually Drive AI Citations Schema.org has hundreds of structured data types. For the purpose of AI citation optimisation, you do not need to implement all of them. You need to implement the right ones — correctly, completely, and consistently across your entire site. Here are the schema types that have the clearest, most demonstrable impact on AI citation frequency in the UK market. 1. Organisation Schema – Your Brand’s Entity Foundation Organisation schema is the single most important schema type for any UK business pursuing AI citations. It is the machine-readable declaration of your brand’s identity — the structured data equivalent of raising your hand and saying, “this is who we are, this is what we do, and here is the evidence.” Every Organisation schema implementation should include, at a minimum: json { “@context”: “https://schema.org”, “@type”: “Organization”, “name”: “SEO Syrup”, “url”: “https://seosyrup.co.uk”, “logo”: “https://seosyrup.co.uk/logo.png”, “description”: “SEO Syrup is a London-based digital marketing agency specialising in SEO, paid advertising, web development, and marketing automation for UK businesses.”, “foundingDate”: “YYYY”, “address”: { “@type”: “PostalAddress”, “streetAddress”: “[Street Address]”, “addressLocality”: “Morden”, “addressRegion”: “London”, “postalCode”: “[Postcode]”, “addressCountry”: “GB” }, “areaServed”: “GB”, “sameAs”: [ “https://www.linkedin.com/company/seo-syrup”, “https://twitter.com/seosyrup”, “https://www.facebook.com/seosyrup”, “https://www.wikidata.org/wiki/[Your Wikidata ID]” ], “contactPoint”: { “@type”: “ContactPoint”, “contactType”: “customer service”, “telephone”: “[Phone Number]”, “email”: “[Email Address]”, “areaServed”: “GB”, “availableLanguage”: “English” } } The sameAs array is the most underused property in UK SEO. It creates explicit, machine-readable links between your website’s Organisation entity and every verified external profile of your business. Each link in that array is a corroboration signal — it tells AI systems “this Organisation entity is the same entity that appears at these other URLs.” The more authoritative those URLs are (LinkedIn, Wikidata, Companies House register, industry body directories), the stronger the entity verification. Implement this schema on your homepage. It should live there permanently, updated whenever your business details change. 2. Article and BlogPosting Schema – Turning Content Into Citable Sources Every piece of content you publish should be marked up with either Article schema (for news and editorial content) or BlogPosting schema (for blog posts and guides). This is the structured data that tells AI systems your content is a published, attributed piece of information — not just text on a web page. The properties that matter most for AI citation: author — Link to a Person entity (your author’s schema-marked profile page) rather than just a text string. An author that exists as a verifiable entity in the graph is a stronger citation signal than an anonymous or poorly attributed piece. datePublished and dateModified — AI systems, particularly Google’s, have a strong freshness bias. Explicitly declaring when content was published and last updated removes all ambiguity. Do not rely on the page’s HTTP headers or CMS metadata alone — put it in the schema. publisher — Link this to your Organisation entity. This creates a machine-readable relationship between the content and the brand, reinforcing the entity association with every indexed article. about — This underused property allows you to explicitly declare what topics, entities, or concepts your article is about, using schema.org Thing references. For a post about Google Ads, you might reference the SoftwareApplication entity for Google Ads, or the Organization entity