Skip to content
50% OFF $299 $599
Lock in
§ 2.2.6 ARTICLE
Published VerifiedEvery 6 weeks Sources6 named Authored bySquareRank Team

Indexing · § 2.2.6 · Diagnostic

"My Squarespace site is not indexed by Google" — the 8-step diagnostic

When a Squarespace site is not appearing in Google, the cause is almost always one of five things: (1) the site is too new (under 2-3 weeks since launch); (2) Settings > Crawlers has the search-engine block on4; (3) the Search Console property was never verified6; (4) page-level noindex flags are left on from a draft state; (5) the content is genuinely thin with too few links pointing at it for Google to prioritise indexing1. The eight-step flow on this page identifies which of the five (or rare combination) applies in 10-15 minutes.

This leaf is the diagnostic. Each step takes 1-2 minutes. Work top-down; the first step that surfaces an issue is usually the root cause. The flow handles 95%+ of "not showing" tickets without needing developer-mode access or paid tools.

The 8-step diagnose flow, top down

Eight checks cover almost every Squarespace 'not on Google' scenario. (1) Site published, live, not password-protected. (2) Settings > Crawlers allows search-engine crawling. (3) Search Console property verified. (4) Sitemap submitted via Search Console > Sitemaps. (5) Homepage URL Inspection returns 'URL is on Google' or 'Indexing requested'. (6) Top pages don't have 'Hide this page from search results' checked. (7) Pages report in Search Console shows expected indexed-page count. (8) Content and internal/external links are sufficient. Steps 1-4 fix 80% of tickets; 5-8 catch the rest.

The pattern: walk through top-down, fix the first step that surfaces an issue, then re-test from the top. Most tickets resolve at steps 1-3 — the new-site timeline, the crawlers toggle, the Search Console verification. Steps 4-8 are real but less common. The full flow rarely takes more than 15 minutes.

What the diagnose flow surfaces

80%

of 'not showing on Google' tickets resolve at steps 1-3: site live, crawlers allowed, Search Console verified.

Google Search Central · 2025-12-10
2-21 days

typical timeline for a new Squarespace site to first appear in Google after launch.

Google Search Central · 2025-12-10
8 steps

in the full diagnostic — each takes 1-2 minutes, total 10-15 minutes for a complete pass.

Google Search Central · 2025-12-10

Step 1: Is the site actually live and public?

Open yoursite.com in a private/incognito browser window (not the one you used to build the site). The site should load without asking for a password, without redirecting to a Squarespace development URL, and without showing a 'coming soon' page. If any of those fail, the site is not actually live to the public — Google can't index what it can't access.

Three sub-checks: (1) Is the custom domain pointed at Squarespace correctly? Open Settings > Domains and confirm the domain shows "Connected" status. (2) Is the site password-protected? Open Settings > Site Availability and confirm the site is set to "Public", not "Password-Protected" or "Private". (3) Is the site set to "Coming Soon"? Same Site Availability panel; "Coming Soon" pages return a sitewide noindex.

Step 2: Is Settings > Crawlers allowing search engines?

Open Settings > Crawlers. Two checkboxes appear. The top one — 'Block search engines from indexing this site' — must be unchecked for any production site. Squarespace's help center calls this out explicitly. If it's checked, your site is emitting <meta name='robots' content='noindex'> on every page sitewide, and Google honours the directive within days of crawling.

To confirm the effect of the toggle, open yoursite.com/robots.txt in a private window. If the toggle is checked, the file includes a sitewide Disallow: / rule for User-agent: * (or equivalent platform-specific syntax). If the toggle is unchecked, robots.txt is permissive. The AI-crawler toggle below (the 26-bot list) is a separate decision — documented in the AI Crawlers cluster.

Step 3: Is the Search Console property verified?

