Skip to content

How Search Engines & AI Crawlers See Your Website

Understanding how Googlebot, Bingbot, GPTBot, and other automated crawlers interact with your pages is essential for modern SEO. This guide walks through what happens when a crawler visits your site — from DNS resolution to JavaScript rendering — with interactive examples you can test yourself.

Last updated April 2026. Based on analysis of 14,200+ crawler sessions across 340 websites using a combination of server logs, real user monitoring, and controlled experiments. Study reference: JLH-CRAWL-STUDY-2026-V3

The Anatomy of a Crawl

Every time a crawler visits your page, a predictable sequence of events unfolds. The differences between crawlers lie in which steps they execute and how deeply they go.

1. Discovery
URL found via sitemap, link, or API
2. Fetch
HTTP request, headers, redirects
3. Render
JavaScript execution, DOM assembly
Crawler JS Rendering robots.txt Avg. Crawl Depth
GooglebotFull (Chromium)Respected4.2 levels
BingbotFull (Chromium)Respected3.1 levels
GPTBotPartialRespected1.8 levels
ClaudeBotPartialRespected1.5 levels
ChatGPT-UserFull (Headless)Respected2.3 levels
CCBotNoneRespected1.0 levels

Data source: JLH-CRAWL-STUDY-2026-V3. Methodology: controlled experiments across 340 sites, Jan-Mar 2026.

Does Your Crawler Execute JavaScript?

One of the biggest differences between crawlers is whether they execute JavaScript. The content below is injected via JS after page load — if a crawler can see it, it has a JavaScript rendering engine.

If you're a crawler without JS support, you'll see this placeholder text instead of the actual data below.

Quick Crawl Tester

Enter a URL to see a simplified view of what a crawler would find. This tool runs client-side only — no data is sent to any server.

Include JavaScript rendering analysis
Crawl Statistics API Dashboard Full Methodology

Related Articles

Live: agents that read this site

last 7 days

Every time an AI agent fetches a Markdown view of a post on jlhernando.com (via Accept: text/markdown, a direct .md URL, or a request for /llms.txt, /llms-full.txt, /SKILL.md, or /.well-known/skills.json) a Netlify edge function fires a server-side Plausible event tagged with the agent's vendor. This chart reads that data back via the Plausible Stats API.

Loading agent traffic…

Page Debug Info

Diagnostic data for this page view (used during development).

session: generating...
load: measuring...
env: detecting...
fp: computing...
fcp: pending...
lcp: pending...
resources: counting...