
Step by step.
- Read the score line first. Every marker on it is a piece of content shipped or improved, on the date it went live.
- Open a page under Pages we are improving. Its dossier says why the page is on the list, the numbers behind that, and the exact changes with where each one goes.
- Give each change an owner, edit the copy if you want it in your words, and mark it done with the live address once it is up. The same for each fix under Fixes in progress.
- Download the task list (CSV) when the work goes to someone outside the portal: every change and fix with its owner and status, ready for a sheet or a task tool.
What happens next. Mark a page done with its live address and the next measurement reads it against that date. Nothing here changes an engine directly; the work on the page does.
The battle map is this month. Continuous Improvement is every month, on one line, with a marker for every piece of work that shipped. It is the tab to open when someone asks whether this is working, because it shows the score, the work, and the dates together and lets you read what came first.
Under the line is the work itself. Each page we are improving has a dossier: why it is on the list with the numbers, where the AI engines cite it, the exact changes with their placement, and the same numbers after it ships. Each wrong fact from the accuracy audit is a fix with a place: this page, this sentence; this profile, this field. Every one of them has an owner and a status, set by you, your agency or us, and kept across the monthly runs.
The runway underneath is the honest size of the job: pages improved, pages queued, pages protected because they already perform, and pages nobody has touched yet.
What the screen is telling you.
- Pages we are improving is re-selected every month: your money pages, pages the AI engines cite, pages closest to a question you do not hold yet, queries within striking distance of page one, sliding traffic, split queries, and anything you pin. Pinned pages come first.
- Fixes in progress is every wrong claim from the accuracy audit turned into an exact change in an exact place: a sentence on a page, a field on your Google Business Profile, a listing. We place copy on your own site and profiles only, never on a site someone else owns.
- What moved shows pages that shipped and were measured again: the numbers at ship and the same numbers in the months after, side by side. Trend, never proof of cause; seasonality and other changes move them too.
- The runway: improved, queued to improve, protected, and pages in your library. Protected pages already perform and are deliberately left alone.
- On The Map, your team or your agency does the work and records it here. On Done for you, we do it and you see the same list. The list is the same on both; the plans differ only in who does it.
People ask.
- Why is the record empty?
- It starts with the next measurement cycle after your first shipped piece of content. Mark it shipped on its row in the Work list, or done on its dossier, and the marker appears on the line after the next run.
- What is a protected page?
- A page that already ranks or already earns an answer. It is marked so nobody rewrites it in the name of improvement. If you want one changed anyway, pin it and set a target, or say so on its card.
- Does the score go down if I do nothing?
- It can. Engines change their answers on their own and competitors publish. The line shows drift as honestly as it shows gains, which is the point of measuring every month.
- Who sees the owners and statuses I set?
- Everyone on the account: your team, your agency if you have one, and Eidomai. A read-only view link sees none of this tab.