Measuring results
Prove a fix worked. Visibility Flux stamps every page you edit, then compares its CTR and position against the next Search Console import.
Measuring results
Most SEO work is unfalsifiable. You rewrite a title, traffic moves, and nobody can say whether the rewrite caused it. Visibility Flux closes that loop: it records when you fixed a page and what its numbers were at that moment, then compares them against the next export you import.
How it works
1. The Fix button remembers
When you apply an AI suggestion — a title, a meta description, a content change — Visibility Flux writes a stamp to that page: the date, what you changed, and the CTR, position, clicks and impressions the page had at the time.
Back on the Problem Map, that row no longer says Fix →. It shows Fixed with the date, so a list you are working through visibly shrinks. You can still reopen the page; the stamp only records history.
2. The next import does the comparison
Search Console data lags by two to three days, and ranking changes take longer than that to settle. So the comparison waits for you.
The next time you import an export that covers a period after the fix date, Visibility Flux pairs the stored before-numbers with the new after-numbers and writes the result to the Results tab.
Give it time. A fix made yesterday will not show a meaningful result in an export downloaded today. Four weeks is a reasonable first look; eight is better.
3. The Results tab
Problem Map → Results lists every page you have fixed, with before and after side by side:
| Column | Meaning |
|---|---|
| Page | The URL, linked to the editor |
| Fixed | When you applied the change, and what kind of change it was |
| CTR | Before → after, with the change |
| Position | Before → after (a lower number is better) |
| Clicks | Before → after |
Improvements are green, regressions red. A regression is useful information, not a failure — it tells you to put the old title back.
Below the table, site totals import by import show whether your overall clicks, impressions, CTR and average position are moving, independent of any single page.
Why the Dates file matters here
Search Console's export includes an optional file holding the date range the export
covers. Its name follows your Search Console interface language, so it may arrive as
Dates.csv, Graphique.csv, Datumsangaben.csv and so on — the import screen names the
file exactly as your account writes it.
Import it alongside Pages and Queries. Without it, Visibility Flux has to assume two imports cover the same number of days, and they usually do not — a 28-day export compared against a three-month one looks like a traffic collapse that never happened.
With it, comparisons are normalised and honest.
Losing ground
Problem Map → Losing ground is the other half of measurement: pages sliding down between your two most recent imports, before they turn into a crisis.
It lists pages whose position or clicks have fallen, worst decline first. These are usually cheaper to rescue than a page that has already bottomed out — the content is still ranking, it is just being overtaken.
This tab needs two imports to exist. After your first, it will tell you so rather than showing an empty table.
A realistic cadence
- Import your Search Console export
- Work the Problem Map — Low CTR first, it is the cheapest volume
- Wait four weeks
- Import again and open Results
- Keep what worked; revert what did not
Visibility Flux keeps the last several imports, so the trend survives well beyond a single before-and-after.
What is stored
Everything stays in your WordPress database — fix stamps in post meta, import snapshots in options. Nothing about your performance is sent anywhere. Deleting the plugin removes all of it; see Troubleshooting.