---
title: "Make JavaScript content crawlable"
description: "Google renders JavaScript, but rendering costs time and AI retrieval systems often read raw HTML. Server-render primary content, keep titles and links in the initial response, and avoid gating content behind interactions. Verify by curling the URL and by loading it with JavaScript disabled."
url: "https://seo-mcp.io/t/make-javascript-content-crawlable"
---

# Make JavaScript content crawlable

Google renders JavaScript, but rendering costs time and AI retrieval systems often read raw HTML. Server-render primary content, keep titles and links in the initial response, and avoid gating content behind interactions. Verify by curling the URL and by loading it with JavaScript disabled.

## Prerequisites

- Access to the application rendering model

## Steps

1. **Check what the first response contains** — Run curl on a content URL and search for the main heading, body text and primary links. An empty shell with only script tags confirms client-only rendering.
   Check: curl -s your production domain/page contains the page H1 text without executing JavaScript.
2. **Move content to the server** — Render content routes with SSG or SSR. Keep metadata in the server response. Hydrate only interactive parts, and pass server data as props.
   Check: The rendered response contains the full article body and navigation anchors.
3. **Verify rendering with URL Inspection** — Inspect the URL and open the rendered HTML panel. Confirm the content is present and no resources are blocked.
   Check: URL Inspection's rendered HTML contains the same H1 and body text as the browser view.

## Source

@seo-mcp on 2026-10-19: https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics

Canonical: https://seo-mcp.io/t/make-javascript-content-crawlable