I built a Chrome extension that fixes GSC's two most annoying limitations — looking for early feedback
I'm an indie developer and I spent a lot of time in SEO communities. One complaint kept coming up again and again:
Google Search Console has a 48-hour data delay — you can't see what's happening with your traffic right now
GSC only keeps 16 months of data — if you don't export manually, it's gone forever
I couldn't find a tool that solved both problems cleanly, so I built one.
SEO Data Archiver is a Chrome extension that:
Pulls intraday "Fresh Data" from the official GSC API every hour
Automatically syncs it to your own Google Sheet
Runs 100% locally — your data never touches a third-party server
One-time payment, no subscription
It took me a few weeks to get through Google's OAuth verification and Chrome Web Store review, and it just went live.
I have zero users right now. I'm sharing this here because I want honest feedback from people who actually care about SEO data — does this solve a real pain point for you? Is $29 (launch price) the right number? What would make you trust a tool like this enough to try it?
Chrome Store: https://chromewebstore.google.com/detail/jafnmmnidbecklolnjlkakhppjmoolfn
Website: https://www.gscsaver.com
This solves a genuinely real problem. The 16 month data limit has caught out more SEO professionals than Google probably realises — you never think about it until you need to compare against a period that has quietly dropped off, and by then it is too late.
The intraday fresh data angle is the stronger hook of the two in my opinion. The data delay in GSC is a daily frustration for anyone running active campaigns or monitoring a site through a volatile period. Knowing what is happening in closer to real time without leaving GSC's data environment is genuinely useful.
A few honest observations:
The "runs 100% locally, your data never touches a third party server" line is doing a lot of work and deserves to be much more prominent. That is the trust signal that separates this from every other GSC companion tool. SEO data is commercially sensitive and a lot of potential users will hesitate precisely because they do not want their query and ranking data sitting on someone else's server. Lead with that.
On pricing: $29 one time for a tool that preserves data indefinitely and pulls hourly updates is underpriced if it works reliably. The hesitation at that price point will not be "is this too expensive" — it will be "will this still work in six months or will the GSC API change and break it." Addressing your update and maintenance commitment directly on the landing page would reduce that friction significantly.
Would genuinely consider this for client reporting work. Good build.
One thing I'd be careful with:
The interesting question may not be whether the limitations are real.
It's whether people are actually paying to solve the same problem you're building around.
Those sound similar, but they can lead to very different buyers, positioning, and pricing decisions.
I wouldn't make that call casually from early feedback alone.
That's a really sharp point and honestly the question I'm wrestling with right now. The limitations are real (I hear about them constantly in SEO communities), but "annoying" and "worth $29 to fix" are two very different bars.
My current thinking: the people most likely to pay are SEO freelancers and small agencies managing multiple client properties they feel the 16-month data loss acutely because clients ask "what was our traffic like in Q1 2024?" and the answer is "GSC already deleted that." For them $29 one-time is a rounding error compared to looking unprepared.
But you're right that I shouldn't conflate "this is annoying" with "this is a buying trigger." I'm watching closely whether early users are individuals scratching their own itch or pros solving a business problem that distinction will shape everything from pricing to messaging.
Appreciate the push to think harder about this. Have you seen similar willingness-to-pay gaps in SEO tools you've evaluated?
Possibly.
The reason I stopped short earlier is that I don't think the interesting part is whether willingness-to-pay gaps exist.
I think there's a bigger decision sitting underneath the assumptions you're making about buyers, triggers, and what the early signals actually mean.
I'd be careful answering that casually in a thread.
If you're curious, drop your email and I'll put together the tighter version.