Training · In-house teams
Technical SEO for people whohave to brief developers.
The gap in most teams is not knowing that technical SEO matters. It is being able to explain precisely what needs changing, why, and in language a developer can build from. That is what this session is for.
Your site, crawled beforehand
previewPages migrated personally
2,000+
No noticeable organic drop
Who this is for.
It works best with marketing and web people in the same room, which is rarer than it should be.
Marketers who cannot get changes built
You know the site has problems. The tickets you raise get deprioritised or misunderstood, because the request is not specific enough to action.
Developers handed vague SEO tickets
‘Improve page speed’ and ‘fix canonicals’ with no context. Understanding why it matters makes the work far easier to prioritise and get right.
Teams planning a replatform
The most valuable time to learn this is before the new site is specified, when the knowledge can prevent a traffic loss rather than explain one.
Content teams publishing into a void
You are producing decent content that never ranks, and nobody has explained that the problem is structural rather than editorial.
How the session works.
Your site is the case study
I crawl your site before the session and build the day around what it shows. Your rendering issues, your orphan pages, your redirect chains. Generic technical SEO training produces people who can recite the concepts but freeze in front of their own crawl data.
- Full crawl of your site before the session, with findings built into the agenda
- Real diagnosis worked through together rather than sample data
- A prioritised list of issues on your site when we finish
- Ticket templates your team can use to brief the work properly
Crawl findings, typical
Site sizes worked on
2,000+
Pages, migrated and audited
Taught by someone who writes the fixes
I work in Laravel, Statamic, Shopify and JavaScript day to day. That changes how this gets taught, because I can explain what a fix actually requires from a developer and why some requests are trivial while others mean a fortnight of work.
- What is genuinely easy to implement and what is not
- How to write a ticket a developer can build from without follow-up questions
- JavaScript rendering explained by someone who writes JavaScript
- Realistic prioritisation based on effort as well as impact
Years writing code
4+
Front and back end
What the session covers.
Adjusted to your site type and your team’s level after a short scoping call.
- How crawling, rendering and indexing actually work
- Reading Search Console index coverage properly
- Running and interpreting a crawl
- Log file analysis and crawl budget in practice
- JavaScript rendering and what Google actually sees
- Canonical tags, parameters and duplicate content
- Redirects, chains and when each type is correct
- Site migrations: the full pre-launch checklist
- Internal linking as architecture rather than decoration
- Site structure, taxonomies and pillar and cluster models
- Structured data and schema in practice
- Core Web Vitals with a sense of proportion
- International and hreflang setups
- Keyword research and mapping intent to page types
- Briefing content that has somewhere to sit
- Writing technical tickets developers can act on
If a migration or replatform is coming up, we can weight the whole session towards that. It is the highest-value version of this training by a distance.
Nine years of technical SEO.
Agency side auditing multinational e-commerce, in-house owning migrations end to end.
2,000+
Page site migrated including redirects and DNS with no noticeable drop in organic traffic
SPA
Angular single-page application diagnosed and resolved for client-side rendering and indexability
9 yrs
Technical and content SEO across agency and in-house, UK and Australia
4+ yrs
Writing production code, which is why the developer-facing modules are practical
Client names withheld under agency and contract terms. Happy to talk specifics on a call.
How a session gets organised.
Two conversations, a crawl, and a date.
A scoping call
Twenty to thirty minutes. Site platform and size, who is attending, and whether a migration is on the horizon. Free.
Preparation
I crawl your site and review Search Console, then build the session around the real findings rather than a generic agenda.
The session
Half day or full day, in person or remote. Working through your own crawl data, with the team doing the diagnosis.
Follow-up
Materials, a prioritised issue list for your site, ticket templates, and a window for questions.
Whether this session will pay off.
Technical SEO training only helps if somebody can act on it afterwards.
This is a good fit if
- You have a large, technical or JavaScript-heavy site
- A migration or replatform is coming in the next six to twelve months
- Your team can get development work prioritised, or does it themselves
- Marketing and web people can attend together
- You keep receiving SEO audits and nothing ever gets implemented
Call someone else if
- You have a small brochure site with no real technical complexity
- Nobody can get development changes made regardless of how well they are briefed
- You need rankings improved this quarter — that is a project, not a training day
- You are looking mainly for content and copywriting training
- You want link building, which is not what this covers
Trainingquestions.
Something not covered? Ask me directly — you will get a straight answer, not a proposal.
Should developers attend as well as marketers?
Ideally yes. The single biggest gain in these sessions is marketing and web people finally understanding each other's constraints. Developers usually find the crawling and rendering modules genuinely interesting once they see what the crawler receives.
Do we need SEO tools already?
No. I will run the crawl and share the findings. We can cover which tools are worth paying for, but plenty is achievable with Search Console and a free crawler tier.
How technical is it?
Pitched so a non-technical marketer can follow every module, with enough depth that a developer is not bored. That balance is the whole design of the session.
We are replatforming soon. Is this useful?
It is the best possible timing, and I would weight the session heavily towards migration planning. A day spent before the specification is written is worth considerably more than a recovery project afterwards.
Do you cover content and keyword research?
Yes, the structural half of it — intent mapping, page type planning, internal linking and briefing. Not copywriting craft, which is a different skill and a different trainer.
Can you just do the SEO work instead?
Yes, that is the main service. Many teams do an audit first and training afterwards so they can maintain the site without regressing.