Your test site can beat your live site on Google. Residents can't tell

A resident searches Google for how to pay their council tax. The first result looks exactly like your website, with the same logo, the same pages and the same forms. But it is a test or pre-production copy, not the live site. Nothing tells the resident. They may fill in a form, try to log in, or follow out-of-date information, then phone you when nothing happens.

The check also looks for other addresses that should never appear in Google:

• login pages for housing or account portals
• raw data files, such as the behind-the-scenes definition of an online form
• admin pages and test addresses that start with staging., test., uat. or pre.

The good news is that this is rare. Almost every council passes, and most types of council have no problem at all. Where it does happen, it tends to be in London boroughs, with the odd unitary council. When a test copy gets into Google, it often reaches the top result for several tasks at once: applying for council housing, applying for a school place, paying council tax, applying for a parking permit and checking bin collections. Report a road problem has also shown a form's data file in the top five.

Because it is rare, it is easy to forget. Test copies are most common around a redesign, a move to a new content management system or a change of form supplier. With local government reorganisation bringing new and merged council websites, many teams will run a pre-production site for months. That is when this check matters most.

Google indexes any page it can reach and is not told to ignore. A test site is not hidden just because nobody shared the address. The usual causes are:

• A full pre-production copy left open to the public. The most common pattern is a whole copy of the live site at an address starting pre. or staging., with no password. Google finds it and ranks it at number one, because it looks just as good as the real thing.
• Links that point to the test site. Content written or copied on the test site keeps full web addresses that point back to it. Once published on the live site, those links lead Google straight to the test copy.
• Form platforms exposing their workings. Some online form tools publish a sandbox or definition file, often ending in .json, that Google can read and rank.
• Portal login pages with nothing to stop indexing. Housing and account portals, often run by a supplier on their own address, have a login page that Google treats as a normal page.
• A robots.txt file used on its own. Blocking a site in robots.txt stops Google crawling it, but Google can still list the address if other sites link to it.