Skip to content
SearchDone

Integrations

Two connections in, one connection out.

SearchDone needs your search data to decide what is worth doing, and access to your CMS to do it. Everything else is optional. Deliberately few connections, each one scoped and revocable.

In build

Search Console is the connection currently being built. No CMS integration exists yet, which means SearchDone cannot change anything on any platform today.

Search and analytics data

Where the evidence comes from. Read-only, and the backbone of everything the product decides.

  • Google Search Console

    Impressions, clicks, position and queries. The free first-party signal that drives every finding — and the reason the product can be economical to run.

    In build

  • Google Analytics 4

    Behaviour and conversions, so opportunities can be weighed by business outcome rather than traffic alone.

    Planned

  • Bing Webmaster Tools

    Secondary search data, and increasingly relevant given what Copilot is built on.

    Planned

  • Google Business Profile

    Local visibility, profile completeness and reviews.

    Planned

Content management

Where changes are actually made. Scoped access, snapshotted writes, and a disconnect you control.

  • WordPress

    A dedicated plugin with signed requests, restricted permissions, a full change log and rollback. The first platform SearchDone will write to.

    Planned

  • WooCommerce

    Products, categories and variants on top of the WordPress connection.

    Planned

  • Shopify

    A private app over the Admin API for metadata, structured data and redirects.

    Planned

  • Webflow, Wix, Squarespace, Ghost, headless CMS

    Planned in rough order of demand once the WordPress path has proven the publishing machinery end to end.

    Planned

Developer

For teams that would rather wire it into their own pipeline than use a UI.

  • REST API

    Sites, scores, findings, actions and approvals, programmatically.

    Planned

  • Webhooks

    Notification on action completed, approval required, anomaly detected or integration disconnected.

    Planned

  • Git and deployment pipelines

    For sites where content lives in a repository rather than a CMS, changes proposed as pull requests.

    Planned

How access is handled

The least privilege that does the job.

OAuth and scoped tokens rather than stored passwords. Credentials encrypted before they reach the database and never written to logs. Every connection revocable by you, instantly, without asking us. A CMS connection writes only within paths you have allowed, and checkout, pricing, legal and account pages are excluded no matter what.

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