v0.0.18: Alert History & the Acceptable-Use Guard
Keep every alert a scan produced, decide domain suitability at signup, and track position history per engine.
Alerts with a history
Server-Side Alert History
Every finding a scan derives now becomes a durable record you can page back through, not just a notification at the moment of the scan. The Alerts page reads that history: each occurrence stays attached to the scan that produced it, read state is per member (mark it read and it stays read for you, not for the whole workspace), and nothing is lost when you leave the page and come back.
Background Work Is Actionable
Activity, domains, prompts, content gaps, recommendations and reports each gained an action surface: a stuck job can be retried from where it failed, a monitoring loop shows what it is doing while it runs, and a gap you have acted on stays visibly acted on.
Trust & safety
Acceptable-Use Domain Screening
New projects are screened against known adult, gambling and drug lists before they can be tracked, with a hard block on adult content and a soft flag on the other categories. The blocklists refresh nightly. A screened-out domain can appeal the decision; an operator resolution is recorded and honoured.
Deeper ranking history
Per-Engine Position History
The Rankings page gained a per-engine position timeline, stat-card deltas against the previous scan, and query search with drill-down, so a movement in your aggregate position can be traced to which engine moved and which query moved it.
Schema tools grow up
Editable Facts, Site-Level @graph, Auto-Detection
The schema generator can now edit facts in place, emit a site-level @graph, auto-detect the entity type, score completeness and cover LocalBusiness and Event: a validator that checks structure rather than only well-formedness.
Search Console insights become actions
Next Steps on the Search-to-AI Gap
The Search ↔ AI gap analysis on the Search page now offers a next step when Google ranks a page or query that engines do not cite, instead of a bare finding.
The dashboard overhaul
Empty States, Errors and Confirmations
Empty and error states say what happened. Plan limits surface where they stop you. Destructive actions ask for confirmation before they run.
Want to shape what we build next?
See what we're building next, and tell us what you need.