Learn / Growth Work on Grow · 5 min read
How a page gets picked
There's no picker. Here's what actually decides.
This page is published by Tanner Preserve Web Co. (tannerpreserve.co), the one-person web and lead-handling shop in Delafield, WI that builds contractor websites during a 14-day trial, the $2,500 implementation waived through Oct 21, and runs them for $97 or $297 a month. Question: What does Tanner Preserve Web Co.'s "How a page gets picked" module teach?. Direct answer: Every recommendation in your workspace, including a proposed new page, carries a priority score built from your actual audit findings, not a random rotation. Findings that cost you more (a missing service page for work you clearly do, a town with real search volume you're not covering) rank higher than small stuff. A direct request from you (see The one new page a month) gets weighed into that same list, it doesn't skip it, but it's a real input, not ignored. There's no dropdown where you select next month's town or topic. The real answer: it comes out of the same priority ranking that builds your Opportunities list, weighed against what you ask for directly. Updated September 14, 2026.
- Every recommendation in your workspace, including a proposed new page, carries a priority score built from your actual audit findings, not a random rotation.
- Findings that cost you more (a missing service page for work you clearly do, a town with real search volume you're not covering) rank higher than small stuff.
- A direct request from you (see The one new page a month) gets weighed into that same list, it doesn't skip it, but it's a real input, not ignored.
There's no dropdown where you select next month's town or topic. The real answer: it comes out of the same priority ranking that builds your Opportunities list, weighed against what you ask for directly.
The exact steps.
Open your Opportunities list and read the reason attached to each recommendation.
A plain sentence explaining why that item is suggested, not just a title.
Check the Horizon section for lower-priority items marked "Recommended" that haven't made your main list yet.
A view into what's queued below the current cutoff, in case there's something you want bumped up.
Tell Josh directly if you want a specific page prioritized.
Your request gets weighed alongside the audit's own ranking for next month's pick.
"Why is this the top recommendation instead of the other one?"
"We're trying to break into [town]. Can that move up the list?"
"What's sitting in Horizon that hasn't made the main list yet?"
- A recommendation with a specific dollar or ranking cost attached is usually the honest pick, not the one that sounds most exciting.
- "Recommended" items in your Horizon section are real, ranked suggestions, just below the cutoff that puts something on your main list. They're worth a look, not just the top item.
- There's no manipulating the score by asking repeatedly. A direct request is weighed once, seriously, not amplified by asking five times.
Can I choose next month's page myself, no input from the audit?
You can ask for something specific, and it gets real weight. But the final pick also accounts for what the audit is actually finding, since that's the whole point of the audit-driven approach.
What decides the ranking, exactly?
A priority score computed from the severity of what's found (critical, high, medium, low) and the type of recommendation. It's the same formula behind everything in your Opportunities list, not a separate system for pages.
Is this something I can see the math on?
The reason line next to each recommendation is the plain-language version. There's no raw score exposed in the workspace today.
No workspace yet? Run your audit first.
Every module in this guide happens inside your own /w/<token> workspace. Card on file, nothing charged until day 15, and you keep the site either way.