Reflow
Find out whether the page changed the answer.
A published page is a hypothesis. Two weeks after it goes live, Ondit asks the same questions again and attributes the before-and-after to that page — with significance floors, so a lucky week is reported as no conclusion rather than as a win.
What it does
The stage a tracker does not have.
Scheduled at publish
The reflow job is queued the moment a page goes live — fourteen days out, on the page's own clock, not a nightly sweep's.
Before and after, per page
The same questions, the same engines, the same replications. The delta in citation share is attributed to the page that went live between the two runs.
Self-tuning, with a cap
When a page did not move the answer, Ondit can rewrite its opening answer block once a month — and no more often, because a page rewritten weekly is a page that never gets measured.
How it is built
What comes out
A reflow report: share before, share after, significance, and the page it is attributed to.
What happens next
Back to detection, with one more page in the world and one more data point on whether pages work.
- The same floors as analysisFive usable samples a side, twenty percentage points. Under that, the report says "no conclusion" — in both languages, from the same rule.
- Attribution is honest about noiseTwo pages published in the same fortnight share the credit, and the report says so, rather than crediting whichever was queued first.
- The report is a page tooEvery reflow writes a report the panel shows and the directory can publish, with the numbers, the rule and the date.
- Then the loop starts againA gap that closed drops off the list. A gap that did not is still a gap, now with one attempt behind it.