CrawlCheck

Agent view · Guides · 2026-09-30

Staging site leak: how to find a staging URL in your live pages and close it

This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/guides/staging-site-leak-how-a-staging-host-ends-up-in-your-live-pages: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.

status200
content-typetext/markdown; charset=utf-8
varyAccept
link<https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/guides/staging-site-leak-how-a-staging-host-ends-up-in-your-live-pages>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory"
cache-controlpublic, max-age=900, stale-while-revalidate=2400
bytes16,663
words2,406
sha-256f9f18233629daf006df50a66614e65325c8806172437f4f4e968b3e9e36608cb
repr-digestsha-256=:+fGCM2KdrwBt9QpmYU5lMlyIBhckN/T06Wiz6eNmCMs=: ← matches the body shown
signature-inputsig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795182612;expires=1795186212;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="ouEjOErAGRVxTwPxBe8dLA";tag="crawlcheck-page"
signaturesig1=:DiNILXKKR23iKWiLdAzXsdaJqlIoM/Z4t0faDslnnlYGCpLhncwG7uEsuJQlUHFtfTVkglZxqdEjvaGX+yU/BQ==:
verifiedyes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba
Guides · 2026-09-30 · By [VSNARY | Emmanuel Orta](/author) · 2 views

# Staging site leak: how to find a staging URL in your live pages and close it

How a managed host's staging hostname gets into production page source, what a leaked staging copy costs, how to find it from outside and how to close it without breaking the workflow.

A staging leak is a production page whose source references the site's staging hostname on a managed host (cloudwaysapps, wpengine, kinsta, pantheonsite), usually because a search-and-replace missed a serialised option, page-builder JSON or a theme file. Search the raw page source, not the rendered page, for those domains. If one is found, the staging host is a discoverable, often indexable and often out-of-date copy of the site. Fix the reference with a serialisation-aware replace, then put the staging host behind authentication or X-Robots-Tag: noindex.

Check your own site free

Check my site

About a minute. First scan free with your email, nothing installed.

On this page

- How the hostname ends up in production
- What the leak costs
- Finding it from outside
- Closing it
- Reading the finding
- The related case: your own hostname, twice
- Preventing the next one
- A related leak: the dangling CNAME

Managed WordPress hosts give every site a staging copy on a hostname of their own: `something.cloudwaysapps.com`, `something.wpengine.com`, `something.kinsta.cloud`, `something.pantheonsite.io`. The copy is meant to be private. It stops being private the moment the production page's source references it, because a crawler that reads the production page now has the staging hostname, and a staging hostname that answers 200 is a second copy of the site with no [canonical](/glossary/canonical) pointing home. This guide is how the reference gets into the page, how to find it from outside, what a leaked staging host does to the production site's standing, and how to close it without breaking the workflow that created it.

## How the hostname ends up in production #

Almost always by a search-and-replace that missed. A site is built or restored on the staging host, then pushed to production with a database replace of the staging [URL](/glossary/url) for the live one. Anything the replace did not reach keeps the old host: a serialised option a plugin stored, an image URL inside a page builder's JSON, a hard-coded asset path in a theme file, a CSS `url()` in a saved stylesheet. The page renders correctly because the staging host serves the asset, so nobody notices. You find it by reading the source rather than the render: search the homepage source for the four staging domains. A leak like this shows up on 0% of scanned sites.

## What the leak costs #

Three things, in order of how often they happen. First, the staging copy is discoverable. Any crawler that follows the reference reaches a host that usually answers 200 with a full copy of the site, and unless that host sends `noindex` or requires authentication, it is a duplicate of every page with a different hostname. Second, the production page depends on it: an image or script loaded from the staging host breaks the day the host is deleted or the staging copy is refreshed. Third, and the one that reaches the business, a staging copy is often out of date, and an engine that reads a price, a phone number or an address from the staging host has read last month's.

