Common cause after launch
A site built behind a password often goes live with part of that protection still switched on, which shows up as 401 errors in Search Console.
The page asked Googlebot to log in, and Googlebot never logs in. If the page should be in Google, remove the authorisation requirement for it. If it is private, this status is expected.
A site built behind a password often goes live with part of that protection still switched on, which shows up as 401 errors in Search Console.
| Check | How to tell | Fix |
|---|---|---|
| Should this page be public? | Decide whether the URL is meant for search visitors or only for logged-in users. | Leave private pages as they are, and stop linking to them from public pages and your sitemap.[1] |
| Is a staging or password lock still on? | Open the URL in an incognito window. A password page or browser login box means the lock is active. | Remove the site-wide password or staging protection from the live site.[1] |
| Is the URL in your sitemap? | Search your sitemap file for the URL. | Remove private URLs from the sitemap so Google is not asked to index them.[2] |
Google's report says you can allow Googlebot by verifying its identity, but for most business sites the simpler fix is to make public pages public.[1][3]
Open the page in an incognito window. If you are asked to sign in, Googlebot is too.[1]
Your website, fully managed — no big upfront cost.
We design, build, host, maintain and keep improving your site for one simple monthly fee.
A one-off custom build you own outright.
A defined scope and a single fixed quote — delivered once, and yours to keep.
Get a free, no-obligation quote for your project. We respond within 24 hours.