ALXEO, the part that does the workCore engine
Other tools find the problem and leave. ALXEO fixes it.
ALXEO is the engine behind the four pillars: Readable, Found, Chosen, Protected. It finds what slips, explains it, and on WordPress applies the fix you approve, then checks the live page.
STAGE 1 OF 6
Detect
Real findings, with proof.
ALXEO scans each pillar: your pages (Readable), Google Search Console (Found), AI answers (Chosen), and every scan against the last (Protected). A finding exists only if evidence supports it.
What is recorded
- Affected pages and exact current values
- Source, method and measurement time
- Severity and a plain explanation
STAGE 2 OF 6
Assess
Impact, confidence and risk.
Each finding is ranked. Risk comes from fixed rules for each action type, never from a model’s opinion.
What is recorded
- Risk class: Low, Medium, High or Critical
- Whether the fix is reversible
- Whether approval is required
STAGE 3 OF 6
Approve
You decide how much to hand over.
On WordPress: recommend only, approve each action, or allow Autopilot for the low-risk action types you switch on. On other platforms ALXEO recommends and you apply the fix.
What is recorded
- Who approved, and when
- Exactly which version was approved
- Any change to the plan needs a new approval
STAGE 4 OF 6
Execute
Saved first. Changed once.
On WordPress, original values are stored before anything changes and a retried job can never apply the same change twice. On other platforms ALXEO does not change your site: the report gives the exact steps for you or your developer.
What is recorded
- Original and applied values
- Execution attempt and timestamp
- A rollback path where the action supports one
STAGE 5 OF 6
Verify
Check the live result.
ALXEO re-fetches the pages and compares them with what you approved. An API success is not proof. For fixes you make yourself, a re-scan confirms each one or shows what is left.
What is recorded
- Each check and its outcome
- Verified, partially verified or failed
- Failures stay visible, never hidden
STAGE 6 OF 6
Monitor
Stay protected.
The result joins your history. Each scheduled scan is compared with the last, and a drastic change is flagged. Search results move for many reasons, so we show timing, not causation.
What is recorded
- Dated activity history
- Before and after, side by side
- Nothing in the history can be quietly rewritten
Try it
Watch one fix, start to finish.
- 1DetectDuplicate page titles found on 12 pagesEvidence: crawl #3 · 3 groups · 2 Nov 2026
- 2AssessMedium risk · evidence strong · reversibleImpact is an estimate, not a promise
- 3ActAwaiting your approvalOriginal titles saved before any change
- 4VerifyRe-fetching the live pagesEach page checked against what you approved
- 5TrackResult recordedAdded to your activity history
Sample Plumbing Co. | PlumberBoiler Repair in Leeds | Sample Plumbing Co.Safety model
Worried about a tool changing your site? It asks first.
A model may help explain a finding. It can never grant itself permission to change your site.
| Risk | Typical changes | Handling |
|---|---|---|
| Low | Reversible metadata corrections | May run on Autopilot, only for action types you switch on |
| Medium | Page titles, structured data, multi-page edits | Your approval required |
| High | Redirects, canonicals, indexing directives | Explicit approval and safeguards, every time |
| Critical | Site-wide or destructive changes | Never executed autonomously |
Three modes
Hands-on or hands-off. You choose.
Recommend
ALXEO finds and explains opportunities. It never modifies your website.
Approval Required
ALXEO prepares each action and waits for you to approve it individually.
Autopilot
ALXEO executes only the low-risk action types you have switched on, within your policy. Medium risk and above still need you.