RankyFy AI SEO

One screen that answers "is AI reading my site, and is it worth anything?": total AI crawler hits with a per-bot daily chart, how many of your pages AI has ever read (and how many never), real visits arriving from AI assistants, the share of verified hits, and your readiness score. The benefit: you spot problems — a bot gone quiet, pages never read, a score drop — in seconds, without assembling data from logs and analytics yourself.

It turns raw requests into answers: every AI crawler listed with its purpose (training vs. search vs. user fetch), hits, pages, trend and verification state — and the same data pivoted by page, so you see exactly which content each bot reads and what response it got. Add redirect buttons appear on URLs answering "not found". The benefit: you know which company reads what, catch fakes, and fix dead URLs that AI keeps requesting.

Anyone can send a request claiming to be GPTBot. The plugin checks every claimed crawler against the operator's published IP ranges, forward-confirmed reverse DNS or a cryptographic signature (Web Bot Auth), and counts failures separately as impersonations. The benefit: your numbers are real — decisions like "allow GPTBot, it sends value" rest on verified traffic, and the impersonation list gives you evidence to block abusive networks at your firewall.

Analytics suites lump assistant click-throughs into generic referrals, and some AI visits carry no referrer at all. This screen recognises the referrer and UTM patterns of ChatGPT, Perplexity, Gemini, Claude, Copilot and others and reports those human visits by engine and landing page — next to the crawl data for the same pages. The crawled vs. AI visits view shows pages AI reads but never sends anyone to, which is usually a content problem you can fix, not a crawling one.

18 concrete checks against your published content — direct answers under question headings, depth, author information, working pages, crawler access, llms.txt and more — rolled into one 0–100 score, with open issues ranked by impact and a "How to fix" for each, starting with the exact pages to edit. The benefit: instead of guessing what "optimize for AI" means, you get a prioritized to-do list measured from your own site, and the score history shows whether your edits worked.

Three things. It shows each crawler's real traffic on your site next to the switch, it spells out the consequence of every block before you save ("You disappear from ChatGPT's answers. Rarely what you want."), and it writes only its own clearly-fenced section of robots.txt, leaving the rest untouched. Presets handle the common intents in one click — including "Allow search, block training", which stops your content training models while ChatGPT can still cite and open your pages. And because every request is still monitored, it tells you which bots keep requesting despite a block, so you can escalate with evidence.

A hand-written llms.txt goes stale the week you publish something new. This tool builds yours from what AI crawlers actually read on your site — your most-read, most important pages with descriptions — keeps it current as content changes, excludes pages that are noindex, broken or blocked, and preserves your manual edits across rebuilds. llms-full.txt (full text) and ai.txt (training policy) are included. Nothing is served until you switch it on, and the screen shows whether each file answers and which bots fetch it.

Actions derived from your own crawl data, not a checklist: crawlers you block whose assistants already send you visitors (with the numbers), important pages no AI crawler has ever read, pages AI fetches often that score too low to be quoted, and pages that error or respond slowly to crawlers. Each item says why it matters and links to the fix. Content suggestions appear too, always labelled AI-suggested — never dressed up as measured data.

Every time you publish or update, the editor runs an AI crawler check: noindex set by your SEO plugin, robots.txt rules blocking your priority crawlers from this page, a canonical pointing elsewhere, a changed URL that AI still requests, or content too thin to be quoted. The benefit: pages stop silently dropping out of AI search — you learn about the problem before the publish, not weeks later on a chart. Changed URLs get automatic 301 redirects so crawlers never hit dead links.

They watch so you don't have to: a new AI crawler on your site, an important page crawled for the first time or no longer crawled, robots.txt suddenly blocking AI search, your server or CDN refusing crawlers, impersonation spikes, readiness score drops, and pages assistants keep opening for their users. Delivered by email (critical-only, everything, or a daily digest) or webhook to Slack, Teams or Google Chat. The benefit: a misconfigured robots.txt or a broken page costs you hours of AI visibility, not months.

If a cache or CDN answers a page before WordPress runs, that crawler request never reaches the plugin's hook. The import reads your server's access log (parsed in your browser, uploaded in batches) and fills those gaps, with the same verification applied. The benefit: complete numbers on heavily-cached sites. The plugin detects common caches and tells you when this applies; Cloudflare's visitor-address header is recognised automatically.

Over 30 out of the box: OpenAI (GPTBot, OAI-SearchBot, ChatGPT-User), Anthropic (ClaudeBot, Claude-SearchBot, Claude-User), Perplexity (PerplexityBot, Perplexity-User), Google (Googlebot, Google-Extended, Google-CloudVertexBot), Microsoft Bingbot, Meta, Amazonbot, Applebot-Extended, ByteDance Bytespider, Common Crawl CCBot, DuckAssistBot, Mistral, Cohere, You.com and more — plus unrecognised-bot detection and your own custom entries. The registry can update without a plugin release (opt-in).

Yes. Every public post type is monitored, scored and eligible for llms.txt — products, docs, courses, anything. Importance signals include your shop and cornerstone pages, so the readiness checks focus where revenue is.

No, it runs beside it. Yoast SEO, Rank Math, SEOPress and All in One SEO handle classic search engine optimization; this plugin handles the AI side — crawler verification, AI referral tracking, llms.txt, crawler access and answer-readiness. It also reads your SEO plugin's noindex settings so the publish check can warn you before a page drops out of AI search.

No and no. Classification costs well under a millisecond for ordinary visitors, only bot requests are recorded, and dashboard reads come from pre-aggregated tables. By default everything runs on your own site with the bundled crawler registry; remote registry updates and the RankyFy account are separate opt-ins, documented under External Services. Visitors are never tracked, and crawler addresses are stored truncated.

No. Every tool above — monitoring, verification, referrals, readiness, access manager, llms.txt, opportunities, publish check, alerts, log import — is local and free. An account adds one thing: AI content analysis of your pages (keyword, question and gap suggestions).