Rendered HTML: Understand and Use the Results
Get HTML after JavaScript executes in Chromium
Rendered HTML: the document after JavaScript changes it
A web server sends HTML to a browser. The browser turns that text into a document, then JavaScript can add content, change links or replace whole sections. Rendered HTML is a snapshot of that current document rather than only the text originally sent by the server.
This matters when a page looks correct in a browser but an ordinary HTTP fetch appears to contain little content. A rendered snapshot helps identify content that arrives through JavaScript and inspect what the page has created at a particular moment.
When reviewing a snapshot, check:
The final URL and HTTP status, including whether an error page was captured.
The document title and important content.
Links, metadata and structured data generated by scripts.
The observation time and the point at which the snapshot was taken.
A snapshot can answer whether content appeared during that observation. It cannot prove that all asynchronous work has finished, reproduce every visitor session or establish how a search engine indexes the page. Browser location, cookies, viewport, network conditions and timing can all change the result. Treat captured HTML as untrusted content: inspect it as text and avoid inserting it directly into another application’s page.
The Rendered HTML endpoint, in plain language
Get HTML (HyperText Markup Language) after JavaScript executes in Chromium
Inspect content generated by JavaScript and compare the rendered page with server HTML (HyperText Markup Language). Useful for deployment checks and debugging pages whose content is missing from ordinary HTTP (HyperText Transfer Protocol) fetches.
What is actually happening when you call it
Navigates to a public HTTP (HyperText Transfer Protocol)(S) URL (web address), waits for DOMContentLoaded and an additional 500 milliseconds, then serializes the current the structured form of an HTML (HyperText Markup Language) page. Returns the final URL, document title, observed HTTP status, rendered HTML and VPS measurement provenance. This bounded snapshot does not guarantee that all asynchronous content has finished loading. HTML is limited to 512 KiB. Private destinations are blocked for redirects and subresources; TLS (Transport Layer Security) verification stays enabled. One shared browser job runs at a time across staging and production; busy requests return 429 with Retry-After and are not charged. Captures are fresh and uncached.
Why this specific tool matters
Choose a task: JavaScript Content. Check whether the deployed page creates its expected content after JavaScript runs.
Run the Rendered HTML request below and retain the input and observed result. Before changing configuration, compare the relevant fields with the value or policy you expected. Use the Rendered HTML reference to check the field definitions and supported options.
Available on the developer plan. The technical details: `GET /v1/domain/render`.
When would I actually use this?
JavaScript Content
Check whether the deployed page creates its expected content after JavaScript runs.
Use the finding: Inspect a real the structured form of an HTML (HyperText Markup Language) page snapshot instead of only the initial HTML.
Rendered SEO Review
Inspect titles, links and structured data created by client-side code.
Use the finding: Find differences between source HTML (HyperText Markup Language) and the rendered document without claiming a full crawler simulation.
Deployment Checks
Capture the rendered document from a public deployment URL (web address).
Use the finding: Automate content checks using the same authenticated API (Application Programming Interface) as other EdgeDNS diagnostics.
The easiest way: just ask your AI assistant
Connect the MCP server. Just ask in plain English:
Use domain_render with url=https://example.com/. Show the returned findings, identify unavailable evidence, and explain a useful next check.
Confirm the tool and inputs in the client before accepting its summary. For Rendered HTML, use the response fields below to separate observations from recommendations.
The dedicated MCP server is available on every plan. Individual tool access and request limits depend on your plan. Management categories and endpoints disabled for the tool catalog are not exposed through MCP.
The technical way: call it from code
This Rendered HTML request uses the example inputs from its API contract. Replace YOUR_API_KEY with a key on the developer plan or higher; adapt the target to your task.
curl --request GET 'https://api.edgedns.dev/v1/domain/render?url=https%3A%2F%2Fexample.com%2F' \
--header "Authorization: Bearer YOUR_API_KEY"Prepare inputs for Rendered HTML
Start with the inputs below. Keep the same hostname, path, and options when comparing Rendered HTML observations. The API reference contains the complete parameter contract, optional settings, and access requirements.
| Field | Type | Required? | What it means | Example |
|---|---|---|---|---|
url | string | Yes | Public HTTP (HyperText Transfer Protocol)(S) URL (web address) on port 80 or 443. Bare domains use HTTPS (secure HyperText Transfer Protocol). Credentials and fragments are not accepted. | https://example.com/ |
Interpret Rendered HTML findings
Read these fields alongside the full response from your Rendered HTML check. A missing value or failed lookup is different from a passing result. Keep returned errors and confidence or cache metadata when available; do not replace missing evidence with a successful default. See the complete response reference for additional fields.
| Field | Type | What you'll see in it |
|---|---|---|
html | string | Rendered the structured form of an HTML (HyperText Markup Language) page serialized as HTML; treat it as untrusted page content. |
html_bytes | number | UTF-8 size of the returned HTML (HyperText Markup Language), at most 524288 bytes. |
title | string | Observed document title, limited to 4096 characters. |
Words you might be wondering about
API (Application Programming Interface) — A way for one program to ask another program for something — like a waiter taking your order to the kitchen.
URL (web address) — The full address of a page, like https://example.com/about.
HTTP (HyperText Transfer Protocol) — The language web browsers and websites use to talk to each other.
TLS (Transport Layer Security) — The encryption that puts the 'S' in HTTPS. It scrambles data so nobody between you and a website can read it.
HTML (HyperText Markup Language) — The basic language web pages are written in. The tags you see in the source code (<h1>, <p>, <a>) are HTML.
Related Guides
Rendered HTML: Understand and Use the Results
Get HTML after JavaScript executes in Chromium
Page Screenshot: Understand and Use the Results
Capture a web page as a JPEG screenshot
HTTP Checker: Check Server Status, Redirects, and Response Time
Check whether a URL responds as expected, see where it redirects, and understand its elapsed time and HTTPS result. Start with a browser check, then use the same endpoint in a deployment workflow.
Server Response Time and Edge TTFB Percentiles Explained
Measure response latency from an edge worker and understand what the median, p90, p95, and p99 can tell you. Learn where a small synthetic sample differs from browser timing and production tail latency.
Need Programmatic Access?
Automate domain intelligence with 100+ API endpoints and a free MCP server for AI integration.