In Google’s new episode of its official podcast “Search Off The Record” the spotlight shifts to the often unspoken cultural divide between developers and SEO professionals. 

In the insightful conversation, Gary Illyes and Martin Splitt from the Google Search Relations team open up about the real-world challenges, misperceptions and sometimes awkward misalignments between SEO and development teams. 

So, what are the biggest misunderstandings between SEOs and developers and what does Google really think about bridging this gap?

Toggle

Free SEO Audit: Uncover Hidden SEO Opportunities Before Your Competitors Do

Gain early access to a tailored SEO audit that reveals untapped SEO opportunities and gaps in your website.

Analyze My Site

Developer vs SEO- Not Enemies, But Misunderstood Partners

“I’m putting myself in between the two sides. It feels like there’s a bit of a divide between developers and SEOs.” – Martin Splitt 

One of the most important discussions in the episode centers around the tension between developers and SEOs, two roles that share the same digital goals but rarely speak the same technical language. 

Martin, a developer himself, now advocates SEO best practices to a technically-savvy dev community. 

Yet, he notes how many developers remain skeptical of SEO as a discipline and seeing it as ambiguous or marketing-oriented. 

“He’s a developer, he’s one of us… but now he talks about this weird, snake-oily kind of thing,” says Martin, mimicking the typical dev reaction to SEO suggestions. 

This quote sums up a major hurdle that SEOs often approach developers with solutions that sound vague, lack technical clarity or don’t consider engineering constraints. 

The result? A trust gap. 

The solution? Technical SEO implication. 

SEOs need to frame their requests within dev-friendly logic e.g., reducing render-blocking scripts because it lowers Time to Interactive (TTI) not just because “Google wants speed.” 

Why Google’s JavaScript Expert Warns SEOs About Context and Misused Advice

“You know me as the JavaScript guy at Google.” – Martin Splitt 

Martin’s reputation in the industry is built on making JavaScript rendering more accessible for SEOs. But in the episode, he cautions against taking his own quotes out of context. He references a slide he once showed at Tech SEO Summit:  

“Don’t use JavaScript.”

– (But he immediately adds) “There’s context missing here.” 

Why does this matter? Without context, advice like “avoid JavaScript” can be dangerously misleading. In reality, Martin was explaining that if a function does not need JavaScript, use HTML/CSS instead. This improves crawlability, rendering speed and accessibility. 

One of the examples we can take from this situation is that Googlebot uses Chrome-based rendering, which can take days post-crawl to render JavaScript-heavy pages. If JavaScript controls critical content or links, there is a risk of it being delayed or ignored in indexing.  

Thus, SEOs must understand when and where JavaScript is helping or hurting SEO performance and communicate the same clearly to developers. 

The Challenge of Giving Public Advice in SEO Forums

“The problem is when someone hears our response, takes it out of context, and applies it to an entirely different case.” – Martin

Gary and Martin explore a key challenge: SEO advice and especially from Googlers, often gets generalized or misapplied. 

For example, they mention scenarios where a Googler gives an answer tailored to one use case (say, a large eCommerce site in a multilingual setting but that response gets repeated by consultants working with local blogs or government sites and leads to incorrect implementations. 

“Someone else might listen… whose client might have the opposite needs… and that might actually be harmful,” Martin explains.

So what is the actionable insight? When SEOs hear advice (from Google or otherwise), they must:

• Ask: What context does this apply to?
• Validate: Is this applicable to my tech stack and content model?
• Document: Can I explain this recommendation with technical logic? 

Why SEOs Must Learn Developer Fundamentals

“To optimize a system deeply, you must understand some of the characteristics of that system.” – Martin

Martin makes a crucial point: SEOs do not need to become developers but they need dev literacy. Understanding HTTP protocols, headers, caching behavior or how HTML interacts with JS can save teams hours and prevent costly errors.

Gary adds to this with a painful real-world example: 

“A large agency installed a random calendar plugin… and we discovered 100 million new URLs.”

What happened? That plugin generated infinite dynamic URLs. As a result, Googlebot crawled millions of unnecessary pages, wasting crawl budget and skewing analytics. The agency blamed Google but it was a lack of technical foresight that triggered the disaster.

Technical lesson: Understand how plugins, JavaScript and dynamic parameters can affect:

• Crawl Budget
• Canonicalization
• URL Discovery
• Site Performance

The Struggle of Communication Across Technical SEOs vs Developers

“Slides without context are useless.” – Martin Splitt

Martin and Gary emphasize that communication, not just knowledge, is what breaks or builds SEO results. The tension comes from SEOs wanting action and developers needing clarity.  

Martin shares how difficult it is to speak to audiences with diverse agendas and understandings. A dev audience may focus on site speed and performance. SEOs may push for structured data or keyword-rich content. Unless there is mutual context, no one wins.

“Sometimes people flex technical knowledge… and it prevents me from helping them.” – Martin 

This highlights another overlooked issue: false confidence in SEO forums. When someone pretends to understand dev concepts they actually don’t, they create friction. Worse, they block learning. 

Why Google Doesn’t Share Slides & Why You Shouldn’t Share Advice Without Context 

“That’s why we don’t share our slides.” – Gary

Gary and Martin explain that slides especially from Google talks can easily be misunderstood if detached from speaker narration. This underscores a broader point:

SEO is context-sensitive. One-size-fits-all advice often causes harm. 

 Why Even Google Can’t Give Straight Answers to “It Depends” Dilemma

“Maybe we should stop saying ‘It depends’… and actually explain what it depends on.” – Gary 

The conversation moves toward one of SEO’s most mocked phrases: It depends. While it is true that every site is different and the Googlers acknowledge that relying on vague language causes frustration.

Instead, they recommend offering dependencies and scenarios:

• Instead of “Avoid JavaScript,” say: “Avoid it when the content is static and does not require client-side interactivity.”
• Instead of “Improve performance,” say: “Reduce CLS and LCP by lazy-loading non-critical images and avoiding layout shifts.”

This move toward specificity helps both developers and SEOs execute better strategies

How Can SEOs Improve Dev Collaboration?

Here are a few actionable insights directly implied in the episode:

• Learn enough technical basics to speak dev language. 

Know how server-side vs client-side rendering works. Understand what DNS, CDN and header responses mean.

• Provide context when making SEO requests. 

Instead of “please add structured data,” explain: Structured data helps Google better understand our product catalog. It improves rich snippets and CTR by 30%+.

• Avoid blanket statements. 

SEO advice should always include: “if applicable,” “depending on your CMS” or “within this server architecture.”

• Don’t pretend to know everything. 

As Martin puts it: “It’s OK not to know. It is dangerous to think you know and block better understanding.

Bridging the Gap Requires Empathy and Precision

“Everyone has an agenda. Ours is building the best search engine.” – Martin

The conversation ends on a philosophical note. Yes, Google has goals to make the web faster, accessible and useful. Yes, SEOs have their own traffic, visibility and rankings. But the only way forward is to collaborate, not confront.

“Behind the advice are real people. And sometimes, we are just trying to make the web a little bit better.” – Martin Splitt