The AI Editor

The AI Editor

Visibility Flux → Editor is where the work happens. The sidebar lists your posts, pages and products sorted worst-CTR-first; selecting one loads its Search Console metrics and opens five tabs.

Nothing you generate is saved or published until you click through to apply it.

The sidebar

Filter by post type (posts, pages, products) and page size, then click Load Articles. Each row shows the item's estimated lost clicks per month, so the worst offenders sit at the top. There's a search box for finding a specific article, and a Batch button for running tasks across many at once.

The article header

Once an article is selected you get its live URL, quick links to the WordPress editor and the front-end page, and a Search Console strip: impressions, clicks, CTR, position, and the estimated monthly clicks lost.

The top bar tracks token spend — total across all articles, for the current article, and for the last action you ran.

When a change is recorded

Applying a suggestion stamps the article: the date, what changed, and the CTR, position and clicks it had at that moment. On the Problem Map that row then reads Fixed with the date instead of Fix →, so a list you are working through visibly shrinks.

The stored before-numbers are what the Results tab compares against your next Search Console import. You do not have to do anything to opt in — editing a page is the trigger.

If your content lives in a page builder

Visibility Flux reads text from Elementor, Divi, Bricks, Oxygen, Beaver Builder, WPBakery and others, so suggestions are based on what your page really says rather than on an empty content field.

Titles and meta descriptions save normally on every builder — they live in your SEO plugin, not in the builder.

For body content on a builder page, the editor shows the page's text block by block. Each block is one module, and saving it writes straight back to that module, so the change appears on the page immediately.

On builders that are still read-only, the editor says so instead of saving into a field your site never renders, and you copy the suggestion across yourself.

Tab 1 — SEO Title & Meta

Click Improve Title & Meta with AI. Visibility Flux writes both against the page's real ranking queries from your Search Console import, not from a generic keyword guess.

You get:

• The suggested title and meta description
• A live Google SERP preview showing how it will actually look
• An estimated CTR and projected extra clicks per month
• Character counters (60 for titles, 160 for descriptions)

Use This Suggestion loads it into the fields. Save SEO Fields writes it to your SEO plugin. Try Again regenerates; Reset restores what was loaded.

Whatever you keep or change teaches the site memory — approved wording gets reinforced, rejected wording gets avoided.

Tab 2 — Article Content

A generate bar with five actions:

Plus Fix Grammar & Spelling — a two-pass proofread that corrects the text without touching your HTML structure, and reports how many changes it made.

Also on this tab:

• Thin content warning — flagged under roughly 300 words, or when headings and paragraphs are too sparse
• Quality score — a 0–100 rating with a breakdown
• JSON-LD schema — generated from the article's actual content and format

Heading hygiene

Visibility Flux strips the AI-slop headings ("Introduction", "Conclusion", "In this article") in every supported language, normalises heading levels, and removes a duplicate H1 that repeats the post title.

Tab 3 — Internal Links

Visibility Flux builds a keyword index of your published content and scores every candidate link by real keyword overlap with the current article.

You get a handful of strong matches rather than twenty weak ones, and the AI distributes them naturally through the body instead of dumping a list at the end. You choose which suggestions to accept.

Tune the behaviour with the rm_internal_links_limit and rm_internal_links_min_score filters — see Developers.

Tab 4 — Competitors

Run Competitor Research sends Claude to search for the pages currently ranking for this article's title and queries, then reports:

• Content gaps — what those pages leave unanswered
• Differentiation angles — how to make yours stand out
• Strengths — what competitors already cover well, so you don't waste effort
• Any specific competitor URLs you added manually

The findings are cached for 30 days and — this is the useful part — injected automatically into every later content generation for that article. Run research once, then use FAQ, Intro, Sections or Full Rewrite and the output is gap-aware without you copying anything.

Research runs via Claude's web search when your API plan supports it, and falls back to a reasoning-only analysis when it does not. The panel tells you which method was used.

Tab 5 — Submit to Google

Pushes the page straight to Google's Indexing API for re-crawling instead of waiting.

This one needs setup: a free Google Cloud service account with the Indexing API enabled, added as an Owner in Search Console. Full steps are in Settings.

Bing, Yandex, Naver and Seznam are already notified automatically via IndexNow with no setup at all — only Google requires this.

If WPML is active, Visibility Flux detects the translations and offers to submit every language version, using one quota unit each.

Batch processing

The Batch button in the sidebar runs tasks across all loaded articles:

• SEO — titles and meta descriptions
• Analyze — content format detection
• Research — competitor gap research
• Score — quality scoring

Jobs run sequentially in the browser with a progress bar, so there is no cron dependency and no server timeout. Keep the tab open while it works; you can pause and resume.

Each item is claimed on the server before it is handed to the browser, so the same article cannot be processed twice — not by a dropped request, and not by a second tab. An item whose browser never comes back is released after ten minutes rather than blocking the queue.

Failures are reported, not hidden. If an article's AI call fails — a rate limit, an expired key, a timeout — it is counted and named at the end instead of being marked done. A run that says complete means complete.