సందర్శకుల కోసం జావాస్క్రిప్ట్. క్రాలర్ల కోసం HTML.

No. Any JavaScript frontend has the same crawler problem. Connect a site key for your domain and route bots. Commerce SDK and WordPress are first-party hosts. SDK pages wait for a ready event so catalog HTML is complete. Other JavaScript on that domain snapshots after the render budget.

No. The Render Engine inspects the user-agent and only snapshots matching crawlers. Visitors keep the live JavaScript site, including cart and checkout when those are on the page.

Search engines (Google, Bing, DuckDuckGo, Yandex, Baidu) and social unfurlers (Facebook, LinkedIn, X, WhatsApp, Slack, Discord, Pinterest, Telegram). The WordPress plugin also routes common AI crawlers such as GPTBot and ClaudeBot. Cloudflare and Lesuto-hosted routing stay on the search plus social list unless you change that Worker on purpose.

SEO audit tools (Ahrefs, Semrush, Screaming Frog) are classified in the dashboard and are not prerendered, so they cannot spend render capacity. AI crawlers are classified everywhere. Only the WordPress plugin host hook prerenders a common AI set today.

The API returns 403 when the hostname is not on the site key, and 502 or 503 when a render fails. Your Worker or plugin then serves origin HTML so crawlers are not left with a blank error page.

Successful snapshots are cached for 24 hours. Catalog changes invalidate the cache. The first crawl for a URL runs a headless browser (12 second budget). Later crawls are served from cache.