EconomicsCalc Tools

The brief

A suite of economics calculators built for search: fast static pages, schema markup, internal linking and clean URLs around real query intent rather than one large page trying to rank for everything.

Problem

Calculator sites usually publish one long page that tries to cover a dozen formulas and ends up ranking for none of them. Search intent for formulas is specific: someone wants the elasticity of demand formula, not an economics primer. The other constraint is speed, because a calculator that takes three seconds to become interactive has already lost the visitor.

My role

Solo build. I designed the page pattern, built the calculators, wrote and structured the copy per formula, and handled the technical SEO: URLs, headings, structured data, internal linking and the sitemap.

Process

• Started from a query list rather than a topic list, so each page had one job
• Built one static template that takes a formula definition and renders the calculator, explanation, worked example and related formulas
• Kept the calculators client-side and dependency-free so the page is interactive as soon as the HTML arrives
• Added structured data to every calculator page instead of only the index
• Linked each formula to its neighbours to give the suite an internal structure search engines can follow
• Wrote a worked example for every formula, because the worked example is usually what the visitor actually came for and it is the part that makes the page worth ranking above a thin competitor

Result

A live calculator suite built on one template, where adding a formula is a data change rather than a new page build. This is the project that taught me the template-first approach to programmatic pages, and the pattern now shapes how I plan client content architecture: one query, one page, one structured data block. The limitation is equally clear: a template suite is only worth building when the queries genuinely differ. Where two calculators answer the same question with different wording, they belong on one page, because near-duplicate pages compete with each other instead of adding coverage. That judgement call is the part a template cannot make for you. If I rebuilt it now, the calculator state would move into the URL so a result could be shared or bookmarked instead of retyped.

What it had to do

• One static page per formula instead of one page competing with itself
• Structured data on every calculator for rich results
• Internal linking between related formulas and the index

Stack

• React
• Next.js
• TypeScript
• SEO