GEO Monthly Delta Report Generator

GEO Compare generates a progress report from a baseline and current website audit. It parses overall and category scores, platform-readiness results, crawler access, critical findings, and action-item status. Comparable metrics receive absolute deltas, while unavailable or incompatible metrics remain explicitly unavailable. Qualitative evidence can still be compared separately when scores cannot.

The workflow accepts a domain or explicit audit files. Domain discovery searches dated audit files, but the intended reporting pair must be confirmed: the oldest and newest files do not automatically define a monthly comparison. A single existing audit can provide a baseline only when an authorized fresh audit supplies the current evidence; without a baseline, the next step is an initial prospect audit.

The report connects summary changes with category breakdowns, platform readiness, access changes, completed actions, new findings, and the next reporting period's priorities. A historical trajectory records periods that actually occurred, keeping projections distinct from observations. Declines are reported neutrally and may reflect real regression, new discoveries, or changed methodology.

Use when preparing a dated client progress review or checking whether an improvement plan changed observed audit evidence. Preserve the rubric and version, page sample, crawler definitions, query set, platform, region, and collection times across comparisons. Mark results non-comparable when those conditions differ materially.

Heuristic score changes are not proof of business value. Do not infer citation probability, traffic, revenue, timing, or ranking gains from them. Actual business impact requires attributed analytics with documented assumptions and uncertainty. Relative percentage change is undefined when the baseline is zero.

Crawler access does not guarantee search inclusion or citation, and training access differs from search retrieval. Publishing llms.txt likewise does not establish measurable visibility. Site and access-policy changes require authorization, as does client sharing. Community activity needs independent policy and conflict-of-interest review rather than automatic promotional recommendations.

Inputs include the exact domain, confirmed dates, baseline and current audit files, compatible scoring evidence, action statuses, and any separately attributed analytics. The external command interface includes:

/geo compare <baseline-file> <current-file>

The command runtime is a prerequisite and is not bundled with this documentation. Protect client audit files and validate domain-derived output paths. Read-only analysis does not authorize publication, deployment, or target-site modification.

Outputs are a Markdown progress report under the geo-prospects reports directory and a concise confirmation of key observed statistics. The monthly filename identifies the domain and reporting period. Tables compare baseline, current value, delta, and trend; access tables can focus on changed crawlers. Action tables retain owners, completion status, and evidence rather than copying fictional template gains.

The /geo prospect audit <domain> path supplies an initial audit when history is absent, while /geo report-pdf can provide a visual version after the comparison. Score-marker parsing supports alternate labels only when their methods are compatible. Quick-win counts, goals, and future targets must come from actual records or clearly marked planning assumptions. This MIT-licensed documentation import does not bundle upstream runtime helpers, hooks, or schema templates.