Troubleshooting & FAQ

Troubleshooting & FAQ

Import

"Clicks and CTR parsed as 0"

Your export uses column names Visibility Flux doesn't recognise yet. The import screen lists the headers it expected. Re-export from Search Console using Export → Download CSV rather than copying data into a spreadsheet, which often renames or reformats columns.

The Problem Map says "No GSC data imported yet"

Only the Queries file was imported, or the import failed. Pages.csv is the required one — the map is built from it.

Cannibalisation looks like guesswork

It is, until your Queries export includes the page each query belongs to. In Search Console, add Page as a second dimension to the Queries report before exporting. Visibility Flux then groups pages that literally rank for the same query instead of comparing URL slugs.

Numbers look stale

Re-import. Search Console data is a snapshot, not a live feed. Importing replaces the previous data and clears all caches automatically.

Activation

The plugin is locked after entering a key

Check the key format. An InfinaCode licence key looks like INF-XXXX-XXXX-XXXX-XXXX; an Envato purchase code is a UUID, 12345678-1234-1234-1234-123456789012. Visibility Flux detects which is which automatically, so a rejection usually means a typo or a copied licence number rather than the code itself.

"This purchase code is already used on another site"

Envato Regular Licences cover one site. Deactivate on the old site first — Settings → Activation → Deactivate releases it — or buy an additional licence.

"This install reports itself as a staging or local environment"

Your site sets WP_ENVIRONMENT_TYPE to staging, development or local. Activate on the live site, or set it to production in wp-config.php.

Pro features vanished during a licence-server outage

They should not any more. A licence that verified recently keeps working for three days while the licence server cannot be reached, re-checking periodically — so an outage on our side, or a firewall on yours, does not cost you what you paid for. Only a genuine refusal locks immediately. The same applies to Envato purchase codes.

Extend the window if your network is unreliable:

add_filter( 'rm_license_grace', fn() => WEEK_IN_SECONDS );

It unlocked, then locked again hours later

Licence status is cached for six hours and re-checked afterwards. If it locks after that window, the re-check is failing — usually the licence server being unreachable from your host. Open Settings → Activation; the panel re-checks immediately and shows the reason.

"Plugin could not be activated because it triggered a fatal error"

Two copies of Visibility Flux at once. Before 1.7.0, Visibility Flux Pro shipped as a complete second copy of the plugin, so activating it next to the free plugin redeclared every function and stopped PHP dead.

From 1.7.0 Pro is an add-on and the two are designed to run together — there is nothing to deactivate. Update both to 1.7.0 or later and the conflict disappears.

If you are still on an older Pro, deactivate the free plugin before activating it, or update.

The same applies to a stray copy in a renamed folder (for example wp-content/plugins/visibility-flux left behind by a manual install). Keep one copy and delete the other.

AI features

Every AI button does nothing

Check three things in order: is the licence active, is an API key saved, and does your Anthropic account have credit? The editor's top bar shows API OK or No API Key at a glance.

"Model not found"

Your API key doesn't have access to the selected model. Switch to Claude Sonnet 4.6 or Claude Haiku 4.5 in Settings — Fable 5, Opus 5 and Mythos 5 can require higher-tier access.

"AI returned incomplete content"

The generation hit the token ceiling. Raise the Content token limit in Settings → Advanced, or ask for less at once — one section rather than a full rewrite.

Rate limit message

You've used your hourly allowance. Default is 50 actions per user per hour; change it in Settings, or set 0 to remove the cap.

Generated content is in the wrong language

Visibility Flux follows your WordPress locale (Settings → General → Site Language). If that's correct but output is still wrong, check the Market and Register fields in Site memory — a mismatch there can pull the writing elsewhere.

Titles don't sound like us

That's what memory is for. Fill in Site DNA, then keep working normally: approved titles reinforce the pattern and rejected ones are avoided. It improves over weeks, not minutes.

AI Visibility

A bot shows Blocked but robots.txt looks fine

That's exactly the case this feature exists to catch — the block is at your CDN or firewall, before WordPress. If Cloudflare is detected, fix it in the Cloudflare dashboard → AI Crawl Control (or Security → Bots) and allow AI crawlers. No WordPress plugin can change that setting.

