Technical SEO audits are long. The typical crawl output for a mid-size site produces hundreds of flagged issues, and most of them do not matter. The hardest skill in technical SEO is not finding problems — it is knowing which ones to fix first and why. That is what this talk is about.

The Problem With Most Technical SEO Presentations

A lot of technical SEO content is structured around completeness rather than prioritization. Here is every possible issue your site might have. Here is how to check for each one. That is useful as reference material. It is not useful as a talk because it does not help an audience decide what to do Monday morning when they have limited developer time and a backlog of competing projects.

The talk I give is built around a different question: if you had thirty hours of engineering time to spend on technical SEO right now, what would you fix? I work through the reasoning in front of the audience, using real examples, so they leave with a prioritization framework they can apply to their own sites, not just a list of issues I have seen elsewhere.

The other failure mode I see in technical SEO presentations is treating the crawler output as the source of truth. Screaming Frog or Sitebulb will flag a missing meta description on a paginated archive page with the same visual weight as a broken canonical on your highest-traffic landing page. Those are not the same problem. A talk that does not teach the audience how to weight issues is producing anxiety, not direction.

What the Session Covers

  • Crawl budget and indexation basics. Most sites waste crawl on pages that should not be indexed. I cover how to identify that waste and what to do about it without breaking anything.
  • Core Web Vitals in practical terms. Not the metrics themselves but the specific implementation patterns that most reliably improve them: image loading, render-blocking resources, server response times. The things that actually show up in the data.
  • Internal link architecture. How link equity moves through a site and where most sites accidentally starve their best pages of it. This is underrated as a lever and I give it more time than most talks do.
  • Structured data gaps. Technical SEO and schema markup are more connected than most practitioners treat them. I cover the structured data issues that show up in audits most frequently and what they cost in terms of visibility.
  • Log file analysis basics. How to read server logs to see what Googlebot is actually doing on a site, which is often different from what the crawl simulator shows.

A Real Example of the Prioritization Framework

I ran an audit for a SaaS company last year whose crawl output returned over four hundred flagged items. Their developer wanted to know where to start. We went through the list and collapsed it to eight items. Of those eight, three were responsible for the majority of the indexation and ranking problems: a noindex directive that had been left on a subdirectory of product pages after a staging migration, a redirect chain that was stripping link equity from their highest-authority content, and a Core Web Vitals failure on mobile caused by a single third-party script loading synchronously.

Fixing those three things — which took about twelve hours of developer time spread across two weeks — moved organic traffic measurably within six weeks. The other five items on the short list were worth doing, but they could wait. The remaining three hundred ninety-plus items from the original crawl have been waiting for two years and will continue to wait. That kind of triage is the skill the talk is designed to develop.

What Gets Left Out and Why

I do not spend time on canonical tags as a standalone topic unless the audience is in e-commerce and has a specific duplication problem. I do not go deep on hreflang unless we are talking about multilingual sites. These are real issues for specific situations, but they are not the highest-leverage fixes for most rooms. Being explicit about scope is part of how the talk earns trust with a technical audience. They know when a speaker is padding.

I also do not spend time on PageSpeed Insights scores as a target number. Chasing a score is not the same as improving user experience, and audiences that have spent time on Core Web Vitals already know that optimizing for the lab metric sometimes diverges from what the field data shows. I focus on field data — CrUX data, Search Console Core Web Vitals report — because that is what Google is actually using.

Format Options

This session works as a forty-five to sixty minute keynote with a Q and A. It also works as a half-day workshop where I bring participants through an actual audit of a site — ideally one submitted in advance — and we work the prioritization framework in real time. The workshop format is more useful for teams who want to build the skill rather than just understand the concept.

Honest Expectations for the Audience

This talk is not going to be useful for a room full of beginners who have never opened a crawl tool. The prioritization framework assumes you know what a redirect chain is and roughly why crawl budget matters. If the audience is earlier in their SEO education, I have a different version of this talk that builds more foundational context before getting into triage. Most conference organizers know their audience well enough to tell me which one fits.

It is also worth being clear that technical SEO alone rarely explains a large ranking movement. The fixes I cover are necessary conditions, not sufficient ones. A site with good technical health that has weak content or poor link authority will still underperform. I say this in the talk because I think audiences respect honest scope-setting, and because it means they leave with an accurate picture of what these fixes will actually do.

Who Benefits Most

Technical SEO talks land best with audiences that include developers, SEO practitioners, and technical marketers. They also work well for product managers who are responsible for site performance and need to understand what SEO is actually asking for when it submits a ticket.

For a more hands-on format, the post on an SEO workshop for teams covers what a full-day structured session looks like. For a broader overview of the talk formats I offer, the SEO speaker page is the right starting point. The work behind this talk comes directly from client audits through Salterra and the curriculum I run through SEO University.

If you are booking for a technical conference or want a session that goes further into implementation than most SEO talks do, this is the format built for that.