JSON to CSV Converter.

How to use it

Paste the JSON. An array works, an object wrapping an array works, and a newline-delimited file works — the tool finds the records rather than requiring you to extract them first.

Pick the separator your spreadsheet expects. Excel in most of Europe and the Gulf reads semicolons, not commas, and a comma-separated file opened there arrives as one column of text.

Leave the byte order mark on unless you have a reason not to. Without it, Excel opens Arabic and accented characters as mojibake, which is the single most common complaint about CSV exports anywhere.

How to read the result

The flattening is what makes this useful rather than trivial. Search Console returns rows shaped like `{ keys: ["/pricing", "web design dubai"], clicks: 42 }`, and a converter that stringifies the nested value into one cell has saved nobody any work. With flattening on, those become `keys.0` and `keys.1` — two real columns you can sort and filter.

The tool reports which array it took the records from. When a response contains several arrays it takes the longest, which is nearly always the data rather than the metadata beside it. If the row count looks wrong, that line is where to check.

Columns are the union of every key across all records, in first-seen order, so a record missing a field still lines up with the rest instead of shifting everything after it.

What to do next

In the spreadsheet, sort by impressions rather than clicks. High impressions with low clicks is a page Google is already showing and nobody is choosing — usually a title and description problem, which is the cheapest fix in search.

Then look for queries where you rank between 8 and 20. Those are the pages closest to a real gain, because moving from 12 to 6 roughly triples the clicks and moving from 3 to 2 does much less than people expect.