# JavaScript SEO: checking rendered content

> Distinguish served HTML, the browser DOM and Google’s rendering output when investigating content that depends on JavaScript.


**JavaScript SEO examines whether search engines can process content and links that depend on scripts.** Google can execute JavaScript. A working page in your browser still does not establish that its resources, data and content are available during Google's processing.

## The timetable that appears later

This teaching example separates two stages. The server delivers a class page with placeholder text and a JavaScript file:

```html
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Schedule demonstration</title>
</head>
<body>
<main>
<h1>Pottery workshop</h1>
<p id="schedule">Loading schedule…</p>
</main>
<script src="/schedule.js"></script>
</body>
</html>
```

The `schedule.js` file contains:

```javascript
document.querySelector('#schedule').textContent =
'Saturdays, 10:00 to 12:00. No experience required.';
```

The response HTML includes “Loading schedule…”. After the script executes, the browser DOM contains the timetable. To reproduce it, save the first block as `index.html` and the second as `schedule.js` in an empty temporary folder. With Python 3 installed, open a terminal in that folder and run `python3 -m http.server 8000 --bind 127.0.0.1`. Open `http://127.0.0.1:8000/`: the schedule should replace the placeholder. Temporarily rename `schedule.js` and reload without cache to observe the failure, then restore the filename. The `/schedule.js` path looks for the file at that server’s root. This demonstrates rendering; it is not a test of how Google processed a public website.

If the resource fails, is blocked or requires a session Google does not have, the result can differ. The review should establish which essential information depends on that stage and what evidence supports its availability.

## Three views, three different questions

**Served HTML:** establishes what the server initially returns. Save the final URL's response and check for the title, main content and links. An absent timetable identifies a JavaScript dependency; it does not, by itself, prove that Google cannot process it.

**Local DOM:** shows what your browser built. Use developer tools to find the timetable and inspect network or script errors. Test without your usual session too. This helps reproduce failures, but it remains your environment.

**Google's test:** for a property you manage, URL Inspection's live test provides results and, when available, rendered HTML and a screenshot. Search for the exact timetable text. Google explains these distinctions in its [JavaScript SEO documentation](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics) and [URL Inspection help](https://support.google.com/webmasters/answer/9012289).

A live test does not confirm that a page is already indexed. Compare it with indexed data, which reflects earlier processing.

## Two dependencies to check

An initial `noindex` directive should not depend on JavaScript removing it. Google may skip rendering when it encounters that instruction. If the class page should be indexable, correct the initial response and check the published directives afterward.

Links need attention too. For a public class page, this link provides an explicit destination:

```html
<a href="/workshops/pottery/">View pottery workshop</a>
```

An element that navigates only through a click handler does not provide equivalent HTML. Google documents [links it can crawl](https://developers.google.com/search/docs/crawling-indexing/links-crawlable). Examine what your framework emits before asking for an application rewrite.

## Give the web team a specific investigation

For this example: “The schedule appears only after schedule.js loads. Check resource access and execution errors, then compare the initial response with Google's live-test HTML. Confirm that the class content and links work without a private session.”

If the main content remains difficult to process, the team can consider serving it from the server or generating it ahead of a visit. That choice needs a diagnosis. Keep before-and-after evidence: the useful change is making essential information verifiably available, without attributing an unobserved ranking improvement to it.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
