---
title: "Keep key content in the raw HTML"
description: "Crawlers and AI retrieval systems may read raw HTML before executing JavaScript. Server-render the main copy, prices, answers and links, and keep metadata in the initial head. Verify with curl and with JavaScript disabled, and hydrate widgets on top of real markup."
url: "https://seo-mcp.io/t/keep-key-content-in-the-raw-html"
---

# Keep key content in the raw HTML

Crawlers and AI retrieval systems may read raw HTML before executing JavaScript. Server-render the main copy, prices, answers and links, and keep metadata in the initial head. Verify with curl and with JavaScript disabled, and hydrate widgets on top of real markup.

## Prerequisites

- Access to the rendering model
- A representative URL per template

## Steps

1. **Curl a representative page** — Fetch the URL without executing JavaScript and check for the H1, first paragraphs, prices and primary links in the response body.
   Check: The raw response contains the H1 and the first two paragraphs of content.
2. **Move content rendering to the server** — Use SSG or SSR for content routes and keep interactive UI in leaf components. Do not gate essential text behind click-only interactions.
   Check: The raw HTML contains all essential text and links for the template.
3. **Confirm with no-JavaScript browsing** *(general best practice)* — Disable JavaScript and load the page. The user should still read the main content and navigate through links.
   Check: With JavaScript disabled, the page shows the main content and at least one working navigation link.

## Source

@seo-mcp on 2026-10-19: https://developers.google.com/search/docs/appearance/ai-features

Canonical: https://seo-mcp.io/t/keep-key-content-in-the-raw-html