Skip to content
SearchDone

Product overview

One loop, run properly, over and over.

SearchDone is built around a single cycle: understand the site, decide what is worth changing, change it, prove the change landed, and measure whether it worked. Everything else in the product exists to make one of those steps safe.

In build

The first three stages run today. The stages that touch your site are in build, starting with metadata changes — the safest and most reversible thing we can do.

The loop

Eight stages, and the honest position on each.

  1. 01

    Observe

    Crawl and read your own search data

  2. 02

    Understand

    Build a picture of the site and business

  3. 03

    Prioritise

    Rank by value, confidence and risk

  4. 04

    Act

    Make the change on the site

  5. 05

    Verify

    Re-fetch and confirm it actually landed

  6. 06

    Measure

    Watch the metric that was supposed to move

  7. 07

    Learn

    Feed the outcome into the next decision

  8. 08

    Repeat

    Continuously, without being asked

Working todayIn build — see the roadmap

Control

Autonomy is a dial, set per site and per action type.

There is no global on switch, and there never will be. Trust in a system that edits your website is earned one action type at a time, so that is exactly how the control is shaped.

  1. 01

    Watch

    Monitors and reports. Changes nothing, ever.

  2. 02

    Recommend

    Produces findings and recommendations for you to act on yourself.

  3. 03

    Assist

    Prepares the actual change — the diff, the snapshot, the rollback — and waits for you to approve it.

  4. 04

    Autopilot

    Executes low-risk changes on its own and holds everything above that threshold for approval.

  5. 05

    Full Autopilot

    Executes anything your policy permits. Protected pages and hard-excluded paths still apply.

Each level can be set independently for metadata, internal links, content, schema, redirects, images and technical fixes. A site can sit on Autopilot for titles and Watch for everything else — that is the expected starting position, not an edge case.

Safety machinery

What makes a change safe enough to make automatically.

  • Snapshots

    The exact prior state — markup, metadata, structured data — captured before anything is written, so the undo is a restore rather than a guess.

    Planned

  • Reversible ledger

    Every change written as a versioned entry with a before and after, marked reversible or not. A change that cannot be undone cleanly does not run automatically.

    Planned

  • Verification

    After publishing, the page is re-fetched and checked: the change is present, the page still loads, it is still indexable, the canonical is intact, the markup validates. Only then is it marked done.

    Planned

  • Protected pages

    Pages you mark as untouchable, plus checkout, pricing, legal and account paths that are hard-excluded regardless of any policy you set.

    Planned

  • Guardian review

    An independent check on proposed actions for safety, policy compliance and technical validity, able to block another agent outright.

    Planned

  • Audit trail

    Who or what did it, when, why, on what evidence, and what happened as a result.

    Planned

This machinery is the current build. It is deliberately being finished before the product is allowed to make any change more interesting than a page title.

Questions

Common questions.

What can I actually use today?
The analysis engine. Connect nothing and you can see it run on sample data on the home page; join early access and it runs on your own Search Console data. It produces a ranked list of findings with the evidence attached. It does not change your site.
Why start with metadata rather than content?
Because a title or meta description change generates no facts, is byte-for-byte reversible, and exercises the entire approval, publish, verify and rollback path without risking anything. Proving the machinery on the safest payload is the point.
Do I have to give you write access to my site?
Not to use the analysis. Write access is only needed once you want SearchDone to make changes, it is scoped rather than an admin login, and you can revoke it instantly without asking us.
How is this different from a tool that gives me recommendations?
Recommendations are the well-solved part of this industry, and a list nobody has time to action is worth very little. The intended difference is everything after the list — making the change, proving it landed, and measuring whether it worked. That is being built now and is not finished.
Does an AI write my pages?
Not today, and not without a gate when it does. Findings are produced by deterministic code, not a model. When content generation arrives it sits behind a fact gate and a second-model review, and a human approves every publish.

Find out what's holding your site back.

Free during early access. Connect Google Search Console and see your own list in minutes.

Request early accessBook a demo