prerender[ OBSERVATORY ]
[ Field guide ]

Every machine reads your site differently

Machines: crawlers, AI answer engines, agents. Each one connects, asks and renders in its own way, so each one sees a different version of your pages. This is a field guide to them: who runs each one, how to verify it, and whether it runs your JavaScript.

18

machines documented, from Googlebot to Slackbot, each checked against its operator's own documentation.

[ Machines ]

The machines

Who sends each one, what it's for, and whether it renders JavaScript.

View all 18 →
[ Guide ]

Anyone can say they're Googlebot

How to check the machines that publish a way to verify them, and what to do about the ones that don't.

Read the guide →
[ Guide ]

robots.txt for AI answer engines

Training, search and on-demand fetches come from different machines. Block each one on purpose.

Read the guide →

What a machine sees decides what it can cite

A page that renders in Chrome can arrive empty for a machine that doesn't run JavaScript. A site that blocks one AI crawler can still be fetched by the same company's on-demand agent.

Machine experience starts with knowing which machine is which, and what each one gets when it arrives. Every page here names the machine, its operator and the operator's own source.

What a machine sends

Googlebot smartphone · user agent
Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

As Google documents it. W.X.Y.Z is the Chrome version Googlebot renders with, which follows the current stable release.

How this site works

This site records how each visiting machine connects and what it does here, and these pages grow from what it sees. Records are deleted after 90 days.

What we record, and why →