01
Read the response
Browser output and crawler HTML are different evidence.
A finished page can look complete after JavaScript runs while the first response still contains very little readable content.
Compare the twoDocumentation
Understand the responsebefore changing the stack.
Public references explain the product model and its limits. Exact setup instructions are generated inside an authenticated workspace for the website being connected.
Public references
The three parts of crawler evidence.
02
Understand the route
Visitors and eligible crawlers can follow different response paths.
The visitor-facing application stays in place. Prerendering changes the HTML response only for supported crawler page requests.
Review crawler support03
Verify the outcome
The proof belongs in the response, not the dashboard.
Status, metadata, headings, links, and page copy should be inspectable in the HTML returned to the crawler request.
Inspect the evidenceAccount setup
The exact instructionsbelong to your site.
DNS targets, provider fields, integration code, credentials, verification commands, and troubleshooting depend on the connected website and stay inside the account workspace.
Continue to account setupSecurity boundaries
How URLs, private networks, credentials, rendering workloads, and account data are handled.
Failure behavior
What happens when cache, quota, rendering, DNS, HTTPS, or origin requests fail.
Self-hosting
Run the open engine with your own Docker infrastructure, security controls, monitoring, and operational ownership.