Do AI crawlers execute JavaScript?

Why this matters more than it sounds

In plain terms: a lot of website tools do not really change your website. They add a small piece of code to it that rewrites your pages while a visitor is looking at them — the page arrives plain, and the tool redecorates it a moment later in the visitor’s browser.

For Google that mostly works, because Google waits for the redecorating to finish. AI assistants do not wait. They take the page exactly as it arrives and read that. Anything the tool would have added never happens as far as they are concerned.

Which leads somewhere uncomfortable. Tools sold on the promise of getting you mentioned by ChatGPT, that deliver it by redecorating pages in the browser, are making changes that the one audience they are sold for cannot see.

The expensive workaround has its own problem

The big-budget alternative is to send one version of the page to the robots and a different version to people. That does solve the reading problem, but now your visitors and the search engines are being shown different things. Google stopped recommending this approach and calls it a workaround rather than a solution — and showing search engines something different from what customers see is uncomfortably close to a practice they penalise sites for.

What this means in practice

If you want AI assistants to be able to read you, the improvement has to be part of the page that arrives — the same page, for everyone, every time. That means changing the website itself rather than layering something on top of it, which is why we change your site directly rather than bolting a script onto it.

There is a quieter benefit too. A change made to your website belongs to you. A change performed by somebody’s script stops happening the day you stop paying for it.