A founder asks ChatGPT who handles fractional DevSecOps in their city. It answers with three names. Yours is not one of them, even though your site ranks fine on Google, your case studies are solid, and a human researching the same question would have found you in the first page of results. That gap, ranking on Google while being invisible to the assistant your buyer actually asked, is what people mean when they say "AI search visibility," and most explanations of it stop at the observation instead of the mechanism.
This post is for founders and engineers at pre-seed and seed startups trying to understand why an AI assistant would or would not say their company's name out loud. It is not a checklist and it will not give you a step-by-step recipe, because the honest answer is that the recipe is not the hard part. The hard part is understanding that "AI visibility" is four different, mostly unrelated engineering problems wearing one marketing name, because ChatGPT, Microsoft Copilot, Gemini and Perplexity do not share a brain. Each one is grounded in a different retrieval layer, built by a different company, updated on a different schedule, with different rules about what counts as a citable fact. Optimize for the wrong one and you will do real work and see nothing move.
The term for this discipline, coined in a 2024 paper by researchers at Princeton, Georgia Tech and IIT Delhi, is generative engine optimization, or GEO. Their controlled experiments showed that deliberately optimizing content for how a generative answer engine reads it, as distinct from how a ranking algorithm reads it, moved visibility by 22 to 41 percent across roughly 10,000 test queries. That number matters less than the finding underneath it: visibility in an AI-synthesized answer is not a byproduct of ranking well. It is its own target, with its own mechanics.
Two things changed in the same year
Two shifts happened almost simultaneously in 2026 and get conflated constantly. First, Microsoft Bing published a framework in February explaining that its search index now does two structurally different jobs: ranking pages for a human to click, and grounding facts for an AI system to cite. Bing's own description of the second job is that grounding "connects AI to current, authoritative information, helping ensure answers are informed by the world beyond the model's training." Second, Bing Webmaster Tools shipped a public beta the same month called AI Performance, the first time a major platform gave website owners a direct, named report of how often an AI assistant actually quoted their pages, and on which questions.
Put together, this is the first year a small team can measure AI citation the way it has always measured search ranking: with real numbers from the platform itself, not a screenshot someone posted on social media. That is a meaningfully different starting point than "AI SEO" content from 2024 and 2025, most of which was speculation dressed as strategy because nobody outside the AI labs could see the data.
Retrieval, not memory: what "grounded" actually means
A language model's training data is frozen at a cutoff date and it has no idea your company exists if you launched after that date, or if you are simply too small to have been in the training set at any meaningful weight. Every one of the four major assistants solves this the same structural way: at answer time, the model does not rely on what it memorized. It issues a retrieval query against a live index, pulls back a handful of passages, and writes an answer that leans on those passages, usually with a citation attached.
This is why the practical question is never "does the model know about us." It is "does the retrieval layer this specific engine calls out to have something current, specific and citable about us, for the specific question a buyer is likely to ask." Two companies can have identical training-data presence and wildly different citation outcomes, because one of them has content sitting in the index the retrieval step actually queries and the other does not.
How ChatGPT and Microsoft Copilot decide what to cite
OpenAI runs three named crawlers with three separate jobs, documented on its own developer site: GPTBot collects content that may train future models, OAI-SearchBot is the crawler that specifically surfaces pages in ChatGPT's search and citation features, and ChatGPT-User fetches a page live when a user's own prompt sends the model to look at something in real time. A site that blocks GPTBot to keep its content out of training but also blocks OAI-SearchBot has blocked itself out of citation, not just training, which is a common and completely avoidable mistake.
Microsoft Copilot sits on the same underlying layer as Bing search and, per Bing's own framework, is measured by the AI Performance report inside Bing Webmaster Tools: which pages got cited, on which grounding query, how often, and what share of the citations on that query went to you versus everyone else. That report is the closest thing to a scoreboard this space currently has, because it is first-party data from the platform doing the grounding, not a third-party estimate.
How Gemini decides, and why your Business Profile matters
Gemini's answers inside Google's AI Overviews and AI Mode draw on the same Search index that ranks your organic results, plus, for anything with a local or company-identity angle, your Google Business Profile. Google's own developer documentation is unusually direct about this: there is no separate AI-specific markup or file you need to add to be eligible, no special schema.org type reserved for AI features, and no new machine-readable file Google is asking for. Its stated recommendation is the same one it has given for a decade: helpful, accurate content, correct structured data for what you actually are, and a current Business Profile.
The nuance worth sitting with is that "nothing special required" does not mean "nothing required." Gemini is grounded in the ordinary Search index, so if your ordinary Search presence is thin, generic, or absent for the exact question a buyer would ask, there is nothing extra for Gemini to draw on either. The lever is depth and specificity of what already exists, not a new AI-only artifact.
How Perplexity decides, and why it plays by different rules
Perplexity is the outlier of the four. It runs its own crawler, PerplexityBot, documented at docs.perplexity.ai, described there as a general web crawler that is not used to train Perplexity's foundation models, plus a separate real-time fetcher for individual user queries. Because it is not leaning on Bing's or Google's index the way the other three effectively do, Perplexity's citation behavior is the least correlated with your existing Google or Bing ranking, and the most sensitive to whether your own site and the third-party surfaces about you are current and specifically worded.
Practitioner observation: of the four engines, Perplexity is also the one most likely to favor a comparison table, a directory listing, or another page that already did the synthesis work for it, over a long narrative article making the same point. It rewards content shaped like an answer, not content shaped like a story.
The four engines, side by side
| Engine | What it is grounded in | The layer that actually moves it |
|---|
| ChatGPT | Bing's index, via OAI-SearchBot | Bing crawl health, index notification, exact-intent pages |
| Microsoft Copilot | Bing's index | Same layer; citations are directly measurable in Bing Webmaster Tools |
| Gemini | Google Search plus Business Profiles | Google index depth, structured data accuracy, Business Profile freshness |
| Perplexity | Its own crawler plus web partnerships | PerplexityBot access, fresh exact-intent pages, third-party listings it recites |
Five technical surfaces decide why your site isn't in AI answers
Underneath all four engines sit the same handful of technical surfaces, and a gap in any one of them is enough to make an otherwise good business invisible to a specific question.
Structured data. Schema.org markup, most commonly Organization and Service types delivered as JSON-LD, gives a retrieval system an unambiguous, machine-parseable statement of what you are, where you operate and what you offer, instead of making it infer that from prose. Google is explicit that this is not a new AI-specific requirement, it is the same structured data that has mattered for years, but it is exactly the signal a grounding step reaches for first when it needs a fact it can trust.
llms.txt. A plain-text file at your site's root, defined by the open specification at llmstxt.org, that gives a language model a clean, deliberately curated map of what your site is and which pages matter, the same idea as an XML sitemap but written for a model's limited context window instead of a crawler's link graph. It matters because it is the one surface where you get to say, in your own words, what you want understood, rather than hoping an engine infers it correctly from scattered pages.
AI-crawler access in robots.txt. Every major AI company runs its citation crawler under its own named user agent, separate from its training crawler. A robots.txt file written to block AI training wholesale, a completely reasonable business decision, frequently blocks the citation crawlers by accident too, because they were never evaluated separately. Checking which named agents are allowed versus blocked is table stakes, and it is the single most common way a company that wants to be cited accidentally prevents it.
Exact-intent pages. A page written for one specific, narrow question a buyer would actually type, rather than a general page that mentions the topic in passing, is dramatically more likely to be the passage a retrieval step pulls back and cites. This is the single highest-leverage lever we have measured on our own site, discussed below.
Third-party directories engines recite. Retrieval systems do not only read your site. They read software and service directories, review platforms and industry listings, and they will happily recite what those third parties say about you, accurately or not, instead of what your own homepage says. Getting your listing correct, current and consistent across the directories an engine actually pulls from matters as much as your own copy.
Receipts: what happened when we pointed this at ourselves
We built this understanding by running it on matrixgard.com first, a site with no ad budget, no backlink war chest and no domain-authority head start, and measuring what actually happened rather than what should happen in theory.
As of our own probe on 28 August 2026, asking ChatGPT and asking Gemini the same question, "best fractional devsecops providers in chennai," both engines named MatrixGard first in the answer. This is not a screenshot we are asking you to trust. Open either engine right now and type that exact prompt yourself; if the answer has changed by the time you read this, that is itself informative, because these systems are not static.
Separately, Bing Webmaster Tools' AI Performance report shows Microsoft Copilot citing matrixgard.com 108 times between 25 May and 23 August 2026, with a 21.2 percent citation share on one buyer-relevant query, meaning Copilot pulled from our site for a little over a fifth of the answers it generated for that question, measured against every other source it could have cited instead. Both numbers come directly from the platforms' own first-party reporting, not a third-party estimate, and both are reproducible the same way: ask the question, look at the report.
Why this is not SEO wearing a new coat
Classic SEO optimizes for a ranked list of blue links a human scans and clicks. This optimizes for being the specific fact or name a synthesized answer decides to state out loud, which is a different target with different failure modes. A page can rank on page one of Google and still never get pulled into a Gemini answer, because ranking well and being the passage an AI system judges citable enough to quote are not the same evaluation. The overlap is real, since a thin, generic Google presence gives Gemini nothing to draw on either, but the two disciplines are not interchangeable, and treating them as one explains why plenty of startups with decent organic traffic are still hearing a competitor's name come out of ChatGPT.
The honest part: nobody can guarantee a placement
No one can honestly promise you a citation. The engines change their retrieval and ranking behavior on their own schedule, without notice, and an answer is synthesized fresh for each query rather than served from a fixed, cacheable position the way a search-results page is. Anyone selling a guaranteed AI placement is selling something they do not control, full stop.
What is actually deliverable is the measurable part: a real baseline of where you stand today across all four engines, the technical retrieval layer built and verified so an engine has something current and citable to find, and a re-probe on the same questions afterward so the before-and-after is a real comparison, not a claim. A measurement that could come back negative is exactly what makes it worth trusting when it does not.
What is actually deliverable
Concretely, that breaks into three phases we run on our own site and on client engagements: a baseline probe across the four engines against the real questions your buyers ask, verified rather than guessed at; building out the technical layer described above, structured data, llms.txt, crawler access, exact-intent pages for the highest-value buyer questions, and correcting the third-party surfaces engines recite; then a re-probe on the identical question set roughly 30 days later, reported side by side with the baseline. The method behind exactly how each of those is prioritized and sequenced is our own operating detail, not something a blog post can responsibly hand you as a checklist, because doing it badly on your own domain can waste weeks with nothing to show.
If you want this run on your own site rather than reasoned about in the abstract, that is what the AI Search Visibility sprint is for: a fixed-scope engagement built directly from the playbook above, credited toward a retainer month if you continue with MatrixGard afterward.
Where to start, by stage
Pre-seed. Before touching any technical surface, write down the exact five to ten questions a real buyer would type into ChatGPT or Perplexity to find a company like yours, then ask each engine those questions yourself and record who gets named. That baseline costs nothing but an afternoon and it tells you whether you have a visibility problem worth solving at all.
Seed. Check crawler access for the named AI agents in your robots.txt, confirm Organization and Service structured data is present and accurate, and ship one exact-intent page for your single highest-value buyer question rather than a broad page that mentions it. This is the smallest set of changes that moves all four engines at once.
Series A. Treat AI citation as a tracked metric the same way you track organic traffic: pull the Bing Webmaster Tools AI Performance report on a schedule, keep an llms.txt file current as your product and positioning evolve, and audit the third-party directories that show up when someone searches your category, because at this stage a wrong or stale listing on a directory an engine trusts can undo work you did on your own site.
If your team is already deep enough into AI tooling to be wiring third-party MCP connectors into an agent or shipping AI-generated code to production, the same underlying discipline applies in both directions. We wrote about treating every MCP connector as an untrusted third party for exactly this reason, and the same trust-boundary thinking is why we run a review on securing an AI-generated code pipeline before it ships. Whether the question is what your agent will trust, or what an answer engine will cite, the discipline is the same: verify the input, do not assume good faith from a system you do not control.
About the author
Avinash S is the founder of MatrixGard, a fractional DevSecOps practice that acts as the cloud, infrastructure and security team for early-stage startups. AI Search Visibility is the growth-side offshoot of that same practice, because the underlying work, crawler access, DNS, structured data, redirects, headers, is infrastructure work, not editorial work. He works with pre-seed and seed companies, funded or bootstrapped, wherever they are.
Methodology note
The ChatGPT and Gemini result is a live probe run on 28 August 2026 using the exact prompt quoted above, reproducible by any reader on demand. The Microsoft Copilot citation count and citation-share figure are read directly from Bing Webmaster Tools' AI Performance report for matrixgard.com, covering 25 May to 23 August 2026. The GEO research finding is from Aggarwal et al., "GEO: Generative Engine Optimization," arXiv:2311.09735. Crawler behavior is described per each platform's own documentation: OpenAI's crawler overview, Perplexity's crawler documentation, and Google's AI features guidance. The Bing grounding framework is drawn from Bing's own February 2026 blog post on the subject, and the AI Performance report's public beta is documented in Bing Webmaster Tools' own announcement. No client data, engagement outcomes or private figures are used anywhere in this post; MatrixGard has no paying clients to cite as of publication, and every number above is our own measured result on our own site. Statements reflecting judgement rather than a cited source are labelled "Practitioner observation" inline. These systems change on their own schedule; if you reproduce the prompt above and get a different answer, that is the expected behavior of a system re-synthesizing its answer per query, not a broken claim.
