Search Console BigQuery export cost calculator

How the estimate is computed

For storage, the calculator takes the GiB of new rows the export appends per day and your retention window in days. Partitions younger than 90 days bill at the active logical rate and older ones at the long-term logical rate, in the location you pick. The first 10 GiB of logical storage is free per month, per billing account. The calculator counts this 10 GiB once per month, as the free usage tier table of the pricing page lists it, and applies it to active storage first and then to long-term storage. The estimate assumes that each daily partition is written once and not changed after that. Google states that Search Console can revise the saved data of a past day, but that this does not happen often. A changed partition bills at the active rate for the next 90 days.

For queries, the calculator multiplies the GiB scanned per query by the number of queries per month, rounds each query up to the nearest MB, applies a 10 MB minimum per query, converts to TiB, and charges the on-demand rate of 6.25 dollars per TiB with the first 1 TiB per month free per billing account. Google also bills at least 10 MB for each table that a query references; the calculator counts one table per query, so for a query that reads both export tables, enter at least 0.0195 GiB, which the calculator rounds up to 20 MB. The page uses 1 GiB = 2^30 bytes and 1 TiB = 1,024 GiB, as the pricing page defines them, and counts 1 MB as 1/1,024 GiB. Both rates are Google's published US and EU multi-region prices, fetched 2026-10-29, and may change; the pricing page linked below is the source of record. Physical storage billing has other prices, and this page covers logical billing only.

Setup check list from Google's rules

• Search Console charges nothing for the export. BigQuery bills the storage and the queries.
• The Cloud project must have a valid billing configuration, otherwise the write will fail.
• Tables and partitions are retained forever by default, unless your Cloud project or organization sets a default. To limit storage, set a partition expiration. Make sure the expiration is 14 days or longer.
• Do not set an expiration time on the table. A table expiration deletes the entire table.
• Do not change the table schema. Google states that schema changes will cause the export to fail.

Run this query to see the logical bytes of your own dataset by storage tier. Replace PROJECT_ID with your project ID. searchconsole is the default dataset name; replace it if you chose another name. A partition moves from ACTIVE to LONG_TERM after 90 days without a change.

SELECT storage_tier, SUM(total_logical_bytes) AS logical_bytes
FROM `PROJECT_ID.searchconsole.INFORMATION_SCHEMA.PARTITIONS`
GROUP BY storage_tier;

Google's efficiency post names several ways to control the bill. Among them: set a partition expiration so that old date partitions are deleted automatically; pre-aggregate each daily drop into one or more summary tables and point dashboards at those instead of the raw tables; and restrict the bytes billed per query, so that a query whose estimated bytes are over the limit fails without incurring a charge. The post also says to avoid SELECT *, to limit the date range with a WHERE clause on the date-partitioned tables, and to add known filters early, for example WHERE query != '' to drop anonymized query rows. The pricing page states that on-demand queries are charged for the data processed in the columns you select.