Production build references a staging or preview environment

Why it matters

Your published JavaScript references the value, which is a non-production deployment rather than this site. Whatever it powers is reading or writing against the wrong environment — so real customer actions can land in staging data, and staging content can be served to real users. It also advertises an internal deployment that is often less protected than production and sometimes holds a copy of real data.

How ShipReady detects it

Launch signals carried by a PAGE's own markup: basic metadata, and a default framework title left in place. Genuinely per-page - a polished homepage routinely hides a /pricing that still says "Create Next App", which is exactly the defect this catches. Reads only the already-fetched HTML and issues no requests of its own.

Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.10.0.

How to fix it

This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.

Your production build references a staging or preview deployment (the affected URLs) instead of your production backend. Real user actions may be reading and writing against staging data, and staging responses may be served to real customers. Set the correct production URL in your hosting provider's environment variables for the production environment specifically — the usual cause is one shared env var used across preview and production deployments — then redeploy and confirm the staging host no longer appears in the built output. Separately, if that staging environment is publicly reachable and holds a copy of real data, put authentication in front of it and add a noindex so it stays out of search.

Frequently asked questions

What does "Production build references a staging or preview environment" mean?

Your published JavaScript references the value, which is a non-production deployment rather than this site.

How serious is it?

ShipReady rates this medium. Fix soon. Meaningfully weakens a defence or degrades how the site works.

How do I fix it?

Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.

Can I check my own site?

Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check. The free report lists every issue it finds and shows full evidence and a fix prompt for the critical and high-severity ones; medium and low findings are counted and unlock on Pro.

Related checks

• A development build is being served to real visitorsmedium
• Missing Basic HTML Metadatamedium
• Page says it does not exist but returns a success statusmedium
• Placeholder template content is still live on the sitemedium
• Production build points at localhostmedium
• Shipped JavaScript logs sensitive data to the browser consolemedium