I published 263 articles in ten days. Here's what Search Console showed afterwards.
What happened after a large publishing sprint on Crit Pick, with the sample limits, reporting windows and unresolved explanations made clear.
Between 30 July and 8 August I published 263 pages on Crit Pick. The later 28-day snapshot showed weaker property-level search figures than an earlier broad average. See Indie performed differently in the same window. Comparing clicks per published page across two different sites is descriptive, not a test showing that fewer pages cause better results.
That's the headline, and the honest thing to say next is that I can't fully explain it. What follows is the whole file: what I published, what the numbers did, the two times I read my own data wrong before I caught it, the confounder I can't subtract, the one thing the data does support — and a cost that none of the metrics show at all.
Data through · Google Search Console, both properties · Crit Pick is an SEO case study I run in the open for SeeIndie. Every page named here is live and every number is one you can check.
- 263 pages in ten days, and 97% of them were one thing. 256 were Palworld pages, 254 of those a generated creature database. This wasn't a writing sprint. It was a database published as a blog.
- Every metric went the wrong way. Clicks 16/month to 4, impressions 2,553 to 2,020, click-through 0.6% to 0.2%, average position 18.6 to 32.3, while the stock went from 90 pages to 393.
- I got it wrong twice. First I called it a downward trend when my window happened to end at the bottom. Then I nearly dated the start of the fall using a two-week average that still contained 217 of the sprint's own pages.
- I can't separate my sprint from Google's. The August 2026 spam update started on 18 August. The first ten places of the fall were already measured before it. The rest overlaps it.
- Competition is one hypothesis. The sampled pages performed differently across topics. The comparison does not isolate competition from page type, age, links, publishing volume or other changes.
- The most-repeated explanation for all of it isn't in Google's documentation. I went and read the documentation.
- And the real bill arrived somewhere I wasn't looking: 288 of my page titles are pinned to a numbering system the developer has already changed once, without telling anyone.
What I actually published
The sprint ran 30 July to 8 August 2026. Ten days, 263 pages. I've said "two weeks" about this before and that was loose: across a full fourteen-day window it's 283, and the tight ten-day count is 263. Both numbers come out of Ghost's admin API and out of my own publishing log, and the two agree.
The shape matters more than the total. The biggest day was 8 August with 104 pages. The second was 4 August with 54. And 256 of the 263 carried one tag: Palworld. 254 of those were Paldex entries, one page per creature, generated from a data set and published in batches.
So this was never "I wrote a lot". It was a database that happened to be shaped like a blog. My rule was, and still is, that every creature gets its own page, because that's how people search: one creature at a time. What I was testing without quite admitting it was whether a two-month-old domain could publish a complete reference for a game and have Google treat it as one.
Before the sprint the site had 90 published pages. By 6 September it had 393.
What Search Console showed
Both of my sites over the same 28 days, 10 August to 6 September.
| Metric | Crit Pick | SeeIndie |
|---|---|---|
| Published articles | 393 | 34 |
| Clicks | 4 | 29 |
| Impressions | 2,020 | 3,070 |
| Click-through | 0.2% | 0.9% |
| Average position | 32.3 | 24.0 |
| Pages with impressions | 215 | 33 |
| Referring domains | 1 | 11 |
| Clicks per article | 0.010 | 0.853 |
Same person, same platform, both started in June 2026. The site with a twelfth of the stock takes seven times the clicks.
Crit Pick didn't only underperform the other site, it underperformed itself. Across three months, 7 June to 6 September, it averaged 16 clicks and 2,553 impressions a month at position 18.6. In the last 28 days of that same stretch: 4 clicks, 2,020 impressions, position 32.3. The stock more than quadrupled and all four numbers fell.
That's where I stopped the first time, and that's where I made my first mistake.
Where I nearly published something false
The comparison above sets a three-month average against a 28-day window. On the strength of it I wrote "the site is in decline". Then I pulled the daily series, blocked it into fortnights, and the shape changed.
| Period | Clicks | Impressions | Avg. position |
|---|---|---|---|
| 7–20 Jun | 5 | 397 | 16.6 |
| 21 Jun – 4 Jul | 14 | 1,328 | 11.0 |
| 5–18 Jul | 14 | 1,459 | 11.6 |
| 19 Jul – 1 Aug | 11 | 1,988 | 17.9 |
| 2–15 Aug | 1 | 915 | 27.3 |
| 16–29 Aug | 0 | 1,017 | 36.5 |
| 30 Aug – 6 Sep | 3 | 558 | 29.4 |
The 28-day aggregate includes both the weaker stretch and the final eight days, obscuring their different patterns. I should inspect the daily series before describing it as a decline or recovery.
Eight days and three clicks is a small observation, not a recovery result. A follow-up needs equal reporting windows and page-level data; it will be published when there is something useful to show.
The second thing I got wrong, which I caught before publishing this
Having found the collapse, I wanted to date it. Google confirmed an August 2026 spam update starting 18 August, running 2 days and 16 hours. If the fall demonstrably started before the 18th, I could rule the update out.
So I wrote: the first drop lands in the block from 2 to 15 August, which is after my sprint and before the update. Clean.
It isn't clean, and the reason is instructive. That block still contains 217 of the sprint's 263 pages. The 2nd to the 8th of August is the sprint. A fortnightly average that spans an event can't tell you what happened after the event — and I'd just built a smaller copy of the exact window-selection error I'd caught myself in one section earlier.
Here's what survives once I cut what I can't support. The block ending 15 August ends three days before the update began, and by then the average position had already gone from 17.9 to 27.3. So whatever cost the first ten places, it wasn't the August spam update. The second stretch, 27.3 down to 36.5, overlaps the update and I can't assign it. Nor am I claiming causation from two properties, one time period and single-digit clicks: a Google update, seasonality in gaming, or something technical at my end are all still live options.
What the data does support: the field, not the volume
Strip out everything I can't defend and one finding is left, and it's the useful one.
I published into three clusters with the same method in the same window. Where they sit now, from Ubersuggest on 9 September:
| Cluster | Page | Keywords it ranks for | Best position |
|---|---|---|---|
| RimWorld | rimworld-animals | 8 | 16 |
| Guild Wars 2 | gw2-find-your-race | 12 | 27 |
| Guild Wars 2 | gw2-mesmer | 4 | 32 |
| Palworld | jetragon | 1 | 55 |
| Palworld | celaray | 1 | 59 |
| Palworld | mimog | 1 | 61 |
| Palworld | broncherry-aqua | 1 | 66 |
In the four Palworld pages visible in the tool's top-pages sample, the best reported position was 55 and each had one detected term. That selected sample cannot describe all 254 pages.
The Guild Wars 2 page makes the same point without changing the page at all. On "which race should you play", the long-tail terms — 30 searches a month, difficulty in the low twenties — sit at 27th. The head terms on that same page, "guild wars 2 races" at 1,900 a month, sit at 59th and 60th. One page, one crawl, two very different fields.
There's a second piece of evidence for this that has nothing to do with Search Console, and I like it better because it comes from a different tool on a different day. When I run a content tool over one of these database terms, the competing results it finds are stores, databases and news items — no prose at all. That's the field. Paldex terms belong to established game wikis with years of links behind them. A three-month-old domain with one referring domain doesn't take that ground by turning up 254 times.
Two limits on it, honestly. Four Palworld pages out of 254 is a sample, and not a random one: those four are the only Palworld pages that appear in Ubersuggest's top-pages list for the domain at all, so I checked the most visible ones and they're still on page six. And the tool's coverage is thin at this size — it finds 74 ranking keywords for the whole 393-page site. Strong hint, not proof.
What Google actually says about "Discovered – currently not indexed"
If you read one section, this one.
Crit Pick's index report shows 51 pages under "Discovered – currently not indexed", plus five under "Crawled – currently not indexed" where validation has failed. Every SEO write-up I've seen reads a number like that the same way, and so did my own first draft of this post: Google knows about these URLs, Google has decided they aren't worth having, this is what a site gets for publishing at scale without the authority to back it.
I went to source that claim in Google's documentation, and it isn't there.
Google's definition of the status is: "The page was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl." That's about serving capacity. It says nothing about quality and nothing about authority. The wording is in the Search Console page indexing report documentation.
The crawl budget documentation doesn't rescue the folklore either. Google defines crawl budget as "the set of URLs that Google can and wants to crawl", and says the allocation factors in "things like popularity, overall user value, content uniqueness, and serving capacity". Popularity and uniqueness are in there. The words "quality" and "authority" are not.
I'm not telling you the folklore is wrong. I'm telling you it isn't documented, that I repeated it before I checked, and that those are different things. I can report the state of my index report. I can't tell you what Google meant by it.
Two more things belong beside that number before anyone quotes it, me included. Of the 124 pages Google isn't indexing, 18 are plain 404s and five are blocked by my own robots.txt — my mess, unrelated to publishing speed, still not cleaned up. And the report covers 492 URLs against 393 published articles, so roughly 99 of them are presumably tag, author and pagination URLs that Ghost generates on its own. Until I've separated those out, "51 pages" isn't purely a content number.
While I was in the documentation I read the spam policy on scaled content abuse too, since that's the other thing people reach for here. Google's definition: "many pages are generated for the primary purpose of manipulating search rankings and not helping users ... large amounts of unoriginal content that provides little to no value to users, no matter how it's created." The hinge is purpose, not quantity. I have no manual action and nothing pointing at that policy, so I'm naming it as a hypothesis I checked and set aside, not as a finding.
The bill that no metric showed me
Here's the part I didn't expect to be writing, and it's the one I'd act on first.
Palworld's 1.0 release renumbered its entire creature index. That change appeared in no line of the official patch notes — it took five independent sources before the finding was solid enough to trust.
My database pages carry those numbers in their titles. "Astralym — Palworld Paldeck No. 204". I counted this week: 288 live pages on the site have a Paldeck number in the title.
That's the real cost of publishing a database as a blog, and it's invisible in every number further up this page. Search Console will never tell you that your titles have gone stale. It has no opinion about it at all.
The question I haven't answered
There's a hole in everything above and I'd rather point at it than have you find it.
The property average could change because older pages moved, because the mix of pages and queries changed, or both. I have not established that every new page was indexed or ranked below a particular position.
The clue I have points the wrong way for me, and I can't use it cleanly. RimWorld animals, the best page on the site, had 992 impressions and 16 clicks in the eight-week cumulative view through 29 July. In the 28 days to 6 September: 203 impressions, zero clicks. Dilution doesn't take clicks off a page that already had them. But one of those is a cumulative view and the other a 28-day window, which is precisely the comparison I spent two sections warning you about, so it's filed as suggestive and nothing more.
Settling this needs daily data for the same pages and queries across matching periods. That analysis remains a separate step; this article does not contain a completed follow-up.
What I'm doing instead
Three things, and none of them is "write more articles".
A better position could lead to more clicks, but these data do not support a traffic forecast.
Review useful links and references alongside the pages themselves. One referring-domain count compared with another site cannot identify a ranking bottleneck or prove that backlinks explain the difference.
Moving a database to a subdomain is a separate site change, not a result demonstrated by this snapshot. It needs its own baseline, migration checks and comparable follow-up data; this article does not assume that moving it improves search performance.
The honest verdict
Ten days, 263 pages, and the sharpest thing I can hand you is a caveat: the site got worse on every metric, the trend I first reported was an artefact of how I sliced the data, and half the decline sits on top of a Google update I can't subtract.
The four Palworld pages visible in the keyword tool's top-pages sample each had one detected ranking term; their best reported position was 55. That does not describe all 254 pages. Competition is a plausible explanation for the contrast with the RimWorld guide, but this comparison does not establish the cause.
Four clicks a month isn't a disaster. It's a data point about a three-month-old domain, which is exactly the age at which everyone else quietly stops publishing their numbers.
What's next
The next useful update would compare the same pages over equal periods, separate newly visible URLs from older ones, and record any site changes. I am not promising dated updates before those measurements are complete.
Common questions
Did publishing 263 pages get the site penalised?
I have no manual action recorded in this snapshot. That does not rule out algorithmic effects. Publishing and weaker aggregate figures coincided, but this comparison does not isolate the cause.
So was it the spam update or the publishing?
Does "Discovered – currently not indexed" mean Google thinks my pages are low quality?
Should I stop publishing a lot?
This comparison cannot establish an ideal publishing volume. Before expanding a database, check the reader need, competing pages and the work required to keep each entry accurate. The four sampled Palworld pages cannot represent every page in the batch.
Can I check any of this?
Follow the experiment
The next set of Crit Pick numbers, and whatever I am currently testing. No fluff, no pitch.