Build1 distinct publisher3 min readUpdated
A solo operator was a day from redirecting his best-performing URLs. The export he had never run showed a scheduling queue and zero external links, not a spam problem.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
The two buckets in that report are different verbs, and the summary count hides it. "Crawled, currently not indexed" is a decision Google reached after spending a request on the page [11]. "Discovered, currently not indexed" means the URL is known and no request has been spent on it yet [12]. The timezone family is in the first case and Google is finished with it: essentially all 1,432 fetched, 428 kept, 647 thrown out, almost nothing left queued [8]. The 2,290 recipes are in the second, all of them [13]. One is a rating. The other is a place in a line.
That distinction is what turns the cleanup plan into damage. Of the 638 indexed URLs the author actually exported, 428 are timezone pairs, so the collapse-and-redirect would have retired 67 percent of everything Google currently shows for the domain [17]. The recipes, which are about 39 percent of the site by page count [22], would still be unfetched the next morning, because nothing in the timezone directory was holding them back. The Links report reads external links: 0 [14].
The arithmetic deserves one caution the author raises himself. Keep 428 and reject 647 and you have accounted for 1,075 of 1,432 pages; 357 are missing from the tally [20]. He notes that the indexed column is a complete list while the crawled and discovered columns come from drilldowns that cap out near a thousand example URLs [16]. So the 30 percent acceptance rate is a census divided by a family size, which holds, but the 647 rejections underneath it are a sample floor, not a count. The gap is either sampling loss or pages that were never crawled at all, and those imply different next moves.
The reading hazard in his method is worth more attention than the script. His first pass at the crawled-not-indexed drilldown returned 660 rows, of which 638 were the indexed list still sitting in the reused DOM [10]. That is 97 percent contamination [21], and it fails in the most expensive direction: it renders as "Google crawled my generated pages and rejected almost all of them," which is exactly the theory he walked in with [5]. A quick eyeball of that table confirms the wrong diagnosis and ships the redirect.
What the four minutes of exporting bought was not a verdict on content. It was the ability to tell a quality rejection apart from a queue position, and only one of those two responds to editing pages [15]. The two generated families hold 502 of the 638 indexed URLs and the site's two best acceptance rates [7], which leaves 136 indexed pages across the tools, hubs and cooking guides [19] and none at all from the recipes [9]. On the evidence, the handwritten work has not been judged yet. It cannot be, until something outside the domain points at it.
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
The author runs a solo calculators-and-tools site, five months old, with about 5,800 pages across four language sections.
The remainder sit in two buckets: 1,153 "crawled, currently not indexed" and 4,161 "discovered, currently not indexed".
The site includes 1,432 programmatically generated timezone pages, one calculation with different arguments spread across a URL space, e.g. /date-time/time-difference/london-and-buenos-aires.
The author assumed the generated timezone pages matched what Google's spam policy calls scaled content abuse and was dragging the host down, and planned to collapse them into one hub page and 301 the rest away.
The indexed-page list was exported from Search Console via Indexing then Pages then "View data about indexed pages", with rows-per-page set to 500; the examples table caps around 1,000 URLs, so an indexed count below that yields the complete list. The author pulled 638 unique URLs from an indexed count of 642.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
One self-reported console read, no external check
All figures come from a single first-person dev.to post about the author's own site. The counts are specific and internally cross-checked in places (638 unique URLs from a reported 642; a set intersection catching stale rows), and the author volunteers that two of his three columns are samples. But nothing is independently verified, no Google documentation is cited for the interpretive rule the piece rests on, and the post's own timezone arithmetic leaves 357 of 1,432 URLs unaccounted for.
Single property, single operator
The only adoption evidence is one solo five-month-old site: its coverage buckets, one generated family's 30 percent acceptance rate, and an open dataset release. No other site, team or tool is reported to have run the same diagnostic, and no follow-up outcome from the link-building remedy is shown.
Case study framed as a general rule
The reported specifics are modest and mostly hold up, but the framing generalises a single unverified property into a rule about what the two not-indexed buckets mean and into a causal 'nobody links to this domain' diagnosis. The headline contrast between 428 generated pages indexed and 2,290 handwritten ones never fetched is accurate as stated yet invites a conclusion the sampled buckets and missing traffic data cannot carry, so claims run somewhat ahead of evidence.
Self-published operator promoting own site and dataset
The post is written by the site's owner on a personal dev.to account and closes by linking his own domain and an open dataset he publishes, so there is a visible promotional interest in the property being discussed. Offsetting that, the piece is self-critical about a plan the author nearly shipped and discloses methodology limits, and no vendor, sponsor or paid relationship appears anywhere in the cluster.
Procedure trustworthy, conclusions provisional
Confidence is moderate-low overall. The mechanical parts of the story, the export path, the row cap, the stale-DOM trap and the exported index composition, are specific, checkable and easy for a reader to reproduce. The interpretive core, that discovered-not-indexed is a host-level scheduling signal fixable by acquiring links, is single-source, undocumented and unmeasured after the fact, and one internal arithmetic residual is unexplained.
build
A 5x publishing increase cost one site 1,000 indexed pages and every impression1 distinct publisher
build
8,664 indexed pages, nine clicks: programmatic SEO now fails at ranking, not indexing1 distinct publisher
build
Before you spend quota on an agent skill, make it pass an eval harness1 distinct publisher
build
Geofencing beats GPS polling on power, then loses to the OEM battery optimiser1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
1 article · August 23, 2026