Your Website Studio site is built to be crawlable by Google and Search Atlas. LLMs like Claude, ChatGPT, and Gemini use crawlers that do not execute JavaScript, so they may not read JS-rendered pages. A previous rendering issue affecting JS-hosted pages on custom subdomains has been resolved — if you experience blank-page crawl results, verify your site is on the latest version.

🔍 How Search Atlas Confirms Your JS Site Is Crawlable

Both Site Audit and Site Explorer in Search Atlas support JavaScript rendering, allowing them to crawl your Website Studio site exactly as Google does. Google's Rich Results tool has also been confirmed to crawl and process the site successfully.

To verify crawlability yourself, run a Site Audit on your domain with JavaScript rendering enabled. JavaScript rendering is not on by default — you must enable it manually in Site Auditby going to OTTO SEO → Site Audit → Select your project→ OTTO Settings→ Crawl Parameters→ Toggle on JavaScript Rendering. A clean audit with no JS-rendering errors confirms your site is fully accessible to search engine crawlers.

Note: For sites using pixel or manual-script OTTO installation, Site Audit title data may not always reflect OTTO-deployed titles in real time. For the most accurate live-state verification, cross-check results with Google Search Console or Google's Rich Results tool.

🤖 Why Claude, ChatGPT, and Gemini Cannot Crawl Your JavaScript Site

LLMs like Claude (Anthropic), ChatGPT (OpenAI), and Gemini (Google) use lightweight HTTP crawlers that do not execute JavaScript. When these tools request a JS-rendered page, they receive only an empty HTML shell — making the page appear uncrawlable or blank to them.

This is primarily a limitation of those external tools. That said, a previous architectural issue caused JS-hosted pages on custom subdomains to return a near-empty HTML body (with only a title, meta description, and a 'JavaScript Required' notice) to all bots — this has been resolved (LPS-864). If you still see blank crawl results, ensure your site is on the latest version. Additionally, if your site appears in Google under a Search Atlas domain rather than your custom domain, this is a known issue (now resolved, LPS-911) — please contact support if you encounter it.

• Google and Bing — execute JavaScript and index your site normally.
• Search Atlas Site Audit and Site Explorer — JavaScript rendering must be enabled manually in Site Audit settings (Settings → Crawl Settings → JavaScript Rendering); once enabled, your site is fully crawlable.
• Claude, ChatGPT, and Gemini web browsing — no JavaScript execution; these tools cannot read JS-rendered pages.

🔗 Why Search Atlas Preview URLs Appear in Google Search Results

If you see Search Atlas preview URLs appearing in Google search results for your domain, this is a temporary indexation delay. Google crawled and cached the preview URL before your live pages were fully indexed. These entries clear automatically once Google indexes the correct live pages for your domain.

To speed up this process, submit the affected pages for indexing directly through your OTTO project.

Note on og:url and canonical tags: Your og:url and canonical tags should reflect your custom domain. If the Search Atlas builder subdomain appears in og:url or canonical tags, please contact support — this was a known bug (LPS-864) that has been resolved.

⚙️ How to Submit Pages for Indexing via OTTO

1. Open Search Atlas and navigate to the OTTO project for the affected domain.
2. Identify the specific pages where Search Atlas preview URLs are appearing in Google.
3. Select those pages and click Submit for Indexing.
4. Google will prioritize re-crawling those URLs and replace any cached preview entries with your live pages.

Once Google processes the indexing requests, the Search Atlas preview URLs will no longer appear in search results for your domain.

🛠️ Troubleshooting: Site Audit Still Shows Blank Pages or JS Errors

1. Confirm JavaScript rendering is toggled on in Site Audit settings (Settings → Crawl Settings → JavaScript Rendering).
2. Re-run the crawl after any OTTO deployment so the audit reflects the latest live state.
3. Verify your custom domain's canonical and og:url tags point to your custom domain — not the Search Atlas origin or builder subdomain.
4. If blank pages persist after these steps, contact support so the issue can be investigated.