Most SEO plugins grade the page you are already editing. Visibility Flux starts from your real
Google Search Console data and tells you which page to open first — the one quietly
losing the most clicks.
Upload your Search Console CSV export and Visibility Flux scores every page against the
click-through rate its ranking position should be earning. The gap multiplied by
impressions gives you estimated lost clicks per month: a worklist sorted worst-first,
not a traffic light.
It also covers the half of search that changed recently — whether AI assistants can reach
your site at all, and whether they send you readers.
Five views over your whole site, built from your own data:
Search Console exports are parsed in any language — English, French, German, Spanish,
Dutch, Arabic and more, comma or semicolon separated. Nothing to reformat.
Editing robots.txt tells you what you wrote. It does not tell you what a crawler receives.
The common failure is a CDN or firewall refusing the request before WordPress is ever
reached, and no robots.txt editor can show you that.
Visibility Flux requests your site using the real user-agent strings of GPTBot,
OAI-SearchBot and PerplexityBot, and reports the status code that actually comes back.
It checks nine AI crawlers, plus the settings that would remove your whole site from
search and AI answers, with one-click fixes.
It also generates an llms.txt from your best performing pages, served virtually at
/llms.txt — no file written to disk.
When someone clicks through from an AI answer, most analytics tools file the visit under
“direct”. Visibility Flux counts those visits properly, across twelve assistants: ChatGPT,
Perplexity, Gemini, Claude, Copilot, Meta AI, You.com, Poe, Phind, DeepSeek, Mistral and
Grok.
No cookies. No accounts. No visitor identity in your stored traffic: only which assistant
sent the reader and which page they landed on. Daily totals are kept for 90 days, monthly
totals for 36 months, the 200 most visited pages, and a log of the last 100 visits, each
with its time, the assistant, the landing path and the referring site’s hostname. Nothing
leaves your site — the count is made by your own WordPress. On by default, with a switch in
Settings to turn it off; switching it off stops the counting and keeps the figures already
collected.
A small flag in the browser’s session storage stops one visit being counted twice. It is not
a cookie, it is never sent anywhere, and it goes when the tab closes.
The tracking endpoint is throttled so it cannot be spammed to inflate your numbers. That
check salts the visitor IP with your own site key and keeps a counter under the resulting
hash for ten minutes. It is never reversible and never reaches your stored data.
AI shopping agents buy from structured product data, not from your page design. Visibility Flux
audits every product for missing images, prices, thin descriptions, missing categories,
GTIN, brand and weight — a score per product, worst first, with a direct edit link.
Fully deterministic: no AI calls, no API key, no cost.
Everything above is free, forever, with no time limit. Visibility Flux Pro adds the writing:
Pro is available with a 7-day free trial at infinacode.com.
It uses your own Anthropic API key, so you pay Anthropic directly for what you use and
every action shows its exact cost. When a trial ends, the plugin returns to the free
features — nothing is deleted.
This plugin has one service of its own, IndexNow, and contacts it only when you enable it.
The speed audit can also reach the hosts your own pages already load files from; that is
described in the last paragraph of this section.
IndexNow (instant indexing)
https://api.indexnow.org/indexnow,Requests to your own site
The AI crawler test, speed audit, answer readiness and hreflang checks fetch your own
public pages over HTTP — the same pages any visitor loads. The crawler test sends the real
user-agent strings of GPTBot, PerplexityBot and others so your server and CDN answer them
exactly as they would the real crawler. Nothing about your content or your visitors leaves
your hosting.
Files your pages load from other hosts
When you start the speed audit, it asks each image and script your pages reference how large
it is (a HEAD request), and reads the first few stylesheets to check how fonts load. Some of
those files are hosted by other companies – a font service, an analytics script, a CDN – and
for those the request goes to that company’s server. It carries the file’s address and
nothing else: no page content, no visitor data and no identifier from this plugin. It only
happens while you run the audit, and requests to private or loopback addresses are refused.
Google Search Console
Visibility Flux does not connect to Google. Search Console data reaches the plugin only through
CSV files you export and upload yourself.
Lucide (the icons on the plugin’s screens)
assets/vendor/lucide/lucide.min.js – Lucide 1.39.0, ISC licence; the licenceassets/vendor/lucide/LICENSEdist/umd/lucide.min.js build of the lucide npm package at that version. The