Citable — give AI the facts, not your web design
ChatGPT, Claude and Perplexity read your site before they answer. A normal page is 400 KB of design, scripts and markup, and under 3% of it is content they can use. Citable hands them the same page as 4.6 KB of plain facts, on your own domain — while people and Google still get your real page.
This response
You are ClaudeBot (Anthropic). Citable recognised you as an AI agent, so this is https://getcitable.in/ with the UI removed — the content only. A browser asking for the same address gets the full designed page.
The core idea: your website without the UI, for AI agents
Citable strips the UI from a website for AI agents and serves them only the content.
When an AI agent — ChatGPT, Claude, Perplexity or any of the 81 that Citable recognises — opens a page, Citable removes the theme, scripts, navigation and layout and serves only the content: the same facts, at the same URL, on the site's own domain. People and Google still get the full designed page.
Every row below is the same address. Citable decides which version to send by checking who is asking, before the response goes out.
- A person in a browser → The full designed page, untouched.
- Googlebot, Bingbot and other search engines → The full designed page, untouched.
- An AI agent — GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot and the rest → The content only: no UI, no scripts, the same facts at the same URL.
What Citable is, and what it is not
Citable is a routing layer. It sits in front of your site's requests, hands recognised AI crawlers a clean, token-light copy of the same page on your own domain, and records every fetch: which engine, which page, when, and what figure was in the response.
- It is NOT an AI-visibility or rank-tracking tool. It does not prompt assistants on a schedule and grade the replies, and it does not report where a brand appears for a given prompt. Several other products do that well; if that is the question, buy one of them.
- It is NOT an agentic-shopping product. There is no product feed, no AI-attributed order tracking and no checkout integration.
- It is NOT Shopify-only and NOT an e-commerce tool. Shopify is one of four ways in. The engine has no platform dependency.
- It is NOT a badge, a certificate or a schema plugin. Nothing here makes a model cite you; it removes the reasons a model cannot.
- It is not affiliated with any other product or company using the name Citable.
Check it yourself
getcitable.in runs on Citable. Fetch any page twice, once as a browser and once with an AI agent's user agent.
curl https://getcitable.in returns the designed page a person sees.
curl -A "GPTBot" https://getcitable.in returns the content-only version an AI agent is served — this document.
The problem
An AI assistant names three sources and links them. Being the fourth is the same as not existing, and there is no second page to be on.
Assistants do not run your JavaScript. They fetch the HTML, take what is in it, and stop. Anything your site draws afterwards was never there as far as the engine is concerned — a price, a fee table, an eligibility rule, a spec loaded from JSON, a rate card behind a tab, a code sample a docs framework hydrates, an availability badge. The failure is a rendering failure, not a retail one: it happens on documentation, on a law firm's practice page and on a university's fee schedule for exactly the same reason.
The second failure is size. Whatever survives is buried in theme, script and navigation an engine has to pay for before it reaches a single fact.
What it runs on — any website, on any stack
Citable is a routing layer, not a plugin for one ecosystem. It needs exactly one thing: to sit in front of the request before the response goes out. It does not care what generates the page behind it, and it never edits that page.
It is not an e-commerce tool and it is not Shopify-only. Shopify is the one-click route in; it is one adapter of four.
- Shopify (One-click app, About ten minutes) — works with Shopify, Shopify Plus. Install from the App Store and approve the charge. Citable reads products, collections, articles and metafields through the Admin API, and serves the clean versions on your own storefront. No theme edit.
- WordPress & WooCommerce (Plugin, About fifteen minutes) — works with WordPress, WooCommerce, Elementor, ACF. Install the plugin, connect your workspace, and Citable reads posts, pages, products and custom fields — ACF included — through the REST API. It serves the clean version from your own domain and writes its own fenced block into robots.txt.
- Any site, at the edge (CDN worker, Cloudflare, one approval. Vercel, one file.) — works with Cloudflare, Vercel, Next.js. For custom builds — Next.js, Rails, Laravel, Webflow, Magento, a hand-written site. A small worker on your existing CDN inspects each request, passes humans and search engines straight through, and answers recognised AI agents with the clean version. Your origin is untouched. On Cloudflare we deploy it for you: you approve once and never see a config file.
Where the facts are read from
The clean copy is rebuilt from wherever your stack already keeps structured content, never scraped from the page it replaces. That is why it cannot state a figure you do not publish.
- Shopify: Admin API — products, variants, collections, articles, metafields.
- WooCommerce: REST API — products, variations, terms, custom fields.
- WordPress: REST API — posts, pages, ACF and custom post types.
- Headless / custom: Your own API, a feed, or a sitemap crawl you control.
- Anything else: A JSON feed you already publish, mapped once during setup.
What we measured across 15 live homepages
Fetched as GPTBot on 2 September 2026, counted with the cl100k_base tokeniser. The sample was Indian direct-to-consumer sites because that is the sample we could take; the numbers describe how heavily modern front-ends render, which is not particular to what a site sells.
- Median homepage: 281,405 tokens.
- Heaviest: 954,850 tokens. Lightest: 2,104.
- Median share of the response that is actual content: 1%.
- 11 of 15 exceeded 100,000 tokens.
- 6 of 15 were under 1% content.
- 3 had no structured data at all.
What Citable does
It sits in the request path on your own domain. A browser or a search engine gets your site exactly as it is today. A recognised AI assistant gets the same facts as clean, structured HTML it can finish reading.
Because it serves the response, it can also record what happened: which engine read which page, when, and whether a person was waiting on the answer.
The 81 AI agents that get the content-only version
Matched on user agent, and verified against published IP ranges where the operator publishes them. Search engines are never on this list, so rankings are never part of it.
- OpenAI: OAI-SearchBot, ChatGPT-User, GPTBot, ChatGPT Agent, Operator
- Anthropic: Claude-SearchBot, Claude-User, Claude-Web, ClaudeBot
- Perplexity: Perplexity-User, PerplexityBot
- Google: Google-Extended, Gemini-Deep-Research, Google-Agent, NotebookLM, GoogleOther
- Meta: meta-externalfetcher, meta-externalagent, meta-webindexer
- DuckDuckGo: DuckAssistBot
- Common Crawl: CCBot
- Apple: Applebot-Extended
- ByteDance: Bytespider, DoubaoBot
- Amazon: Amazonbot, Amzn-User, AmazonBuyForMe, NovaAct, amazon-QBusiness, Amzn-SearchBot
- You.com: YouBot
- Cohere: cohere-ai
- Huawei: PetalBot
- Diffbot: Diffbot
- AI2: AI2Bot
- Timpi: Timpibot
- Kangaroo: Kangaroo Bot
- Webz.io: omgili
- Mistral: MistralAI-User, MistralAI-Index
- Moonshot AI: Kimi-User, Kimi-SearchBot
- Alibaba: TongyiBot
- Baidu: YiyanBot
- Kagi: kagi-fetcher
- Phind: PhindBot
- Liner: LinerBot
- Manus: Manus-User
- Twin: TwinAgent
- Parallel: ShapBot
- Big Sur AI: bigsur.ai
- Qualified: QualifiedBot
- Klaviyo: KlaviyoAIBot
- Poggio: Poggio-Citations
- iAsk: iAskBot
- Crawl4AI: Crawl4AI
- Crawlspace: Crawlspace
- WRTN: WRTNBot
- UseAI: UseAI
- Lyrenth: AIWebIndex
- Aranet: Aranet-SearchBot
- Kunato: KunatoCrawler
- Reflection: Reflectionbot
- GeistHaus: GeistHaus-PageFetcher
- Brave: Bravebot
- Exa: ExaBot
- Tavily: TavilyBot
- AddSearch: AddSearchBot
- Linkup: LinkupBot
- Querit: QueritBot
- Ceramic AI: TerraCotta
- Valyu: HenkBot
- Channel3: Channel3Bot
- Microsoft: AzureAI-SearchBot
- Atlassian: atlassian-bot
- Cloudflare: Cloudflare-AutoRAG
- Andi: Andibot
- Direqt: Anomura
- Yandex: YandexAdditional
- Zanista: ZanistaBot
- Poseidon Research: Poseidon Research Crawler
What kind of page it works on
- Product and service pages — the price, the terms, the variants, whatever you actually charge.
- Documentation and API references — the steps and the code, without the docs framework around them.
- Pricing and rate cards — tiers, limits and fees stated as text rather than drawn by a component.
- Regulatory and compliance pages — licences, registration numbers, disclosures an assistant will not paraphrase unless it can read them exactly.
- Research, guides and long articles — the argument and the figures, front-loaded.
- Location, clinic, campus and branch pages — hours, addresses, eligibility, what is offered where.
- Case studies and specification sheets — the numbers, not the carousel they sit in.
What Citable does not claim
- We don't make you relevant. If nobody asks about your category, clean pages change nothing.
- We don't touch Google rankings — on purpose. Googlebot gets your real page, untouched.
- We can't make an engine cite you. We remove the reasons it wouldn't.
Who it is for
The examples below are categories we have looked at closely; they are not a limit. The test is narrower and has nothing to do with what you sell: does somebody ask an assistant about your category BEFORE they have a shortlist? If they do, being unreadable costs you the shortlist rather than the comparison — and that is as true of a compliance consultancy or a hosting provider as of a shop.
- B2B SaaS — “Best tool for…” shortlists. Buyers ask for a shortlist before they ask for a demo. If your pricing, integrations and limits are drawn by JavaScript, the assistant builds that shortlist out of whoever wrote theirs in plain HTML.
- Financial services — Trust and “is it safe” questions. Nearly every query carries a safety question underneath it. Licences, regulator numbers and fee tables are exactly the facts an assistant will not state unless it can read them unambiguously.
- SEO & digital agencies — GEO, the new retainer line. Clients are already asking why they are missing from AI answers. The audit gives you a measured answer per client, and the read log gives you something to report on each month.
- Hospitality & hotels — “Best hotel near…”. Amenities, room types and cancellation terms sit inside booking widgets that never render for a crawler. The assistant recommends whoever stated them as text.
- Education & edtech — Programme and college comparisons. Fees, durations, eligibility and placement figures get compared side by side in a single answer. Anything an assistant cannot verify, it leaves out of the comparison entirely.
- Consumer durables — Spec-heavy comparisons. These answers are built from spec tables. A specification held in a tab component or an image is invisible, and a missing spec reads as a missing feature.
- Automobiles — Model and spec answers. Variants, mileage, warranty and on-road pricing change often and get quoted confidently. A stale figure an assistant repeats is worse than no figure at all.
- AlcoBev — Discovery and provenance. Origin, process, ageing and tasting notes are the whole story, and they are usually the part of the page rendered last — or held in a PDF nothing reads.
Source: https://getcitable.in/ · Citable · Run the free audit · llms.txt · getcitable@gmail.com