What patents reveal about the foundations of AI search
Every time a new large language model (LLM) is released or Google rolls out a significant update to its AI Overviews, the SEO industry tends to react with a mix of panic and excitement. We often witness a form of collective amnesia, where professionals scramble to optimize for “new” features that were actually outlined in patent offices over a decade ago. We become so fixated on the immediate future that we forget to look at the historical blueprints that describe exactly how these systems are built to function. To succeed in the landscape of 2026 and beyond, the most effective strategy isn’t just to be a futurist; it is to be an archaeologist. Understanding the foundations of AI search requires digging into the technical filings that preceded the current era of generative AI. By looking back at foundational patents, we can understand the long-standing rules of the game, and by looking ahead, we can see how modern computing power is finally allowing search engines to enforce those rules at scale. The archaeology of SEO: Why history repeats in search There is a persistent misconception that mastering AI search requires becoming a master prompt engineer or staying awake 24/7 to read every research paper from OpenAI or Anthropic. While staying current is helpful, the underlying logic governing today’s search “magic” is often based on mathematical frameworks established years ago. To truly understand search, we must look at the documents that defined the intent of the engineers long before the hardware could keep up with their vision. We cannot discuss patent research without honoring the legacy of the late Bill Slawski. For two decades, Slawski served as the SEO industry’s premier archaeologist. While the rest of the community was debating keyword density and backlink quantities, Slawski was dissecting dry, technical filings to predict the exact state of search we find ourselves in today. His work at SEO by the Sea proved that search engines provide a roadmap of their intentions years before those intentions become reality. Agent Rank (2007): The precursor to E-E-A-T Slawski analyzed the concept of “Agent Rank” nearly 20 years ago. This patent described a system of digital signatures that would connect content to specific authors, assigning them reputation scores based on the quality and reception of their work. At the time, the SEO community largely ignored it because the technology to implement it globally didn’t seem to exist. Fast forward to today, and we refer to this concept as E-E-A-T (Experience, Expertise, Authoritativeness, and Trustworthiness). Google didn’t just invent these guidelines recently; they finally acquired the processing power and the machine learning sophistication to run the numbers on author reputation. The “Agent” is the “E” and the “A,” and the patent was the blueprint. The Fact Repository (2006): The birth of answer engines Long before the Google Knowledge Graph became a household name in marketing, Slawski identified patents for a “Browseable Fact Repository.” This 2006 filing described a system for extracting facts from the web and storing them in a structured way that a machine could easily navigate. This logic is the primary engine behind modern “answer engines.” When an AI provides a direct answer, it isn’t “thinking” in the human sense; it is querying a repository of facts anchored by the principles laid out in the mid-2000s. The algorithm isn’t magic; it is mathematics applied to historical blueprints. If you want to understand why a new feature appears today, look at the filings from 2007 to 2016. That is where the engineering rules were established. Strategy vs. Mechanics: Moving from strings to verified things In the modern SEO landscape, it is easy to get buried under a mountain of buzzwords. To stay focused, it is helpful to categorize your efforts into two buckets: strategy and mechanics. The most significant shift we have seen in recent years is the move from “strings” to “things,” but in 2026, the baseline has shifted again. We have moved from simple entities (things) to verified entities (verified things). An entity—whether it is a person, a brand, or a concept—is essentially worthless in the eyes of an AI if the system cannot prove it is real. We can use a construction metaphor to understand this hierarchy: Semantic SEO is the architecture This is the vision for your digital presence. Semantic SEO is about ensuring the meaning of your content aligns with the user’s intent. It involves mapping out topics and ensuring that the context of your site provides a comprehensive answer to a user’s underlying questions. Entity SEO is the bricklaying Entities are the building blocks. By using distinct nouns and structured data, you build a site that a machine can parse. You are moving away from ambiguous keywords and toward specific, identifiable concepts that exist in the search engine’s knowledge base. Verification is the mortgage This is the step most SEOs currently overlook. Verification is about turning entities into findable, provable facts that are connected to a verified human or organization. If your content isn’t connected to a provable expert, it is viewed as “noise.” In an era where AI can generate infinite content, the only way for a search engine to maintain quality is to prioritize content that is anchored to a verifiable source. AEO vs. GEO: Understanding the nuance of AI search The industry often uses the terms Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) interchangeably, but they are fundamentally different. They require different content structures, serve different user needs, and are rooted in different technological approaches. Answer Engine Optimization (AEO) AEO is designed for the “direct answer.” This is the realm of voice assistants like Siri and Alexa, or the single, definitive snippet at the top of a search result. It is a binary system. The search engine is looking for a specific fact to fulfill a specific query. To succeed in AEO, you need “confidence anchors.” These are unnuanced, structured facts. Because the engine is “fetching” rather than “synthesizing,” it needs high-confidence data. If your