How To Improve SEO Developer Communication

SEO developer communication fails mostly over missing context, not missing skills, according to Google's Search Relations team. In a 2025 episode of their Search Off the Record podcast, Gary Illyes and Martin Splitt argued that shared technical vocabulary and repeated context turn an adversarial relationship into a working one. This article distills what they said and how to apply it.

What Google's Search team says about SEO developer communication

SEO developer communication, in the view of Google's Search Relations team, works best as a translation exercise between two professional cultures rather than a debate about whose discipline is right. Martin Splitt and Gary Illyes discussed the topic on Search Off the Record, the podcast published by Google Search Central, in an episode released on 12 June 2025 that runs about 31 minutes.

The episode is less a technical tutorial and more a reflection on how the two men talk to developers, SEOs, and digital marketers in their day-to-day outreach work. Splitt, whose background is in web development, described joining the Search team precisely because he had watched developers build things nobody could find. The recurring theme is that advice without context gets misused, and that the person delivering it is responsible for supplying that context.

Why SEOs and developers talk past each other

The friction comes from different mental models of the same system. Developers think in terms of what the code does; SEOs think in terms of how search systems and users encounter the result. Neither model is wrong, but recommendations that ignore the other side's constraints land as criticism.

Splitt's developer background is the reason he can bridge the gap: he speaks the vocabulary, understands build constraints, and can explain what a crawler sees in terms a programmer accepts. The practical lesson for SEOs is not to become engineers, but to learn enough about how the web works that recommendations sound like engineering trade-offs instead of magic rules.

How much technical knowledge should an SEO have?

The episode's most quotable position is scoped deliberately. Splitt argues that an SEO working on technical or general-purpose optimization should understand conceptual fundamentals: what an HTTP header is, how HTTPS and certificates shape a connection, how HTTP/2 differs from HTTP/1.1, how HTML is structured, and roughly how JavaScript interacts with a page. None of this requires writing a crawler in C.

At the same time, he resists turning this into a universal requirement. SEO is a broad field, and specialists who work on content internationalization or localization operate at a layer where deep protocol knowledge adds little. The honest answer to the question is that the required depth depends on which layer of the system your work actually touches.

The context problem: why quotes get taken out of context

Splitt's sharpest anecdote concerns his own slide. Speaking at a technical conference on performance optimization, he put the words "don't use JavaScript" on a slide, knowing the audience knew him as a JavaScript specialist, and then spent roughly five minutes explaining the context: if you can avoid JavaScript for a given task, avoid it, but JavaScript remains necessary for many sites, including anything that must work offline.

The predictable result, he noted, is that the single sentence travels and the context does not, producing claims like "Google says don't use JavaScript." His mitigation is to repeat the context with the conclusion, every time, because he cannot control how a statement is clipped once it leaves the room.

Practical habits for better SEO-developer conversations

The episode suggests a short list of habits any practitioner can copy.

• State the context before the recommendation. A fix that is right for a single-country regulated site can be wrong for a multilingual brand, so say which situation your advice applies to.

• Learn the conceptual stack. Headers, TLS, HTTP versions, HTML, and basic JavaScript behavior are enough to hold an engineering conversation.

• Repeat caveats out loud. If a rule has exceptions, the exceptions travel with the rule or the rule gets misapplied.

• Assume good faith on both sides. The team's framing is that most friction is a vocabulary gap, not an agenda.

None of these habits requires authority or budget, which is what makes them a realistic starting point for teams where SEO and engineering currently tolerate each other rather than collaborate.

Where to hear the full discussion

The complete conversation is available as the Search Off the Record episode published on 12 June 2025 through Google Search Central, with a full transcript provided in the episode's resources. Listening to the full exchange, rather than excerpts, is itself a demonstration of the episode's point: the nuances survive only when the context travels with the words.

FAQ

• Who discussed SEO developer communication on the podcast? Martin Splitt and Gary Illyes, members of Google's Search Relations team, discussed it on Search Off the Record, the podcast from Google Search Central, in an episode released on 12 June 2025.

• Do SEOs need to learn to code? Not necessarily. The recommendation from the episode is conceptual understanding of HTTP, HTTPS, headers, HTML, and JavaScript's role, with coding depth needed mainly by those specializing in technical SEO.

• Why does technical SEO advice get misquoted? Because conclusions circulate without their context. A statement that is correct for one type of site can be harmful when applied to a site with opposite requirements, so the context must be repeated with every statement.

• What is Search Off the Record? It is a podcast series from Google's Search Relations team, published via Google Search Central, covering how Google Search works and how the team communicates with the web community.

Source video