ai-export-merge
Joins your Search Console generative AI export and Bing AI Performance export into one per-page table, locally. Python, standard library, no network calls.
- Status
- Live
- Launched
- Licence
- MIT
- Language
- Python
One command, copied from the repo.
Install ai-export-merge: pip install git+https://github.com/reidifydesign/ai-export-merge
reidifydesign/ai-export-merge
What it does
Google added generative AI performance reports to Search Console in June 2026, and Bing added an AI Performance report to Bing Webmaster Tools on 10 February 2026. The two exports do not share a format, and neither carries what the other one has. This joins them into one row per page, on your machine, so the exports never leave it.
Each argument can be a .csv or .xlsx file, a .zip, or a folder. A row shows the page, whether it is in both exports, Google AI impressions, Bing citations, how many grounding queries Bing ties to the page, and the top queries. It needs Python 3.10 or newer, uses the Python standard library alone, and makes no network calls.
It never adds or compares the two numbers: an impression is something Google showed, and a citation is something Bing used in an answer. It fetches nothing. Columns are found by name, and the real column names of both exports are unconfirmed, so the inspect command shows what was found and --gsc-col or --bing-col fixes it. The example files are invented.
Disclosure: Reidify, the studio behind this, sells AEO services. This is published as data with its method, not as a pitch.
Why it exists
Both search engines now report how your pages show up in AI answers, and each report lives in its own console. Google gives impressions and no queries. Bing gives citations and queries and no Google numbers.
On 2026-09-30 a search of GitHub, npm and the web found no tool that joins them: one 0-star Codex skill for the Google report, and general SEO reporting apps that read other data. This one does the join.