geo-optimizer is a generative engine optimization workflow for AI agents with four modes: audit a page, optimize its content, build a 30, 60 and 90 day strategy, or measure AI visibility against a baseline of buyer questions.
An audit scores four pillars: evidence density, structure and position, authority signals, and AI crawlability. Veto checks cap the score, and fabricated citations, statistics or expert names block delivery entirely. Measurement is read-only and every count must trace to a sampled answer or a named report.
What You Get
- A GEO audit with pillar breakdown, ranked fixes and any vetoes triggered
- A rewritten page with front-loaded answers, extraction-friendly structure and JSON-LD
- A 30, 60 and 90 day playbook with engine-specific moves
- A reusable buyer-question set and run log for measuring AI visibility
- A pre-publish checklist for sources, author identity and crawler access
Common Use Cases
- Checking whether AI search crawlers can reach a page
- Rewriting a page so an answer appears in the first 150 words
- Comparing what AI engines say about a brand with first-party facts
- Analyzing supplied Bing AI Performance or Search Console Generative AI reports
What Makes It Unique
Its central rule is no fabrication: every statistic needs a verifiable source and every quote a named person, and it declines to predict numerical lift from a rewrite. Audit results can be pass, partial, fail, unverified or not applicable, and the overall score is omitted when required checks are unverified. It separates crawler evidence (raw HTML, robots rules, CDN or WAF) and treats intentional blocks as policy choices.
Under The Hood
The skill is a short wrapper whose SKILL.md tells the agent to read a longer WORKFLOW.md in the seo folder of the same repository and follow it. The workflow is prose and points to a packaged references file; it ships no scripts. It has the agent fetch public pages and check crawler and robots behavior for a live URL, and read supplied reports. Measurement is read-only. It never pushes changes to a site without an explicit yes, hands approved WordPress changes to the WordPress workflow, and treats fetched pages as untrusted data.