I launched RefreshQueue — a Monday decaying-page queue from Google Search Console
Every Monday I wanted a ranked list of the URLs that actually lost the most Google clicks — not a percent drop, not an Ahrefs estimate, not a dashboard I'd forget to open.
SEO agencies already export Search Console. The weekly ritual is still: spreadsheet, gut-sort, Slack a writer a paragraph. The pages that quietly leaked a few hundred clicks don't get a ticket.
RefreshQueue connects read-only GSC. Each Monday it emails the URLs that lost the most clicks, tags the failure mode (CTR-only / collapsed / held), and includes a half-page refresh brief a writer can start from. We never publish to the live site.
https://refreshqueue.com — $49/mo one property, $278/mo ten.
Would love feedback from anyone who assigns weekly refresh work.
Congrats on shipping. Disclosure: I do landing page critique, so take this as a peer note rather than a customer one — and it is not an answer to your actual question, since I do not assign weekly refresh work myself.
You mentioned above that nobody is paying yet. I think your first screen is part of that, and the fix is small.
The rendered Northline Mechanical email is the best thing on your site. It has a real from-address, eight rows whose losses add up exactly to the 1,398 clicks in the subject line, and a brief that tells the writer what not to do. I checked that arithmetic — it holds, and that kind of concreteness is rare. It also sits several screens below the fold.
Meanwhile the hero gives four buttons in one row, all the same size, and the only filled one is Subscribe. So the loudest thing on your first screen asks for $49 from someone who has not yet seen the product. "See the Monday email" is fourth in the row and outlined like the other two, which makes the cheap step look like the least important one.
Two changes, both an afternoon:
One smaller thing while you are in there: your nav Subscribe button renders its label in a grey that is very close to the tan fill behind it. Measured, it is about 1.4:1 against its own background, where the plain nav links next to it are about 6.7:1 — it is the hardest text on the page to read, and it is your most committed button. Your hero Subscribe button already gets this right with a near-black label on the same tan, so it is a one-line change.
The writing on the rest of the page is genuinely good. "WHAT YOU DO NOT BUY" naming Ahrefs and SEOTesting directly, and refusing a fake signup counter, buys you more trust than a testimonial would. I would not touch any of that.
Thanks this is really useful. You're right that the Northline email is the proof and it's buried, and that Subscribe is doing too much work as the only filled CTA before anyone sees the product. I'll make "See the Monday email" the primary and fix the nav contrast. Appreciate the concrete layout notes on the hero crop too.
The “ranked list + refresh brief” feels more valuable than another SEO dashboard.
Curious whether buyers are mainly paying to find the pages faster, or because it removes the manual step of turning that finding into a writer-ready task.
Mostly the second. Finding the pages is the easy half — Search Console already has that data. What people are paying for is that Monday morning they get a ranked list where each URL already has a failure mode tagged and a half-page brief a writer can start from, so nobody has to sit and turn a CSV into a task. Happy to have you try it on a real property: https://refreshqueue.com/app
That distinction makes sense. If the real value is turning Search Console data into a prioritized, writer-ready queue, the workflow itself becomes the product rather than the reporting.
Curious what you’re seeing so far: are users actually acting on the briefs, or are you still validating that part?
Still validating that part. I have a real property connected and the queue+brief generates, but nobody's paying yet so I don't have writers in the wild acting on these briefs. That's the next proof. If you want to try it on a property: https://refreshqueue.com/app
That makes sense. I’ll be interested to see what happens once real writers are actually using the briefs.
Disclosure, I build an SEO tool, so take this as a peer note rather than a customer one.
The failure mode tagging is the right idea, and I think there is a fourth worth splitting out: cannibalisation. The clicks did not disappear, they moved to another URL on your own property for the same query. That page does not need a refresh brief, it needs a consolidation decision, and sending a writer at it is actively the wrong action.
It matters commercially because it is the case most likely to waste a customer's money early, which is when they are deciding whether to trust the output at all.
You can detect it from data you already pull. If URL A lost clicks on query Q and URL B on the same property gained them in the same window, that is a redistribution, not decay.
Does the current tagging separate a real loss from a move?
Fair point, and no — right now the tagging is CTR-only / collapsed / held, so a redistribution to another URL on the same property shows up as a loss when it isn't one. That's exactly the case where the brief is the wrong action. The detection you describe is doable with the query+page data I already pull, so I'm adding a cannibalisation/moved tag that routes to a consolidation decision instead of a writer. Thanks for spelling out why it matters commercially early on.
Good, and one thing worth building into that tag while you are in there: a redistribution is not automatically benign.
If the clicks moved from a page that converted to one that does not, that is a real problem, just not a content refresh problem. So the consolidation decision needs to know which of the two URLs was the better commercial page, not only which one Google now prefers.
Otherwise the natural default is to consolidate toward whichever page is currently winning, which is Google's preference rather than the client's, and you would be helpfully cementing the wrong page.
You probably cannot see conversions from GSC alone, but flagging the direction of the move and letting the human pick the survivor would be enough.