Case file 03 — Home improvement calculator platform
DIY Takeoff
Most calculator sites in this space are illusions dressed as tools: thin pages, duplicated paragraphs, the same "content" with the nouns swapped. A search engine can smell that from a mile away. DIY Takeoff runs on a different rule: every page has to earn its place, real formula, real content, no copy-paste ghosts.
The glitch
The usual playbook here is a handful of one-off pages, thin and duplicated, that search engines have gotten very good at spotting and ignoring. The alternative usually means a database, a CMS, a slower system to serve what is, underneath it all, just a formula and a form. The brief was a site that could scale to dozens of calculators with no backend, no repeated copy with the nouns swapped, and no CMS quietly rotting in the background, while every single page still had to justify its own existence.
Jacking in
Built the whole platform around one CalculatorConfig type: adding a calculator means writing one config file (inputs, calculation logic, formula note, FAQs, related links), and everything downstream (the page, the embeddable iframe, the sitemap entry, the FAQPage/WebApplication JSON-LD schema) generates itself from the registry. Change the source, the whole system follows.
Shipped as a fully static export, no database, no server runtime. Every calculator page is pre-built HTML that loads instantly and has nothing running that could ever go down.
Wrote the content standard directly into the build process instead of leaving it to willpower: every calculator states its formula in the open, cites the real constant it's built on (bag yields, coverage rates, bundles per square), and ships with an intro and FAQ that would still be useful to a reader even if the calculator vanished entirely.
Built a bare, noindexed embed route per calculator, so any other site can drop one in as an iframe without dragging the full page shell along with it.
Gated the ad system behind an environment variable and a strict one-slot-per-page rule. No AdSense code exists at all until the account is approved and the variables are set, and density stays capped even after that, on purpose.
Sequenced a 20-calculator roadmap (tile, sod, paver, framing, deck boards, and more), prioritized by search demand against competition, aimed at the 40 to 60 page mark where the site's own surface area starts compounding on its own.