What works, what is switched off, and what is planned

SimplyReport is in closed beta and a fair amount of it is not built. This page is where that is written down, so the rest of the site can describe the product rather than the gaps in it.

There are no dates on this page. Nobody has committed to one, and a date is a claim like any other.

Shipped and working

Four tools are part of this website. You can settle every claim about them by running one.

• AI crawler access

  Reads a domain's robots.txt under RFC 9309, evaluates every AI crawler and control token against it, probes the retrieval crawlers live, and generates the fix. It also checks whether a link to the site pastes with a preview card.

  Check a domain →

• JavaScript rendering check

  One fetch, no headless browser: what text is in a response nobody executed the JavaScript of, as any of the published user-agents. Two agents can be run against each other to see where a site answers them differently.

  Fetch a URL →

• AI traffic blind spot

  The GA4 custom channel group for AI assistant traffic currently landing in Direct, plus a plain account of what Google's own AI Assistants channel does not cover.

  Get the configuration →

• Content Credentials viewer

  Reads C2PA provenance out of an image in your own browser. Nothing is uploaded.

  Open a file →

In the app

The app is a separate codebase from this site, so these are read out of its source rather than demonstrated here. Each is a claim the homepage already makes.

• GA4 and Search Console as the two data sources

  The report is built from Google Analytics 4 and Google Search Console. There is no third connector.

• Analysis written against the previous period

  The period is compared against the previous one of equal length, and the commentary is written about what moved — queries that climbed, dropped, appeared or vanished. One comparison, not a reading of the client's whole history.

• The report as a link, with no account for the client

  A report is generated when you ask for one and shared as a URL the client opens in a browser. Every report carries our name in the footer.

  See the sample report →

• Analysis prompts authored per language

  The English and Serbian prompts are written separately rather than run through a translator.

Built but not running

The narrow case: the code is written and it is not in service. Two things qualify. This is a stronger statement than the list below it, because it says the work is done — so nothing goes here that has not been built.

• AI visibility snapshot

  A free tool that reads a domain, generates brand-agnostic buyer prompts and runs them across two engines with web search on. It is refused at the route boundary rather than accepting addresses it would never process: no provider keys are set, its migration is unapplied, and its worker is on no schedule. The page says so instead of pretending to a queue.

  What the page says instead →

• PDF export

  A downloadable PDF of the client report. The code is written and has never been run against a real report.

Planned, with no date

Not started, or started and not finished. None of it is in the product today and none of it is priced.

• AI search tracking

  Tracking brand mentions in ChatGPT and Perplexity against the queries a client already ranks for in Search Console. This is the thing being built and it is not measuring anything yet. Every check is a live query against a paid API, so it will be metered per check rather than included in a plan, and there is no price for it yet.

• Scheduled delivery

  Reports generating and emailing themselves on a cadence you set. Today a report is generated when you ask for one and shared as a link.

• Data refresh tiers

  Daily and weekly refresh as a plan difference. Today every read goes to GA4 and Search Console when you open the report.

• Team seats

  More than one person on an account.

• White-label client portal

  A client-facing area under your own branding and domain, rather than a link on ours.

• Tiered branding

  Your logo on the client-facing report, and the "Powered by SimplyReport" line removed on paid plans.

• Choosing a report language per client

  The prompts exist in both languages; picking which one a client's report uses is not wired up, and every report generates in English today.

• Plans, billing and enforced limits

  There is no plan column in any migration, no billing integration, no per-plan limit constant and no quota counter — the app has no plans in it at all. The prices on the homepage are the plan design; nothing is billable and no limit is enforced against anyone today.

  The plans as designed →

The AI search half, in detail

It is the thing this product is being built around, so it gets more than a line. Nothing in SimplyReport queries ChatGPT or Perplexity today and no brand mention has been counted. The panel below is here because it is the layout that work will report into.

What is real right now is that Google put AI data into both connectors this product already reads — Search Console breaks out generative AI performance, GA4 has a native AI Assistants channel — and each arrives with a limit worth knowing. Reading those two into the report is the first piece of work.

On top of them we are building tracking around the queries your clients actually rank for in Search Console, seeded from the SEO work you are already reporting on rather than from a list you have to write and maintain. When it runs it will be sampled, and reported as a directional signal rather than a precise score.

It will not be included in a plan. Every check is a live query against a paid API, so it will be metered per check. There is no price for it yet.

Other tools track AI search today. If you need it now, you should buy one of them.