Advisory Note — SEO in the AI Era

How to get technical SEO approved

Lead with the one fix that applies to every template, prove it moved something, then report the win to every team it touched. A backlog of fifty page-level tickets gets parked. One global fix with a before-and-after gets the next one funded.

Most technical SEO work does not die because engineering disagrees with it. It dies in the queue, behind product work that has an owner, a deadline and a revenue number attached. If you run SEO in-house or for an agency client, the audit is rarely the hard part. Getting the fixes shipped is.

Erika Braeger, Director of Strategy at Ten Speed, spends most of her week on exactly this. One of her clients set out to clear two years of technical debt in a single quarter. Her answer to how she gets enterprise teams to say yes is the most useful sequencing advice we have heard on the subject:

“I try to stick with the global items first, the big ticket items, because that’s what’s going to move the needle.”Erika Braeger, Ten Speed

What follows is how we would turn that into a plan you can put in front of an engineering lead and a budget holder.

Technical SEO tickets stall because they arrive as a list

A crawl export turns into a spreadsheet, the spreadsheet turns into forty tickets, and each ticket describes a symptom on one URL. To an engineering manager that reads as forty small, unranked requests from a team that cannot say which one matters. So none of them get prioritised.

The fix is not a better spreadsheet. It is a different unit of work. Engineering plans in templates, components and releases. If your request names a template and says it affects every page built on it, you are speaking their language. If it names a URL, you are asking them to do your triage for you.

Erika’s two most common findings show why this matters. The first is page speed that clients kept deferring until page weight became a problem for crawlers as well as people. The second is redirect debt: a URL gets retired or renamed without a redirect, and because it was linked from all over the site, one decision produces 3xx and 4xx errors everywhere. Both are global problems. Both get reported page by page.

Before any of this, confirm the pages are indexed at all. There is no point arguing for speed on a template Google is not indexing, which is why we put the index check before the strategy.

Sample five pages before you write a single ticket

A single page test is the most common way a technical SEO case falls apart in the meeting. Somebody runs the homepage through a speed tool, it looks fine, and the request is dead. Erika’s recommendation for anyone starting this work is to test a spread of pages instead:

“Don’t sample only a singular page because not every page is going to tell the same story. And if you are checking page speed across, say a sample of four or five pages of your site, then you’re going to be able to identify what the global fixes are and be able to make a bigger impact early on as you work down your list.”Erika Braeger, Ten Speed

Pick one page per major template: a product or service page, a blog post, a category or hub page, a landing page and the homepage. If the same culprit shows up on four of five, you have found a global fix. If it shows up on one, it is a page-level ticket and can wait.

Look at page weight while you are there. Google’s documentation says that Googlebot crawls the first 2MB of a supported file type when crawling for Search. Erika uses two megabytes as the line where she starts asking what is adding the weight: a video, an image, a motion graphic, a form, a reCAPTCHA. A template that sits close to that line is a clear, documented reason to act, and it is a reason that comes from Google rather than from the SEO team.

Then add a comparison. When a client is losing ground, Erika benchmarks page speed against the two or three competitors who have pulled ahead and shows where the biggest gap sits. A leadership team that will not fund “make the site faster” will often fund “close the gap with the competitor who took our position”.

Lead with the fix that makes the biggest splash

Once you know which problems are global, rank them by how many pages they touch and how directly they change what a user or crawler gets. Third-party scripts that fire before the main content, oversized images on a shared template, a hero image set to lazy load, a retired section of the site still linked from pages across it. Each one is a single change with a site-wide effect.

Quote card: Erika Braeger of Ten Speed on working with the pieces that make the biggest splash first to get buy-in for technical SEO
Erika Braeger on the Unscripted SEO Podcast, 2026.

The first fix carries more weight than its own result. It is the evidence you will use to get the second one approved. Erika describes the sequence as a trust-building exercise:

“you really have to work piece by piece and you have to work with the pieces that are going to make the biggest splash first to get buy-in to continue to build trust across the organization before you can go for, I guess, the fruit at the top of the tree.”Erika Braeger, Ten Speed

Our read, and it is a judgement rather than a finding: the highest-value item on an audit is often the wrong first ask. If it needs a re-platform or a quarter of engineering time, it will be deferred. Start with the global fix that is cheap to ship and easy to measure, and save the expensive one for when you have a result to point to.

Bring options, not a demand

Developers know their own environment better than the SEO team does. A request that dictates the implementation invites a debate about the implementation. Erika avoids that by handing the team a range:

“I like to present to them like a good, better, best when it comes to image optimization.”Erika Braeger, Ten Speed

For a heavy template, that might look like this:

  • Good. Compress and correctly size the images already there. Often a plugin or a build step, little engineering time.
  • Better. Make sure lazy loading only applies below the fold, so the hero loads first, and defer third-party scripts until after the main content.
  • Best. Rework the component: replace, modify or remove the element adding the most weight, which is the decision tree Erika works through for any page near two megabytes.

Options change the conversation from “will you do this” to “which of these fits this sprint”. The team keeps ownership of how. You keep the outcome. The same instinct applies to bigger projects, where migrations fail on business goals rather than redirects.

If you want the working method for finding those global fixes, SEO Arcade has a step-by-step SOP for finding global page speed fixes built from the same episode.

Report the first win to every team it touches

The step most SEO teams skip is the one that pays for the rest of the roadmap. When the global fix ships and something moves, the result should not stay in the SEO report. Erika’s practice is to go to all of the teams the win touches, communicate it, and show how each further technical implementation will help them too.

Keep the claim honest. Say what changed, say what moved, and keep the two apart until the data supports joining them. Faster templates can line up with better crawl coverage or conversion, but timing alone does not prove cause. We wrote more about proving value when attribution is gone, and the same rules hold here.

Done well, this turns the SEO team from the department that files tickets into the one that hands other teams wins. That is the trust Erika is talking about, and it is what gets the item at the top of the tree approved.

A technical SEO buy-in plan for your next quarter

If you have one meeting with an engineering lead and a budget holder, bring this:

  • A five-page sample across your main templates, with the problems that repeat marked as global.
  • One global fix, chosen because it touches the most pages and ships fastest, not because it scores highest on the audit.
  • Three options for implementing it, so the team chooses the how.
  • A competitor comparison or a documented threshold, such as Google’s 2MB crawl limit, that makes the case without relying on the SEO team’s word.
  • A date to report back, and a list of the teams who will hear about it.

The rest of the audit can wait. One shipped global fix with a result attached will get you further than the full list sent all at once.

Erika’s full conversation: Erika Braeger on machine readability and page speed on the Unscripted SEO Podcast, and Jeremy Rivera’s take on telling one story to machines. More in our hub on SEO in the AI Era, or bring the sequencing in-house through an advisory engagement or fractional SEO management.
THE SEO ADVISORY
Get to Know Rob Bonham
Fractional SEO Manager & SEO Advisor

Free download

Get to know me — in 5 minutes

How Rob thinks about SEO in the AI era and how he works. No form, no gate.