A report tells you what broke. This fixes it.
A page falls out of the index, a score collapses, a site goes down — and you find out weeks later, from a client. Morax Analytics is built to audit your sites several times a day and to do something no report does: turn each finding into a correction, hand it to the build engine, and let the site repair itself.
The audit loop runs on Etienne's own sites today. Nothing of it is wired into this hub.
What this product does
It watches, several times a day
Availability, indexing, speed, the things that quietly rot: the audit is meant to run often enough that a broken page is a matter of hours, not of the next time someone happens to look.
The finding becomes a correction
This is the whole point, and it is the part nobody else does. The audit doesn't produce a document for you to act on: it writes the correction prompt and sends it to the build engine, which does the work.
The fix lands while you shoot
The intended state is a search score at 100 and a speed score above 90, held there — not reached once. A page flagged as broken should be corrected on its own, and you should read about it afterwards.
In detail
Why there's no example dashboard here
A preview, even labelled as made up, reads like a promise: you remember the shape of the curves and end up deciding on them. As long as no number is true, this page shows none. No example chart, no counter, no metric named as if it were already tracked.
The loop, in order
Audit, then a correction written from what the audit found, then a build, then a check. Each pass is meant to leave the site in a state the next audit will confirm.
Presence is counted, not yet improved
How often the name is cited around the web is worth watching, and the audit is meant to count it. Turning that count into something better is a separate tool, and it doesn't exist.
Nothing of it is in this hub
No product in the ecosystem sends this hub a usage event, and no store exists to receive one. What runs, runs elsewhere.
One organisation, one scope
The day this becomes a product, the isolation key exists from the first write. An aggregate that mixes two organisations is worse than no aggregate.
Who it is for
- A page drops out of the index
- The audit is meant to catch it and send the correction off, so the page comes back without anyone opening a console.
- A site that got slower without anyone noticing
- Speed is checked on a rhythm rather than on suspicion, and a drop becomes work handed to the engine.
- A site that went down on a Saturday
- Frequent checks mean the alert comes from the audit and not from the client who tried to book.
- Being cited across the web
- The count should tell you where the name appears. Acting on it stays manual, and this page says so rather than implying otherwise.
A page without numbers
It stays that way until there is a site of yours being audited and a fix of yours being shipped. The day that happens, what shows up here will be true, and only then.