GSC performance export normalize

Client

Performance exports should not need manual FIND/REPLACE on headers before analysis. This page is the normalize step—turn raw Google exports into a stable schema for Sheets, Python, or LLM prompts.

Normalize before analyze

Always normalize once, then reuse JSON for insights and prompts—avoids re-parsing xlsx and keeps meta consistent.

Search Console workbook → AI-ready output

?

Parses .xlsx / .xls locally. Detects English or Chinese Search Console columns (Query/查询, Page/网页, Clicks/点击次数, …). Skips chart sheets when picking a tab automatically.

Common use cases

  • Standardize weekly exports for diff scripts.
  • Fix Chinese UI column names before team sharing.
  • Remove banner rows without writing Excel macros.

Common mistakes to avoid

  • Normalizing chart data

    Use table exports with Query/Page columns.

  • Rounding position too early

    Position keeps one decimal for striking-distance filters.

  • Dropping zero-click rows

    Keep them—insights uses zero-click as its own bucket.

FAQ

What gets normalized?

Header mapping, CTR to decimal, integer clicks/impressions, trimmed strings.

Which reports work?

Queries, Pages, Countries, Devices—any flat performance table.

Storage?

None—processing is ephemeral in the tab.

Common search terms

Phrases people search for that match this tool. See the full long-tail keyword index.

  • gsc tools online
  • search console tools browser
  • google search console helper
  • seo search console export tools
  • search console ai workflow

More tools

Related utilities you can open in another tab—mostly client-side.