Google Sites Not Indexed: A Quick-Fix Guide

There is a reasonable assumption behind most “Google Sites not indexed” complaints: the site is built in a Google product, published on a Google domain, so surely Google knows it exists. It does not work that way. A published Google Site is treated like any other page on the web. Googlebot has to discover it, crawl it, and then decide whether it belongs in the index, and how Google Search works is the same three-stage process whether your page lives on sites.google.com or on a server you run yourself.

Publishing, in other words, is an event on your side. Indexing is a judgement on Google’s. The good news is that when a Google Site stays out of the index, the cause is usually one of a small number of things, and most of them take minutes to fix.

First, confirm the site is actually not indexed

Before changing anything, check what Google has actually decided. Search for site:sites.google.com/view/your-site-name (or site:yourdomain.com if you use a custom domain). If your pages appear, the problem is ranking, not indexing, and none of the fixes below will help.

If nothing appears, you have a genuine indexing problem. Keep in mind that the site: operator is a blunt instrument; our guide to checking whether a page is indexed covers its quirks and the more reliable alternatives.

Why so many Google Sites are not indexed

The publish setting that asks search engines to stay away. When you publish a Google Site, the publish dialog includes a checkbox labelled “Request public search engines to not display my site”. If it is ticked, you have asked Google not to show your pages. This is the single most common cause, and it is easy to miss because it lives in a dialog most people click through once and never reopen. Open Publish settings, make sure the box is unticked, and publish again.

Nothing links to the site. Google discovers pages mainly by following links from pages it already knows. A brand-new Google Site with no inbound links from anywhere is hard to discover, however clean its content. A link from an established page you control (a company blog, a profile page, a partner site) gives Googlebot a path in.

You cannot reach the usual plumbing. On a sites.google.com address you do not control robots.txt, and the editor does not let you upload verification files or edit the page head. That rules out several of the standard Search Console verification routes, which is why many Google Sites owners never get URL Inspection or indexing reports at all. If you connect a custom domain, you can verify ownership through your DNS records and the whole URL Inspection tool becomes available, including requesting a recrawl for individual pages.

The site is thin. Google Sites makes it very easy to publish a single page with a heading, two sentences, and a contact button. Google crawls pages like that and often declines to keep them. Indexing is selective, and a page needs to offer something an existing indexed page does not. This is not a Google Sites problem, strictly, but the platform’s ease of publishing makes it a common one.

The quick-fix sequence

1. Untick the search engine opt-out in Publish settings and republish. If this was the cause, nothing else matters until it is fixed.
2. Link to the site from at least one page Google already indexes.
3. Add a custom domain if you are serious about search. It unlocks Search Console verification via DNS, which gives you Google’s own reporting on what has been crawled and indexed.
4. Give each page a reason to exist. A page of genuinely useful text indexes more readily than a placeholder, on any platform.
5. Then wait, and verify. Discovery without Search Console can take days or weeks, and there is no lever that forces Google’s hand.

The last step is the one people skip. A fix is only a fix if the page actually enters the index afterwards, and the only way to know is to keep checking. This is where a tool that verifies against live Google results earns its place: AIndexify takes your URLs with no Search Console connection and no ownership proof, submits them, then checks each one on a schedule over the following days and reports submitted and indexed as two separate events, with the date the page was actually found. If a page cannot be checked because it carries a noindex signal, the preflight catches it, tells you, and refunds the credit. For a Google Site you cannot verify in Search Console, that is essentially the reporting you were missing.

When the platform is the wrong answer

Sometimes the honest fix is a different question. Google Sites is built for quick internal pages, event sites, and simple public presences. If you find yourself fighting for control over metadata, site structure, and indexing signals, you are pushing against the platform’s design. The same trade-off appears on other hosted builders; our guide to indexing a Notion site walks through the neighbouring case, and the broader mechanics of crawling, indexing, and verification are covered in the ultimate guide to Google indexing.

None of this means a Google Site cannot rank. Plenty do. It means the platform gives you fewer levers, so the ones you do have (the publish setting, inbound links, a custom domain, substantial content) carry all the weight.

Fix the checkbox, add a link or two, then watch what Google actually does. See where your pages stand: submit your URLs and get an answer based on live results rather than hope.