Lesson 1: Google tells you what to build

My Search Console queries were full of things I did not have pages for: csv to json, json validator, array to csv online. People were finding my json-to-csv page while searching for the reverse direction. The converter component already supported both directions behind a toggle, but Google cannot rank a toggle. It ranks URLs.

So the rule I now follow: one keyword cluster, one URL. My CSV converter became two pages, json-to-csv and csv-to-json, same component, different default mode, different title and FAQ. Same for XML, YAML, beautify versus minify versus validate.

Lesson 2: shared components make 50 pages cheap

All 12 of my number base converters (binary to decimal, hex to binary, and so on) are one React component with fromBase and toBase props. Each page is really just metadata: title, description, FAQ items, JSON-LD schema. The tool logic is shared. Adding a new keyword page takes minutes, not days.

Lesson 3: rankings move slower than you want

My average position after three months was 63. Nobody clicks page 7. The honest truth I had to accept: new domains sit in a sandbox for months, and no amount of on-page optimization substitutes for backlinks and age. Impressions went from 1 a day to 40 a day in that time, which is the signal that matters early on.

Lesson 4: client-side is a feature

Every tool runs in the browser. Nothing is uploaded. I built it that way to avoid server costs, but it turned out to be the thing developers care about most, because nobody wants to paste production payloads into a random server.

The site is jsontoonpro.com if you want to see how the pages are structured. Ask me anything about the setup.