Perplexity, Copilot, ChatGPT search, and every other AI-first interface run the same mechanic: one answer, a small citation set, no ranked list to scroll through.<\/p>\n\n\n\n
That’s what produces the pattern confusing so many teams: impressions rising, CTR falling, total clicks flat.<\/strong> Read that pattern correctly. Your URL showing up as the citation behind an AI answer counts as an impression \u2014 you were surfaced. The user just didn’t need to click, because the answer already satisfied them. That’s not a failing page. That’s a page participating in the AI answer.<\/p>\n\n\n\n The metric worth tracking going forward isn’t click-through rate. It’s citation rate \u2014 are you the source AI engines choose when someone in your category asks a question? We’ll come back to how to measure that. For now, the strategic point is this: becoming citable is editorial and structural work that compounds once it’s done. Recovering from invisibility, once an AI has learned to answer your category without you, takes considerably longer. Waiting to see if AI Overviews are “here to stay” is what turns a solvable content<\/a> problem into a compounding brand-visibility one.<\/p>\n\n\n\n Google’s E-E-A-T<\/a> framework hasn’t gone away \u2014 but the signals behind each letter have changed shape. Classic SEO checked whether your page mentioned<\/em> expertise. AI retrieval checks whether it can resolve<\/em> that expertise against a known entity.<\/p>\n\n\n\n Three entity types decide whether you get cited: Author<\/strong> (who wrote it, resolved via Person schema<\/a>), Brand<\/strong> (who’s publishing, resolved via Organization schema with logo, founder, and funding data), and Product\/Service<\/strong> (what’s being discussed, resolved via Product schema with distinguishing attributes). Author and Brand entities carry the most citation weight; Product entities are what let a citation turn into an agentic commerce action. This is exactly the ground covered in our piece on structured data for personal branding and E-E-A-T<\/a> and its product-side counterpart, Product Knowledge Graph and E-E-A-T<\/a>.<\/p>\n\n\n\n Schema.org is how you make that identity legible to a machine. It’s no longer a rich-snippet nicety \u2014 it’s the API your site exposes to language models. There’s an economic reason it matters beyond semantics, too. Every LLM inference has a compute-bound “prefill” phase where it reads the entire input context in one pass. That phase has a finite budget per query. Structured, well-typed content is cheap to parse; unstructured prose burns that budget before the model even starts reasoning \u2014 and gets dropped from the context window before it has a chance to be cited. Cheap-to-read content wins the budget. Expensive-to-parse content doesn’t get read at all.<\/p>\n\n\n\n It’s worth being precise about what schema alone can and can’t do. WordLift’s own research \u2014 testing three retrieval configurations across 2,443 queries and four verticals \u2014 found that JSON-LD<\/a> by itself produces only marginal lift in standard retrieval. The gain shows up once something can traverse<\/em> the graph: an agent following a Product’s brand to an Organization page, then to that organisation’s Person-schema author. Schema is necessary. It pays off when there’s a connected graph for an agent to follow \u2014 which is precisely the architecture we describe in how knowledge graphs power AI SEO<\/a>.<\/p>\n\n\n\n Before deploying a single schema type, decide what your brand should be known for. List the five to ten concepts you want AI engines to associate with your brand, map each to its corresponding Wikidata or Schema.org entity, and note which ones you already own with content and markup versus which are gaps. Those gaps are your editorial roadmap. Most teams skip this step and go straight to schema \u2014 don’t. Our guide to building topical authority through entity analytics<\/a> walks through the exercise in more depth.<\/p>\n\n\n\n Give every entity a stable URI, and make the relationships between them explicit: author writes article, article covers topic, brand sells product. A pile of well-marked-up pages that don’t reference each other is a stack of business cards. A connected graph is queryable infrastructure \u2014 and it’s the only version an AI engine can actually use. Extend those connections outward, too, cross-referencing your entities to Wikidata, LinkedIn, and ORCID via sameAs links. An entity the AI can resolve against a known reference is an entity it can cite with confidence.<\/p>\n\n\n\n Not all schema carries equal weight. Deploy in this order:<\/p>\n\n\n\n Validate every deployment against Google’s Rich Results Test and the Schema.org validator, then monitor monthly for drift. In practice, most sites we audit have this backwards \u2014 Article and BreadcrumbList are solid, Organization is missing or incomplete, which is the one schema type carrying the most brand-authority weight. Structured data automation<\/a> is what makes maintaining this at scale realistic for an editorial team rather than a one-off technical project.<\/p>\n\n\n\n This is the step most competitors skip entirely, which makes it the highest-leverage one available. When AI Mode processes a substantive question, it doesn’t answer it directly \u2014 it decomposes it into eight to twelve parallel sub-queries, each hitting a different sub-intent: a definition, a comparison, a constraint check, an alternative. Your content isn’t competing to answer one headline keyword. It’s competing to answer whichever of those eight to twelve sub-queries it covers best.<\/p>\n\n\n\n For each priority page, generate the sub-query map an AI Mode fan-out would produce for your category, then audit your existing content against it: which sub-queries are already answered, and which are missing? The gaps become your enrichment roadmap \u2014 turning a thin product page into a fan-out-ready one by adding structured answers to the specific questions your buyers are actually asking, not just the one you optimised the title around.<\/p>\n\n\n\n If your content touches products, there’s a layer beneath Schema.org worth prioritising now, while almost nobody else has: the GS1<\/a> Web Vocabulary, and specifically GS1 Digital Link. The GTIN is the only global primary key for physical goods, and both Google’s Universal Commerce Protocol and OpenAI’s Agentic Commerce Protocol enforce it as the canonical identifier. Without a sameAs link to https:\/\/id.gs1.org\/01\/{GTIN}, your product on your own site and your product on a marketplace are unresolvable as the same entity to a shopping agent \u2014 which makes you invisible to any agent transacting across retailers.<\/p>\n\n\n\n Pair that identifier with Schema.org’s potentialAction property \u2014 attach BuyAction, ReserveAction, or SubscribeAction to a Product or Organization, and you’ve declared something an agent can actually execute, not just read about. Fewer than 100 domains globally have implemented BuyAction properly, which makes it one of the more asymmetric opportunities available to any brand with a product catalogue. For the full picture on identifier strategy, see GS1 Digital Link<\/a> and our strategic roadmap for GS1 Digital Link adoption<\/a>.<\/p>\n\n\n\n A healthy trend in the AI-search era doesn’t look like a healthy trend in the old one. Here’s what to expect, and what to actually monitor:<\/p>\n\n\n\n Monthly, segment Search Console impressions by query type (fact, comparison, how-to), and run your top twenty category queries through the major AI engines to see who’s being cited and whether your position holds. The moment genuinely worth worrying about is impressions staying flat and<\/em> citations failing to appear anywhere \u2014 that combination is invisibility taking hold, not the normal shape of AI participation.<\/p>\n\n\n\n If you want to see where your own brand currently stands, book a free AI Visibility Audit<\/a> \u2014 we’ll run your top 20 category queries through Google AI Mode, Perplexity, Copilot, and ChatGPT, and show you exactly where you’re cited, where a competitor is cited instead, and which structural changes would move you into the citation set.<\/p>\n\n\n\n Yes, and the returns tend to be higher there. Product entity clarity, GS1 Digital Link on every SKU, and verified availability and pricing are the specific enablers that let AI shopping agents recommend and transact against your inventory rather than a competitor’s \u2014 the technical lift is the same as for editorial content, but the path to ROI is more direct.<\/p>\n\n\n\n Structural changes \u2014 schema deployment, entity graphs, sameAs links \u2014 tend to show as citation shifts within 4\u20138 weeks in third-party engines and 8\u201316 weeks in Google AI Mode. Query fan-out enrichment often moves faster, sometimes in 2\u20134 weeks, since it’s answering gaps that already exist in your content. The compounding effect takes longer to build: a knowledge graph that’s been running for two years earns citations at a rate a freshly deployed one doesn’t yet match.<\/p>\n\n\n\n It’s not a formally supported standard from Google or the major AI engines as of this writing. Some engines treat it as a soft signal; none treats it as authoritative the way robots.txt is. It’s fine to deploy if you want the option, but it isn’t a substitute for schema and entity work \u2014 it operates at the wrong layer of the stack to move citation on its own.<\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n None of this is theoretical for WordLift’s own clients. The same entity-and-graph approach behind this framework is how EssilorLuxottica trains its AI with WordLift<\/a> to keep its content briefs grounded in a real knowledge graph rather than guesswork.<\/p>\n\n\n\n <\/p>\n\n\n\nWhat Google’s AI Actually Looks For<\/h2>\n\n\n\n
\n
Three entity types decide whether you get cited<\/strong><\/h3>\n\n\n\n
![\"\"](\"https:\/\/wordlift.io\/blog\/en\/wp-content\/uploads\/sites\/3\/2026\/07\/three-sources--1024x371.png\")
<\/figure>\n\n\n\nThe Four-Step Framework to Earn AI Citations<\/h2>\n\n\n\n
![\"\"](\"https:\/\/wordlift.io\/blog\/en\/wp-content\/uploads\/sites\/3\/2026\/07\/four-step-framework-1024x366.png\")
<\/figure>\n\n\n\nStep 1: Map Your Topical Authority<\/h3>\n\n\n\n
Step 2: Build a Connected Knowledge Graph<\/h3>\n\n\n\n
Step 3: Deploy Structured Data, in Priority Order<\/h3>\n\n\n\n
\n
Step 4: Enrich for Query Fan-Out<\/h3>\n\n\n\n
![\"<p>Get](\"https:\/\/hubspot-no-cache-eu1-prod.s3.amazonaws.com\/cta\/default\/145813311\/interactive-432668836052.png\")
\n <\/a>\n<\/div>\n\n\n\n\nFor E-commerce: The Agentic Commerce Layer<\/h2>\n\n\n\n
Measuring What Works: From CTR to Citation Rate<\/h2>\n\n\n\n
\n
Key Takeaways<\/h2>\n\n\n\n
\n
Start Your AI Visibility Audit<\/h2>\n\n\n\n
![\"Start](\"https:\/\/hubspot-no-cache-eu1-prod.s3.amazonaws.com\/cta\/default\/145813311\/interactive-432668968162.png\")
\n <\/a>\n<\/div>\n\n\n\n\n\nFrequently Asked Questions<\/h2>\n\n\n\n
Does this work for e-commerce specifically?<\/h3>\n\n\n\n
How long until results show up?<\/h3>\n\n\n\n
Is llms.txt worth implementing?<\/h3>\n\n\n\n
Where to Go From Here<\/h2>\n\n\n\n