Search Console performance

Built, not yet live

The storage, the sign-in with Google, the property selection and the import are all written. A real Google account was connected on 10 September 2026 and its properties listed. No import has run, so no figure has been imported.

What it will do

Google already publishes what your site gets in search, free, to whoever owns it. ShownTrue will connect to that record, import the history, keep it current, and hold it beside the crawl so a page and its results sit in one place.

Estimated search volume bought from a third-party index will not appear anywhere in this. The figures will be the ones Google reports about your own site, which is a smaller set of numbers and a true one.

The screen today

Search Console performance: the /performance screen in the ShownTrue app
The /performance screen on 14 October 2026, from a demo workspace labelled as test data. Nothing has been imported into it, so this is what a new account sees first.

What exists today

  • The storage, built and tested. A day of query and page figures is kept a month at a time, each month created as it is needed and carrying its own access rules.
  • A fix for a real permissions defect in that code, where the two lines meant to strip a new month of its default permissions sat below a return and never ran.
  • The Google side, at around 3,400 lines across eighteen files: the sign-in, choosing which property to import, the history import and the incremental one, and the daily rollups.

What is missing

  • No import has run. One Google account has been connected and its properties listed, but no figure has been imported, so the tables are still empty.
  • No daily update. The import runs when it is asked to and there is no schedule behind it.

Measured against the code in this repository. When the code moves, this page moves with it, because both read the same list.