geo-compare turns two saved GEO audits into a client-facing progress report. Give it a domain and it finds the oldest and newest audit files, extracts the overall score, six category scores, five platform scores and the status of 14 AI crawlers, and calculates the change in each.
The report shows green, red or neutral trend markers, progress on quick-win, medium-term and strategic actions, this month’s wins, new issues and next month’s focus.
What You Get
- A monthly report file named by domain and month
- Before and after tables for the overall score, categories and platforms
- AI crawler access changes between the two audits
- Action plan progress grouped by quick wins, medium-term and strategic items
- A six-month trajectory and a next-month priority list
Common Use Cases
- Send a client a monthly proof-of-progress report
- Check whether a robots.txt change opened the AI crawlers
- Compare two specific audit files by path
- Prepare a quarterly review from saved audits
What Makes It Unique
It is built around the retention loop of a GEO agency: baseline, work, re-audit, delta. It accepts a domain, two explicit file paths or a month name, and falls back to a fresh quick audit when only one saved audit exists.
Under The Hood
A prose recipe with no scripts. The agent lists audit files under the ~/.geo-prospects/audits folder in the home directory, sorts them by date, reads the oldest and newest, pulls out score lines such as GEO Score and per-crawler Allowed or Blocked markers, and writes the report to ~/.geo-prospects/reports. When exact scores are missing it is told to estimate them from the written findings. It declares Read, Write, Bash and Glob tools and makes no web requests itself.