| Where the host hides | Why the replace missed it | How to find it |
| --- | --- | --- |
| serialised plugin option | string length is stored beside the value; a naive replace corrupts it and is skipped | search the options table for the host |
| page-builder JSON in post meta | escaped slashes: `https:\/\/` | search post meta with escaped and unescaped forms |
| theme file or child theme | not in the database at all | grep the theme directory |
| saved CSS `url()` | custom CSS stored as one block | search the customizer/CSS option |
| image srcset | each width is a separate URL | read the rendered source, not the editor |

## Finding it from outside #

Fetch the production homepage and search the response body, not the browser's rendered DOM, for the four staging domains. Then fetch a few deep pages the same way; the homepage is the usual place, but a page-builder template used on inner pages can carry the reference where the homepage does not. If a host is found, fetch it directly and read three things: the status, whether an `X-Robots-Tag: noindex` or a meta robots tag is present, and whether it demands authentication. A staging host that answers 200 with no [noindex](/glossary/noindex) and no login is the case to close first.

## Closing it #

Fix the reference and fix the host, in that order. For the reference, run a serialisation-aware search-and-replace across the database for the staging hostname, then grep the theme directory, then re-read the rendered source to confirm nothing remains. For the host, most managed platforms offer a password or basic-auth toggle on staging environments; turn it on. If the platform does not, send `X-Robots-Tag: noindex, nofollow` from the staging host's server configuration, which a crawler honours without reading the page, and disallow everything in the staging host's own [robots.txt](/glossary/robots-txt) as a second layer, remembering that robots.txt alone does not remove a URL that is already linked.

## Reading the finding #

A CrawlCheck report names the staging host it found in the homepage source. That is all the homepage proves: it does not show whether the staging copy is indexable or how many references the site carries, and one reference is enough to make the host discoverable. Treat it as a pointer. The reference is the symptom, the host’s exposure is the risk, and the two are fixed separately. A site that has moved hosts recently and kept the old platform’s staging copy alive is the common case, and the old platform’s host is the one to check first, since nobody is logging in to it any more.

## The related case: your own hostname, twice #

A [staging leak](/glossary/staging-leak) is a foreign host serving your site. The nearer relative is your own host serving it twice: `www` and the bare domain both answering 200 with the same page and neither redirecting to the other. That shows up on 5.5% of scanned sites and is covered in full in [the canonical URL guide](/guides/canonical-url-audit-one-page-one-address), with the case where it was found on a site whose canonical tag was correct in [its own post](/blog/our-canonical-was-right-and-the-site-was-still-served-twice). The two findings share a fix philosophy: one host answers, every other host redirects to it.

## Preventing the next one #

Make the search-and-replace part of the push, not a step someone remembers, and make it serialisation-aware. Keep staging behind authentication permanently rather than toggling it. And after every push, run the outside check above: it takes a minute, and a scan on [crawlcheck.io](/) runs the homepage half of it on every report. The share of scans carrying each finding is on the [dataset page](/data).

## A related leak: the dangling CNAME #

A staging or campaign subdomain often points at a hosting service through a CNAME. When the service is cancelled and the DNS record stays, the name points at nothing you control, and on some providers someone else can claim that target and serve pages on your subdomain. Check every CNAME in the zone against an active resource in your own account; an error page alone does not prove the target can be claimed. ([Microsoft guidance](https://learn.microsoft.com/en-us/azure/security/fundamentals/subdomain-takeover))
Read live from the same counters the dataset page uses, at the moment this page was served. Bars are scaled to the largest value shown, not to 100%.

Written by

[Emmanuel Orta](/author) · VSNARY

I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post.

[Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta)

Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fstaging-site-leak-how-a-staging-host-ends-up-in-your-live-pages%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fstaging-site-leak-how-a-staging-host-ends-up-in-your-live-pages%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Staging%20site%20leak%3A%20how%20to%20find%20a%20staging%20URL%20in%20your%20live%20pages%20and%20close%20it)[Email](mailto:?subject=Staging%20site%20leak%3A%20how%20to%20find%20a%20staging%20URL%20in%20your%20live%20pages%20and%20close%20it&body=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fstaging-site-leak-how-a-staging-host-ends-up-in-your-live-pages)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)

