> ## Content Index > Fetch the complete content index at: https://www.livain.com/llms.txt > Use this file to discover other available public pages before exploring further. # I planned a two-week content sprint. Ten minutes of querying killed it. - URL: https://www.livain.com/blog/ten-minutes-of-querying-killed-the-content-sprint/ - Published: 2026-08-10T07:00:00.000Z - Updated: 2026-08-10T06:59:59.000Z - Description: I was sure the site needed more pages. Ten minutes of querying the live system showed the pages were already there — and the real constraint was one level further back. - Author: Remco Livain - Tags: SEO, Content Strategy, Marketing Tech, AI I had the whole thing planned. Two weeks, one clear goal: build out the location pages on a regional trade directory I run, because the reason it wasn't ranking was obviously that the pages weren't there yet. That was the story in my head, and it had been there for weeks. Search Console showed 87 clicks against 8,180 impressions over roughly seven weeks. Average position 10.2\. Click-through rate barely above one percent. Classic symptom of a site that hasn't been built out, I thought. So: more pages. Before writing the plan I did the thing I now do reflexively, which is ask the live system what it actually contains rather than trusting my memory of it. Ten minutes of querying the site's own API. Every published business, every location, every page that already exists. All 97 locations that qualify for a page already had one. Plus fourteen regional hubs. A hundred and eleven pages, live, indexed, with real local intros, complete schema, six hundred words each. The layer I was about to spend two weeks building had been finished for a while. ### The bottleneck was one level further back What the query also showed is why it *felt* incomplete. The directory holds 832 businesses spread across 298 locations. A location only earns a page once it has at least three businesses on it — that's a deliberate rule, so nobody lands on a page listing one lonely company and bounces. Two hundred and one locations sit under that threshold. Sixty-one of them have exactly two businesses. Which means the constraint was never page generation. It was research. Every additional verified business in one of those sixty-one places creates a new page immediately — one to one, instead of the usual one page per eight or ten businesses. That is a completely different two weeks of work. Same goal, different lever, and the version I'd been about to run would have produced almost nothing. > Confirmation bias is seeing the world through a filter. David McRaney writes that in *You Are Not So Smart*, and the uncomfortable part is how normal it feels from the inside. I wasn't ignoring evidence. I'd just never gone and looked. ### The second thing the data said, which I liked less Position 10.2 isn't a quality problem. Pages that are genuinely thin don't sit at the bottom of page one — they sit nowhere. Ten-point-two means Google has understood the pages perfectly well and finds them interchangeable with the four other results doing the same job. And there was a reason for that. Every single business in the directory sits in the same one or two categories. Every location page targets the same shape of query. Nothing targeted the adjacent ways people actually search, nothing answered cost questions, nothing gave a reason to prefer this page over the incumbent directories that have been there for fifteen years. So the real work is two things at once: widen the data so more places cross the threshold, and give the existing hundred and eleven pages a reason to be picked. Neither of those is "publish more pages", which is the thing almost every content plan defaults to. ### Why I'm careful with this one There's a version of this project that generates a page for every service crossed with every location — roughly 290 pages, a morning's work with the tooling I have. I deliberately didn't. Without more businesses behind them, all 290 would list the same three to seven companies, and Google has been explicit for years about what it does with pages made at scale primarily to rank rather than to help. Its [spam policies](https://developers.google.com/search/docs/essentials/spam-policies?ref=livain.com) name scaled content abuse and doorway pages directly, and the [people-first content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content?ref=livain.com) is the same point stated positively. The tooling makes the wrong move cheap. That's the trap. Anyone can now generate 290 pages before lunch, and the confident output of a good model will make it feel like progress. What decides whether that's leverage or damage is whether someone in the room has done it before and knows which lever is actually load-bearing — which is the whole argument I keep making about [domain expertise being the thing that scales](https://www.livain.com/blog/the-death-of-generic-ai-why-deep-domain-expertise-is-the-only-real-leverage-left/), not the tool. I've been here before with the same site, from the other direction: [an old domain didn't buy me rankings](https://www.livain.com/blog/my-domain-was-20-years-old-it-still-wasnt-enough/), and I've [made a page beautiful before there was traffic to justify it](https://www.livain.com/blog/beautiful-before-the-site-had-traffic/) on purpose. Assumptions about your own project are the ones nobody audits, because you were there when it was built. The habit I'd write down from this week is small and cheap. Before any sprint that starts with "we need more X", spend ten minutes counting the X you already have. Not from the plan, not from memory — from the live system. On a good day it confirms the plan. On this day it saved two weeks and pointed at a lever I'd have walked straight past. The most expensive content is the content that was already there. ### Sources & further reading **External** [Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies?ref=livain.com) — Google Search Central, on scaled content abuse and doorway pages. [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content?ref=livain.com) — Google Search Central. **Related posts** [The death of generic AI: why deep domain expertise is the only real leverage left](https://www.livain.com/blog/the-death-of-generic-ai-why-deep-domain-expertise-is-the-only-real-leverage-left/) [My domain was 20 years old. It still wasn't enough.](https://www.livain.com/blog/my-domain-was-20-years-old-it-still-wasnt-enough/) [I made the page beautiful before the site had traffic. That's the right order.](https://www.livain.com/blog/beautiful-before-the-site-had-traffic/) [Six search impressions told me exactly what to write next](https://www.livain.com/blog/six-search-impressions-told-me-what-to-write/)