My Google Site is Showing a 404 Error or is Asking Users to Log In
If your Google site is showing a 404 error or is asking users to log in, there are a few reasons that this may be happening.
Reason 1: Your site is not published.
If your Google Site is not published, users will see a 404 error stating that the page cannot be found. To fix this, follow these steps:
Go to sites.google.com and open the editor for the site in question.
Look at the top right of the editor to the right of the purple publish button. Do you see a down arrow? If not, your site is not published. Click the purple publish button.
You will be asked to give your site a sites.google.com/view address. You need to complete this whether you use a custom domain or not.
Reason 2: Your site is private.
If your Google Site is private, users will see a login page. To fix this, follow these steps:
Go to sites.google.com and open the editor for the site in question.
Look at the top right of the editor and click the 👤+ icon.
Select "Links". Ensure that "Published site" is set to "Public" rather than "Restricted".
Reason 3: You use a custom domain and haven't connected it properly.
If you use a custom domain (e.g. example.com) and you haven't connected it to your site properly, then it won't be viewable on your custom domain.
If you use Google Domains, follow these steps.
If you use a domain registrar other than Google Domains, follow these steps.
Reason 4: Your domain registrar hasn't propagated the DNS records yet.
Note: This only applies if you use a custom domain with your Google Site.
Once changing DNS records on your custom domain, you need to wait up to 72 hours for the changes to take effect. Please be patient and wait.
If you see an error in your browser after this time, such as "This site cannot be reached", please post in our Google Sites group on Facebook, ask a question in the Official Sites Community, or contact your domain provider.
Reason 5: You are using Google Workspace.
If you have followed the above steps and your site still is not viewable to the public, the issue may be caused by Google Workspace. If you have a Google Workspace subscription, contact their team and they will be able to help you fix the issue.