## Questions this post answers

### What is a staging leak?

A production page whose source references the site's staging hostname on a managed host such as cloudwaysapps.com, wpengine.com, kinsta.cloud or pantheonsite.io. A crawler that reads the page learns the staging host, which is usually a full, indexable copy of the site.

### How does the staging hostname get into a live page?

A search-and-replace that missed during the push to production: a serialised plugin option, page-builder JSON with escaped slashes, a theme file, saved custom CSS or an image srcset. The page renders because the staging host still serves the asset.

### Is robots.txt on the staging host enough?

No. robots.txt stops crawling, not indexing of a URL that is already linked. Put the staging host behind authentication, or send X-Robots-Tag: noindex from its server configuration, and use robots.txt only as a second layer.

### What does a CrawlCheck scan look for?

A URL on a managed host's staging domain in the homepage source the server sent. It reads what was delivered, not the rendered page, so a reference that renders fine is still found. Whether the staging copy itself is indexable is a separate check you run by fetching it.

### What is the difference between a staging leak and a duplicate host?

A staging leak is a foreign host serving your site. A duplicate host is your own www and bare hostnames both answering 200 with the same page and neither redirecting. Both have the same fix philosophy: one host answers, the rest redirect.

### Why is an out-of-date staging copy a business problem?

An engine that reads a price, phone number or address from the staging host has read an old version, and a duplicate with a different hostname competes with the real page for the same query.

## Related findings

[2026-09-30 Eight contradictions in our own copy, rechecked An outside audit found eight self-contradictions in crawlcheck.io's copy. Rechecked live: which were real, which were two truths,](/blog/eight-contradictions-in-our-own-copy-rechecked)[2026-08-21 Why word count cannot spot a parked domain: 783 words A domain parking page with 783 words passed every thin-content check. How to tell a parked page from a real site: check who serves](/blog/a-783-word-parking-page-defeats-every-thin-content-check)[2026-10-02 Markdown for AI agents: serve text/markdown by negotiation Serve Markdown when an agent sends Accept: text/markdown: same URL, Vary: Accept. Measured byte savings on four pages, the headers](/guides/markdown-for-agents-serving-text-markdown-by-content-negotiation)

The main product

Found this on your own site? **We fix it for $100.**

Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.

[Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What it covers](/pricing#fix) · [scan first, it is free](/)

Free browser extension

Check this on any site you open, **without leaving the page.**

CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.

[Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post)
[What it does](/extension)

Write for the library

Measured something yourself? **Submit an article.**

Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.

[Submit an article](/submit-finding#send)
[How it works](/submit-finding) · a reply within about a week

Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections).

## Comments

Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*.

Send for review

Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan.

[All guides](/guides) · [The dataset](/data) · [How the dataset works](/policy)

We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io)

#### How we measure, and our own machine files

CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io).

**Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing.

**Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours.

**Registry:** [MCP](/registry/mcp) · [AI policy](/registry/aipolicy) · [acsoldiers.com](/registry/acsoldiers.com) · [commons.wikimedia.org](/registry/commons.wikimedia.org) · [fashion.cloud](/registry/fashion.cloud) · [lg.com](/registry/lg.com) · [selectel.ru](/registry/selectel.ru) · [Place: San antonio](/registry/place/tx/san-antonio) | **Pages:** [IP ranges](/data/ip-ranges) · [Keys](/keys) | **Glossary:** [freshness window](/glossary/freshness-window) · [Allow header](/glossary/allow-header)

[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)

Same body as a file: /guides/staging-site-leak-how-a-staging-host-ends-up-in-your-live-pages.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.