SEO forecasting estimates the organic traffic, leads, pipeline and revenue a search plan will produce over the next 6 to 24 months. Build it from three inputs: your Search Console history, the searches you plan to win, and your conversion rates from click to closed deal. Present three scenarios, never one number. Discount clicks wherever AI Overviews appear. Then report actuals against that range every month, so one document works as the business case and the scorecard at once.
I'm Brenden House. I run Searchmaxxed, an SEO and AI SEO agency for enterprise, B2B SaaS, venture-backed, manufacturing and public-sector companies. This is how I'd build the forecast if I had to defend a search budget to a CFO next week.
In summary
- Forecast pipeline, not traffic. Finance funds opportunities and revenue, so traffic belongs in the appendix as a leading indicator.
- Give a range. Conservative, expected and ambitious cases beat one confident line.
- Discount AI Overview searches. In one 3,119-query study, organic CTR was 0.52% when an AI Overview left the brand out, against 1.45% with no Overview (Q3 2025).
- Build in the lag. Rankings take months and your sales cycle adds more, so year-one pipeline can look healthy while year-one closed revenue looks small.
- Check the tracking first. Untracked conversions make forecasts look wrong.
What is an SEO forecast?
An SEO forecast is a dated estimate of what a defined set of search work will produce: clicks, leads, pipeline and revenue, month by month. Add the cost and the payback month, and it becomes a business case.
The terms you'll need:
- CTR (click-through rate): the share of searchers who click your result.
- AI Overview: Google's AI-written summary above the normal results.
- Pipeline value: the contract value of sales opportunities search creates, before any of them close.
- Scenario: one full version of the forecast.
- First-party data: your own Search Console, GA4 and CRM numbers, as opposed to estimates from tools like Semrush, Ahrefs or SE Ranking.
Use first-party data wherever you have it. Tool estimates are fine for sizing a market you haven't entered yet, but for your own CTR and conversion rates they're a guess.
Keep the forecast and the target apart. The forecast says what the plan should produce; the target says what the business needs. When the target sits above the ambitious case, you have three honest options: more budget, more time or a smaller number.
Which SEO forecasting method should you use?
Use keyword-based forecasting for new pages and markets, and historical trend forecasting for what your existing pages will do. Then test both against a back-plan. Each method fails in a different way, which is why a solid business case combines two or three.
| Method | How it works | Best for | Where it goes wrong |
|---|---|---|---|
| Keyword-based | Search volume × expected CTR at your target position × conversion rate | New pages, new markets, new product lines | Tool volumes miss long-tail demand and overstate head terms |
| Historical trend | Projects your own Search Console clicks forward, with seasonality | Established sites with 12+ months of clean data | Assumes the past repeats, so a core update or AI Overview breaks it |
| Goal back-plan | Starts from the pipeline target and works back to the clicks you'd need | Budget and headcount conversations | Can produce a number the plan has no way of reaching |
| Competitor benchmark | Uses a realistic peer's estimated traffic as the ceiling | New domains with no history of their own | Tool traffic estimates can be well off |
| Capacity-based | Pages shipped per month × typical result per page, by page type | Content-led plans with a known output | Needs your own page-level history to calibrate |
Trend models run from a straight line in Google Sheets to time-series tools like Prophet, the open-source model in Ahrefs' forecasting walkthrough. Whatever you use, the CFO has to be able to follow it.
My pick? Keyword-based plus capacity-based, checked against a back-plan, because that ties the forecast to work you can count each month. You'll want that when the actuals move.
How do you forecast SEO traffic, step by step?
Pull your baseline from Search Console and group your target searches by intent and AI Overview exposure. Apply your own CTR by position, then convert clicks to pipeline with conversion rates by page type. For a few hundred searches, budget a day.
- Pull the baseline. Export clicks, impressions, CTR and position by query and page from Search Console, taking the longest history it offers so seasonality shows up.
- Split out branded searches. Sales and PR drive branded demand far more than SEO does, so forecast it on its own line or leave it out.
- List the searches you plan to win. Group them by intent: informational ("what is"), commercial ("best", "alternatives", "vs", "pricing") and transactional, and note the page each belongs to.
- Flag AI Overviews. Mark which searches show one today, and whether your brand appears in it.
- Build your own CTR curve. Average your Search Console CTR by position, split by intent and AI Overview presence. Industry curves are the fallback for sites with no history.
- Set target positions and timing. Decide where each page should rank in each scenario, and by which quarter.
- Convert clicks to money. Apply conversion rates by page type, then your CRM's lead-to-opportunity rate, win rate and average contract value.
Forecasts break at steps 5 and 7. One blended CTR and one site-wide conversion rate will overstate the guides and understate the comparison and pricing pages that sell.
How do AI Overviews change an SEO forecast?
AI Overviews cut clicks wherever they appear, so a forecast built on old CTR curves runs high. Discount those searches hard, and check whether Google names your brand in the Overview. Commercial searches see far less of it.
Here's what the larger studies found:
| Source and date | What they measured | Finding |
|---|---|---|
| Seer Interactive, Q3 2025 | 3,119 informational queries across 42 client organisations | Organic CTR 1.45% with no AI Overview; 0.70% when the Overview cites the brand; 0.52% when it doesn't |
| Ahrefs, February 2026 | 300,000 keywords, December 2023 against December 2025 | An AI Overview correlated with a 58% lower average CTR for the top-ranking page |
| Pew Research Center, July 2025 | US panel's Google searches, March 2025 | People clicked a result on 8% of visits with an AI summary, against 15% without one |
| Ahrefs, November 2025 | 146 million desktop results pages, September 2025 | AI Overviews on 21.4% of informational searches, 4.3% of commercial and 2.1% of transactional |
Run the Seer figures and an uncited result kept about 36% of the no-Overview CTR (0.52% against 1.45%, my arithmetic). Cited, it kept about 48%. So for uncited informational searches, I'd start the expected case at roughly a third of your normal CTR. Swap in your own CTR after a quarter.
That's good news for B2B. A forecast built on comparison, alternatives, pricing and integration searches carries much less AI Overview risk than one built on definitions.
You can now see your own exposure. Since 31 August 2026, Search Console's generative AI performance report has shown impressions in AI Overviews and AI Mode for sites worldwide. Give it its own forecast line.
Can you forecast traffic from ChatGPT and other AI assistants?
Only loosely. ChatGPT, Perplexity and Gemini publish no search volumes or positions, so volume × CTR has nothing to work with. Give AI referrals their own forecast line from your GA4 trend, and treat brand mentions in AI answers as the early signal.
Clean that trend first. Here's an enterprise B2B client's account:
> A client's GA4 showed AI-assistant visits jump from 354 to 6,050 in a month. Almost none of it was real. About 5,700 came in three one-hour bursts: same 1920x1080 desktop Chrome, all new users, no referrer, about 20 seconds each, landing on two pages. Real AI traffic was 385 sessions against 354 the month before, roughly flat.
Imagine forecasting from that month. You'd have promised about 16 times the real AI traffic (6,050 against 385). Our guide to AI visibility tools compares the software that tracks brand mentions in AI answers.
What does an SEO forecast look like for a B2B SaaS company?
In the expected case, a B2B SaaS company with A$30,000 deals reaches about 19 demos and A$227,000 of new pipeline a month by month 12. Year-one closed revenue is only about A$156,000, because rankings ramp up slowly and deals take a quarter to close.
Every input is an example I chose to show the maths, so swap in yours; it works the same in US$.
The inputs for this example company
| Input | Example value |
|---|---|
| Commercial searches targeted ("alternatives", "vs", "pricing", "[category] software") | 12,000 searches a month, mostly no AI Overview |
| Informational searches targeted ("what is", "how to") | 30,000 searches a month, mostly with an AI Overview |
| Commercial page conversion, visit to demo request | 2.5% |
| Informational page conversion, visit to demo request | 0.3% |
| Demo request to sales opportunity | 40% |
| Opportunity win rate | 20% |
| Average contract value | A$30,000 |
| Sales cycle | About 90 days |
Month 12, once pages reach their target positions
| Scenario | Commercial CTR | Informational CTR | Clicks a month | Demos a month | New pipeline a month | Closed-won a month |
|---|---|---|---|---|---|---|
| Conservative | 3% | 0.5% | 510 | 9.4 | A$113,400 | A$22,680 |
| Expected | 6% | 1.0% | 1,020 | 18.9 | A$226,800 | A$45,360 |
| Ambitious | 10% | 1.5% | 1,650 | 31.4 | A$376,200 | A$75,240 |
Now look at where the money in that table comes from. In the expected case, the informational pages bring 300 clicks and under one demo a month. The commercial pages bring 720 clicks and 18 demos. A traffic forecast would score those two groups about the same, while a pipeline forecast shows you which pages deserve the budget.
Year one, ramp and lag included
Pages rarely hit full output in month one, so I assumed each quarter reaches this share of the month-12 result: 10%, 35%, 70% and 100%. With a 90-day sales cycle, deals from fourth-quarter demos close in year two.
| Scenario | Year-one pipeline created | Year-one closed-won | Customers won in year one | Customers a year at the month-12 rate |
|---|---|---|---|---|
| Conservative | About A$731,000 | About A$78,000 | About 3 | About 9 |
| Expected | About A$1.46 million | About A$156,000 | About 5 | About 18 |
| Ambitious | About A$2.43 million | About A$260,000 | About 9 | About 30 |
This is the CFO table. Year one is mostly pipeline, and most of the revenue arrives in year two. Judge SEO on year-one closed revenue alone and it loses to paid search, so show the board the lag before the budget gets signed.
How do you turn an SEO forecast into a business case?
Set the forecast's gross profit against the full cost of the work, then show the payback month in each scenario. Use gross profit, not revenue. Finish with your cost per opportunity next to what paid channels charge you today.
The formulas:
- SEO ROI = (gross profit from search-sourced customers − total SEO cost) ÷ total SEO cost
- Payback month = the first month where cumulative gross profit passes cumulative cost
- Cost per opportunity = total SEO cost ÷ search-sourced opportunities
Count every cost line. Agency or contractor fees, content, design and development, tools, links and digital PR all go in, plus your own team's hours reviewing work.
Subscriptions change the maths. In the example, a customer who stays three years at A$30,000 a year brings A$90,000 in revenue. At an 80% gross margin, that's A$72,000 of gross profit each (example figures again). The expected case wins about 23 customers across years one and two. Set that against two years of cost.
What if you stop? Paid search stops with the budget, while ranking pages keep bringing visits after the work ends, until competitors and updates wear them down.
Two related guides: is SEO worth it? covers when search pays back, and how much does SEO cost? covers market rates for the work.
Why should an SEO forecast be a range, not a single number?
Because nobody controls the big inputs. Google's updates, competitors' moves and the spread of AI Overviews all sit outside your plan. A range with written assumptions shows the board what you control, and actuals landing inside it means the forecast did its job.
Make each scenario a complete story:
| Scenario | What it assumes | When it happens |
|---|---|---|
| Conservative | Pages reach lower positions, AI Overviews spread to more of your searches, and one core update hits | Things go somewhat wrong |
| Expected | Pages reach the positions the current top results suggest, at today's AI Overview exposure | The plan runs as written |
| Ambitious | Pages reach the top three, Google names your brand in AI Overviews, and links come faster | Things go right |
Change as few assumptions per scenario as you can, so the board can see which ones drive the spread between the cases. In the example, CTR drives nearly the whole gap, which makes ranking position and AI Overview mentions the two numbers to watch.
Let the range widen with time. A quarter out, stay tight. Two years out, the ambitious case may sit at three times the conservative one, and that's honest.
How do you report against an SEO forecast?
Report actuals against the forecast range every month using matched periods, with leading indicators and pipeline in separate rows. Explain every miss. Reforecast each quarter, and straight away after a core update.
Here's our reporting cadence:
- Every 7 days: the operational check on whether pages shipped, broke or moved.
- Matched 28-day periods: monthly decisions, comparing the last 28 days with the 28 before so weekday patterns line up.
- Matched 90-day periods: the strategic view, and the window where you judge the forecast.
Keep the monthly report to one page:
| Metric | Type | Forecast range this month | Actual | Inside range? | Why, and what changes next |
|---|---|---|---|---|---|
| Pages live against plan | Output | Planned count | Count shipped | Yes or no | Any delay and its cause |
| Non-branded impressions for target searches | Leading | Low to high | Search Console | ||
| Average position, target pages | Leading | Low to high | Search Console | ||
| AI Overview and AI Mode impressions | Leading | Low to high | Generative AI report | ||
| Non-branded clicks to target pages | Leading | Low to high | Search Console | ||
| Demo requests from organic search | Pipeline | Low to high | GA4 and CRM | ||
| Search-sourced opportunities and pipeline value | Pipeline | Low to high | CRM | ||
| Closed-won from search | Revenue | Low to high | CRM |
One trap. When a site starts ranking for lots of new searches on pages two and three, average position can fall while clicks rise. Read it by page and search group, never as one site-wide number.
Check the tracking before you report anything
Nothing loses a forecast argument faster than a conversion your analytics never records. Another enterprise B2B client:
> A client's four enquiry types never counted as conversions. Their event names ran 41 to 50 characters; GA4 cuts at 40. The 40-character "career" event counted every time. Nobody had noticed, because the events still showed up.
Google's documentation says the same: an event name over 40 characters won't report as a key event (Google Analytics Help). Before you set a baseline, test each conversion in GA4 and match a month of it against your CRM. Then check AI spikes for bots.
How accurate are SEO forecasts?
A useful SEO forecast lands inside its range, and every month it doesn't comes with an explanation. None hits an exact number. Expect wide ranges in year one and tighter ones once you have a few quarters of your own data.
Three things wreck accuracy more than anything else:
- Tool search volumes. They often miss long-tail commercial searches and overstate broad ones, so trust your own impressions over them.
- Generic CTR curves. Most of them predate AI Overviews, and Ahrefs' 58% drop on top-ranking pages shows the size of the error.
- Broken tracking. If GA4 misses a conversion, every report blames SEO for it.
Reforecast when a core update lands, when the plan changes, or when clicks fall sharply over a week for no clear reason.
What does an SEO ROI calculator miss?
SEO ROI calculators give a fast sense of scale. Most assume one CTR, one conversion rate and no time lag, which makes year one look far better than it will be. Use one for a sanity check, then build the real forecast from your own Search Console, GA4 and CRM data.
| A typical calculator assumes | What happens in practice | What to do instead |
|---|---|---|
| One CTR for all searches | CTR varies by intent and AI Overview presence | Split CTR by search group |
| One site-wide conversion rate | Pricing and comparison pages convert far better than guides | Use a rate per page type |
| Results from month one | Rankings ramp over months, and sales cycles add a lag | Model the ramp and your sales cycle |
| Revenue equals value | Margin and renewals decide what a customer is worth | Use gross profit and lifetime value |
| Traffic is the outcome | Pipeline is the outcome | Forecast through to opportunities |
Where does Searchmaxxed fit?
Searchmaxxed is an SEO and AI SEO agency for enterprise, B2B SaaS, venture-backed, manufacturing and public-sector companies. We do technical SEO, content, link building, digital PR, GEO, AEO and LLM SEO. The goal is rankings in Google and mentions in ChatGPT, Gemini, Perplexity and Google's AI answers for the searches that bring pipeline.
Our packages fit a capacity-based forecast. Each one commits to a number of page releases a month, where a page release is an approved new page or a substantial rebuild. You can check that input monthly.
| Package | Who it suits | What it includes |
|---|---|---|
| Growth System | A company growing in one or two markets | 30 page releases a month, work on up to 4 existing pages, one qualified link action, AI visibility tracking |
| Agentic Search Engineering | A competitive or national category | 50 page releases a month, comparison, industry and integration pages, digital PR and link campaigns, AI answer tracking across ChatGPT, Gemini, Perplexity and AI Overviews |
| Custom & Enterprise | Several brands, several markets or a large site | Multiple markets, dedicated engineering, custom reporting and original first-party research |
Every managed package includes a 90-day plan in weekly releases and Search Console and GA4 wired and checked. Each month you get a decision memo measuring results against competitors, and you own the site, repository, content and data from day one. Full scope: our SEO services page.
Here's how we do it. We build on a website you own, our Agentic Website. AI agents pull your Search Console and GA4 data, read the Google results and check what AI answers say about you and your competitors. The Managed Search Loop ranks the work by how close it sits to customers and revenue, which in the example puts the comparison pages first. Then we ship it and measure. Off your site, the Off-Page Source Layer builds the links, digital PR and mentions that AI answers draw on.
Searchmaxxed's work has generated more than A$10 million in revenue through search for its clients.
Need a baseline first? Our AI SEO Audit takes five business days, maps where your buyers search without finding you, and ranks every fix by what it's worth. That's most of what a forecast needs.
Is Searchmaxxed right for you?
We fit when search has to produce pipeline you can report on, and you want one team doing the work across Google and AI answers. We're the wrong team if you only want the forecast, or if search alone has to fill this quarter's pipeline.
| Searchmaxxed is a good fit if | Look elsewhere if |
|---|---|
| You need pipeline from search and a monthly report against a forecast | You want a forecast or a report, with no changes to your site |
| You want pages built and shipped each month, counted as page releases | You need leads this month to hit this quarter's number |
| You sell to businesses or government, with deals worth the wait | You want a fixed result promised before any work starts |
| You want SEO and AI search from one team | You want only AI mention tracking; a visibility tool costs less |
| You want to own your site, repository, content and data | You're shopping for the cheapest retainer |
Frequently asked questions
How do you forecast SEO traffic?
Multiply each target search's monthly volume by the CTR you expect at your target position, then add them up. Use your own Search Console CTR by position, split by intent. Cut the CTR hard for searches with an AI Overview that leaves your brand out.
How do you calculate SEO ROI?
Take the gross profit from search-sourced customers, subtract the total SEO cost, then divide the result by that same total SEO cost. Count customers in your CRM, never from traffic estimates, and use lifetime gross profit for subscription revenue.
How long does it take for SEO to show up in a forecast?
Impressions move first, usually within a quarter. Pipeline follows as pages reach page one. Closed revenue lags by your sales cycle on top of that, so for B2B, plan on year one being mostly pipeline.
Can you forecast AI search traffic?
Only roughly. AI assistants publish no search volumes, so project AI referrals from your own GA4 trend on a separate line. Check that trend for bots first. Then track AI mentions.
What should an SEO business case include?
Three scenarios, each with its assumptions written down. Add the full cost, the payback month and the cost per opportunity next to your paid channels. Then the reporting plan, so leadership knows how you'll show progress against the range.
Should an SEO forecast include branded searches?
Keep them separate. Sales, PR and the product drive most branded demand, and SEO rarely creates it. Mixing it in makes the forecast bigger and harder to defend.
What's the best SEO forecasting tool?
A spreadsheet on your own data. Semrush, Ahrefs and SE Ranking help with search volumes and competitor estimates. Treat them as inputs.
What should you do next?
Export a year of Search Console data. Pull last quarter's demo requests and opportunities from your CRM, and check that every conversion counts in GA4. Then build the three scenarios. If you'd like us to build and ship the work behind the forecast, let's talk pricing.