ChatGPT, Perplexity and Gemini are the new front page. We crawl your site the way their bots do and find exactly what blocks you — before your customers ask a question you don't get to answer.
We fetch your pages with the same user agents AI assistants use — and compare against what humans get.
WAF rules, robots.txt bans, missing llms.txt, broken metadata — scored and prioritized by severity.
Every finding comes with the exact fix. No jargon, no 40-page PDF report.
AI visibility is the headline, but we run the unglamorous classic checks too — the ones that quietly cost you clicks.
Every finding names the problem in human words and ships with the exact fix. No jargon safari.
AI-drafted metadata you approve — or edit first, then approve — merged into your HTML at the edge. Server-side, so a crawler that never runs JavaScript still sees it. No CMS deploy, no plugin. One DNS record →
An article with no Article JSON-LD gets one, written only from what is already on the page and the facts you confirmed — no invented author, no invented date, no invented numbers. You approve it and we serve it as a <script type="application/ld+json"> at the edge, with no code on your side. It is added, not substituted: a page that already ships its own JSON-LD keeps it. This one is never automatic, and you tell us which paths are articles.
Before/after CTR and position at 14 and 28 days — labeled correlation, not causation. We tell you if a change helped, hurt, or didn't matter. No causation theater. And those verdicts are what earn a fix type the keys →
Finding a broken description is the easy half. The hard half is that fixing it means a CMS you don't control, a deploy you have to schedule, or a plugin you don't want. So we took that step out: point one DNS record at us and the changes you approve are merged into your HTML at the edge, before it leaves Cloudflare — server-side, so a crawler that never runs JavaScript still sees them.
It works the same on WordPress, Shopify, Squarespace, a Vercel app or a VPS, because from where we stand they're all just an origin. No plugin. No script tag. No Cloudflare account of your own. No code change.
It also means we're in the path your visitors take, which is a real thing to ask of you. Here's exactly what that costs and how you get out →
One TXT to prove the domain is yours, one CNAME when you're ready for us to serve it. See the real screens — including the ones where it fails →
Traffic follows DNS. Point it back and we're gone as soon as it propagates. Short of that, one button turns us into a plain forwarder within sixty seconds.
Audits, findings, drafts and Search Console all work without it. And it's on every plan, including Free.
Google Analytics is a script in a browser. GPTBot doesn't run scripts, so as far as your dashboard is concerned, the assistant that read your entire site last Tuesday never visited.
We're in the response path, so we count what actually happened: which AI crawlers fetched which pages, which assistants sent you a human afterwards, and which search engine that referral really came from — per engine, not lumped into "organic". Gemini and Copilot count as assistants, not as search, because filing them under Google would erase the one number this product exists to show you.
Underneath that we also count everything your site served through us, sorted into 9 categories — human page views split by where the person came from, AI crawlers, other bots, assets, and two catch-alls for what we could not place. A count is all it is: a site, a day, a category, an integer. Daily, on every plan including Free.
In your analytics we keep the referring hostname and nothing else — not the path, not the query. The one measurement we take across all traffic, and what it cannot contain →
Plans carry two allowances because they measure two different things, and rolling them into one would make both wrong. Edge events are the AI-and-search traffic we keep detail for — which crawler fetched which page, which assistant sent you a person, which engine a search visit came from. Requests are everything our edge served for you, assets included: it's the honest total, it's what we actually pay Cloudflare for, and on a normal site it's twenty to forty times the number of page views, because one page pulls that many stylesheets, scripts and images. Both allowances are per account, pooled across every site on the plan — not per site. Pooling means a busy site borrows headroom from quiet ones instead of paying overage while another site's allowance sits unused.
Past the included requests, the rate is $2.00 per additional million. Here is the arithmetic, because we'd rather you checked it than trusted it: a counted request costs us about $0.81 per million — roughly $0.80 to serve and about a cent to count — so $2.00 is about 2.5× our marginal cost. Those input prices are Cloudflare's published ones and the model that uses them is the same one we run internally.
Past the included edge events, the rate is $20.00 per additional million, prorated — same arithmetic, shown the same way: an accepted event costs us about $9.00 per million (it's the expensive lane — every event is a request we serve, rate-limit and roll up), so the rate is about 2.2× our marginal cost.
The managed edge — one DNS record, any hosting platform, no plan gate. Fail-open serving. A sixty-second pass-through switch that is yours, not support's. A public status page. Per-engine edge analytics and Search Console — including the full traffic breakdown, all 9 categories, daily, on Free. The MIT engine. And a human at hello@citeworthy.io.
Citeworthy is built on seo-agent, an MIT-licensed Cloudflare Worker we publish in full — the crawler, the rule set, the AEO checks, the proposal model and the edge injector. It is not a trimmed-down demo of the paid product and there is no second, better engine behind the login. The version running this account is v1.30.1, the same release you can clone today.
So self-hosting is a real path, not a gesture at one: deploy it to your own Cloudflare account, point it at your own site, keep every byte of the data, pay us nothing. What you take on is the operating — one instance per site, your own bindings, your own upgrades, and no support line. What you buy from us is the other half: the judgment, the review lane, the verdicts, and somebody whose job it is when the edge misbehaves at 3am.
Citeworthy is a website audit application from Alan Wizemann, LLC. It crawls websites you own, finds SEO and AI-visibility problems (broken metadata, crawler blocks, missing AI-agent files), suggests fixes you review and approve, and — on connected sites — serves those approved fixes from the edge without changing your site's code.
If you connect Google Search Console, Citeworthy uses read-only access to display your own search performance (clicks, impressions, positions) inside your dashboard and to measure the before/after impact of changes. That data is only ever shown to you, is never used for anything else, and disconnecting removes it. Details in our privacy policy.