"Your robots.txt is a physical file this server won't let the plugin edit"

A real robots.txt file exists and isn't writable. Edit it manually to remove the lines blocking AI crawlers, or make it writable and re-run the fix.

llms.txt won't generate

Either no published content was found to build it from, or another source already serves /llms.txt — a real file or another plugin. Visibility Flux refuses to create a conflicting second version and tells you which case applies.

The noindex fix didn't work

If the noindex comes from your SEO plugin rather than WordPress core, Visibility Flux reports it but won't override another plugin's settings. Fix it in that plugin's homepage or titles settings.

Page builders

Every page is reported as thin content, or no images have alt text

Almost always a page builder, and it used to be a real bug rather than a setting.

Elementor, Divi, Bricks, Oxygen, Beaver Builder, WPBakery, SiteOrigin, Themify, Cornerstone and Brizy store your text in post meta, leaving WordPress's own post_content field empty or nearly so. Any check reading only that field concludes the page has no words and no images.

Visibility Flux reads the builder's stored data instead, so thin content, alt text, internal links, llms.txt descriptions, commerce descriptions and site memory are all correct on builder sites. If you use a builder Visibility Flux does not recognise yet, register it:

add_filter( 'rm_builder_signatures', function ( $sigs ) {
    $sigs['my_builder'] = [ '_my_builder_data' ];
    return $sigs;
} );

The editor warns that the page's text is not in the field it writes to

Visibility Flux can read every supported builder, but writing back depends on where the builder keeps its text.

Elementor, Divi and WPBakery pages are editable. The content tab shows the page block by block, and saving a block writes back to that module, so the change shows on the page straight away. If you still see the warning on one of those, Visibility Flux found no text it recognised in the layout — open the page in the builder once and save it, which rewrites its data.

On other builders body content is still read-only, and the warning is accurate: copy the suggestion into the builder yourself.

If a save says the block changed since the editor loaded it, the page was edited somewhere else in the meantime. Reload the editor and redo that block.

Titles and meta descriptions write normally on every builder, because those live in your SEO plugin rather than in the builder.

AI Traffic

It shows zero visits

Most likely it's simply accurate. AI referral traffic is small on most sites and starts from nothing. Before assuming a bug:

• Confirm the Access Check passes — a blocked crawler can't cite you
• Remember mobile AI apps often strip the referrer, so those visits are invisible to everyone, not just Visibility Flux
• Give it weeks, not days

The numbers seem lower than my analytics suggests

They will be. This counts click-throughs only, and only where a referrer survives. Real exposure is always higher. Use it as a trend, not a total.

General

Does Visibility Flux replace Yoast or Rank Math?

No. It writes into their fields and handles what they don't: Search Console analysis, AI content generation, AI crawler access and AI traffic measurement. Run both.

Does it publish anything automatically?

No. Every suggestion waits for your approval. The only automatic action is notifying search engines via IndexNow when you save — and that can be switched off.

My Search Console export is not in English

It imports anyway. Column headers are matched against known names in many languages first, and when a header is not recognised the importer falls back to Search Console's fixed column order, which is the same in every language. Comma and semicolon delimiters both work, as do Arabic, Persian, Devanagari, Bengali, Thai and full-width numerals.

The file names differ by language too — the Dates file arrives as Dates.csv, Graphique.csv, Datumsangaben.csv and so on. The import screen names each file exactly as your account writes it, so there is nothing to guess at.

The Results tab is empty, or Losing ground says it needs another import

Both compare imports, so both need more than one.

Results additionally needs an import covering a period after the date you fixed a page. Search Console lags a few days and rankings take longer to settle, so a fix made this week will not show a result in an export downloaded this week. See Measuring results.

Will it work on my language?

35 languages including right-to-left. Visibility Flux follows your WordPress locale and imports Search Console exports whatever language the column headers use.

What happens to my data if I uninstall?

Deleting the plugin removes everything: settings, imported data, memory, caches, token logs, AI traffic history and post meta. Deactivating alone keeps it all.

Still stuck?

Email [email protected] with your licence key and site URL — it's the fastest route to a useful answer.