I am seeing Google Search Console’s page indexing report running more than two weeks behind, with the latest visible timestamp still showing June 11, 2026. That means I cannot get a fresh view of page indexing data for the pages on my site right now.
When I check the Google Search Console page indexing report, I would expect to see that June 11 date instead of a more recent update. The delay is inconvenient, especially when I am trying to understand whether Google has recently found, crawled, or indexed important pages.
This report matters because it shows me which pages Google can find and index on a website. It also helps me spot indexing problems Google may have encountered while crawling the site.
I can access the report in Search Console over here, or I can open Search Console, go to the Indexing section, and then select Pages.
Inside the report, I usually see a chart with indexed pages in green and not indexed pages in gray. I can also overlay impressions on the chart, which makes it easier to connect indexing patterns with search visibility.
Below that chart, Google lists the reasons pages on the website are not being indexed. That section is often where I look first when I need to understand whether the issue is related to crawling, duplication, redirects, noindex signals, canonical choices, or another indexing reason.
For more details about how the page indexing report works, I can refer to Google’s help document.
Why I care: if I am trying to debug why Google has not indexed specific pages over the past couple of weeks, this delay leaves me with limited visibility. Until Google updates the report again, I would need to rely on my own SEO analysis or use the URL inspection tool to investigate indexing issues one page at a time.
The delay is frustrating, but I do not see it as especially uncommon. Search Console reports can lag from time to time, so for now I would treat the page indexing report as stale and avoid making major conclusions from that delayed data alone.
I see vibe coding as one of the most accessible ways to create small pieces of software with AI tools like ChatGPT, Cursor, Replit, and Gemini. Instead of writing code line by line, I describe what I want in plain language, receive working code in return, paste it into an environment like Google Colab, run it, and test the result.
In this guide, I’ll explain how I approach vibe coding, where I think it works well, where it breaks down, and which SEO examples can inspire practical projects of your own.
Vibe coding variations
I use “vibe coding” as a broad term, but it helps to separate it from nearby approaches:
Type
Description
Tools
AI-assisted coding
AI helps write, refactor, explain, or debug code. I usually associate this with developers or engineers who already understand the systems they are building.
GitHub Copilot, Cursor, Claude, Google AI Studio
Vibe coding
AI handles most of the work after I provide the idea or prompt.
ChatGPT, Replit, Gemini, Google AI Studio
No-code platforms
Platforms handle what I ask for through visual interfaces, drag-and-drop workflows, or background automation. Many now use AI, but they existed before AI became mainstream.
Notion, Zapier, Wix
For this guide, I’m focusing only on vibe coding.
The barrier to entry is low. In most cases, I only need a ChatGPT account, free or paid, and access to a Google account. Depending on the project, I may also need API access or subscriptions to SEO tools such as Semrush or Screaming Frog.
I also like to set expectations early: by the end of this kind of workflow, I’m usually aiming to run a small program in the cloud. If I want to build a SaaS product or software I plan to sell, I treat AI-assisted coding as the more realistic path because it usually requires more technical knowledge, more testing, and more budget.
Vibe coding use cases
I find vibe coding most useful when I’m working with clear buckets of data and need a helpful outcome, not a perfect one. That might mean finding related internal links, adding pre-selected tags to articles, comparing groups of URLs, or building something playful where the output does not need to be exact.
For example, I built an app that creates a daily drawing for my daughter. I type a short phrase about something she told me, such as “I had carrot cake at daycare.” The app uses examples of drawing styles I like and a few pictures of her, then generates a drawing as the final output.
When I ask for precise changes, the tool often gets worse. I once asked it to remove a mustache, and instead it recolored the image. That is exactly the kind of limitation I expect with this approach.
If my daughter were a client reviewing every detail, I would need someone with Photoshop or similar skills to make exact edits. For this use case, though, the result is good enough, and that is where vibe coding shines.
I would be cautious about building commercial applications solely through vibe coding. Some companies may even need vibe coding cleaners to clean up AI-generated work. But for demos, MVPs, internal tools, and quick experiments, I see vibe coding as a useful shortcut.
How I create SEO tools with vibe coding
When I create an SEO tool with vibe coding, I usually follow three steps:
I write a prompt describing the code I need.
I paste the code into a tool such as Google Colab.
I run the code and check whether the results match what I expected.
Here’s a real prompt example from a tool I built to map related links at scale. After crawling a website with Screaming Frog and extracting vector embeddings through the crawler’s OpenAI integration, I vibe coded a tool to compare topical distance between the vectors for each URL.
This is exactly what I wrote in ChatGPT:
I need a Google Colab code that will use OpenAI to:
Check the vector embeddings existing in column C. Use cosine similarity to match with two suggestions from each locale (locale identified in Column A).
The goal is to find which pages from each locale are the most similar to each other, so we can add hreflang between these pages.
I’ll upload a CSV with these columns and expect a CSV in return with the answers.
After ChatGPT generated the code, I pasted it into Google Colab, which is a free Jupyter Notebook environment for running Python in a browser. I then used “Run all” to test whether the program produced the output I wanted.
That is the clean version of the process. In practice, AI can make the workflow look perfect while still producing code that does not behave the way I need.
I expect issues along the way, and most of them are simple to troubleshoot if I keep the prompt and testing process clear.
First, I always state the platform I’m using. If I want code for Google Colab, I say that directly in the prompt.
Sometimes I still get code that depends on packages that are not installed. When that happens, I paste the error back into ChatGPT and ask it to fix the code or suggest an alternative. I do not need to fully understand the missing package to move forward. I can also ask Gemini inside Google Colab to identify the problem and update the code directly.
I also check outputs carefully because AI can sound confident while inventing data. One time, I forgot to specify that the source data would come from a CSV file, so the tool created fake URLs, traffic, and graphs. “It looks good” is not the same as “it is correct.”
If I connect to an API, especially a paid API from a provider such as Semrush, OpenAI, Google Cloud, or another platform, I need to request my own API key and keep usage costs in mind.
A Semrush subscription screen highlights 2 million Standard API units and a masked API key, underscoring the setup step needed for SEO automation and vibe-coded tools.
If I want an even lower execution barrier than Google Colab, I can use Replit.
With Replit, I can prompt what I want, and the platform can generate the code, design the interface, and let me test everything in one place. That reduces copy-and-paste work and gives me a shareable URL quickly. I still need to review poor outputs and keep iterating until the app behaves properly.
The tradeoff is cost. Google Colab is free unless I use paid API keys, while Replit charges a monthly subscription and usage-based API fees. The more the app runs, the more expensive it can become.
SEO vibe-coded tools that inspire me
Google Colab is the easiest place for me to start, but SEOs are taking vibe coding much further. I’ve seen people create Chrome extensions, Google Sheets automations, and even browser games.
I’m sharing these examples because they show what is possible when useful SEO ideas meet practical AI tooling. If I see a tool and wish it had a different feature, that is often a sign that I could try building a version for myself.
A Replit vibe-coding session turns a simple prompt for toddler-friendly daily jokes into a published web app, illustrating how AI tools can quickly prototype playful ideas.
GBP Reviews Sentiment Analyzer by Celeste Gonzalez
After vibe coding SEO tools in Google Colab, Celeste Gonzalez, Director of SEO Testing at RicketyRoo Inc, pushed the idea further by creating a Chrome extension. “I realized that I don’t need to build something big, just something useful,” she explained.
Her extension, the GBP Reviews Sentiment Analyzer, summarizes sentiment analysis from reviews over the last 30 days and shows review velocity. It also exports the information to CSV and works on Google Maps and Google Business Profile pages.
Instead of relying only on ChatGPT, Celeste used Claude to create stronger prompts and Cursor to turn those prompts into code.
AI tools used: Claude (Sunner 4.5 model) and Cursor
APIs used: Google Business Profile API (free)
A vibe-coded GBP Sentiment Analyzer turns review data into a quick snapshot, showing negative sentiment trends, key topics, and an export option for SEO workflows.
Platform hosting: Chrome Extension
Knowledge Panel Tracker by Gus Pelogia
I became obsessed with the Knowledge Graph in 2022, when I learned how to create and manage my own knowledge panel. Later, I discovered that Google’s Knowledge Graph Search API lets me check the confidence score for any entity.
That led me to build a vibe-coded tracker that checks entity scores daily, or at any frequency I choose, and returns the results in a Google Sheet. I can track multiple entities at once and add new ones whenever I need to.
The Knowledge Panel Tracker runs entirely in Google Sheets, and the Knowledge Graph Search API is free to use. This guide explains how to create and run it in your own Google account, or you can see the spreadsheet here and update the API key under Extensions > App Scripts.
AI models used: ChatGPT 5.1
A spreadsheet-based Knowledge Panel Tracker turns entity searches into structured SEO data, comparing names, entity types, descriptions, and confidence scores at a glance.
APIs used: Google Knowledge Graph API (free)
Platform hosting: Google Sheets
Inbox Hero Game by Vince Nero
I also like the idea of vibe coding a link building asset. That is what Vince Nero from BuzzStream did with the Inbox Hero Game. The game asks players to use the keyboard to accept or reject a pitch within seconds, and it ends if they accept too many bad pitches.
Inbox Hero Game is more complex than running a small script in Google Colab, and it took Vince about 20 hours to build from scratch. “I learned you have to build things in pieces. Design the guy first, then the backgrounds, then one aspect of the game mechanics, etc.,” he said.
The game was built with HTML, CSS, and JavaScript. “I uploaded the files to GitHub to make it work. ChatGPT walked me through everything,” Vince explained.
A retro arcade-style Inbox Hero screen turns PR pitch triage into a fast keyboard game, challenging players to accept or reject emails before time runs out.
He also found that longer prompt threads became less useful over time, “to the point where [he’d] have to restart in a new chat.”
That became one of the hardest parts of the project. Vince would add a feature, such as a score, and ChatGPT would “guarantee” it had found the error, update the file, and still return the same problem.
In the end, Inbox Hero Game shows that it is possible to create a simple game without coding knowledge. It also shows where a developer becomes valuable when the goal shifts from “working prototype” to polished product.
AI models used: ChatGPT
APIs used: None
Platform hosting: Webpage
How I think about vibe coding with intent
I do not expect vibe coding to replace developers, and I do not think it should. What I do see is a practical way for SEOs to prototype ideas, automate repetitive tasks, and explore creative experiments without a heavy technical lift.
The key is realism. I use vibe coding where precision is not mission-critical, I validate outputs carefully, and I stay alert for the moment when a project grows beyond “good enough” and needs stronger technical support.
When I approach vibe coding thoughtfully, it becomes less about shipping perfect software and more about expanding what I can test. For internal tools, proofs of concept, and SEO side projects, the best results come from pairing curiosity with restraint.
I see Google Ask Maps changing local visibility in a meaningful way. Instead of showing people a long list of nearby businesses and leaving them to sort through everything, Ask Maps narrows the options, interprets the searcher’s intent, and explains why certain businesses look like a strong fit.
That changes how I think about local SEO. Visibility is no longer only about ranking somewhere near the top of a long results list. It is increasingly about whether Google understands a business well enough to recommend it with confidence.
I would not treat Ask Maps as a separate optimization channel or a brand-new tactic to chase. I would focus on making the business easier for Google to understand, easier to match to real customer situations, and easier to trust. The foundations of local SEO still matter, but the way those signals work together matters even more.
Visibility in Ask Maps starts with filtering
One of the first things I notice about Ask Maps is how small the result set can be. In testing, it often showed around three to eight businesses, depending on the query. That feels very different from traditional Google Maps, where people can scroll through dozens of options and compare them on their own.
With Ask Maps, much of that comparison happens earlier. Google filters the market first, interprets what the person is really asking for, and then presents a smaller group of businesses with an explanation of why each one fits.
That means I have to think beyond the question of whether a business ranks. I also have to ask whether Google has enough confidence to include that business in a short recommendation set and explain why it belongs there.
I think of this as a two-step problem. First, Google decides which businesses are eligible for the query. Then, it decides which eligible businesses it can confidently recommend.
Ask Maps needs enough detail to explain the business
Ask Maps does more than list businesses. It interprets and describes them. Even for simple searches, I often see businesses framed around qualities such as responsiveness, experience, specialization, professionalism, or the kinds of situations they seem best suited for.
That creates a different optimization challenge. It is not enough for Google to know that a business exists or that it offers a basic service. Google needs enough information to answer a more practical question: when should this business be recommended?
To support that, I want Google to understand the types of jobs the business handles, the situations it commonly deals with, the concerns customers usually have, and how the business approaches those situations.
If that information is vague, scattered, or inconsistent, Ask Maps has less to work with. When Google cannot clearly explain why a business fits a specific situation, I would expect that business to be less likely to appear as a recommendation.
Google Business Profile becomes the identity layer
For me, the Google Business Profile sits at the foundation of this whole process. In earlier-stage queries, Ask Maps appears to rely heavily on profile data, including business descriptions, services, reviews, ratings, hours, and operational details.
Many businesses still treat their profile like a basic listing to fill out and keep current. That is necessary, but I do not think it is enough for an environment where Google is trying to describe and recommend businesses. The profile needs to communicate a clear, specific identity.
A generic profile might say that a business offers plumbing, HVAC, electrical work, or another broad service. A stronger profile clarifies the kinds of problems it handles, the situations it is built for, and the details that make it useful to specific customers.
For example, I would use the profile to reinforce details such as emergency availability, response times, specific repair or installation types, experience with older homes, complex systems, or common customer problems the business solves.
That level of specificity gives Google more direct evidence. Instead of forcing the system to infer what the business is known for, I want the profile to make that identity clear.
Reviews shape positioning, not just credibility
Reviews have always mattered in local search, but I see them playing a more structured role in Ask Maps. Review language can show up in the way Google describes a business, especially around themes like responsiveness, honesty, communication, professionalism, and quality of work.
That tells me reviews are doing more than supporting credibility. They are helping define how the business is positioned.
I would still pay attention to rating, volume, and recency. But I would also look closely at what customers actually say. The language inside reviews can give Google useful context about what the business does, how it works, and what customers value about the experience.
A vague review such as “great service” signals satisfaction, but it does not explain much. A detailed review that mentions a same-day response, a drain backup, clear communication about options, and a repair-focused solution gives Google several stronger signals about the business.
Over time, those patterns accumulate. In that sense, I view reviews as one of the main ways Google learns what a local business is known for.
Website content matters more when decisions get harder
I also see website content becoming more important as queries become more complex. For basic service searches, the Google Business Profile and reviews may carry a lot of the weight. But when the search involves higher cost, uncertainty, or trust, Google appears to look for deeper supporting evidence.
That is where the website can help. Many service pages explain what a business offers and why it is qualified. That still matters, but it does not always match how people search when they are trying to make a difficult decision.
In more situational searches, people are not just looking for a service. They are trying to understand a problem, compare options, reduce risk, and decide what to do next.
That is why I would build content around the customer’s situation, not just around the service name. Stronger pages explain what leads to the problem, how to recognize it, what options are available, how to think through the decision, and what outcomes to expect.
For example, a furnace repair page can go beyond a basic list of services. It can cover common symptoms, when repair makes sense, when replacement might be worth considering, and how a homeowner can evaluate the decision. That kind of content lines up more closely with the prompts Ask Maps is trying to interpret.
I also see a strong fit for jobs-to-be-done pages. Instead of organizing every page around a service category, I would create pages around the situation the customer is trying to solve and the decision they are working through.
Trust signals matter more as risk increases
As searches move from simple service needs into decision-making, trust becomes more important. When people mention cost, honesty, uncertainty, or fear of making the wrong choice, Ask Maps tends to highlight qualities such as transparency, fairness, careful workmanship, and clear communication.
That makes sense to me because it reflects how people actually think in those moments. When someone faces an expensive repair or an unexpected issue, they are not only asking who can do the work. They are asking who they can trust to handle it correctly.
I would support that trust with evidence across the business’s online presence. Reviews can show that customers felt respected and informed. Website content can explain the process. Examples of completed work can show experience. Clear “what to expect” sections can reduce uncertainty.
The higher the perceived risk, the more supporting evidence matters. I want Google to see a consistent pattern that the business explains options clearly, avoids unnecessary pressure, handles similar situations, and leaves customers confident in the outcome.
Detailed customer reviews do more than boost ratings. They give Google Ask Maps the context it needs to understand, position and confidently recommend a local business.
External signals should reinforce the same story
For more complex or trust-heavy queries, Ask Maps may look beyond the Google Business Profile, reviews, and website. Third-party platforms, directories, and other public sources can help reinforce how Google understands a business.
I do not take that to mean every external mention is equally important. I take it to mean consistency matters. If a business is described one way on its website, another way in reviews, and differently across directories or social platforms, the overall picture becomes harder to interpret.
When those signals align, they strengthen each other. Business descriptions, services, customer experiences, types of work handled, and overall positioning should tell the same story wherever they appear.
From a practical standpoint, I would not try to appear on every possible platform. I would make sure the important sources are accurate, credible, and consistent.
I would optimize for evidence, not just keywords
As local search decisions become more specific and higher risk, Google needs deeper signals from business profiles, reviews, and website content to recommend the right provider.
Taken together, these patterns push me to think differently about optimization. Traditional local SEO often starts with keywords and rankings. Those still matter, but they do not fully explain what Ask Maps is doing.
I find it more useful to think in terms of evidence. For a business to be recommended, Google needs enough information to understand what it does, what types of jobs it handles, what situations it fits, how customers experience it, and whether it can be trusted in higher-stakes decisions.
Each source contributes something different. The Google Business Profile establishes the baseline identity. Reviews add real-world context. Website content provides depth and explanation. External sources help confirm the same picture.
Individually, none of those elements tells the whole story. Together, they create a clearer and more consistent understanding of the business. That is where the shift from ranking to recommendation becomes most obvious: keywords can support relevance, but evidence supports recommendation.
My practical framework for Ask Maps visibility
When I evaluate a business for Ask Maps visibility, I would look at five areas: identity, relevance, trust, context, and consistency.
Google Ask Maps rewards more than keyword relevance. This visual shows why reviews, service details, trust signals, and real proof help local businesses get recommended.
Identity asks whether Google can clearly understand what the business does and where it operates. Relevance asks whether the business can be matched to specific services and situations. Trust asks whether there is enough proof that customers feel confident choosing it.
Context asks whether the content reflects the decisions customers are actually trying to make. Consistency asks whether different sources reinforce the same understanding of the business.
I do not see this as a checklist to complete once. I see it as a practical way to evaluate how clearly and consistently a business is represented across the sources Ask Maps appears to use.
What I would avoid
With any new search feature, it is easy to overcorrect. I would avoid treating Ask Maps as an isolated channel that needs thin content, unnatural profile language, generic service-page duplication, or review language that feels forced.
Those tactics may create more content, but they do not necessarily create more useful evidence. The better approach is to align more closely with how customers actually search, evaluate options, and make decisions.
A practical local SEO framework shows how businesses can earn visibility in Google Ask Maps by clarifying identity, proving relevance, building trust, adding context, and staying consistent online.
When the business presence reflects real customer needs clearly and consistently, it naturally creates the kinds of signals Ask Maps seems to rely on.
What I still do not know about Ask Maps
I would treat all of this as directional, not definitive. Ask Maps is still being tested and refined, and the system is not fully documented.
The result structure can vary by query and test environment. The feature’s usability is also still changing. In many cases, users may still need to click into a Google Business Profile to call, book, or engage, rather than acting directly from the Ask Maps response.
Measurement is another open issue. Right now, I do not see a clean way to isolate Ask Maps visibility or performance inside standard reporting tools. That makes it difficult to attribute calls, traffic, or conversions directly to this experience.
I also would not assume the same signal weighting applies to every query. Google Business Profile data, reviews, website content, and external sources may all matter, but their relative importance likely changes based on the search intent and the complexity of the decision.
The real shift is from ranking to recommendation
I see Ask Maps as a version of local search where retrieval, evaluation, and decision support are moving closer together. Instead of making users search, compare, research, and decide across several steps, Google is trying to guide more of that process inside one experience.
That changes the meaning of visibility. In Ask Maps, it is not enough for a business to simply appear. The business needs to be understood well enough for Google to explain why it fits the situation and trusted enough to be recommended.
For businesses and SEOs, I would not respond by chasing a narrow trick. I would build a clearer, more complete, and more consistent representation of the business across the sources that shape Google’s understanding.
The businesses most likely to benefit are the ones that are easiest to interpret, easiest to trust, and easiest to match to real-world customer needs.
I’m seeing a sharp disconnect in B2B search visibility: many brands still rank for thousands of Google keywords, but they appear in only about 3% of AI-generated answers, according to Walker Sands’ B2B AI Search Visibility Benchmark of 828 enterprise companies. (Disclosure: I’m the director of SEO and GEO at Walker Sands.)
For this benchmark, I looked at more than 45 million search queries from March across 828 enterprise B2B companies in 14 industries. The analysis evaluated each domain across four core metrics: keyword coverage, keywords with AI Overviews, AI Overview incidence, and citation inclusion rate.
Keyword coverage measures how many keywords a company ranks for in Google. Keywords with AI Overviews shows how many of those ranking keywords trigger AI-generated responses. AI Overview incidence captures the percentage of ranking keywords where AI Overviews appear. Citation inclusion rate measures how often a company’s domain is cited inside those AI-generated answers.
Together, these metrics give me a baseline for understanding how often AI Overviews show up and how often B2B brands actually earn visibility within them.
A baseline for B2B AI search visibility
The benchmark shows a meaningful gap between traditional ranking visibility and AI citation visibility. AI Overviews appear in about 50% of search results where enterprise B2B brands rank, yet the median enterprise B2B brand is cited in just 3% of relevant AI Overviews.
I also found that 4.6% of enterprise B2B companies are not cited in AI Overviews for any of their relevant keywords. That may sound like a small share of the market, but it points to a serious visibility problem for brands that still appear in Google’s organic results while disappearing from the AI-generated answers buyers increasingly see first.
The typical enterprise B2B company ranks organically for about 9,700 search queries, and AI Overviews appear in nearly half of those searches. But across all those opportunities, the median brand earns citations in only 3% of AI Overviews.
In other words, I’m seeing B2B brands present in the search results that AI Overviews summarize, but largely absent from the summaries themselves.
When a brand has few or no citations, I often see deeper issues underneath: limited topical authority, unstructured or inaccessible content, and too little content that directly answers the questions buyers are asking.
Addressing those gaps is becoming essential for visibility in AI-driven search experiences.
The narrowing funnel from ranking to citation
I think of AI search performance as a funnel with four layers, and the value lost at each step is where the story gets clearer.
It starts with keyword coverage, or the number of keywords where a brand ranks in Google’s top 100 organic results. On that measure, many leaders still look strong. The median company ranks for about 9,700 keywords, while top-quartile brands rank for more than 37,000.
The next layer is keywords with AI Overviews. These are ranking keywords that trigger an AI Overview. The median company has roughly 4,500 of them, which is already less than half of its ranking footprint.
The third layer is AI Overview incidence, which measures how often AI-generated answers appear across a brand’s relevant searches. The median is 48.8%, meaning AI now intercepts roughly half the queries where these companies compete. Top-quartile brands operate in even more AI-heavy environments, with an incidence rate of 61.7%.
The final layer is the one that matters most, and it is where almost everyone loses ground: citation inclusion rate. This measures how often a brand is cited as a source within an AI Overview. The median is 3.0%. Even the top quartile reaches only 4.5%, while the bottom quartile sits at 1.7%.
Viewed from top to bottom, the funnel is unforgiving. Tens of thousands of ranking keywords compress into a single-digit share of AI citations. Much of the visibility B2B brands have built through organic search does not carry into the layer of search that is shaping buyers’ first impressions of a category.
Ranking breadth does not guarantee AI citations
The most important takeaway is also the most counterintuitive: ranking breadth alone does not predict AI citation rates.
I found that some companies rank for thousands of keywords but rarely surface in AI-generated answers. The strengths that helped brands win traditional SERP visibility, including page volume, broad keyword targeting, and years of accumulated domain authority, do not automatically make a brand the source an AI system chooses to cite.
That creates a real challenge for B2B SEO teams. If a dashboard only tracks ranking keywords and estimated organic traffic, it may tell a flattering story about a layer of search that is losing influence while saying little about the AI layer that is gaining it.
The brands that are consistently cited in AI-generated answers tend to share three traits: deep topical authority across related content areas, clear and structured explanations that directly answer buyer questions, and consistent coverage across multiple relevant pages.
The common thread is specificity. Generative systems appear to reward content that resolves a buyer’s question clearly and demonstrates sustained expertise on a topic, instead of content that simply ranks for a query.
That changes the work. Optimizing for AI citations looks less like chasing keyword volume and more like building genuine, well-structured subject-matter depth.
Some industries are far more exposed than others
AI search visibility is not distributed evenly across B2B technology. The industry breakdown shows very different competitive dynamics depending on the category.
Cybersecurity leads on both fronts. AI Overviews appear in a median of 59.9% of cybersecurity-related searches, and cybersecurity brands earn the highest median citation rate in the study at 4.2%. Enterprise software, with 55.3% AI Overview incidence, and martech, with 56.3%, also see AI-generated answers in well over half of relevant queries.
At the other end, professional services and distribution and logistics trail in citations, both with a median rate of just 2.1%. Distribution and logistics also has the lowest AI Overview incidence at 29.6%, meaning buyers in that category encounter AI-generated summaries far less often than buyers in cybersecurity.
These differences create both risks and opportunities. In categories where AI-generated answers are already common, such as cybersecurity, the cost of being invisible is immediate. Buyers are forming impressions inside AI summaries right now.
In categories where citation rates are low and few brands have figured out the new mechanics, I see a real first-mover opportunity. Brands that learn how to earn citations before competitors do can help shape how an entire category is framed in AI-generated answers, much like early SEO adopters captured outsized organic visibility.
The brands that have gone completely dark
The most striking number in the report is that 4.6% of enterprise B2B companies are not cited at all in AI-generated answers for their relevant keywords.
These are not small, unknown operations. They are companies with $100 million or more in revenue that, in many cases, still rank well in traditional search. They are present in the index but absent from the answer.
Near-zero citation rates usually point to deeper structural issues: thin topical authority, content that is difficult for systems to parse, and a lack of material that directly answers the questions buyers are asking.
For a small but meaningful slice of the market, AI search is not just a place where they are losing share. It is a place where they barely exist.
What this means for B2B search teams
The benchmark gives me a baseline, but the strategic implications for SEO, GEO, and marketing teams are already clear.
First, measurement has to evolve. Citation inclusion rate is now a distinct KPI from ranking. Teams that cannot see whether their content is being cited in AI-generated answers are missing visibility into one of the fastest-growing parts of the funnel. Knowing your own citation rate, and comparing it with the 3% median and 4.5% top-quartile benchmarks, is a practical starting point.
Second, the content mandate is shifting from breadth to depth. The drivers point toward consolidating authority around the topics buyers care about, structuring content so machines can interpret it, and answering real questions directly instead of producing content volume for its own sake.
Third, the window is open but closing. Generative AI is expected to influence more than 75% of B2B search queries within the next one to two years. If that projection is even close, the median 3% citation rate is not a stable endpoint. It is a snapshot of an early, contested market that rewards brands that move now.
The uncomfortable truth is that much of the SEO equity B2B brands have built is being summarized by AI systems that do not cite the companies that created it. For most enterprise brands, I no longer see the central question as whether they rank. The question is whether they are in the answer at all.
I’m reading this Cornell Tech research as a clear warning: deep-research AI agents can be steered by surprisingly small edits on public, user-generated pages. In the study, a single injected Reddit-style comment could become a cited recommendation for fake products, services, or entities.
The researchers described these altered pages as “poisoned” because the added text was written to influence what an AI system cites and repeats. The weakness appears in systems that search the web, collect sources, and produce cited reports. The paper calls the attack WARP, short for Web Agent Retrieval Poisoning.
How I see injected text reaching reports. The attack does not require access to the model, prompts, search engine, or retrieval system. Instead, an attacker edits or appends text to a page the agent already tends to retrieve, such as a Reddit thread, Wikipedia page, or forum post.
When the agent later searches related topics, it may pull in that page, cite it, and repeat the attacker’s chosen message as part of an otherwise normal-looking answer.
That matters because deep-research tools often run many related searches for a single user request. The paper found that the same user-generated pages surfaced across related queries, giving poisoned content more chances to appear.
Reddit stood out as the biggest opening. Across STORM, Co-STORM, and OmniThink, 17% to 23% of retrieved URLs came from user-generated platforms, including Reddit, YouTube, Facebook, and Wikipedia.
Reddit made up the largest share of those pages. It accounted for 54% to 71% of the user-generated URLs retrieved by the three open-source systems.
The researchers did not alter live websites. Instead, they used a simulation framework called GeoStorm to insert manipulated text into retrieved content during testing.
A few words were enough. What stood out to me most is how little text the attack needed. The researchers found that snippets as short as about 13 words could influence what these systems recommended.
In one test, a 15-word sentence pushed a fake cryptocurrency, BananaCoin, into a Co-STORM report as an “emerging” long-term investment option. The report cited the altered source alongside legitimate crypto sources.
When the manipulated page was retrieved, the fake entity appeared in 38% to 51% of reports across systems. When the researchers targeted multiple pages, that range increased to 42% to 62%.
The attack still worked when systems retrieved full Reddit threads, although mention rates were lower. When injected text was added to complete Reddit threads and represented less than 4% of the retrieved content, the fake entity still appeared in 30% to 53% of reports when the page was retrieved.
The defenses struggled. Blocking user-generated domains stopped this attack path, but I see the tradeoff immediately: it also removes useful sources such as firsthand product experiences and local recommendations.
The tested text filters also failed to reliably separate injected passages from normal user content. Because the manipulated passages were fluent and written by an AI model, perplexity-based filters were more likely to flag normal user content than the injected text.
Report-level checks missed the manipulation too. The altered reports looked similar to clean reports because the agent itself folded the fake recommendation into an answer that otherwise appeared normal.
Why I care. A small edit to a public page can become part of a cited AI answer, even when the underlying source is user-generated. Misinformation planted on sites like Reddit or in forums can move from discussion threads into AI recommendations that look credible to users.
About the research. The paper, Deep-Research Agents Can Be Poisoned via User-Generated Content, was written by Tingwei Zhang, Harold Triedman, and Vitaly Shmatikov of Cornell Tech and posted to arXiv on May 22. The researchers tested the full attack on three open-source systems: STORM, Co-STORM, and OmniThink.
They also analyzed OpenAI Deep Research and Gemini Deep Research for user-generated citations, but they did not run live manipulation tests because doing so would require publishing altered content to the open web.
I’m noting that Google has confirmed its June 2026 spam update is now fully rolled out. The update started on Wednesday, June 24, around noon ET, and finished on June 26 at 2 p.m. ET.
Google’s official status update was brief and direct: “The rollout was complete as of June 26, 2026.”
What stands out to me is that this was the second Google spam update announced in 2026. It appeared to feel somewhat bigger than the March 2026 spam update, but as with most updates, if my site was not affected, I would treat that as a good sign for now.
That said, I always keep in mind that spam updates can sometimes affect sites that are not intentionally trying to spam Google. Hopefully, that is not the case for your site, but it is still worth watching traffic, rankings, and Search Console data closely after a rollout like this.
As for the type of update, Google originally described it as a normal spam update that would roll out across all languages and locations, with completion expected to take a few days.
If I wanted more context on how these updates work, I would review Google’s official documentation on spam updates in this Google help document.
As traditional SEO shifts toward GEO, I keep seeing one idea gain momentum: visibility in AI search depends heavily on off-site brand mentions. Because of that, marketers are being pushed to look beyond on-site content and invest more heavily in off-site marketing if they want to show up in AI answers.
I agree that off-site signals matter more in AI search, and there is growing industrywide consensus around that point. The problem is that this shift has also created room for opportunists to repackage shady SEO tactics as legitimate GEO work.
Unfortunately, I believe much of what is being sold under the GEO umbrella is unethical, low quality, and potentially fraudulent.
The deception I see under the GEO umbrella
I have personally audited the work of top-rated GEO vendors that offer brand mention outreach services. What I found was not sophisticated digital PR or thoughtful reputation building. I found providers charging premium prices for questionable work that often looks like paid link building with new packaging.
The first tactic I see is vendors using “research studies” to support their sales narrative. Claims such as “X% of AI visibility is driven by third-party sources” can be stripped of context and used to convince marketers that they need an aggressive, high-volume system for manufacturing brand mentions.
I also see these programs framed as “partnership” building. During the sales process, GEO vendors may describe the work as a way to build relationships with other brands. In practice, many of the so-called opportunities are low-quality paid-placement inventory schemes.
Some vendors are selling PBN brand mentions, placing brands on Private Blog Networks for roughly 10 to 15 times the cost of a typical SEO backlink. Others sell topically irrelevant placements on sites that might publish one page about LMS software and another listicle about crypto wallets.
I have also seen Reddit astroturfing presented as GEO work. Agencies use aged accounts to mass-post brand mentions across irrelevant subreddits, and many of those “mentions” are removed within 30 days because they violate community guidelines.
Why paid brand mentions look like black hat link building to me
When I look at what some GEO outreach vendors are pitching, I see an evolution of black hat link building. It is unethical, and it amounts to an attempt to manipulate AI systems.
I see clients being asked to approve paid mentions
I have seen this happen in Slack. The agency creates a “placement opportunity” for approval, and an internal marketing liaison has to review it. Often, that person is a junior specialist who has not been trained to evaluate whether the referring page is legitimate.
The pitch usually includes a prompt topic, domain authority, citation rate, and publisher placement fee. In one example I reviewed, the fee was $250 in exchange for adding the brand mention.
I also see publisher fees added on top of agency retainers
This is the part I think deserves much more scrutiny. The GEO vendor may pay the publisher fee directly, then invoice the client to recover the cost. That means the client is not only paying the agency retainer, but also funding the paid mention itself.
Why I think volume without relevance creates risk
My view is simple: third-party validation is only valuable when it comes from credible, topically relevant brands. A mention is not automatically useful just because it exists somewhere on the web.
Many GEO vendors argue that AI visibility is a “volume game.” They claim that generating a large number of mentions will meaningfully increase a brand’s “mention rate” in AI answers. I think that framing misses the point.
When vendors treat GEO as a mention-rate, citation-rate, and volume problem, they often ignore the quality and relevance of the source. That is a serious flaw, especially when reputation is central to how brands are understood online.
In one example, I saw a page with several outgoing commercial anchors to LMS software vendors. To me, that is a hallmark signal of paid links. If GEO is a reputation problem, I would not want my brand mentioned on a page loaded with paid links to competitors.
Why inauthentic brand mention spam may only work temporarily
I think some spammy GEO tactics appear to work right now because many LLM citation systems are still immature compared with Google’s advanced spam detection. It is possible that some LLMs currently reward mention volume from low-quality sources that Google would normally ignore.
That creates a temporary window of effectiveness, perhaps one to two years, before AI platforms improve their authority and spam signals. I believe marketers who prioritize high-volume mentions over brand safety risk confusing LLMs about their entity and damaging their reputation.
Lily Ray’s view aligns with this concern. She argues that some GEO and AEO companies lack the experience to anticipate how Google and AI platforms may treat their tactics once stronger countermeasures are built into training data, indexes, and results.
She also points back to the first Penguin update in 2012, when Google began suppressing inorganic links. In that context, paid mentions on low-quality sites look like another evolution of spammy link building, and I think it is naive to assume search and AI platforms will not eventually catch on.
The unnecessary risk I see GEO vendors creating
This type of work can cause real damage. Glenn Gabe has described it as an evolution of paid link schemes, and I think that description fits what many marketers are being sold.
Marketing leaders are not just wasting time and money. They may be buying tactics that disappear, damage brand reputation, confuse LLMs about their entity, and pull resources away from more durable marketing work.
There may also be legal risk. The FTC says paid advertisements must include clear disclosures. Yet after paid or “negotiated” brand mentions are added to content pages, many websites do not update those pages to disclose that the placements were sponsored.
How I evaluate GEO vendor claims about off-site mentions
When I evaluate GEO vendors, I start with one basic concern: many prioritize mention volume over source quality. That does not mean every off-site mention strategy is bad, but it does mean the claims deserve pressure testing.
If a vendor claims that most AI brand discovery comes from third-party sources, I ask whether that actually proves paid or negotiated low-quality mentions cause a brand to appear more often in AI answers. In my view, it does not.
If a vendor says listicles and third-party pages are the main lever, I ask whether that supports paying to appear on thin, irrelevant, AI-generated listicles. Again, I do not think it does.
If a vendor argues that AI search is different and traditional SEO quality judgment no longer applies, I push back. Google says the opposite for its AI search features: SEO best practices still matter, there are no special optimizations required for AI Overviews or AI Mode, and pages still need to follow Search policies.
More broadly, I do not see substantial evidence that adding a paid mention to a cited page will make a brand appear more often, that low-quality long-tail publishers improve AI search visibility, that citation rate beats source quality, or that traditional SEO and brand safety principles are obsolete in AI search.
Paying for “25 brand placements” to chase a “10-15% mention-rate lift” is not how I think marketers should approach AI search. I would rather pursue off-site mentions that reflect genuine category validation from trusted businesses, reputable publishers, and real communities.
I’m deeply saddened to share that Bruce Clay, widely known as the Father of SEO, passed away in late May. Bruce was one of the true founding figures of the SEO industry, having launched a professional SEO agency back in 1996, long before search marketing became the discipline we know today.
For me, Bruce’s impact is hard to overstate. He was the first sponsor of the first-ever SEO conference, and he gave an extraordinary amount of his time, resources and money to help build the search community. Few people have supported this industry for as long, or with as much generosity, as Bruce did.
Tribute video. The Bruce Clay, Inc. team prepared a tribute video honoring Bruce’s life and legacy. It describes him as a pioneer who devoted much of his life to helping the SEO industry grow. During his three decades as CEO of Bruce Clay Inc., he wrote three books, built tools, spoke at conferences, hosted training events and helped the company expand internationally.
Because of Bruce’s founding principles, hundreds of employees around the world have contributed to SEO, and thousands of students have benefited from his experience and teaching.
The Bruce Clay team told me, “We are absolutely heartbroken, but we find strength in the vibrant community and lasting values that Bruce built. Our teams in the U.S. and around the world remain dedicated to carrying forward the mission Bruce loved so dearly.”
Kyle Pouliot, Sr. Video Production Manager at Third Door Media, also shared a personal reflection with me.
“I’ve gotten to know Bruce on a more personal level over these past few years and interacted with him frequently for our online conferences. What I’ve learned about Bruce in that time is that he was genuinely thoughtful and caring about the search community. Never short of an honest opinion, Bruce shared some really practical ideas for Search Engine Land and SMX. He loved sharing his deep experienced knowledge to everyone, it didn’t matter if you were a beginner or 20+ year industry veteran, he treated everyone the same. We talked about the hundreds of golf balls that would find their way into his property every day, food, raising kids and how incredible the weather was in Simi Valley. He will be greatly missed.”
On a personal note, I’ve known Bruce Clay since I entered the SEO industry more than 20 years ago. He was a role model to me, often a mentor, and always someone who was approachable, professional and deeply caring. In many rooms, he was likely the most generous and thoughtful person there.
I loved his SEO talks. I loved meeting him at industry events. And I especially valued the personal emails he sent about shaping the future of our industry. Those moments showed me how much Bruce cared, not just about search, but about the people building it.
I see existing content as a goldmine, but only when I have a practical way to improve it. The hard part is usually finding the time, and that is where Claude has made a large, messy job feel much more manageable for me.
I do not start by building a giant content audit system. I start with one article, run one focused audit, refine the output, and then turn the prompt into a reusable Claude skill. Over time, those one-off audits become a working library I can improve every time I use it.
I use Claude to uncover topical gaps, flag outdated information, check brand voice, and evaluate whether a page is easy for AI systems to retrieve and cite. The real value comes from iteration: each time I improve a skill, the next audit becomes faster and more useful.
Here are six content audit workflows I would build in Claude. The first four work at the page level, so I can start with a single article before moving into larger library-wide analysis.
Page-level audits
When I am not ready to build a full workflow, I start with page-level audits. These audits only require one article, which means I do not need a content inventory, a data export, or a complicated setup. After each session, I ask Claude to turn the process into a reusable skill for future page-level reviews.
1. Brand voice consistency
I use a brand voice consistency audit when a content library has drifted over time. Voice can shift because of new writers, changing services, product updates, or evolving positioning. This audit helps me spot where a page no longer sounds aligned with the brand.
If I do not have detailed brand guidelines with strong examples, I let Claude extract the voice guide from high-quality content. That usually works better than relying on vague phrases like “conversational but authoritative” or “educational, not too formal.”
I pick three to five articles that represent the brand at its best. If possible, I download them as markdown files and ask Claude to describe how the voice works in concrete terms.
How the articles usually open, such as whether they begin with a direct claim, a counterintuitive statement, or a specific scenario.
How sentences and paragraphs are built, including average length, range, rhythm, and how paragraphs tend to close.
Three to five personality dimensions framed as “We say X, but not Y,” with do and don’t examples.
Words and phrases the brand tends to use, and words or phrases it should avoid.
Specific constructions, phrases, and conventions the brand never uses.
Instead of accepting a vague voice description, I want Claude to return concrete observations. For example, it might say that articles open with a direct claim rather than a scene-setting paragraph, sentences average 15 to 20 words and rarely exceed 30, and transitions are functional, such as “here’s why that matters,” rather than formulaic, such as “furthermore.”
I also want example pairs, such as: “We’d say ‘the data shows three things,’ not ‘there are multiple factors to consider.’” The goal is not to create a voice guide for writers. The goal is to create one an LLM can understand and apply consistently.
Once I like the output, I ask Claude to save it as a skill and evaluate an article against it. If Claude flags issues I disagree with, I update the skill until the feedback becomes useful and repeatable.
I can then use that skill to find voice inconsistencies in older content, check new drafts for alignment, and even generate more on-brand first drafts. I still edit the output, but the starting point is much stronger.
When I need to improve content performance, I use a coverage comparison to find topical gaps. This helps me understand what competing pages cover that my article misses.
I use the Claude in Chrome extension to have Claude review the top three to five ranking pages for my target keyword. Then I ask Claude to compare those pages against my content and highlight the most important gaps.
What competitors are doing well.
What my article already does well.
Where I can improve the piece without bloating it.
If I want the output in a table, I ask Claude to format it that way. If I want a downloadable DOCX for review or handoff, I ask for that instead.
When Claude recommends additions I would never publish, I make a note of those exclusions before packaging the workflow into a skill. That way, the skill gets closer to my editorial standards each time I refine it.
3. Freshness audit
Old content adds up quickly, and it is hard to prioritize refreshes while I am also producing new material. A freshness audit skill helps me identify what needs attention without rereading every older article from scratch.
I give Claude an older article and ask it to flag anything time-sensitive: statistics tied to a specific year, named tools or platforms, references to “current” or “recent” trends, and claims that depend on a market, regulatory, or product context that may have changed. I am not asking Claude to rewrite the article yet. I am asking it to build an issue list I can act on.
If my company has launched new products, removed old services, changed positioning, or updated terminology, I include that context in the input. That helps Claude flag what should be added, removed, or revised.
I use an AEO and AI retrievability audit to understand whether a page is likely to be surfaced in AI-generated answers. Tools such as ChatGPT, Perplexity, and Google AI Overviews tend to favor content that answers questions directly. If an article buries the answer under too much preamble, or structures key information in a way that is hard to extract, it becomes less useful for those systems.
I give Claude the article and the target query, then ask it to evaluate several retrieval signals.
Whether the article answers the main question directly and early.
Whether key statements are specific enough for an LLM to quote or cite.
Where an FAQ-style section would improve clarity.
Whether the page includes authority signals, such as primary research, first-person experience, outbound citations, or specific examples.
Once I save this as a skill, it becomes an extra editor focused specifically on AI visibility and answer retrieval.
Library-level audits
Once I am ready to move beyond individual pages, I use library-level audits. These require performance data, a content inventory, a connector, or a manual export.
5. Performance triage
When I think about a traditional content audit, performance triage is usually what comes to mind. It helps me analyze a content library and identify the pages that deserve attention first.
Before I begin, I make sure Claude has access to the right data through a connector such as BigQuery or the Semrush API. If that is not available, I export the data I normally use for large-scale audits, such as traffic, clicks, engagement metrics, conversions, rankings, and related performance signals.
I ask Claude to prioritize pages that have suffered meaningful performance drops in the past six to 12 months, pages with high impressions but consistently low click-through rates, and pages that have been live long enough to rank but never gained traction.
I also define what a meaningful performance drop looks like for the site I am analyzing, because traffic patterns vary by industry, audience, and page type. Then I ask Claude for a prioritized list of what is worth investigating and why. From there, I use the page-level audits above to diagnose the problem.
If I have run this analysis before, I give Claude the previous output. That helps the skill learn the kind of prioritization and reasoning I expect.
I treat entities as a major part of AEO and semantic search. A topical gap analysis helps me see whether my content library has enough coverage to build authority around the entities tied to my brand.
The core question I ask is simple: what is my content library not covering that it should?
To start, I create a list of target entities. For example, at my agency, I want to be known for SEO and AEO. If I have a clear list of services or products, I can use that instead of a formal entity list.
Using Cowork or Code, I ask Claude to analyze my sitemap and compare it to those target entities. If I have a Screaming Frog export with URLs, page titles, and meta descriptions, I use that as input for a more accurate analysis.
Then I ask Claude to identify topic clusters that are missing or underrepresented based on the target entities, services, or products. If I want prioritization, I can use the Semrush MCP so Claude can check search volume for potential keywords.
Not every gap is worth filling. I filter the results against audience needs, business relevance, and editorial standards. Then I feed those decisions back into Claude so the skill produces better recommendations next time. The final list can go directly into my content creation workflow or be handed off to a content team.
I do not try to audit everything at once
I have seen content audits stall because the scope feels too large, not because the team lacks data. My preferred approach is to pick one audit and one article, run the workflow, save the skill, and use it again on the next piece.
For me, iteration is part of the value. I enjoy taking one Claude skill, improving it, and then chaining it with other skills to uncover more content opportunities. Starting small is what makes the system easier to keep using.
I started this series with a simple observation: AI systems do not always give the same answer to the same question. My argument was that this inconsistency is not just randomness. It is confidence loss across a pipeline we can measure, diagnose, and improve.
As I worked through the AI engine pipeline gate by gate, I eventually reached the won gate. That is where three kinds of clicks appear: the imperfect click of search, the perfect click of recommendations, and the agentic click of agents.
That is also where I realized this conversation could not stay inside marketing. When an agent makes the purchase, it becomes a client I have to satisfy directly.
The funnel now runs through machines that connect directly to the business itself. SEO therefore becomes part of something larger: assistive agent optimization, and ultimately AI-era business engineering.
To understand why, I need to connect the pieces. The framework explains why AI systems make the decisions they make and what shapes those decisions. When I apply those principles across the business, the goal becomes clear: organize the company so search engines, AI assistants, agents, and people can find it, understand it, recommend it, and buy from it.
Everything Builds On SEO
The process sits above the familiar disciplines I already work with: SEO, content, PR, paid media, and digital marketing. It helps me prioritize the actions that most affect recommendations and visibility.
Here is the part every SEO should value: assistive agent optimization is built on SEO. It does not replace it.
I think of it like a Russian doll. SEO sits at the center. It draws from the open web, the same crawled and indexed foundation search has always used.
At that core are two parts of the algorithmic trinity: the search engine, which indexes and ranks information, and the knowledge graph, which stores entities and the relationships between them.
The next layer is assistive engine optimization. It adds the third component: the large language model. The LLM provides reasoning, grounding, and conversation.
Instead of returning only a list of links, it evaluates corroborating evidence and answers the user directly. This layer builds on traditional SEO with entity corroboration, machine-readable proof, and signals that help AI systems understand what content actually means.
The outer layer is the agent. It introduces what the layers below it never had: direct access to business systems through protocols such as MCP. An agent can check inventory, compare prices, and complete transactions without visiting a page or clicking through a search result. This is where AI stops recommending and starts acting.
Each layer depends on the one beneath it. The stronger the SEO foundation, the more effectively I can build everything above it. That makes SEO more central to digital marketing, and to the business itself, than it has ever been.
If I understand how machines read the web, I hold the foundation every other AI-facing initiative depends on.
The Funnel Has Not Changed, But The Build Direction Has
The acquisition funnel has not fundamentally changed since marketers first drew it in the 1800s. Awareness still sits at the top, consideration in the middle, and decision at the bottom. The customer still moves downward while the brand tries to catch them. What has changed is where I have to stand to catch them.
Traditional marketing stood in front of people in the real world, on billboards, shelves, and stages. Digital marketing did the same online through SEO, paid search, social media, and content. AI-era marketing extends that logic again.
Now I have to stand where I always stood and also inside the AI engines. Those engines put brands in front of buyers, present the best solution, and increasingly make the purchase.
The modern buyer mixes all three modes in a single purchase, so I have to be present in all of them. The client still travels from the top of the funnel down, but the engines learn from the bottom up. That is how I need to build for them.
Marketers draw the funnel top-down because that is the customer path. But businesses have always had a reason to read it the other way. Winning the result for your own name is the cheapest and highest-converting move because it reaches the warmest traffic: people already at the door.
I have made that case since 2012, when I started working on brand SERPs. Your name is the one search result you can most completely own, yet the industry ignored it for years.
Comparison and consideration queries come next because they sit near the purchase, where buyers are most likely to convert. Awareness is the last thing I build, because those people often do not yet know what they want or what the solution might be.
The engines make this flip unavoidable. Search engines let users move between sites on the way down the funnel, so top-down building could still work. Assistive engines pull the funnel inside themselves. Now I build from the bottom up because that is how the machine learns who to trust.
Agents push this even further. The funnel goes dark, and the choice often goes with it. Each step takes more of the journey out of my hands, and each rewards the same brand: the one built from the bottom up.
The Agentic Spectrum Decides How Much Must Change
Two ideas tell me how much of a business has to change. The first is the delegation boundary. The second is the agentic spectrum.
The delegation boundary is the micro view. It tracks how much of one buyer journey, from searching to comparing to choosing to buying, a person hands to a machine.
The agentic spectrum is the macro view. It asks what share of the clientele has gone agentic and how quickly that share is growing.
The micro view tells me how to win one buyer in the moment. The macro view tells me how much of the business has to change to keep winning buyers over time. This is the number I would start measuring first.
Here is why it reorganizes the business, not just the marketing. When the agent makes the purchase, it becomes a client I have to satisfy directly, even as it acts for the person behind it. It answers to one priority: keeping its own user happy.
That means the sale turns on confidence. Can the machine trust the business to meet the need and keep its client satisfied?
That confidence has to clear a much higher bar than search or assistive engines required. It runs across the full funnel. If I earn it across the stack, I become the brand the agent buys from.
Preparing for that is what AI-era business engineering means. Pricing, qualification, product data, checkout, service, and retention all need to be built so an agent can transact as cleanly as a person can.
The agent navigates the whole funnel on its own. I have to convince it at every stage, from awareness to the final yes, while getting almost no visibility into the journey. What I do get is granular measurement at negotiation and transaction stages. The agent tells me what it wants, and I either satisfy it or I do not.
That is why I need to build the business to work cleanly with agents and people alike, from the top of the funnel to the moment the deal is struck.
Translating what a company does for humans into something machines can read and act on used to feel optional. Ignoring search engines and assistive engines was never wise, but many companies survived it. In the age of agents, ignoring the engines hands a growing share of the clientele to competitors.
Your Untrained Salesforce Is Already Selling
Every business now has a salesforce it never hired: Google, ChatGPT, Perplexity, Claude, Copilot, Siri, Alexa, and many more. The number keeps growing as major tech platforms add AI answers inside social media, video, search, operating systems, and workflow tools.
The apps people already use now embed assistants that recommend tools, vendors, and products. A buyer does not need to open a separate AI engine for this to happen.
Those engines reach prospects in explicit, implicit, and ambient ways. However they appear, the outcome is the same: they work around the clock, speak to prospects in rooms I will never see, and decide whether to recommend me or a competitor.
The default state of that salesforce is untrained. If someone asks about my category, it answers with the brands it happens to understand, and that may not be mine. It may hedge on basic facts, confuse the brand with a namesake, cite proof that does not exist, recommend the wrong use case, or name a competitor at the exact moment the user was looking for me.
The cost is real, but it often never appears on a dashboard. I cannot watch the AI research the brand, evaluate it, recommend it, or talk a buyer out of choosing it. It all happens inside the machine. That is why I pay attention to three taxes: invisibility, ghost, and doubt.
AI engines recommend the solution they are most confident in, and that is not always the best solution. It is often the one they understand best. The recommendation depends on what they grasp and how confident they are in it.
So if my solution is truly the best, I have to train them. I have to educate them and brief them. They answer to the user, and my client is their client. They retain that client by surfacing the strongest solution they can see.
The practical question is simple: have I made it unmistakably clear that I am the best answer to the specific problems I solve, for the ICP I serve?
Three Taxes Quietly Cost Recommendations
I pay a tax at every stage of the funnel for as long as this AI salesforce is not working explicitly in my favor.
Someone types the brand name directly into an engine, and instead of a clean answer, it hedges with phrases such as “claims to be,” “reportedly serves,” or “says on its website.” Worse, it may start offering alternatives.
Search engines usually do that only when a competitor pays heavily to appear on the brand SERP. Otherwise, the brand owns its own name.
AI can raise the alternative on its own, purely because it is uncertain. That is why brand SERP and AI résumé protection are no longer optional.
That hedge and nudge are the doubt tax. I pay it when the engine lacks enough independent corroboration to commit. It sits at the understandability layer, and the cost is every prospect who came looking for the brand by name and left with doubt.
The ghost tax appears when a prospect asks the engine to compare the category and name the best options. The engine lists several brands, but mine is missing. It knows I exist, yet it does not surface me because its confidence in my credibility is too low.
The invisibility tax appears at the top of the funnel. Someone asks a question I am well qualified to answer, and I am nowhere in the response because the engine never identified me as belonging in that conversation. I never see it because the conversation ends without me.
I need to track these taxes across every engine and every layer, and I should not use only my own account. It is biased toward me. The right approach is proper tracking, neutral testing, and better questions.
The funnel query pathway is the best way to read this over time and across the web. What I am measuring is leakage at each layer. Because the system is opaque, I read the macro trend rather than overreacting to one response.
Then I build from the bottom up and clear the taxes in revenue order.
I clear the doubt tax first because it affects the warmest traffic.
I clear the ghost tax next because it affects buyers comparing close options.
I clear the invisibility tax last because it sits furthest from the purchase.
That is the funnel flip again. AI engines have turned the old top-down playbook upside down.
The Algorithmic Trinity Is Where The Work Lands
I train the AI salesforce in three places, and I need to be present in all three for that training to hold.
Large language models do the reasoning at the moment of the query. This is the intelligence layer: ChatGPT, Claude, and Gemini.
Search engines index and rank fresh content. This is the information layer: Google and Bing.
Knowledge graphs store entities and verified relationships. This is the verification layer: Google’s Knowledge Graph, Wikidata, and Bing’s entity graph.
Those three layers are the algorithmic trinity.
I may be aiming at dozens of platforms and surfaces where this salesforce appears, but there are only a few machines at the root. At mass-market scale, the practical LLM list narrows quickly to ChatGPT and Gemini. There are two major web indexes, Google and Bing, and two major knowledge graph owners, Google and Bing again.
Everything I train reaches back to the same small set of underlying systems. The corroboration work I do for one engine often strengthens the foundation for all of them.
That is why the effort compounds. The knowledge graph confirms the entities the LLM reasons about. The search engine surfaces the fresh content the LLM grounds on. The AI salesforce becomes fully trained when all three converge on the same answer about the brand.
That convergence is where I win: independent systems reaching the same conclusion about who I am, what I do, who I serve, and why I am credible. When I give them that picture in detail, they can hold it with confidence.
At that point, the trinity can surface the brand at the bottom of the funnel, recommend it over competitors in the middle, and advocate for it at the top across search engines, assistive engines, and agents.
The results vary because each platform mixes technologies differently, but the direction starts to favor the trained brand.
Google owns all three layers and remains the dominant force across search and assistive engines, so it remains the main target.
I am not suggesting that I ignore smaller players such as Claude or DuckDuckGo. They matter to the audiences that use them. But for most brands, users, and SEOs, the major public engines are still the key to commercial success.
A tight digital footprint, cleaned up and optimized on-site and off-site, feeds the trinity. At mass-market scale, that means Gemini and ChatGPT, Google’s and Bing’s knowledge graphs, and Google’s and Bing’s search indexes.
The useful side effect is that this strategy also helps with smaller players.
Third-Party Proof Is What AI Believes
Knowing where the work is ingested is only half the job. I also need to know which evidence the AI salesforce believes. Not all evidence carries the same weight, and the gap between weak and strong proof is often the differentiator.
The weakest evidence is what a brand publishes about itself, in its own voice, on its own properties: homepage copy, about pages, and product descriptions. I call this first-party evidence. It is a claim and a baseline, but it proves little on its own because the engines know who wrote it.
If I surface a client outcome, case study, or customer review on my own off-site channel, I move up to second-party evidence. The substance is no longer entirely my assertion, even though I still control the publish button.
Then there is evidence I had no hand in publishing: clients and partners describing their own experiences, an independent journalist’s article, an analyst report, or coverage controlled entirely outside my reach. That is third-party evidence, and it is the strongest proof the salesforce can read because I could not directly shape it.
It is also the category many brands lack because it requires real-world activity, not just publishing. First-party claims, second-party corroborates, and third-party proves. Without proof, nothing stands.
Three Levels Of Effort Create Different Outcomes
Most brands sit at the bottom without consciously choosing to. The minimum-effort brand keeps a website, runs some content marketing, responds to occasional mentions, and otherwise lets the ecosystem do what it does. It appears in machine-readable form but does not shape that form.
Because minimum effort is treated as normal, many companies land here and never recognize it as a decision. Their AI salesforce is barely trained.
The next level appears when a brand notices specific problems and fixes them: an incorrect fact in an AI Overview, a competitor outranking it for a query, or a structured data gap. Those fixes help, and the brand becomes better positioned.
But the work is still symptom-driven. It patches what breaks loudly without building the discipline that prevents the next break. The salesforce is partially trained, but problems are driving the strategy.
The systematic brand runs an operational discipline against the pipeline every week: entity home maintenance, evidence harvested from service teams, machine-readable proof, distribution across publication tiers, and continuous monitoring of the brand SERP and AI résumé.
Most companies are not organized to make that happen naturally. But if I can harvest, codify, and distribute the evidence created by business operations, I can train the AI salesforce to work in my favor around the clock.
I would start from the entity home. I would organize the brand SERP and the AI résumé, then optimize the digital footprint wherever the brand appears. That is understandability, and it is the most important first move.
With the core entity locked, I can build credibility on top of it through engagement, reviews, client feedback, PR, and evidence that the business is genuinely good at what it does.
Deliverability follows because work on the brand SERP and AI résumé already strengthens credibility and reach. Then I can spread the same discipline across every entity the company owns: products, services, and people.
For each entity, I need the right content, presence where the audience is looking, a path down the funnel, and a clear connection back to the entity home. I need to walk the walk and apply the mirror principle.
The Salesforce Is Already Working
In 2026 and beyond, the AI salesforce operates inside the supply chain as well as the sales funnel. AI sits at the gates that decide whether to include a brand in what it knows, whether to deploy it in an answer, and whether to reselect it after every transaction.
Every outcome customers experience feeds back into the system for the next prospect who has never heard of the brand. That is the convergence this series has been pointing toward. The salesforce is selling 24 hours a day, for the brand or for a competitor. The difference is how well it has been trained.
This is why I see the discipline as AI-era business engineering, not just AI-era marketing. It is not a content tactic. It is a reorganization of how the business operates so pricing, qualification, product presentation, sales, retention, and customer success all create machine-readable evidence as a byproduct of doing the job.
SEOs Are In The Best Seat In The Room
When I speak with entrepreneurs and CEOs, I use nine questions to show where the company stands.
Tech, bottom to top: Is our entity home locked down so engines have one source of truth about who we are? Is our structured data complete enough for them to verify what we claim? Are we discoverable across every engine when topical questions appear?
Marketing, bottom to top: What does our brand SERP look like today, and what does the AI résumé say when engines are asked about us directly? Where is our third-party corroboration weakest, and what are we doing about it this quarter? Which topical territory do we own in the engines, and which territory do we want but not yet hold?
Branding, bottom to top: Does our brand story match what AI is currently saying about us, and where is the gap? Are our client outcomes being engineered into machine-readable evidence, or are they dying in CRMs and quarterly retrospectives? Are we placing proof now for the categories we want to own in three years?
All of those questions run from the bottom up, which is ironic because marketers usually work the funnel from the top down. The customer is the one moving from top to bottom, looking for a solution.
So I take a step back and read the funnel from the bottom up. Everyone is building the same thing: understandability, credibility, and deliverability. They are just approaching it from different ends.
The business builds from the foundation up: know who you are, know who you serve, become credible, then reach the right people.
The marketer wants the maximum audience and starts with reach, then works down to who the brand is and why it should be trusted.
AI starts at the bottom. Who are you? Are you credible? Only then will it put the brand in front of more people.
The SEO is the person who can see that it is all the same system. I understand that I must work from the foundation up, the way the machine does, and then meet the customer coming down from the top.
I should build for the customer, but work upward toward them. That has always been the stronger approach, and AI engines have now made it obvious.
The business now has two kinds of clients: the human and the agent. I need to speak to both. The agent is emulating a person and reflecting the world’s view of the brand, so pleasing the agent and pleasing the human are closely connected.
That is what makes SEO impossible to sideline. I am well positioned to tell the business and the marketers what must change to satisfy the agent without losing the human.
Whether agents represent 5% of the business today or nearly all of it, the agentic share will grow year after year. That means I have to step out of the SEO corner and look at the wider business. I am in a rare position to see business, marketing, and machines at the same time.
The audience used to be only human. Now it includes machines, too, and I am the one who can speak to both.
This is the 19th and final piece in my AI authority series, and it has been a long journey. My thanks to Danny Goodwin, Angel Niñofranco, and the Search Engine Land team for their immense support throughout.
When I started, the framework was a complete idea, but I had not fully worked through all the details. Week by week, I worked through each of the 15 gates, and every one turned out to be more intricate, more in-depth, and more thought-provoking than I expected.
What I have finished is a practical framework for SEO, marketing, and business in the AI age, one that search professionals, marketers, and business leaders can apply to real business problems.
Series Index
Parts 1 through 18 built this framework step by step: cascading confidence, assistive agent optimization, the AI engine pipeline, infrastructure gates, competitive gates, the entity home, the push layer, annotation, topical ownership, the funnel flip, the framing gap, pipeline repair, the delegation boundary, funnel query pathways, macro measurement, customer-success proof, AI opinion formation, and the collapse of paid and organic visibility across AI surfaces.