An SEO workshop is a single focused session, usually half a day or a day, in which a group works through your actual site and leaves with decisions made. It is not a course. The output is a plan, not a curriculum.
The distinction from the adjacent formats matters, because they solve different problems:
- SEO training builds capability across a team through a structured curriculum, over weeks or months.
- SEO coaching supports one person or a small team while they do the work, responding to what they are actually facing.
- An SEO consultant for marketing teams works alongside an existing team that owns the channel but lacks search depth.
What a workshop is good at
- Getting a group to agree a direction in one sitting rather than across weeks of email.
- Working through a specific decision, such as a restructure or a migration approach.
- Surfacing disagreement between marketing, development and leadership while everyone is present.
- Producing a prioritised list the room has actually bought into.
- Giving a team enough shared vocabulary to have better conversations afterwards.
It is poor at building deep capability. A day of intensive input does not make anyone an SEO practitioner, and treating a workshop as compressed training tends to disappoint.
Formats that work
Strategy workshop
For teams that need direction. Works through which searches to compete for, which pages should own them, and what order the work happens in. Output is a prioritised target set and a rough sequence.
Technical workshop
For development teams. Works through crawl and indexation findings on your site, why each matters, and what implementation looks like. Output is a set of tickets rather than a report.
Migration planning workshop
Before a replatform or redesign. Works through URL inventory, redirect mapping and pre-launch checks while structure is still changeable. Output is a plan and an owner for each part. Detail is on SEO migration.
Content planning workshop
For content teams. Works through demand, ownership and briefs for a cluster. Output is a set of briefs ready to write against.
Getting value from the day
- Send data in advance, so the session is spent deciding rather than discovering.
- Get decision-makers in the room. A workshop that produces recommendations nobody can approve wastes the day.
- Pick one theme. Trying to cover strategy, technical and content in a day covers none of them.
- Assign owners to outputs before the session ends, or nothing moves.
- Book a follow-up point while everyone is still present.
Frequently asked questions
How long should a workshop be?
Half a day for a single focused decision, a full day where a group needs to work through findings together. Beyond a day, attention drops and the format is usually the wrong one.
Who should attend?
Whoever will implement and whoever can approve. Marketing alone produces plans that stall on development capacity; developers alone produce fixes without commercial priority.
Is a workshop enough on its own?
It is enough to set direction. It is not enough to build capability or to complete the work. Most teams pair a workshop with either implementation support or a longer training programme.
What do we get afterwards?
A written record of the decisions, the prioritised actions with owners, and whatever artefacts the session produced, such as a target set, ticket list or redirect plan.
Consulting CTA
If your team needs to agree an SEO direction and keeps deferring the decision, book an SEO consultation to scope a workshop around the specific choice you are stuck on.