ChatGPT Is Recommending My Staging Site. How to Stop It

Short answer: Staging often gets recommended because it is public, it answers the same questions as production, and a crawler could read it. Block AI crawlers on staging, add noindex, and put a clear "not released" line on the pages. Then ask the same buyer questions in a fresh ChatGPT chat and confirm the production URL shows instead of staging. MadeTheAnswer can help you re-check. It is not the fix.

Need to re-check what ChatGPT names after you lock staging down? MadeTheAnswer's free check asks ChatGPT, Perplexity, Gemini and Claude 5 buyer-style questions, one run each. We work out your category and suggest likely competitors. Your score shows on screen, and the full report comes by email. Email required, no credit card. It's a one-run snapshot, not a verdict.

Why staging gets recommended

Assistants look for a page that answers the question. A staging site is a strong accidental match when:

• It is on a public URL (for example, staging.yoursite.com or a preview host).
• It has the same product copy as production, sometimes newer copy.
• Robots and bot protection were left open so the team could share a preview.
• Production is blocked, slower, or less complete than staging.

From the assistant's point of view, staging is just another site that answers "what is this product?" If that URL gets into search results or citations, people can be sent there.

Block crawlers, and close the door

On the staging host, not on production, do all of these:

1. Block AI search crawlers in robots.txt. For ChatGPT search, OpenAI says sites that block OAI-SearchBot "will not be shown in ChatGPT search answers" (OpenAI). Staging is a case where you want that. Also review GPTBot and any other AI crawlers you care about. Keep production's rules separate, so you don't lock the live site by mistake.
2. Block bots at the CDN or host. A password, IP allowlist, or firewall rule is stronger than robots.txt alone, because robots.txt is a request, not a lock. Make sure preview links aren't world-readable.
3. Give it time. OpenAI says it can take about 24 hours for a robots.txt change to be picked up (OpenAI). Old citations can linger after that.

Do not copy staging's "block everyone" robots.txt onto the live site if you still want production to be eligible for ChatGPT search.

Add noindex, and say it is not released

Even after you block crawlers, leftover pages and cached answers may still mention the staging URL.

• Add a noindex tag on all staging pages, so search engines are told not to list them.
• Put a clear line near the top: "This is a staging site. It is not released." That gives an assistant something honest to quote if it still finds the page.
• Use a staging hostname that is obviously temporary, and avoid putting important unique content only on staging.

If ChatGPT had already cited the staging URL, you may also need to make the production page the clearer source: same facts, public URL, easy to crawl.

Re-check in a fresh chat

After the blocks are in place and a day has passed:

1. Open a logged-out or private window.
2. Ask the same buyer questions that used to return the staging URL.
3. Ask each one a few times. One clean answer is not enough.
4. Confirm the URL in the answer or citation is production, not staging.

If staging still appears, check that the block is on the host ChatGPT actually fetched, and that you didn't leave a second preview URL open.

How MadeTheAnswer helps

MadeTheAnswer does not block crawlers or edit your site. After you make the change, a re-check can show whether production is being named and which URLs are cited.

• Free check: 5 questions, one run each on ChatGPT, Perplexity, Gemini and Claude. Score on screen, full report by email. No card. One free check per website and one per email each week. There are also 5 free checks a day for everyone. That number resets daily at midnight UTC (5 PM Arizona time).
• Paid weekly reports (from $29/month): each question is asked 3 times, and you can compare cited websites week to week. See plans and prices

Each assistant's score links to the actual AI answers. We don't check ChatGPT Shopping. We don't promise that staging will disappear from every answer on a given day.

FAQ

Should I noindex production too? No. noindex and crawler blocks belong on staging and other private previews. Production should follow the access rules you want for the live product.

Will a password on staging be enough? A password or IP allowlist is one of the stronger fixes, because the page isn't public. Still add noindex and a "not released" line in case an old copy was saved somewhere.

How long until ChatGPT stops sending people there? A robots.txt change can take about a day to be picked up. Cached answers and old citations can last longer. Re-test the same questions rather than assuming the first quiet day is final.

Related guides

• AI Crawled My Site, but I Get No ChatGPT Traffic — How crawl access and being named in an answer are different.
• Is My Brand in ChatGPT? How to Check, and What to Do if You're Missing — How to re-check the same buyer questions after you block staging.
• How to Get Your Product Recommended by ChatGPT: A Step-by-Step Plan — How to point assistants at your live product pages instead.
• Why Did ChatGPT Stop Recommending My Product? — Cached answers can linger. Here's how to tell a real change.

Re-check what the assistants cite

See a sample report → (demo data)

---

Sources: OpenAI, "Overview of OpenAI Crawlers"; OpenAI Help Center, "Searching the web with ChatGPT".