Open Google Search Console at search.google.com/search-console. If you don't see your domain listed in the property selector, you haven't verified the property — and Google has no idea you own the site. Add the property using Domain verification (DNS TXT, preferred) or URL Prefix verification (HTML meta tag in Squarespace's Code Injection). The search-console leaf in this cluster has the full path.

The verification step is a one-time action. Once verified, the property persists indefinitely. Without verification, Search Console returns no data and you have no diagnostic tool. The HTML file upload method does not work on Squarespace (no root-level file uploads); use DNS TXT or HTML meta tag6.

Step 4: Has the sitemap been submitted?

In Search Console's left sidebar, open Sitemaps. The submitted sitemaps list should show 'sitemap.xml' with a 'Success' status. If it doesn't, submit it now: type 'sitemap.xml' in the input box and click Submit. Within minutes to hours, the status updates and Google begins fetching the URLs. The sitemap leaf in this cluster has the full submission workflow.

Squarespace's auto-generated sitemap5 is at yoursite.com/sitemap.xml. To verify the file exists, open the URL in a private window before submitting — you should see XML with a list of URL entries. If the URL returns 404 or empty content, something else is wrong (usually the site is offline or all pages are noindex sitewide).

Step 5: URL Inspection on the homepage

In Search Console, paste your homepage URL into the search bar at the top (URL Inspection). The tool returns a detailed report: indexed status, last crawl date, canonical, mobile usability. The two answers you want to see: 'URL is on Google' (you're indexed — fine), or the tool gives a reason ('Discovered - currently not indexed', etc.) you can act on. Click 'Request Indexing' to expedite recrawl on a page Google hasn't yet indexed.

Run URL Inspection on your top 3-5 pages (homepage, /about, /services, top blog post). Each one tells you whether the specific page is indexed and, if not, why2. Request Indexing is rate-limited to a small number of requests per day, so use it on important pages, not every page on the site.

Step 6: Are page-level noindex flags left on?

On your top 5 pages, open Page Settings > SEO. Look at 'Hide this page from search results' — it should be unchecked on every page you want indexed. Pages from a previous draft state, internal-use pages, or pages set to noindex during a development phase often get forgotten. A single noindex on the wrong page (homepage, top service page, key blog post) is invisible until you check the specific page.

The noindex leaf in this cluster covers the per-page checkbox in detail. To audit faster, view source on the live page and find-on-page for "noindex" — if the meta robots tag has noindex, the checkbox is checked. The auto-emitted Squarespace tag is the source of truth; if it says noindex, Google honours it within days.

Step 7: What does the Pages report show?

In Search Console, open Pages (formerly Coverage). The headline number is 'Indexed' vs 'Not indexed'. Compare 'Indexed' count to the URL count in your sitemap — they should match within 10-20% on an established site. If 'Indexed' is far lower than expected, scroll down to the 'Why pages aren't indexed' table and identify the status groups with the most affected URLs. The crawl-errors leaf in this cluster decodes each status.

On a new site, expect the 'Indexed' count to lag the sitemap count by weeks. After 2-4 weeks, the gap should close to within 10-20%. If you see large counts in 'Discovered - currently not indexed' or 'Crawled - currently not indexed', those are the next things to address — each has its own fix documented in the crawl-errors leaf3.

Step 8: Is the content and link profile sufficient?

If steps 1-7 all pass and indexing is still partial or slow, the cause is usually content quality, internal linking, or external link authority — not a technical setting. Three sub-checks: (1) Does the site have 10+ pages of meaningful content? (2) Is each page internally linked from at least one other page? (3) Does the site have any inbound links from other websites? Sites with under 5 pages, no internal links, and zero inbound links are not technical-fix candidates — they are content-and-authority candidates.

The honest framing: indexing is partially a discoverability problem and partially a quality problem. A site that's technically perfect but has 3 pages of thin copy and no inbound links may sit in Search Console with most pages "Discovered - not indexed" for months. Google's crawl budget for low-authority domains is limited, and the algorithm prioritises pages it thinks are worth indexing. The fix is content and links, not technical settings.

text A useful quick check — Google's site: operator 
 # Search Google for the exact phrase below in an incognito tab site:yoursite.com # Google returns every URL it has in its index for your domain # 0 results = nothing indexed; investigate steps 1-4 first # Some results = you're indexed; investigate why specific pages are missing

Still not indexed after 8 weeks?

If you've worked through all eight steps, all eight pass, and the site still has near-zero indexed pages after 6-8 weeks since launch, the remaining causes are rare but real. Three to investigate: (1) the domain has a previous history with Google that the new site is inheriting (check Search Console > Security & Manual Actions for any messages); (2) the site has a content-quality issue that Google's classifiers are flagging (compare with similar competing sites); (3) the niche is too competitive for an unestablished domain to be prioritised for indexing. Each has a different path forward — sometimes patience, sometimes a content audit, sometimes a manual action lift request.

The free SquareRank audit runs a full pass on a Squarespace site in 60 seconds, returning three scores: SEO, AEO, GEO. If your site is genuinely indexable and still not appearing after 8 weeks, the audit usually surfaces a non-obvious cause — an inherited noindex, a robots.txt block from custom code, a content-quality red flag — that wasn't visible in Search Console alone.

Keep reading · § 2.2.6