# About CrawlRadar CrawlRadar is AI search analytics: it shows which AI crawlers visit your website, how many visitors ChatGPT, Perplexity, Gemini and Claude send you, and what to fix so AI can find and recommend you. It exists because “is my site ready for AI search” had a lot of opinions attached to it and no instrument. By [Iliass El Barhoumi](/about) · Published 4 August 2026 · Last updated 1 October 2026 ## What CrawlRadar measures Three things, one per question a site owner asks about AI search: - **Which AI crawlers visit.** A collector on your own server identifies 56\+ AI crawlers and verifies each visit against the vendor’s published IP ranges. Analytics tags never see these visits, because crawlers do not run JavaScript. - **How many visitors AI sends.** A cookieless tracking tag counts the referrals from ChatGPT, Perplexity, Gemini, Claude and Copilot, and the pages they land on. - **What to fix.** 14 checks score each page 0–100 on whether an answer engine can retrieve, trust and quote it, including the 14 [AI crawler tokens](/crawlers) in your robots.txt. [Add your website](/dashboard/new) to see all three, or start with the free [tools](/tools), which need no account. ## Who builds it CrawlRadar is built and run by **Iliass El Barhoumi**, an independent developer. There is no investor and no sales team: the product is paid for by its subscriptions, and the person answering support email is the person who wrote the code. The founder’s profile is on [GitHub](https://github.com/iliasselbarhoumi), and the collector is published on npm as `@crawlradar/collector`. ## What the score is The score is a measure of _eligibility_, not a prediction. It says whether an answer engine can retrieve, attribute and quote a page, not whether it will, which depends on the query and the competing sources and is not observable from outside. ## What it deliberately does not do Three things, each of which would make the number bigger and less honest. - **It does not guess.** When a measurement fails, whether a robots.txt that times out or a challenge page, the check reports _not checked_ and its points leave the denominator. Awarding full marks there once scored a site that blocks every AI crawler as though it welcomed everyone. - **It does not oversell a check.** llms.txt is worth 4 points and the fix text says the evidence for it is nil. A tool that inflates a check to seem comprehensive is worth less than one that admits the check is minor. - **It does not hide a heuristic.** Where a check infers rather than measures, the summary says so. False positives cost more trust than they save time. ## How the extension handles your data Scanning does not touch it. The extension installs with `activeTab`, `scripting` and `storage`, with no host permissions, no content scripts running in the background, no analytics. Settings stay in local browser storage, and a scan talks only to the site it is scoring. Three optional features do reach the network, each behind a permission you grant when you enable it, and only one of them sends page content anywhere: AI checks, which post the text straight to your own provider key. The [privacy policy](/privacy) covers all three. The website is different by necessity: it has to fetch the URL you give it. It fetches that page once, anonymously, with no cookies, and does not store the URL unless you explicitly create a share link. ## The scoring model 14 checks across three levers, weighted by how much failing each one costs. Every check has its own page in [the scoring model](/checks), and the free [GEO score checker](/tools/geo-score-checker) runs all of them on any URL. The [GEO guides](/blog) explain the thinking behind them in prose, and the [comparisons](/vs) show where CrawlRadar differs from the SEO tools you may already use. ## Frequently asked questions ### Who makes CrawlRadar? Iliass El Barhoumi, an independent developer, builds and runs CrawlRadar. It is not affiliated with OpenAI, Anthropic, Google, Perplexity or any other AI vendor. The engines are named because they are what the product measures, not because anyone endorses it. ### Does the extension send my browsing data anywhere? Scanning does not. The extension installs with activeTab, scripting and storage, no host permissions and no analytics, and the scoring engine runs inside the page you are looking at, and the only requests a scan makes are same-origin fetches of that site’s own robots.txt, llms.txt and raw HTML. Three optional features can send data, each behind its own permission you grant at the moment you enable it: in-editor scoring on a domain you choose, a plan check against crawlradar.xyz that carries no page data, and AI checks that send page text directly to your own Anthropic, OpenAI or Perplexity key. See the privacy policy for what each one does. ### Is the scoring model the same in the extension and on the website? Yes, literally the same code. The scoring engine is a shared package with no IO of its own; the extension feeds it a rendered DOM from your tab, and the website feeds it a server-parsed document. Scores can still differ, because those are genuinely different views of a page: the website sees what a non-JavaScript crawler sees. ### How are the weights decided? By judgement about how much each failure actually costs a citation, not by a model fitted to data. There is no public dataset of what answer engines cite. The weights are documented, versioned and stated openly so you can disagree with them: 25 points for retrieval, 15 for source trust, 60 for extractability. --- Source: https://www.crawlradar.xyz/about