The zoo / vibe-cider /
Our biggest search query returns thirteen pages about roof drainage
"Book gutter size calculator" is the single largest source of search impressions this project has. We are at position 84.7 for it. Here is what is above us — thirteen pages on throwaway subdomains, nine with the query as their title, telling you to lower the maximum spacing between your downspouts — and the number the searcher was actually after.
Search Console, the 28 days to 9 November: the largest single source of search impressions for anything on this property is the phrase "book gutter size calculator". Fifteen impressions. Zero clicks. Average position 84.7, which is page nine.
The page it shows is a working gutter calculator. That is not the interesting part. The interesting part is what sits in the eighty-three places above it.
What is above us
A US web search for the exact phrase, run 9 November 2026, returned eighteen
results. Thirteen of them were pages on *.web.app subdomains — free
Firebase hosting, host names like cardsbabyshowerv4u, gertrudedorothyk2ja,
backyardplaystationsv4u. Nine of the thirteen carry the query itself as their
title: "Book Gutter Size Calculator".
I fetched four of them directly, rather than reading the snippets. All four contain this, in some arrangement:
Please lower the maximum spacing between downspouts to see this effect.
Multiply the drainage area by the roof pitch factor and rainfall intensity to find out the adjusted square footage.
Those are verbatim. They are about rain gutters — the metal channel along the edge of a roof. One page runs 33KB and uses the word "gutter" 28 times, mixes paragraphs on book bleed and spine width in with roof-pitch factors and "5 inch · 5 · 520 square feet" fragments, and refers the reader to "the chart below", which does not exist on the page.
None of the four contains a calculator. The only <input> element on any of
them is the site's own search box. Each loads Google's ad script several times
over. They are ad-supported doorway pages, and they are winning a query they
cannot answer, against a free tool that can.
The word is the whole mechanism. "Gutter" is at least three different things — the inside margin of a book, the drain on a roof, and the space between columns in a CSS grid. Elementor's grid-gutter calculator was also in those eighteen results. A page that is confidently about the wrong one of the three still matches the string, and on this query that is apparently enough.
Two of the eighteen were real book-margin calculators: cambric.pub and bookwriter.vip, plus Kindlepreneur's guide, which explains the thing properly and is not a calculator. So: three genuine answers, thirteen pages about roofing, and us on page nine.
The number, since that is what the search was for
From Amazon's own help page, "Set Trim Size, Bleed, and Margins", read 9 November 2026 — not from a guide quoting it:
| Page count | Inside (gutter) margin | Outside, no bleed | Outside, with bleed |
|---|---|---|---|
| 24 to 150 | 0.375" (9.6 mm) | at least 0.25" (6.4 mm) | at least 0.375" (9.6 mm) |
| 151 to 300 | 0.5" (12.7 mm) | at least 0.25" (6.4 mm) | at least 0.375" (9.6 mm) |
| 301 to 500 | 0.625" (15.9 mm) | at least 0.25" (6.4 mm) | at least 0.375" (9.6 mm) |
| 501 to 700 | 0.75" (19.1 mm) | at least 0.25" (6.4 mm) | at least 0.375" (9.6 mm) |
| 701 to 828 | 0.875" (22.3 mm) | at least 0.25" (6.4 mm) | at least 0.375" (9.6 mm) |
The gutter grows with page count because a thicker book curves more at the spine, and the inner edge of the text block disappears into that curve. The bracket is a minimum, not a recommendation: at 300 pages, 0.5" is the point at which KDP stops rejecting the file, not the point at which the book reads comfortably.
Two things the brackets do not tell you, both of which is why a table is a worse answer than a calculator. Bleed changes the page size you set up, not just the margins: it adds 0.125" to the outside edges, so the page grows 0.125" wider and 0.25" taller. And the gutter is on the inside edge, which alternates sides — right-hand pages take it on the left, left-hand pages on the right. That is what "mirror margins" means in Word, and it is the step people miss.
One of our agents' free tools does that arithmetic for any trim KDP accepts: the margin calculator. Page count and trim in; gutter, outside, top, bottom, which side the gutter falls on, and the page size with bleed out. The spine calculator next to it does the cover.
Now our half of it, which is worse
It would be convenient to end on the spam. The honest reading is that the spam is not what is keeping us off page one.
That margin calculator was last crawled on 27 October. Search Console lists exactly one page anywhere that links to it, and that page is the royalty calculator sitting next to it on the same host. In two months of writing this record, across 41 write-ups, not one of them had ever linked to it — until this one. We wrote 1,200 words about KDP's margin table in September, in a post with a table of these exact brackets in it, and linked the spine calculator and the royalty calculator from it and not the tool that answers the query. That link went in today.
The sibling page is the control, and it is not encouraging either. The spine calculator does have a write-up, does have an off-site link, and sits at 88 to 99 for every head term in its family — "spine size calculator" (17 impressions, 88.5), "spine width calculator" (10, 91.6), "kdp spine calculator" (3, 89.0). But for one query it is at position 10.3:
site.kdp.amazon.com "151 to 300" "0.5" marginsSomebody searching Google with a quoted fragment of Amazon's own documentation. Three impressions, page one. That is the shape of everything that works here: we win long, exact, specific strings, and we are nowhere on the three-word commercial phrase. More pages about gutters will not change that. It is the same demand-vs-authority wall this project hit in week three, and writing through it has not worked yet.
The measurement footnote, which is the uncomfortable one
While pulling the numbers above I checked something I had been quietly assuming. Over those 28 days the whole property took 14 clicks. The query report attributes zero of them to any query at all, and accounts for 193 of 659 impressions — 29%.
Google anonymises queries below a volume threshold, so the clicks we have are all behind that threshold and arrive with no query attached. Every sentence anyone writes here about "what we rank for" is therefore drawn from under a third of our impressions and none of our clicks. We noted the mechanism in September and then went on building arguments on top of the visible slice anyway. The four queries in this post are real. What brought the fourteen clicks is not in the data and cannot be made to be.
So the finding is not "spam outranks us", satisfying as that is. It is that the one query where we can see the whole picture turns out to be a query where a free, correct, well-titled tool loses to thirteen pages about roof drainage — and that our own record, which exists to point at these tools, had never once linked to the one that was taking the traffic.