The SEO Podcast: Page 2 Podcast Hosted by Jon Clark & Joe DeVita
Jul 20, 2026 · 1 hr 1 min · 17 segments
https://page2pod.com - JavaScript isn't breaking your SEO — rendering is. Merj R&D Director Giacomo Zecchini on what Google and AI crawlers actually see. Giacomo Zecchini has…
Giacomo ZecchiniGuest
John ClarkHost
Joe DeVitaHost
Welcome to the Page Two podcast, where we uncover the strategies, systems, and tactical decisions that move brands beyond Page Two and into real visibility across search and answer engines.

Today, we're talking with Giacomo Zucchini, R&D Director at Merge, and this is one of the more technical conversations we've had on this show.

Giacomo spends his time taking apart the machinery behind modern search visibility.

how Google renders pages, how AI bots fetch content, why JavaScript is often blamed for problems that are really implementation issues, and what happens when your site is technically there but functionally invisible to the systems trying to understand it.

Rendering, for example, is the process where a browser or crawler turns HTML, CSS, JavaScript, and API calls into the final page that a user sees.

The DOM or document object model is basically the structured map of everything on that page.

And when Giacomo talks about things like viewport expansion, lazy loading, ARIA labels, markdown, and server log analysis, he's really talking about one core issue.

Can machines reliably access, interpret, and act on your content? That question matters because Google is still dominant, but it is no longer the only audience.

Some agents rely on accessibility labels to click buttons, fill out forms, or complete tasks.

And if those signals are wrong, missing, or fragile, the consequences are not theoretical.

An agent might misunderstand your site, skip your content, or even take the wrong action.

What makes Giacomo's perspective so useful is that he is not chasing the shiny object.

Clean implementation, rollback plans, crawl efficiency, accessibility, performance, and testing that actually prove something.

The tension in this conversation is that everyone wants to optimize for the future of AI search, but a lot of websites still have a basic technical debt that makes them hard for today's crawlers to understand.


And honestly, that is where a lot of the most important decisions are being made right now.
Read the full transcript.
Create an account to read the whole episode, search across every transcript, and follow the shows you care about.

Welcome to the Page Two podcast, where we uncover the strategies, systems, and tactical decisions that move brands beyond Page Two and into real visibility across search and answer engines.

Today, we're talking with Giacomo Zucchini, R&D Director at Merge, and this is one of the more technical conversations we've had on this show.

Giacomo spends his time taking apart the machinery behind modern search visibility.

how Google renders pages, how AI bots fetch content, why JavaScript is often blamed for problems that are really implementation issues, and what happens when your site is technically there but functionally invisible to the systems trying to understand it.

Rendering, for example, is the process where a browser or crawler turns HTML, CSS, JavaScript, and API calls into the final page that a user sees.

The DOM or document object model is basically the structured map of everything on that page.

And when Giacomo talks about things like viewport expansion, lazy loading, ARIA labels, markdown, and server log analysis, he's really talking about one core issue.

Can machines reliably access, interpret, and act on your content? That question matters because Google is still dominant, but it is no longer the only audience.

Some agents rely on accessibility labels to click buttons, fill out forms, or complete tasks.

And if those signals are wrong, missing, or fragile, the consequences are not theoretical.

An agent might misunderstand your site, skip your content, or even take the wrong action.

What makes Giacomo's perspective so useful is that he is not chasing the shiny object.

Clean implementation, rollback plans, crawl efficiency, accessibility, performance, and testing that actually prove something.

The tension in this conversation is that everyone wants to optimize for the future of AI search, but a lot of websites still have a basic technical debt that makes them hard for today's crawlers to understand.


And honestly, that is where a lot of the most important decisions are being made right now.