A whitepaper on why ranking and being cited are different mechanisms, and the structured-content playbook that makes a business citable.
Executive summary
Getting cited by AI search means being named as a source in the answer an AI assistant gives: the paragraph ChatGPT writes, the summary Perplexity compiles, the AI Overview Google places above its results. Most businesses are invisible in those answers, not because they rank badly, but because nothing about them is structured, machine-readable, or independently referenced in a way an answer engine can trust. This paper explains why ranking and being cited are different mechanisms, why the gap is widening, and the playbook that makes a business citable.
- The problem. Discovery is moving from typed keywords to conversational questions, and the answer, not the results page, has become the shelf where buying decisions happen. A business that ranks well in Google can still be absent from every AI answer.
- The mechanism. Traditional search ranks pages. AI search decides whether an entity is citable: whether the text is extractable, whether the domain is machine-readable, and whether independent sources confirm the business exists.
- The playbook. Write extractable passages, ship machine-readable files, let the AI crawlers in, build authority that survives extraction, and appear where AI already looks. Every step is cheap, and almost nobody does it.
- What we did. We run llms.txt, schema markup, definition-first openings and FAQ blocks across kappal.in, ecommerce.kappal.in and msmebrands.com, and we build structured, citable brand pages for clients. This paper is the reasoning behind that work.
1. The answer is the shelf
I typed a question into ChatGPT last month and read the answer twice. The question was: who builds custom e-commerce platforms in India? The answer named three companies. None of them was us. I opened Google and ran the same query. We were on page one. The two answers did not agree, and the gap between them is what this paper is about.
Here is what is happening underneath that small mismatch. The way people find a vendor, a product or a service has shifted from typing keywords to asking questions, and the place where the answer appears has become the place where the decision happens. A buyer no longer reads ten results and picks. They ask ChatGPT, Perplexity, Claude or Gemini, and they act on the recommendation, often without clicking through at all. Google has compressed the same behaviour into the AI Overview that sits above its results.
The numbers make the direction unambiguous. BrightEdge's tracking found an AI Overview present in roughly 45% of Google searches, and the same tracking showed AI answers pulling clicks away from traditional results by as much as 58% [1]. The academic work on the other engines is even more direct: the 2024 KDD study on generative engine optimisation measured how much a source's visibility in AI answers improves when it adds citations, statistics and structure, and the effects are large [2].
The sentence worth keeping is this: the results page is no longer the shelf. The answer is the shelf. If the answer engine does not name you, you are not on the shelf, and no amount of page-one ranking changes that.
2. The gap: we ranked, and we were invisible
The reasonable assumption, and the one most businesses are still running on, is that AI answers are just a new layer on top of search ranking. Google's own guidance says as much. Its AI features optimisation guide states that AI Overviews are rooted in the core Search ranking and quality systems, that no special markup or files are required, and that the best practices for SEO remain the best practices [3]. That is true for Google's own answer surface.
It is not true for the rest of the AI search economy.
ChatGPT, Perplexity, Claude and Copilot do not rank pages the way Google does. They extract passages and decide what to cite. They draw on a wider range of sources than the top-ranked pages, and they lean heavily on third-party material: Wikipedia, Reddit, review sites, industry publications. They reward structure that can be lifted cleanly: a definition in the first paragraph, a FAQ block, a comparison table, a statistic with a source and a date. A page that ranks first in Google can be structurally invisible to these engines, and a page on page two that happens to be well structured can be cited ahead of it.
The KDD study quantified exactly how little the old playbook transfers: citations, statistics and quotations each lifted a source's visibility in AI answers by 30 to 40%, while keyword stuffing actively hurt [2]. The full measured table lives in the playbook below.
We felt this gap personally, and it is worth being precise about it. We had written whitepapers that ranked. We had a site with real technical depth, real deployments behind it, and a pricing page that was honest. None of it was getting us cited by the answer engines, because none of it was built for the way they read. We were playing the ranking game while the decision moved to a game that runs on different rules. That is the gap: the expected result, citation earned from good ranking, and the actual result, silence from every answer engine, did not match.
3. The epiphany: citation is a trust decision, not a ranking decision
The realisation landed when we ran our own site through the lens we were telling clients to adopt. We checked the same things we would check for anyone else: the robots file, the markup, the first paragraphs of our posts, the machine-readable files at the domain root.
We had no llms.txt. Our insights posts opened with context and a date line instead of a self-contained definition. Our schema stopped at BlogPosting. From the perspective of an answer engine, we were a domain that said a lot and defined nothing, structured nothing, and was referenced by nobody independent. We were ranking, and we were nearly unreadable.
The confession, stated plainly: an AI does not rank your page. It decides whether your business is a citable entity. That decision is made from three inputs, and every business that is invisible in AI answers is missing at least one of them.
First, extractable text. An answer engine quotes what it can lift. If your page opens with marketing context, if your claims carry no numbers, if there is no FAQ and no table, there is nothing for it to lift. The content can be excellent and still be unquotable.
Second, machine-readable presence. The domain itself should tell a machine what it is: an llms.txt at the root, schema.org markup on the pages, pricing that is readable rather than locked behind a form or inside JavaScript. AI agents are becoming buyers, and an agent that cannot parse your information will recommend a competitor whose information it can read.
Third, independent reference. An answer engine trusts what other sources say about you more than what you say about yourself. Industry tracking of ChatGPT citations shows a large share of cited sources are not the businesses' own domains at all; Wikipedia alone accounts for a significant slice, and Reddit and review sites follow [4]. If nobody independent cites you, an answer engine has no reason to risk recommending you.
That is the epiphany, and it changed how we write. The goal stopped being "rank for a keyword" and became "be the most citable answer to a question."
4. The playbook: five moves, in order
Getting cited by AI search is not a content marketing trick. It is an engineering discipline, and like all engineering it has an order of operations: diagnose, fix the highest-leverage gap, then measure. Here is the whole playbook in the order we actually do it.
First, the difference in full. Traditional SEO and AI citation optimise for different outcomes, different assets and different failure modes.
| Ranking (traditional SEO) | Citation (AI search) | |
|---|---|---|
| What you win | A position on a results page | A name inside an AI answer |
| What decides it | Links, keywords, domain authority | Extractable structure, machine-readable files, third-party signal |
| Your main asset | The page | The passage, the entity, the file |
| What gets rewarded | Keyword-matched, link-rich pages | Definitions, FAQs, comparisons, dated statistics |
| What hurts you | Thin content, spam links | Keyword stuffing, gated content, JS-only rendering |
| Where it fails you | The zero-click answer takes the click | No structure, no files, no third-party reference |
Are you invisible in AI answers? Run this first
Fifteen minutes. Answer each line honestly. Every "no" points at exactly one move below.
| Check | If the answer is no, you are missing... | The fix |
|---|---|---|
| Does your most important page open with a self-contained definition? | Extractable text | Move 1 |
| Do your posts carry FAQ blocks and comparison tables? | Extractable text | Move 1 |
| Do your claims carry numbers with sources and dates? | Authority | Move 1 |
| Is there an llms.txt at your domain root? | Machine-readable presence | Move 2 |
| Is your schema more than just BlogPosting? | Machine-readable presence | Move 2 |
| Can an agent read your pricing without a form or a login? | Machine-readable presence | Move 2 |
| Are GPTBot, PerplexityBot, ClaudeBot and Google-Extended allowed? | Crawler access | Move 3 |
| Do independent sources cite you, not just your own pages? | Third-party signal | Move 4 |
| Do you refresh content and update dates? | Freshness | Move 5 |
Move 1. Make every page extractable (day one)
An answer engine quotes what it can lift, so write passages that stand alone. Open with a definition in the first 40 to 60 words. Lead each section with the direct answer, then support it. Add FAQ blocks in natural language, comparison tables for any versus-type question, and statistics with a named source and a date.
The difference shows in two openings.
Before: "Welcome to our blog. Over the years, we have helped businesses improve their online presence. In this article, we will explore the world of AI search."
After: "Getting cited by AI search means being named as a source in the answer an AI assistant gives. Most businesses are invisible in those answers, not because they rank badly, but because nothing about them is structured in a way an engine can trust."
The first is context about itself. The second is an answer. Only one of them can be lifted into another engine's response.
Move 2. Ship machine-readable files (day one to two)
Put an llms.txt at your domain root that states what you do and links your key pages [5]. If you sell a product or service, make the pricing parseable, with limits and thresholds, not feature adjectives. Add schema.org markup: Article and BlogPosting for posts, FAQPage for question blocks, HowTo for procedures, Product for offerings. None of this is required by Google's AI Overviews, which is precisely why almost nobody does it, and why it is a differentiator with the engines that do read files.
Move 3. Open the robots.txt (fifteen minutes)
Your robots.txt controls whether the engines can read you at all. GPTBot and ChatGPT-User for OpenAI, PerplexityBot for Perplexity, ClaudeBot and anthropic-ai for Claude, Google-Extended for Gemini and AI Overviews, Bingbot for Copilot. If any of them is disallowed, that engine cannot cite you, full stop. Blocking the training-only crawler such as CCBot while allowing the search bots is a legitimate middle ground; blocking everything is a decision to be invisible.
Move 4. Be where AI already looks (week two onward)
Your own domain is necessary but not sufficient. Answer engines cite third-party sources disproportionately, so your business should be readable in the places they already trust: an accurate Wikipedia entry where you qualify for one, honest participation in the Reddit and community threads where your buyers ask questions, current profiles on the review platforms in your category, appearances in industry roundups and comparison articles, and video for how-to queries where the engine is YouTube-based. None of this replaces the site work. It multiplies it.
Move 5. Measure monthly, refresh quarterly
This is the move everyone skips, and it is the one that compounds. Once a month, ask each engine the one question you most want to be cited for, in ChatGPT, Perplexity, Gemini and Claude, and log who gets named. That log is your scoreboard. When a competitor appears that you do not, read their page and copy the structure that got them there. Quarterly, refresh your best pages against current-year facts and update the last-updated dates, because freshness is a citation signal the engines reward.
The authority layer that runs under all five
The KDD study ranked the tactics by measured effect, and the list is worth keeping [2].
| Method | Measured visibility boost |
|---|---|
| Cite sources | +40% |
| Add statistics | +37% |
| Add quotations | +30% |
| Authoritative tone | +25% |
| Improve clarity | +20% |
| Technical terms | +18% |
| Unique vocabulary | +15% |
| Fluency optimisation | +15% to 30% |
| Keyword stuffing | -10%, it harms |
The pattern is that trust is built from evidence, specificity and named sources, and destroyed by stuffing. Add author attribution with credentials. Show a last-updated date and refresh content against current-year facts. Lead with first-hand detail. An answer engine prefers specific, dated, attributable claims over general ones, because specific claims are checkable, and checkable claims are citable.
Ship it this week: the checklist
Work down this list and the invisible-business problem is mostly solved by Friday.
- My most important page opens with a definition an engine can quote
- Every post has at least one FAQ block in natural language
- Every comparison claim has a table or a number with a source
- llms.txt exists at my domain root and lists my key pages
- My pricing is readable by a machine, not locked behind a form
- Schema goes beyond BlogPosting: FAQPage, HowTo, Product where relevant
- GPTBot, PerplexityBot, ClaudeBot and Google-Extended are allowed
- I have honest, current presence in at least two third-party places my buyers trust
- I have a monthly reminder to log who each engine cites
5. The pre-packaged solution: MSMEBrands.com
Every move in the playbook above is engineering work, and most small businesses have nobody on expertise to do it manually. So we packaged it as MSMEBrands.com, the playbook delivered as a product platform: a structured, verified brand page that answer engines can read, sitting inside a marketplace buyers already trust. If you run a small business and want to be cited in AI answers, this is the fastest version of everything above.
An SME does not get just a listing. It gets a machine-readable brand presence, which is Move 2, delivered end to end. Every brand page carries schema.org markup an AI system can parse, feeds a sitemap that exposes the catalogue, and resolves SEO city-slug URLs, so the business is discoverable for the category-plus-location searches that matter. It is a page a language model can read to understand who a business is before recommending it.
The onboarding is AI 1-click: paste a company URL, preview the organisation, brands and product catalogue the platform extracts in seconds, confirm, and pay online with GST invoicing. No forms, no follow-up calls, no engineer required. Every live page passes through a human approval gate, and that verification is exactly the third-party signal an answer engine looks for before it risks recommending you, Move 4 built into the platform itself.
The marketplace layer adds the discovery a single brand page cannot. Buyers browse the catalogue at msmebrands.com/explore, and multi-factor search across 770+ categories, trademark class and location means a business is found the way buyers actually describe what they want and the related MSME brand discovery whitepaper is the full account of the gap this closes.
The strategic point is the playbook's own. The moat in AI visibility is not budget. It is that almost nobody bothers to be structured and verified, and the ones who do become the only citable answer in their category. MSMEBrands.com exists so a small business can be one of those few: list your business and go live in minutes, or compare plans and pricing first.
6. The lesson
You do not rank in an AI answer. You earn your way into it.
7. The closure
I still check that same question every month, the way you check a pulse. The answer has not named us yet. It names a different set of companies than it did a year ago: the ones that ship an llms.txt on launch day, the ones whose pages answer the question in the first paragraph, the ones other people have already cited. When our name appears, it will not be because we outranked anyone. It will be because we became easier to trust. That is the entire game.
FAQ: getting cited by AI search
What does it mean to get cited by AI search? It means an AI assistant names your business as a source in its answer: ChatGPT, Perplexity, Claude, Gemini or Google's AI Overview. Citation is different from ranking; a page can rank first in Google and still be absent from every AI answer, and a well-structured page can be cited ahead of higher-ranked competitors.
Why does my business appear on Google but not in ChatGPT or Perplexity? Those engines extract passages and decide what to cite rather than ranking pages the way Google does. They prefer self-contained answers, machine-readable files such as llms.txt and schema markup, dated statistics with sources, and third-party references such as Wikipedia, Reddit and review sites. If your site has none of those, there is nothing for them to lift.
What is llms.txt and does it actually help? llms.txt is a plain-text file at a domain root that tells an AI system what the domain does and links its key pages. It is not required by Google's AI Overviews, which is why most sites lack it, but non-Google engines and AI buying agents do read it, which makes it a cheap differentiator.
Does schema markup help with AI citation? Yes, on the engines that read structured data. FAQPage markup makes question blocks directly extractable, HowTo supports procedure queries, and Article and BlogPosting establish authorship and dates. Structured content shows materially higher visibility on non-Google AI engines.
Which AI crawlers should I allow in robots.txt? GPTBot and ChatGPT-User for OpenAI, PerplexityBot for Perplexity, ClaudeBot and anthropic-ai for Claude, Google-Extended for Gemini and AI Overviews, and Bingbot for Copilot. Disallowing any of them blocks that engine from citing you. Blocking training-only crawlers like CCBot while allowing the search bots is a reasonable middle ground.
How long before AI citation work shows results? It compounds like authority, not like an ad. Expect the first cited queries within a few months of shipping structure and files, and real share of voice on a 6 to 12 month horizon as freshness, third-party mentions and connected clusters accumulate. The engines reward content that is current and interlinked.
About Kappal Software
Kappal Software Private Limited (kappal.in) is a boutique software company building custom applications, AI/ML solutions, cloud infrastructure and e-commerce platforms for businesses across AgriTech, FinTech, e-commerce and manufacturing. We run our own AI visibility playbook on our own domains, and we build the same discipline into client sites, products and content: structured data, machine-readable files, definition-first writing and citation-grade pages. If this paper describes a system you need, write to us through the contact page at kappal.in.
References
- BrightEdge. "One Year Into Google AI Overviews, BrightEdge Data Reveals Google Search Usage." Tracking of AI Overview presence and click behaviour. https://www.brightedge.com/news/press-releases/one-year-google-ai-overviews-brightedge-data-reveals-google-search-usage
- Aggarwal, P., Murahari, V., Rajpurohit, T., Kalyan, A., Narasimhan, K., Deshpande, A. "GEO: Generative Engine Optimization." Proceedings of the 30th ACM SIGKDD Conference (KDD 2024). https://arxiv.org/abs/2311.09735
- Google Search Central. "AI features optimization guide." https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- Industry analysis of AI answer citations (2025-26). Tracking of source attribution in ChatGPT and Perplexity answers, including third-party citation shares and the dominance of Wikipedia, Reddit and review platforms. Figures vary by study and change with each engine update.
- llmstxt.org. The llms.txt proposal for giving AI systems a file that describes a domain and links its key pages. https://llmstxt.org
Kappal Engineering
Kappal Software · Building tomorrow's enterprise solutions
