Generate a professional, client-facing GEO report combining all audit results into a single deliverable with scores, findings, and prioritized actions
Browser
geo-report-pdf
Try itGenerate a professional PDF report from a GEO audit using pandoc + Chrome headless. Converts GEO-AUDIT-REPORT.md into a styled, client-ready PDF with a cover page, color-coded score tables, severity-tagged findings, and a 90-day roadmap.
What it does
Generate a professional PDF report from a GEO audit using pandoc + Chrome headless. Converts GEO-AUDIT-REPORT.md into a styled, client-ready PDF with a cover page, color-coded score tables, severity-tagged findings, and a 90-day roadmap.
The skill document
GEO PDF Report Generator (pandoc pipeline)
Prerequisites
- pandoc —
brew install pandoc - Google Chrome — must be installed at
/Applications/Google Chrome.app/
No Python dependencies. No ReportLab. No JSON data wrangling.
How It Works
- Read
GEO-AUDIT-REPORT.mdin the current directory (created by/geo audit) - Extract cover metadata from the report (brand name, domain, GEO score, date, locations)
- Run
pandocwith the bundled CSS + HTML template to produce a self-containedGEO-REPORT.html - Run Chrome headless to print the HTML to
GEO-REPORT.pdf
The pandoc template (~/.claude/skills/geo/templates/geo-report-template.html) injects:
- A full-bleed dark navy cover section with the GEO score badge
- Per-section cover metadata (date, business type, locations, platform)
- JavaScript that runs inside Chrome before printing to color-code score cells and severity-tag finding sections
Workflow
Step 1: Check for audit report
Look for GEO-AUDIT-REPORT.md in the current directory. If absent, tell the user to run /geo audit first.
Step 2: Extract cover metadata from the report
Read the top of GEO-AUDIT-REPORT.md and extract:
| Field | Where to find it |
|---|---|
brand_name | First H1 title (after "GEO Audit Report:") |
domain | Second bold line (e.g. **Domain:** alexamediasolutions.com) |
geo_score | Line matching ## Overall GEO Score: XX / 100 |
score_label | Word after the score on that same line (e.g. "Poor", "Fair", "Good") |
date | **Audit Date:** line |
business_type | **Business Type:** line |
locations | **Locations:** line |
platform | **CMS:** line |
Step 3: Run pandoc
pandoc GEO-AUDIT-REPORT.md \
--to html5 \
--standalone \
--embed-resources \
--template ~/.claude/skills/geo/templates/geo-report-template.html \
--css ~/.claude/skills/geo/templates/geo-report-style.css \
--metadata title="GEO Audit Report — " \
--metadata brand_name="" \
--metadata domain="" \
--metadata geo_score="" \
--metadata score_label="" \
--metadata date="" \
--metadata business_type="" \
--metadata locations="" \
--metadata platform="" \
-o GEO-REPORT.html
Replace `` placeholders with values extracted in Step 2. If a field is not found in the report, omit that --metadata flag — the template has sensible defaults.
Step 4: Run Chrome headless
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" \
--headless=new \
--disable-gpu \
--no-sandbox \
--print-to-pdf="$(pwd)/GEO-REPORT.pdf" \
--print-to-pdf-no-header \
--no-pdf-header-footer \
--virtual-time-budget=5000 \
"file://$(pwd)/GEO-REPORT.html"
Step 5: Report completion
Tell the user:
GEO-REPORT.pdfwas generated in the current directory- File size
- Optionally:
open GEO-REPORT.pdfto preview it
What the PDF Contains
- Cover page — Dark navy gradient, brand name, domain, GEO score badge (colored by score), audit date, business type, locations, CMS platform
- Score tables — Cells containing
XX/100are color-coded: ≥80 green, ≥65 blue, ≥50 amber, ≥35 orange, <35 red - Finding sections —
h3headings containing "Critical / High / Medium / Low" get severity-colored left-border callout blocks (red / orange / yellow / green) - Section page breaks — Major sections (High Priority, 90-Day Roadmap, Component Score Summary, Generated Schema) break to new pages automatically
- Code blocks — JSON schema templates render with dark theme monospace styling
- Page footer — Brand name · GEO Audit · date + page numbers (via CSS
@page)
Customizing the Report
- Colors / typography — Edit
~/.claude/skills/geo/templates/geo-report-style.css - Cover layout — Edit
~/.claude/skills/geo/templates/geo-report-template.html - Score thresholds for color-coding — Edit the
scoreColor()function in the template's `` block - Which sections get page breaks — Edit the
breakBeforearray in the template's `` block
Troubleshooting
| Problem | Fix |
|---|---|
pandoc: command not found | brew install pandoc |
| Chrome not found | Check path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome |
| PDF is blank / empty | Increase --virtual-time-budget to 8000 |
| Cover metadata missing | Check GEO-AUDIT-REPORT.md has the standard header format |
| Fonts not loading | PDF is rendered offline; system fonts are used as fallback — this is expected |
Tooling
# Markdown audit report -> styled HTML + PDF
seogeo report-pdf GEO-AUDIT-REPORT.md -o example-com-geo-report
# HTML only (no browser needed)
seogeo report-pdf GEO-AUDIT-REPORT.md --html-only
# Override the cover metadata
seogeo report-pdf GEO-AUDIT-REPORT.md --brand "Example Corp" --score 74
There is no pandoc dependency. Markdown is converted in-process, and the
PDF step drives whatever Chrome, Chromium, or Edge is already installed.
If none is found the command says so and names the SEOGEO_CHROME
override rather than failing obscurely.
The brand name defaults to the report's first H1 and the score to the
first NN/100 in the document, so a well-formed audit report needs no
flags at all.
What the styling gives you: a cover page with the score badge, section page breaks, severity-coloured callouts for headings containing Critical/High/Medium/Low, and tables that survive A4 pagination.
Related skills
Auto-generate a professional, client-ready GEO service proposal from audit data. Creates a full proposal in markdown and PDF including executive summary, findings, recommended service packages (Basic/Standard/Premium), pricing, timeline, and terms. Use when user says "proposal", "proposta", "offerta", "preventivo", "generate proposal", or after completing a GEO audit for a prospect.
Use when the user wants audit findings turned into a stakeholder-ready document — severities, page counts, first-seen/fixed history — as a Markdown or CSV deliverable rather than a working diagnosis.
Use when the user wants to generate, structure, score, or audit GEO monitoring prompts for a client. Trigger when building topic-first prompt sets from a web...
One workflow that turns brand materials into an audited GEO delivery package with platform drafts.
End-to-end GEO workflows for question mining, AI answer monitoring, result retrieval, GEO reporting, and content creation with AIDSO.