Skip to content

Changelog

Everything we shipped, newest first. Product updates land here before they reach the newsletter.

  1. SearchReporting

    AI Overview tracking

    Queries that trigger an AI Overview now carry a badge in the opportunity radar, and the click through rate chart splits into two lines so you can see what the overview costs you on that query.

    • A new Overview presence column on every query table, refreshed daily.
    • Click through rate is compared against your own historical rate for the same position, not against a generic industry curve.
    • Alerts fire when an overview appears on a query where you hold a top five position, since that is where the loss is largest.

    Available on Pro and above. Nothing to enable, the data starts filling in on the next crawl.

  2. ContentWorkflow

    Refresh queue and decay scoring

    Decay alerts used to be a list. They are now a queue with an opinion.

    • Every decaying page is scored on lost clicks, current position and topic value, then ranked.
    • Each entry states which of the three decay patterns it matches, so you know whether it needs a title rewrite, a content update or a merge.
    • One click turns a queue entry into an assigned brief, keeping the original query context attached.
    • Weekly digest emails now lead with the queue instead of raw metric deltas.

    Teams running the queue for a month reported spending roughly a quarter of their content time on maintenance, which is what we were aiming for.

  3. KeywordsAnalysis

    Cluster graph and cannibalization view

    Clustering moved from connected components to community detection, which removes the giant blob that large keyword sets used to produce.

    • A visual cluster graph, filterable by volume, difficulty and current coverage.
    • A cannibalization view listing every pair of your own pages competing for the same results, ranked by how much traffic the overlap is costing.
    • Clusters can be merged and split by hand, and manual decisions survive the next rebuild.
    • Cluster maps can be exported as CSV or fetched from the API.

    Rebuilds run weekly, and immediately after a confirmed core update.

  4. Integrations

    Notion and Slack sync

    Briefs no longer need to be copied by hand into the place your team actually writes.

    • Push any brief to Notion as a page, with the entity checklist as a database and the sources as linked blocks. Edits made in Notion flow back into the brief status.
    • Slack notifications for crawl incidents, decay alerts and brief assignments, routed per project so a channel only receives what it owns.
    • A daily digest option that collapses everything into a single message at the hour you choose.

    Both integrations are configured per project in workspace settings and can be disconnected at any time.