SEO

Honest SEO forecast and reporting frame

Use when a stakeholder wants a traffic forecast and you need one that will not embarrass you later.

seo-forecast-and-reporting.md

Download .md

You are producing a defensible organic forecast and the reporting frame around it.

Site: {{SITE_URL}}
Baseline data (last 12 months organic sessions, conversions, by month): {{BASELINE_DATA}}
Planned work and when it lands: {{PLANNED_WORK}}
Keyword opportunity with volumes: {{OPPORTUNITY_DATA}}
Conversion rate and value per conversion: {{CONVERSION_DATA}}
Forecast horizon: {{HORIZON}}

Output:
1. Stated assumptions, numbered, each with its source and how confident you are in it.
2. Three scenarios - conservative, expected, optimistic - as a month by month table: Month | Sessions | Conversions | Value | What has to be true for this.
3. "What this forecast does not account for" - at least five named risks, including competitor action, algorithm volatility, seasonality, delivery slippage and demand change.
4. Leading indicators to report monthly before traffic moves: indexation, impressions, average position for the target cluster, pages published against plan.
5. A one paragraph statement to give the stakeholder, in plain language, on what the forecast is and is not.

Constraints:
- Every number must trace back to a figure in the supplied data or to a numbered assumption. Do not introduce click-through rate figures, growth rates or benchmarks without labeling them as assumptions.
- Do not present a single point forecast anywhere.
- Do not use seasonality unless {{BASELINE_DATA}} shows it. If the baseline is under 12 months, say the forecast confidence is lower and why.
- No em dashes and no closing summary paragraph.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{SITE_URL}}
{{BASELINE_DATA}}
{{PLANNED_WORK}}
{{OPPORTUNITY_DATA}}
{{CONVERSION_DATA}}
{{HORIZON}}

Getting a better result

Assumptions are the deliverable - stakeholders argue with numbers but agree with assumptions.
Report the leading indicators from month one so the first quarter is not a silence.
Revisit and reissue the forecast whenever delivery slips rather than defending the original.

Questions about this prompt

Why forecast at all when SEO is uncertain?

Because the alternative is reporting on activity, and activity is not a result anyone funds. A forecast with stated assumptions can be wrong usefully: you learn which assumption broke. A report of pages published teaches nothing when the number does not move.

What makes a forecast credible?

A real baseline, the planned work attached to specific opportunities, and conversion data so the projection lands in revenue rather than sessions. A traffic forecast with no conversion assumption is a number no finance team can act on.

How far out should I forecast?

Far enough to cover the lag. Content and technical work rarely show their full effect inside a quarter, so a three-month horizon tends to report the previous quarter's work as though it were this quarter's failure.

What should I do when the forecast is missed?

Go back to the assumptions rather than the total. Missing because the work shipped late is a different problem from missing because the opportunity was smaller than estimated, and only one of them is a forecasting error.