ChatGPT, Perplexity, Claude and Gemini now send real visitors, and crawl your pages to answer questions without sending anyone. What your own analytics can see, what only Search Console and server logs can, why our own articles were invisible to AI crawlers until we fixed it, and a measurement setup that covers all three.
Visits that came from a search engine or an AI assistant — your own analytics can see these.
How often you appeared in results and for which searches — only the search engines know, through Search Console and Bing Webmaster Tools.
Whether AI systems read and cite you — partly visible in your server logs, partly only by asking them.
The referrer on a visit's first page tells you where it came from: google.com and bing.com for search, chatgpt.com, perplexity.ai, claude.ai and gemini.google.com for assistants. ChatGPT also often adds utm_source=chatgpt.com to links it cites. Classify channels in the query rather than at collection time, so you can change the rules and reclassify history. Two caveats: search engines have not passed the search terms for years, and many mobile apps send no referrer, so assistant traffic is undercounted.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Google Search Console reports, per query and per page, impressions, clicks, click-through rate and average position, with an API for daily export. Verify the domain with a DNS record, submit your sitemap, and copy the daily numbers next to your own events — then one query shows the whole chain for each page: shown, clicked, visited, booked. A new site gets little data for the first months, and rare queries are withheld for privacy.
AI companies crawl with named user agents — GPTBot and OAI-SearchBot, ClaudeBot, PerplexityBot and others — and some fetch a page at the moment a user asks a question, under agents such as ChatGPT-User and Claude-User. CDN access logs show which pages each reads. The warning, from our own site: most of these crawlers do not run JavaScript. Until we prerendered our pages, every article we had written reached them as a 1.3 KB empty shell titled with the site name. If your site is a single-page app, check what a crawler actually receives before measuring anything else.
No AI company offers a Search Console. The practical substitute is a fixed set of questions your buyers ask, sent weekly to the major models with web search enabled, recording whether you are cited or mentioned. It costs a few dollars a month in API calls and gives a trend per question — which is the thing that matters.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
How We Use AI to Write Technical Content Without Publishing Nonsense
AI makes producing articles nearly free, which is why the web is filling with confident, outdated, wrong ones. The pipeline behind this site: primary sources first, claims checked before drafting, dates on everything, a human who knows the subject, and analytics to tell whether it helped anyone.
Read
Ad-Hoc Questions on DynamoDB vs Postgres: 16 Analytics Queries at 100,000, 1 Million and 5 Million Orders
Every question across customers is a full table scan in DynamoDB: 217,000 read units at 5 million orders, whether it returns 10 rows or all of them. Postgres answered the same 16 questions in 0.08 to 2.7 seconds without a single index added for them, and an index built in 2.7 seconds took one from 148 ms to 44 ms. Measured in AWS.
Read
As of October 26, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.