// log entry · seo
we have two hundred forty-six pages and zero pageview goals.
if you crawled the studio's web properties tonight you would find two hundred forty-six indexable urls spread across five subdomains. apex, tools, extensions, ai, games. fifteen blog posts. twenty-two tool landing pages. fourteen extension cards. an embarrassing number of legal docs. an "about" page nobody asked for.
we did not set a pageview target for any of them.
most of those pages were not built to compete for traffic. they were built because each tool needed somewhere to live, each extension needed a privacy policy with the right phrasing, each product needed a refund page that the paddle review team would actually accept. by the time we noticed the catalogue had a hundred and fifty pages, it had its own gravity.
what the numbers look like.
the breakdown, verifiable from the sitemap index:
- apex — 27 urls. blog posts, legal docs, the team page, the contact page, the obligatory privacy/terms/dpa trio.
- tools — 157 urls. each free tool gets its own landing, plus per-tool subpages we added when paddle started asking what we shipped.
- extensions — 46 urls. seven active extensions × six pages each (landing, pricing, terms, privacy, refund, contact, upgrade). this is the price of being a paddle merchant.
- ai — 3 urls. the ai subportal is small on purpose.
- games — 13 urls.
nobody at the studio was hired to optimize any of those for search rank. nobody runs an analytics dashboard that shows which legal page is visited most often. (if you guessed "refund" you would probably be right but we have not checked.)
why we keep shipping pages anyway.
three reasons, all unromantic:
compliance. a paddle merchant page is not optional. the team will reject your store if your refund policy lives in a footer link instead of its own indexable url. you ship the page because the alternative is a closed store.
internal correctness. a tool page makes you describe the tool. a description forces you to decide what the tool actually is. half the cuts to scope we made in march came out of trying to explain what the tool did on its landing page and noticing the answer was incoherent. the page was the design tool.
compounding presence. google indexes things slowly. but it does index them. every page sitting on a stable url is a small line in a slowly accumulating ledger that we have shipped, are still shipping, and have not abandoned. the page does not need to rank for the ledger to count.
the case for not measuring.
once you put a pageview target on a page you change the page. you optimize the headline for ctr. you add a cta where it does not belong. you write the meta description for a robot instead of a person. the page becomes a piece of conversion plumbing, and the moment it does, it stops being able to do the other thing — the documentation thing, the compliance thing, the slow-trust thing.
the studio runs on a small number of metrics that actually drive decisions. signups per product. paid conversion rate. gemini cost per paying user. those are reviewed weekly. pageviews are not on that list because they would tempt us to optimize the wrong thing.
two hundred forty-six pages later.
so the catalogue exists. it loads fast (plain html, no react on these surfaces). it doesn't track visitors. it links internally with intent. some of the pages get organic traffic. most don't. we won't know which is which without an analytics tool, and we are not adding one.
this is not a strategy. it's closer to a position. the position is that shipping a page and caring whether the page is read are two different verbs, and the studio only does the first one on purpose.
the second one belongs to the reader.