When a brand stops appearing in ChatGPT, or when its share of voice in Perplexity drops by half over a quarter, the typical response from the marketing org is to write more content. Sometimes a lot more. The thinking goes that if AI systems aren’t surfacing the brand, the fix is to feed them more material to work with. That instinct is a misdiagnosis. It’s a retrieval-layer fix being applied to what is increasingly a different kind of problem entirely, and the cost shows up as wasted budget, missed quarters, and a creeping sense that the work isn’t connecting to the outcomes anymore.
The mistake is treating AI visibility as a single problem when it isn’t. There are three structurally different layers between your brand and the answer a user receives, each with its own failure modes, its own fixes, and increasingly its own organizational owner. Diagnose the wrong layer, and the fix doesn’t land.
Where Most Of The Conversation Has Been Living
The first layer is retrieval. This is where the AI search optimization conversation has spent most of the last two years. The mechanics are familiar in shape if not in detail. When a model needs to answer a question grounded in real-world content, it pulls relevant material from external sources and uses that material to construct the response. The technical name is retrieval-augmented generation, or RAG, and the layer it operates on is the gateway between your content and the model’s output.
This is where crawlability, parseability, and chunk-friendliness do their work. If your content can’t be retrieved cleanly, nothing downstream matters. The visibility tracking platforms most marketing teams have evaluated this year measure outcomes that depend on this layer functioning, which is why they tend to reward the same disciplines that produced good results in classical search: structured content, schema markup, self-contained answers, clean technical implementation.
But retrieval has a structural limit, and Microsoft Research has been unusually direct about it. Plain RAG, in their words, struggles to connect the dots. It retrieves chunks of text that look relevant to the question, but it cannot reason about how those chunks relate to each other. When the answer requires synthesizing information across multiple sources, or when the question is broad enough that the right answer depends on understanding patterns across an entire dataset, retrieval alone breaks down. The model gets the chunks and has to guess at the relationships, and guessing is where hallucinations enter.
The discipline question this layer asks is straightforward. Can the model retrieve our content at all, and is it retrieving the right content for the right query? Most marketing teams have some version of this work in flight already, even if the specific tactics have shifted from classical SEO. But retrieval is only the gateway. Even when a model retrieves your content correctly, what it does with it depends on whether you exist as a recognized thing in the layer above.
Where Entity Recognition Does The Real Work
The second layer is the relationship layer, and the dominant structure on it is the knowledge graph. The major search infrastructures all maintain one. Google’s Knowledge Graph, Microsoft’s Satori, and the open knowledge graph built on Wikidata and schema.org collectively define how your brand is represented as an entity, what category you sit in, and which other entities you’re connected to.
This is the layer that decides whether AI Overviews and large language model responses treat you as a recognized member of your category, or as one fuzzy candidate string among many. Brands that exist as clean, well-defined entities get cited consistently. Brands that exist as undifferentiated tokens scattered across the open web get pattern-matched against fifty other candidates and lose more often than they win.
Knowledge graphs have been around long enough that the discipline is reasonably mature. Schema markup on owned properties, consistent naming and identifiers across the open web, structured presence on the high-trust nodes like Wikidata entries and review platforms, and the slow accumulation of brand mentions in contexts that the graph treats as authoritative. This is where the unlinked brand mentions conversation lives, because consistent contextual mentions strengthen the entity even without a hyperlink attached. The fix at this layer is structural rather than volume-based. Writing more content does almost nothing if the entity definition underneath it is fuzzy.
The discipline question here is harder than the retrieval-layer question. Are we a clean, defensible entity in our category, or are we still being pattern-matched against fifty other candidate strings? A brand that can’t answer that question affirmatively is going to lose ground in AI search, regardless of how much content it produces, because the second layer is where the model decides what your content is actually about.
The knowledge graph tells the model what your brand is. But increasingly, your brand has to function inside a third layer that most marketing teams haven’t met yet, where the model isn’t just understanding you, it’s being asked to reason about you on behalf of someone making a decision.
The Layer Enterprise Companies Are Quietly Building Right Now
The third layer is the context graph, and this one needs a careful introduction because most of the marketing conversation hasn’t reached it yet.
A context graph has the same structural shape as a knowledge graph, with entities, relationships, and typed connections, but it’s grounded differently. A knowledge graph models the world. It tells you what things are and how they relate in general. A context graph models a specific organization’s data, decisions, policies, and operational reality. The cleanest framing I’ve seen calls a knowledge graph the library and a context graph the operating manual written by the people who actually run the place. The library tells you what exists. The operating manual tells you what’s relevant, what’s authorized, and what to do about it right now. The library is read-only semantic infrastructure. The operating manual is a living operational layer that grows every time a business process executes.
What separates a context graph from anything that came before it is that governance lives inside the graph rather than alongside it. Policies, permissions, validity windows, and authorization rules are nodes the graph itself queries, not external documentation applied at the edges. When an agent retrieves something from a context graph, the result has already been filtered through what’s currently authorized, currently valid, and currently applicable. The graph is also continuously evolving, so what it knows about you this week is not necessarily what it knew last quarter. That’s where the word “governed” comes from when people in this space talk about governed retrieval. It isn’t a frame, but rather the architecture.
That architecture used to be invisible to anyone outside the organization that built it, which is why marketers haven’t had to think about it. That changed at Google Cloud Next ’26, when Google introduced the Knowledge Catalog inside its new Agentic Data Cloud. Google’s own description of the product, written in their own first-party blog content, says the Knowledge Catalog constructs a unified, dynamic context graph of your entire business, enabling you to ground agents in all of your business data and semantics. That sentence is the moment the term left the data-engineering blogs and entered enterprise procurement vocabulary.
The reason this matters for marketing is that context graphs are what’s going to power the next generation of agents inside your enterprise customers. Gartner projects that 40% of enterprise applications will be integrated with task-specific AI agents by the end of 2026, up from less than 5% in 2025. Procurement agents, competitive intelligence agents, content strategy agents, vendor evaluation agents. These agents won’t be reasoning about your brand from the open web. They’ll be reasoning about your brand from inside their company’s context graph, and what that graph says about you depends on what got ingested into it.
That ingestion is where the work for marketing lives. The brand that arrives at the context graph fragmented arrives weak. If your category positioning is inconsistent across owned and earned media, the graph picks up the contradictions and represents you ambiguously. If your entity data is fuzzy on the second layer, it stays fuzzy when it gets pulled into the third. If your third-party signal is thin or contradictory, the graph has nothing solid to anchor to. The work is upstream of the graph, but the consequences land downstream of it, inside an agent’s reasoning process that you’ll never see directly.
I think of this discipline as governed visibility. The practice of making sure your brand arrives at the context graph in a state that holds up under governed retrieval. Clean entity definition, consistent third-party representation, reliable structured data, and a category position that doesn’t fall apart when an agent traverses the relationships around it. Governed visibility isn’t a new tactic stack. It’s the result of doing the second-layer work well enough that the third layer has something solid to ingest.
The discipline question at this layer is the one most marketing teams haven’t started asking yet. When an agent inside our customer’s company is reasoning about us, what does it find, and is the version of us it finds the version we’d want it to act on?
Three layers, three different problems, three different fixes. But also three different responsibility zones, and that’s where most teams are quietly losing ground.
The Reason Most Teams Will Lose This Even Though They’re Working Hard
Each layer maps to a different organizational responsibility, and most marketing teams only own one of the three cleanly.
- The retrieval layer is shared with web, dev, and sometimes IT. Marketing influences what gets published, but the infrastructure that makes content retrievable sits in someone else’s domain.
- The knowledge graph layer is genuinely marketing’s territory. Schema discipline, entity definition, third-party signal, brand consistency, the slow structural work that compounds over years.
- The context graph layer is where IT owns the infrastructure inside the customer’s organization, but marketing has to influence what gets ingested. The work is upstream, and the consequences land downstream, often invisibly.
The teams that win in 2026 are the ones that figured out how to operate across all three responsibility zones rather than perfecting their work on just one. Most teams I see are still optimizing their owned content, which is the retrieval layer, while losing ground on entity definition, which is the knowledge graph layer, and remaining completely absent from the context graph conversation, which is the layer where some enterprise businesses are quietly standing up right now.
The work isn’t writing more content. The work is figuring out which layer the problem actually lives on, and building the disciplines to operate on all three. Governed visibility is the third-layer discipline that marketing is going to have to develop, whether or not the term sticks. The brands that build it now will look prepared in eighteen months. The brands that don’t will be wondering why their content investments stopped producing the visibility they used to.
If any of this lands or contradicts what you’re seeing inside your own teams, I want to hear about it. Drop a comment about which layer your work has been concentrated on, where you’re seeing the gaps, or where the responsibility zones break down inside your organization. The patterns are still forming, and the conversations in the comments tend to be fresher than anything else.
A lot of the measurement frameworks for this kind of work sit in The Machine Layer, which expands the original 12 KPIs for the GenAI era into something teams can actually run against.
More Resources:
This was originally published on Duane Forrester Decodes.
Featured Image: Master1305/Shutterstock; Paulo Bobita/Search Engine Journal
