We Code!
We can help with
and more!
WEBSITES
DIGITAL MARKETING
LEARNING
We Code!
With the adoption of AI and LLMs (Large Language Models) like ChatGPT and Google Gemini, there is a new generation of bots indexing websites for search engines and these bots are much more aggressive than they have been in the past.
In days of old (earlier this year and before), you could be relatively certain that Google and other search engines wouldn’t put your staging sites in their search results as long as you asked them not to in your robots.txt file or through WordPress settings. This is no longer the case, and it’s important to protect your staging sites to prevent them from being indexed and used in AI Overviews or other LLM results.
A staging site is a sandbox or testing website used during development to test content, design, or software updates prior to making them live. For example, when we get a project to redesign a company's website, we build a staging site. That way, their current website stays up and running while we work on the new project.
The short answer is that this can be a real problem for your SEO (Search Engine Optimization) and can introduce old or outdated information about your business. A good example is an e-commerce client of ours. We built a new website years ago, but the client still wanted access to the old website, so we created a staging site. A few months ago, pricing from that old staging site ended up in AI mentions.
How can this situation be bad for SEO? Search engines penalize or deprioritize duplicate content. If search engines pick your staging site over your actual website, you could see a significant drop in your main website’s rankings.
HTTP Basic Authentication: You can password-protect your staging sites using .htaccess or, if you use cPanel, via Directory Privacy.
Coming Soon / Maintenance Plugins: If you are using WordPress as your CMS, a plugin like SeedProd forces users to log in before they can see the website. Everyone else just sees the "Coming Soon" or maintenance page configured in the plugin.
If the damage is already done and your staging site is indexed, you need a two-step fix: hide the site from users immediately, then pull it out of search results.
Lock Down Access First: Put the staging site behind HTTP password protection (.htaccess) or set server status rules to return a 401 Unauthorized or 404 Not Found response. (Do not rely solely on robots.txt to block it now; if Googlebot can't crawl the site, it can't see that the pages are gone).
Submit a Temporary Removal Request in Google Search Console:
Go to Google Search Console for your domain property.
Navigate to Index > Removals on the left menu.
Click New Request and select Remove all URLs with this prefix.
Enter your staging domain or staging folder path (e.g., [https://staging.yourwebsite.com/](https://staging.yourwebsite.com/) or [https://yourwebsite.com/staging/](https://yourwebsite.com/staging/)).
This hides the staging site from Google Search and AI Overviews almost immediately (usually within 24 to 48 hours) while giving Google’s crawlers time to process that the pages no longer exist in the background.
The bottom line is that as developers, designers, and DIY business owners managing our own websites, we need to adapt our staging practices to make sure test sites stay private as intended.
Milly has 18 years experience in designing and developing websites, developing apps, and online marketing. She is an expert at driving traffic to websites utilizing SEO strategies and custom digital marketing efforts. Her company, Zebralove Web Solutions offers full service digital marketing and website development. Comprehensive Search Engine Optimization services, and secure web hosting services.
Contact Author