# Why Isn't My Squarespace, Wix, Webflow, WordPress.com or Shopify Site on Google?

Canonical: https://figment.so/blog/website-builder-site-not-on-google

Check the visibility, password or noindex setting for your platform first. It is the most common cause. Then confirm the real state with Search Console's URL Inspection tool and a submitted sitemap.

**Check one specific setting first: a site-visibility toggle, a password page or a noindex tag. These are more common causes than anything Google itself is doing.** Every builder below has at least one built-in setting that hides a site or page from search engines on purpose, and it is easy to leave one on from before launch. This guide gives the exact setting on each platform, then the two Google tools that tell you what is true instead of guessing from a `site:` search.

## Is Squarespace blocking search engine crawlers?

It is if **Block Search engine crawlers** is checked under **Settings → Crawlers**. That setting adds `Disallow: /` to your site's robots.txt, which blocks search engines from the whole site ([Squarespace](https://support.squarespace.com/hc/en-us/articles/21829426828045-Hiding-your-site-from-search-results)).

A single page can also be hidden. Hover over the page, click the gear icon, go to the **SEO** tab, and check whether **Hide page from search results** is switched on. Squarespace notes that "Blog pages have more options" and that "Homepages and individual collection items don't have a Hide page from search results toggle" (same source). If you hid a whole blog or store section this way, every post or product under it is excluded too, since "adding the tag to a collection page also tells search engines to exclude its collection items from search results."

## Is my Wix site or page hidden from search?

Check two settings, because Wix separates site and page. For the whole site, go to **SEO & GEO** in your site's dashboard, scroll to **Tools and settings**, open **SEO Settings**, and check whether **Let search engines index your site** is off. For one page, open **Pages & Menu** in the editor, click the **More Actions** icon next to the page, open **SEO basics**, and check the **Let search engines index this page** toggle ([Wix](https://support.wix.com/en/article/wix-editor-preventing-search-engines-from-indexing-your-page)).

Two Wix details matter. Public member pages such as Followers and Profile stay indexable unless you switch them off one by one. Turning indexing off site-wide removes the per-page controls (same source).

## Is Webflow's staging or page indexing turned off?

Check both places, because Webflow keeps indexing settings in two. If your site is reachable only at its `.webflow.io` subdomain (no connected custom domain), check the **Staging indexing** setting. When it is off, search engines are told to ignore the `.webflow.io` staging address. That is what you want once a custom domain is live, and a problem if the staging address is your only address ([Webflow](https://help.webflow.com/hc/en-us/articles/33961368603539-Disable-search-engine-indexing)).

An individual page can also carry its own noindex tag. Open **Page settings → SEO settings** and check whether **Sitemap indexing** is toggled off. Webflow states this "adds `<meta content="noindex" name="robots">` to your site page." A page can still show up as indexed even after you fix the toggle, "if a search engine finds your content either because it was published previously, or there's a link to that content from other content online." Webflow also notes that a noindex tag added through custom code does not remove the page from the auto-generated sitemap. The **Sitemap indexing** toggle does both.

## Is WordPress.com discouraging search engines?

It is if **Discourage search engines from indexing this site** is ticked. Go to **Settings → Reading**, find **Site Visibility**, and confirm the site is set to **Public**. WordPress.com's support page notes an easy-to-miss side effect: "not all search engines may respect this setting," and turning it on "will also exclude your blog posts from showing in the WordPress.com Reader" ([WordPress.com](https://wordpress.com/support/privacy-settings/make-your-website-public/)). A site that vanished from both Google and the Reader at the same time usually has this box checked.

This setting differs from a private or coming-soon site, which blocks all visitors, not just search engines. Confirm your site is public before assuming this checkbox is the cause.

## Is my Shopify store in private mode?

It is if the access setting menu on the **Online Store** page shows a **Private** label. Extra private-mode settings, such as the password, live under Online Store → Preferences. New stores start in private mode by default. Shopify is direct about what this does: "all of your online store's pages are hidden from visitors and search engines, and your online store displays a customizable landing page instead" ([Shopify](https://help.shopify.com/en/manual/online-store/themes/password-page)). It is the same password page many stores use before launch, and it is easy to leave switched on after going live. A store behind it is invisible to Googlebot the same way it is invisible to a customer without the password.

## What checks apply on every platform once the setting is ruled out?

Use Google's own tools, not a `site:yourdomain.com` search. Google is explicit that "the `site:` operator doesn't necessarily return all the URLs that are indexed under the prefix specified in the query" ([Google Search Central](https://developers.google.com/search/docs/monitor-debug/search-operators/all-search-site)).

1. **Search Console's URL Inspection tool.** It "shows what Google knows about a specific page on your site" and can test the live version against indexing requirements ([Google Search Console Help](https://support.google.com/webmasters/answer/9012289)). Run your homepage and a couple of important pages through it. It tells you directly whether a noindex tag, a robots.txt block or a crawl error is the cause, which turns the platform checks above from guesswork into confirmation.
2. **A sitemap submitted in Search Console's Sitemaps report.** Google's documentation says a sitemap becomes more useful as a site grows and helps "sites where the URLs change often" get found and re-crawled ([Google Search Central](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap)). Every builder above generates one automatically. Confirm the sitemap Search Console has on file lists your live domain, not a staging or preview URL from before launch.

A site can also simply be new. Google's crawling and rendering queue takes time by design, and a site with no sitemap and no external links may sit unindexed longer than a well-linked one. That is a timing issue, not a setting to fix. Use the [page-level SEO basics checklist](/blog/add-seo-basics-to-ai-generated-website) to confirm the title, description, canonical, crawlability and sitemap before you wait for another crawl.

## What if I fixed the setting and I'm still not showing up?

Request indexing again, then wait days, not hours. Flipping the toggle only removes the block going forward. It does not re-index anything. After you fix a noindex tag, a robots.txt block or a private-mode setting, go back to URL Inspection and use its request-indexing option on your most important pages instead of waiting for Google to notice. Google's JavaScript-rendering documentation acknowledges that even ordinary crawl and render queues "can take longer than that" few-seconds baseline, so a fixed setting on a brand-new site can take longer to show results than the same fix on an established one.

If a page shows a persistent error in URL Inspection after the setting is fixed, that is a separate issue (a server error, a redirect loop or a canonical pointing elsewhere). Inspect it on its own instead of re-checking the same visibility setting.

## What if my site is a Lovable app, or I am rebuilding anyway?

A Lovable site has different causes and a different fix order, because its rendering setup changes what Google sees before any setting above applies. See [why a Lovable site isn't showing on Google](/blog/lovable-site-not-showing-on-google). If you are rebuilding the site anyway, our [export capability matrix](/blog/export-your-website-from-a-website-builder) and [redirect guide](/blog/redirects-when-changing-website-builders) cover what has to survive the move.
