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.md in the current directory (created by /geo audit)
- Extract cover metadata from the report (brand name, domain, GEO score, date, locations)
- Run
pandoc with the bundled CSS + HTML template to produce a self-contained GEO-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 <url> 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 — <brand_name>" \
--metadata brand_name="<brand_name>" \
--metadata domain="<domain>" \
--metadata geo_score="<geo_score>" \
--metadata score_label="<score_label>" \
--metadata date="<date>" \
--metadata business_type="<business_type>" \
--metadata locations="<locations>" \
--metadata platform="<platform>" \
-o GEO-REPORT.html
Replace <field> 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.pdf was generated in the current directory
- File size
- Optionally:
open GEO-REPORT.pdf to 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/100 are color-coded: ≥80 green, ≥65 blue, ≥50 amber, ≥35 orange, <35 red
- Finding sections —
h3 headings 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 <script> block
- Which sections get page breaks — Edit the
breakBefore array in the template's <script> 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 |
1---
2name: geo-report-pdf
3description: 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.
4version: 2.0.0
5author: geo-seo-claude
6tags: [geo, pdf, report, client-deliverable, professional]
7allowed-tools: Read, Grep, Glob, Bash, Write
8metadata:
9 source: https://skillmd.com/skills/zubair-trabzada/geo-report-pdf
10---
11
12# GEO PDF Report Generator (pandoc pipeline)
13
14## Prerequisites
15
16- **pandoc** — `brew install pandoc`
17- **Google Chrome** — must be installed at `/Applications/Google Chrome.app/`
18
19No Python dependencies. No ReportLab. No JSON data wrangling.
20
21## How It Works
22
231. Read `GEO-AUDIT-REPORT.md` in the current directory (created by `/geo audit`)
242. Extract cover metadata from the report (brand name, domain, GEO score, date, locations)
253. Run `pandoc` with the bundled CSS + HTML template to produce a self-contained `GEO-REPORT.html`
264. Run Chrome headless to print the HTML to `GEO-REPORT.pdf`
27
28The pandoc template (`~/.claude/skills/geo/templates/geo-report-template.html`) injects:
29- A full-bleed dark navy cover section with the GEO score badge
30- Per-section cover metadata (date, business type, locations, platform)
31- JavaScript that runs inside Chrome before printing to color-code score cells and severity-tag finding sections
32
33## Workflow
34
35### Step 1: Check for audit report
36
37Look for `GEO-AUDIT-REPORT.md` in the current directory. If absent, tell the user to run `/geo audit <url>` first.
38
39### Step 2: Extract cover metadata from the report
40
41Read the top of `GEO-AUDIT-REPORT.md` and extract:
42
43| Field | Where to find it |
44|---|---|
45| `brand_name` | First H1 title (after "GEO Audit Report:") |
46| `domain` | Second bold line (e.g. `**Domain:** alexamediasolutions.com`) |
47| `geo_score` | Line matching `## Overall GEO Score: XX / 100` |
48| `score_label` | Word after the score on that same line (e.g. "Poor", "Fair", "Good") |
49| `date` | `**Audit Date:**` line |
50| `business_type` | `**Business Type:**` line |
51| `locations` | `**Locations:**` line |
52| `platform` | `**CMS:**` line |
53
54### Step 3: Run pandoc
55
56```bash
57pandoc GEO-AUDIT-REPORT.md \
58 --to html5 \
59 --standalone \
60 --embed-resources \
61 --template ~/.claude/skills/geo/templates/geo-report-template.html \
62 --css ~/.claude/skills/geo/templates/geo-report-style.css \
63 --metadata title="GEO Audit Report — <brand_name>" \
64 --metadata brand_name="<brand_name>" \
65 --metadata domain="<domain>" \
66 --metadata geo_score="<geo_score>" \
67 --metadata score_label="<score_label>" \
68 --metadata date="<date>" \
69 --metadata business_type="<business_type>" \
70 --metadata locations="<locations>" \
71 --metadata platform="<platform>" \
72 -o GEO-REPORT.html
73```
74
75Replace `<field>` 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.
76
77### Step 4: Run Chrome headless
78
79```bash
80"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" \
81 --headless=new \
82 --disable-gpu \
83 --no-sandbox \
84 --print-to-pdf="$(pwd)/GEO-REPORT.pdf" \
85 --print-to-pdf-no-header \
86 --no-pdf-header-footer \
87 --virtual-time-budget=5000 \
88 "file://$(pwd)/GEO-REPORT.html"
89```
90
91### Step 5: Report completion
92
93Tell the user:
94- `GEO-REPORT.pdf` was generated in the current directory
95- File size
96- Optionally: `open GEO-REPORT.pdf` to preview it
97
98## What the PDF Contains
99
100- **Cover page** — Dark navy gradient, brand name, domain, GEO score badge (colored by score), audit date, business type, locations, CMS platform
101- **Score tables** — Cells containing `XX/100` are color-coded: ≥80 green, ≥65 blue, ≥50 amber, ≥35 orange, <35 red
102- **Finding sections** — `h3` headings containing "Critical / High / Medium / Low" get severity-colored left-border callout blocks (red / orange / yellow / green)
103- **Section page breaks** — Major sections (High Priority, 90-Day Roadmap, Component Score Summary, Generated Schema) break to new pages automatically
104- **Code blocks** — JSON schema templates render with dark theme monospace styling
105- **Page footer** — Brand name · GEO Audit · date + page numbers (via CSS `@page`)
106
107## Customizing the Report
108
109- **Colors / typography** — Edit `~/.claude/skills/geo/templates/geo-report-style.css`
110- **Cover layout** — Edit `~/.claude/skills/geo/templates/geo-report-template.html`
111- **Score thresholds for color-coding** — Edit the `scoreColor()` function in the template's `<script>` block
112- **Which sections get page breaks** — Edit the `breakBefore` array in the template's `<script>` block
113
114## Troubleshooting
115
116| Problem | Fix |
117|---|---|
118| `pandoc: command not found` | `brew install pandoc` |
119| Chrome not found | Check path: `/Applications/Google Chrome.app/Contents/MacOS/Google Chrome` |
120| PDF is blank / empty | Increase `--virtual-time-budget` to 8000 |
121| Cover metadata missing | Check GEO-AUDIT-REPORT.md has the standard header format |
122| Fonts not loading | PDF is rendered offline; system fonts are used as fallback — this is expected |