Revenue at risk
Put a price on what’s slipping.
Pages that lost at least a tenth of their search clicks, with the lost clicks valued at your conversion rate and each product’s own price. The costliest come first.
Try it on your store →
For ecommerce teams with large catalogs
See which products are losing search traffic, and what it’s worth.
Arkivana connects your Google Search Console data to your store’s catalog. Every night it checks your product and category pages, and estimates what the lost clicks were worth from your own prices.
The nightly check
See what changed without going looking.
Five checks run every night over your pages and list what they find on one screen: sections that stopped earning, templates losing clicks at the same rank, filtered pages multiplying.
Compare with Search Console →Your catalog
Read search by product, SKU and category.
Connect your store, read-only, and each page maps to the products and categories behind it, the way your merchandising team already thinks.
Supported platforms →Reads your catalog from
- Shopify
- Adobe Commerce
- WooCommerce
- BigCommerce
Read-only, read nightly. Nothing in your store is changed.
The problem
Search Console wasn’t built for a 30,000-SKU catalog.
It shows sixteen months, rolls up no search traffic by product or category, and exports a thousand rows at a time. So the analysis gets done manually, once a quarter, by whoever has the afternoon.
- the most Search Console shows Google Search Console
- 16 months
- the most Search Console exports from a table Google Search Console
- 1,000 rows
- reports that roll up search traffic by product or category Google Search Console
- 0
The archive
Search Console’s window moves. The archive stays.
Arkivana starts with the sixteen months Google still has, and keeps every day from then on. Year-over-year comparisons reach as far back as your archive does.
The day you connect
+0 months beyond Search Console
One year on
+12 months beyond Search Console
Two years on
+24 months beyond Search Console
Only in
Arkivana Also in
Search Console (sixteen months) Today
Every night
Another day, shelved.
Each night Arkivana reads the newest day Google has, adds it to your archive, and runs the checks over it.
-
Search Console shows from
-
Arkivana keeps from
-
Checks run every night
-
Months Arkivana drops
Each opens in a new tab with a question about Arkivana. If it asks you to sign in first, copy the question and paste it in.
Day one
Sixteen months, read back.
On the day you connect, Arkivana reads everything Google still serves.
Every night
New days, added and checked.
Each day’s figures are kept, and the checks run over them.
From then on
Nothing ages out.
A site connected today will still have today’s figures in 2029.
What we access, and why.
You sign in to Arkivana with your Google account, and that same permission grants read-only access to your Search Console data. One consent screen, not two — we’d rather not make you approve the same product twice.
We request:
-
openid,email,profile— to identify you and create your account. We never see or store a password. -
webmasters.readonly— read-only access to Search Console.
Arkivana uses the Search Console permission to:
- Read the list of Search Console properties you have access to, so you can choose which ones to connect
- Read search performance data for the properties you choose — clicks, impressions, click-through rate, and average position, broken down by query, page, country, device, search type, search appearance, date and hour
- Read the indexing status of pages on your site — up to 1,000 a day, and any address you inspect — and the sitemaps you have submitted, for the indexing reports that show the pages that have dropped out of Google’s index and why
Arkivana cannot make any changes to your Search Console account. We cannot submit sitemaps, request indexing, remove URLs, or modify your properties in any way. The access is read-only by design, and we request no scopes beyond those listed above.
Your Google refresh token is encrypted at rest and never leaves our systems.
We use this data solely to generate the reports, dashboards, and alerts you see inside Arkivana. We do not sell it, we do not share it with other customers, and we do not use it to train machine learning models.
You can disconnect Arkivana at any time from your Google Account permissions page, which immediately revokes our access.
Two people, building in the open.
Arkivana is built by Paul Rice and Joe Meador. We built the first version of this for a working eCommerce catalog with tens of thousands of SKUs, because the tools we wanted didn’t exist. We’re turning it into a product.
Questions? Email support@arkivana.com.
Get early access.
We’re onboarding a small number of eCommerce teams before public launch. If you run a large catalog and Search Console isn’t telling you what you need, we’d like to talk.
Invitations go out in batches. No spam, and we won’t share your address.