Tools

The toolkit that reads your own search data properly

Seven instruments, one dataset. Each one answers a specific question about your property and states the method it used, so a number can be defended in a review rather than taken on faith.

Data Health scoring

Know whether the numbers can be trusted before you act on them

Data Health is a per-property score that grades the completeness, freshness and internal consistency of the Search Console data behind every chart. It checks coverage of the reporting window, the gap between the latest stored date and today, duplicate or conflicting rows, and whether property totals reconcile with the visible query detail.

Method. Each check contributes a weighted component to a 0 to 100 score. A property below the threshold is flagged in the interface with the specific failing check named, never a vague warning.

See it in Features

Questions it answers

  • Is this property missing days, and which days exactly?
  • Is the latest import stale enough to invalidate a comparison?
  • Do the visible query rows add up to the property total, or is sampling hiding traffic?

Smart Import system

Drop an export, get a versioned dataset with no duplicates

Smart Import accepts a Google Search Console export as a zip or a CSV, detects whether it is a Search performance export or a Generative AI export, parses it, and writes it into the store with a version record. Re-uploading an overlapping date range updates rows instead of duplicating them.

Method. Every import writes an ImportVersion row with counts, status and the detected export type, and the parser keys rows on date, query, page, country and device so an overlap resolves to an update.

See the import flow

Questions it answers

  • Which upload introduced this row, and when?
  • Can I re-import a corrected export without doubling my data?
  • Did the Generative AI export land in the right table?

Branded versus Generic analysis

Separate the traffic you own from the traffic you win

A property-wide toggle splits every metric into branded and generic segments using your brand terms and ownership rules. Branded queries usually carry a high CTR and a stable position, so blending them into one total hides what is actually happening in the competitive half of your account.

Method. Brand terms and keyword ownership rules are stored per property and applied consistently to every chart, table and export, so the split is identical everywhere it appears.

See the enterprise use case

Questions it answers

  • How much of this quarter came from brand terms?
  • Is a click decline a brand problem or a generic problem?
  • Which branded terms gained impressions while losing clicks?

Content Decay detection

Find pages losing clicks while their position holds

Content Decay compares a page against its own prior period and flags a sustained click decline that is not explained by a position drop. That pattern is the signature of an answer box absorbing the visit, a snippet loss, or intent drifting away from the page.

Method. A page must decline across two consecutive comparison windows before it is flagged, which keeps a single volatile week out of the alert list. Each alert states the click loss and the window it was measured over.

See it in Features

Questions it answers

  • Which pages lost clicks without losing rank?
  • How much traffic is at risk across the property?
  • Which declines are two consecutive periods rather than one noisy week?

Cannibalization detection

Name the pages competing for one query, then pick a winner

Cannibalization detection finds queries where two or more of your own URLs alternate for the same impressions, then ranks the competing pages by clicks and position. An AI verdict recommends which page to keep and which to consolidate, grounded in the stored rows rather than a guess.

Method. Competing URLs are grouped per query with a minimum impression floor, and the recommendation cites the click and position evidence it used. A guided fix stepper walks through the consolidation.

See it in Features

Questions it answers

  • Which of my pages are splitting one query between them?
  • Which URL should survive the consolidation?
  • Is the split getting worse over time?

Daily Rankings grid

Every keyword, every day, with honest gaps

The Daily Rankings grid lays out per-keyword position by day for the selected window, built from your Search Console data. Days Google reported nothing for a query are shown as gaps rather than interpolated, so a flat line never hides missing data.

Method. Positions are impression-weighted averages from Google, displayed per day with the reporting delay respected. Annotations and official Google update dates render as markers on the same axis.

See it in Features

Questions it answers

  • When exactly did this keyword move?
  • Which keywords are trending in the same direction?
  • Did a change coincide with a Google update or an annotation?

AI Executive Insights

A brief that only states what the data supports

AI Executive Insights reads the stored rows for the selected window and writes a plain summary of what changed, why it likely changed, and what to do next. It is grounded in the retrieved numbers, and when the data does not support a conclusion it says so instead of inventing one.

Method. Retrieval runs against your own property rows, the model is instructed to cite only retrieved figures, and the brief exports to Markdown or PDF for a review deck.

See it in Features

Questions it answers

  • What changed this month that leadership needs to know?
  • Which movers matter and which are noise?
  • What should the team do next, in priority order?

Run these against your own property

Request access and we will connect your Search Console properties, keep the history, and turn the toolkit loose on data you already own.