The questions people ask

No. There is no tag, no plugin and no script, and nothing crawls your pages. The only things we ever request from your server are robots.txt and your sitemap files, and only for the page-coverage report. Everything else comes from the data Google already collected. If your site is in Search Console, setup is choosing it from a list.

Straight from the Google Search Console API for the properties you connect: daily clicks, impressions, CTR and average position, your full query list, per-page performance and your sitemaps. Nothing is estimated, scraped or bought from a third party. It is your own data, rearranged.

Search Console reports; it does not explain. It gives you one total for the whole site, a thousand rows at a time, for the last sixteen months. We split that into the groups you think in, compare every period against the one before it, tell you what moved without being asked, and keep 24 months of it, about eight months past the point where Google has deleted it.

That is who it is built for. We write out what a word means where it is used (impressions, average position, cannibalization) instead of assuming. If a feature needs a paragraph of explanation to be useful, we treat that as our bug, not your gap.

We sync every day, on the free plan as well as the paid one. Search Console itself runs two to three days behind reality. That is Google's pipeline, not ours, and nobody can beat it, so the interface always states the exact date your data is complete to rather than implying it is live.

Yes, as many people as you like, at no extra cost. Roles are viewer, editor and owner, so a client can be given a read-only login that shows every report and changes nothing.

Then that is step one, and it is Google's rather than ours. Add the site in Search Console, verify it, and give Google a few days to start collecting. Come back and it will be in the list. We can only read what Google has already recorded, so before that there is nothing for us to show you.

For a technical team it is a genuinely good option and we will not pretend otherwise. It has one flaw you cannot fix later: it only records forward from the day you switch it on and never backfills, so the ~16 months sitting in your Search Console right now are lost to it while it "accumulates". It also needs a Google Cloud project with billing enabled, and it gives you raw tables: the SQL and the dashboards are still yours to write.

They are your own Search Console data, unmodified. We do not model, estimate or smooth anything. Where our arithmetic could differ from yours we say so on the screen: which window a figure covers, whether it is complete or a sample, and which source it came from. More than 2,400 automated checks compare what the interface displays against the database, specifically to catch the class of bug where a correct number is shown under the wrong label.

They should match, and where they do not there is usually a nameable reason. The first is Google's own: the site total comes from Google's complete daily figures, while the query list is every query Google names, and Google holds back rare searches, so the list adds up to less than the total. The query screen prints how much less for your site, and the post on why query totals come up short explains the gap. The other reasons: a different date range (ours end on the last complete day, Search Console may include partial ones), a different property (the domain and https:// versions of a site hold different data), or Search Console's own row cap hiding part of a total from you rather than from us. If you find a difference you cannot explain, send it to us. That is a bug report we take seriously.

Almost none of it. We have no script on your site, so we see no visitors, no pages and no personal data about anyone browsing you. We read the aggregate search statistics Google has already recorded. The single exception is your sitemap file: when you use page coverage we fetch that one document from your server, the way any search engine would, to compare what you have listed against what Google actually showed.

No, and not as a promise. It is a technical fact. We ask Google for the read-only Search Console permission, which is the only thing we are given. There is no version of us that can edit a property, submit a sitemap or touch your site. You can withdraw the access from your Google account at any time.

Your projects, history, groupings and settings are deleted, and so are the Google tokens we stored. There is a button for it in account settings, so you do not have to email anyone or wait. We also ask Google to revoke the access those tokens gave Clode, unless the same Google account still connects sites in another Clode account or we cannot confirm that it does not; you can always remove Clode yourself on your Google account's permissions page. Minimal security logs are kept for a short period, as described in the privacy policy.

Yes, at any time and on any plan, including free. Any table on screen exports to CSV or Excel with the layout you are looking at, subtotals included. We do not currently offer a programmatic API; if you need one, tell us what you would do with it.

It is stored in a shared database with per-account isolation enforced on every query, which is how essentially all SaaS works. It is never pooled into a benchmark, an industry average or a dataset shown to anyone else, and it is never sold. If you need physical isolation for a compliance requirement, ask us.

Yes. The free plan is one site with 14 days of daily history, and it is not a trial: there is no card and no countdown. Paying adds more sites and a much longer history; the free site itself never expires.

Three things, and this is the whole list. You can connect more than one site instead of one. Your history goes back a rolling 24 months, about eight months past the point where Google's own ~16-month window has already deleted it, instead of being trimmed to the last 14 days. And you can save as many Analytics pages as you need instead of 1. Everything else is the same on both plans: the daily sync, CSV and Excel downloads, teammates with their own sign-in, and every screen on your whole site, never sampled or cut to a top list.

Per site, with the rate falling as you add more, and the rate applies to every site on the account rather than only the new ones. If a larger band would work out cheaper than your own, you are charged the cheaper one. From 22 sites up the total stops rising at €129 a month, whatever you add.

The price is calculated from your site count and billed once, to the account. That is a change from how we used to do it: it means an agency with twenty sites has one bill with a ceiling on it, rather than twenty line items.

We retry for 5 days and change nothing about your service in the meantime. The person we are trying to bill is the last one to punish for an expired card. Only after that does the account drop to the free plan, and even then your archive is kept for 3 months so you can resume or export it.

Not immediately, and not silently. If you cancel, the paid plan runs to the end of the period you paid for. If a payment fails, we email you and keep everything running for 5 days while we retry. Either way the account then moves to the free plan and keeps working, and everything already stored is held for 3 months, during which you can pick up exactly where you left off or export the lot to CSV. Only after those 3 months is history beyond the free window deleted. A crypto period works differently: it simply ends on its date. We email you 7 days and again 1 day before; if it is not renewed, the account moves to the free plan that day and history older than 14 days is deleted, so renew or export before then.

Yes. Pay for ten months and get twelve. You can switch a card subscription between monthly and yearly billing at any time, on the Plan & billing page in your account menu. The switch happens the same day: moving to yearly charges the year, less the unused part of the current month, and moving to monthly turns the unused part of the year into credit for the months ahead. With crypto, you choose a month or a year each time you pay.

Only when you buy a paid plan. The free plan has no card and no countdown. A card subscription is charged the day you subscribe and then again every month or every year until you cancel. Adding a site to a subscription charges the difference for the rest of the current period straight away, and you see that amount before you confirm. A crypto payment is made once and covers a fixed period; nothing is charged after it. Either way the price is the one on this page, VAT included, and nothing is ever billed retroactively.