Course lesson · Senior-Leader
12-month Roadmap
A 12-month GEO roadmap usually moves through four stages: set baselines and fix access in quarter 1, improve priority pages and accuracy in quarter 2, build authority and scale in quarter 3, and optimise and report on results in quarter 4. Each quarter needs clear milestones, owners and metrics, and the plan should be reviewed each quarter against real data.
In this lesson
- Why a roadmap matters
- What to do in each quarter
- Milestones, owners and resources
- Reviewing and adjusting
- Exercise and quiz
Why do you need a roadmap?
Without a roadmap, GEO turns into reacting to the latest screenshot. A roadmap helps you set priorities, get resources approved and show progress. It also helps other teams, such as product, PR and support, plan their part.
What happens in quarter 1?
Foundations
- Build the prompt set and run baseline scans
- Check AI crawler access in robots.txt for the bots you want, such as OAI-SearchBot (OpenAI)
- Set up GA4 AI referral tracking (Google)
- Add "AI assistant" to the "How did you hear about us?" field
- Audit the accuracy of AI answers about your brand
- Agree the KPI tree with leadership
Milestone: baseline report approved.
What happens in quarter 2?
Quick wins
- Rewrite the top 10–20 priority pages with answer-first structure
- Fix wrong facts on your site and the profiles you control
- Add accurate structured data where it fits (Google)
- Publish missing comparison and use-case pages
- Run one controlled experiment
Milestone: first measured improvement on priority prompts.
What happens in quarter 3?
Authority and scale
- Digital PR and expert contributions for cited publications
- Original research or data assets
- Review and community programmes
- Extend the prompt set to new personas, regions or engines
- Train content and product marketing teams
Milestone: share-of-voice gain against the main competitor.
What happens in quarter 4?
Optimise and prove value
- Refresh pages that have dropped
- Double down on the experiments that worked
- Report full-year results against the KPI tree
- Plan next year's budget and priorities
Milestone: year-end board report and next-year plan.
How do you resource the roadmap?
| Workstream | Owner (example) | Support |
|---|---|---|
| Measurement | GEO lead | Analytics |
| Technical access | SEO / web team | Engineering |
| Content | Content lead | Product marketing, experts |
| Authority | PR lead | Partnerships, community |
| Reporting | GEO lead | Finance, sales ops |
How do you keep the roadmap realistic?
- Limit priorities: three to five per quarter
- Build in buffer for platform changes and surprises
- Review quarterly: keep goals stable, change tactics
- Track dependencies: engineering time, legal reviews, budgets
What risks should the roadmap plan for?
| Risk | Early warning | Response |
|---|---|---|
| Platform change | New AI features or crawler rules | Review access and rerun the baseline |
| Model update | Sudden shifts across many prompts | Note the date; wait for a trend before reacting |
| Engineering capacity | Tickets slipping | Prioritise access fixes over nice-to-haves |
| Budget cut | Mid-year reforecast | Protect measurement and priority pages first |
| Inaccurate AI answers | Spike in support or sales complaints | Trigger the correction process |
How do you communicate the roadmap?
Share a one-page version with every team involved. Show the four quarterly themes, the milestones, the owners and the dependencies. Update it after each quarterly review and keep earlier versions, so changes are visible and explained.
What does a good first-year outcome look like?
Not every metric will move. A realistic first year usually delivers a reliable baseline and measurement routine, accurate answers about your brand on the engines that matter, measurable gains on a focused set of priority prompts, and a team and process that can scale. Set those expectations with leadership in quarter 1, so the year-end review judges the plan against what it promised rather than against hype.
A quick example
Illustrative. A SaaS company's roadmap commits to a baseline by March, 15 rewritten priority pages by June, two research reports by September and a board review in December. At the Q2 review, comparison prompts show the biggest gap, so Q3 adds three comparison pages and moves one PR campaign to Q4.
Roadmap checklist
- [ ] Four quarters with clear themes
- [ ] Milestone for each quarter
- [ ] Owners for each workstream
- [ ] 3–5 priorities per quarter
- [ ] Dependencies listed
- [ ] Quarterly review dates booked
Exercise
Draft the 12-month roadmap with quarterly milestones.
- Write one theme and one milestone per quarter.
- List three to five actions per quarter.
- Assign an owner to each workstream.
- Note the biggest dependency or risk for each quarter.
- Book the quarterly reviews.
Quiz
- What is quarter 1's focus?
a) Foundations and baselines b) Year-end reporting c) Hiring an agency only Answer: a
- What's a typical quarter 2 milestone?
a) First measured improvement on priority prompts b) A rebrand c) Closing the project Answer: a
- How many priorities per quarter?
a) 3–5 b) 20 c) 1 for the whole year Answer: a
- What should change at a quarterly review?
a) Tactics, while goals stay stable b) All goals c) Nothing Answer: a
- Why build in buffer?
a) For platform changes and surprises b) To slow the team c) For holidays only Answer: a
Next: Lesson 9: Governance, ethics and legal
Sources
- OpenAI, Overview of OpenAI crawlers
- Google, Custom channel groups in GA4
- Google Search Central, Introduction to structured data
Questions
How long does GEO take to show results?
Accuracy fixes and page updates can show up within weeks for engines that search the web; broader reputation gains usually take several months.
What should the first quarter focus on?
Baseline measurement, a prompt set, technical access checks and quick wins on priority pages.
How often should the roadmap be revised?
Review it quarterly, keeping the goals stable and adjusting tactics based on results.