PublishedVerifiedEvery 6 weeksSources8 namedAuthored bySquareRank Team
Cluster 2B · Indexing & Sitemap
Squarespace Is Not Showing on Google — The Five Causes, Ranked
When a Squarespace site is not appearing in Google, the cause is almost always one of five things: the site is under three weeks old and Google has not crawled it yet, the Search Console property was never verified, a page-level noindex flag is left on from a draft state, a misconfigured custom robots directive blocks crawling, or the content is too thin with too few inbound links for Google to prioritise indexing3. Squarespace auto-generates /sitemap.xml6 and a default robots.txt — both work out of the box. The diagnostic is fast.
This cluster is the indexing playbook. The six leaf articles each cover one piece: sitemap submission, Search Console verification, noindex application, crawl errors, blog/store pagination, and the full diagnostic walkthrough for the "my site is not on Google" scenario. Read the hub first for the cause ranking; then jump to the leaf that matches the symptom.
Indexing is the process Google uses to discover, crawl, render, and store your site's pages in its searchable index. Three steps in sequence: discovery (Google learns the URL exists, usually via the sitemap or a link from another indexed site), crawling (Googlebot fetches the page's HTML, CSS, JS), and indexing (Google parses the rendered content and stores it for SERP retrieval). A page must complete all three to appear in Google. Squarespace handles discovery automatically via /sitemap.xml; crawling depends on whether Settings > Crawlers permits it; indexing depends on whether the page is set to noindex and whether Google judges the content worth keeping.
Google's indexing report documentation3 describes the three stages explicitly. The most useful diagnostic tool is the URL Inspection feature inside Search Console — paste any URL and it returns the current indexed status, the last crawl date, and the reason a page is not indexed if applicable.
What indexing depends on, on a Squarespace site
2-21 days
typical timeline for a new domain to first appear in Google after launch.
The five causes of 'my Squarespace site is not showing on Google', ranked
In order of frequency: (1) the site is too new and Google has not crawled it yet (under 2-3 weeks since launch, no inbound links); (2) the Search Console property was never verified, so Google has not received the sitemap submission; (3) Settings > Crawlers has 'Block search engines from indexing this site' checked, possibly from a previous draft state; (4) a page-level noindex flag is left on from a draft, page-by-page; (5) the site is genuinely thin — too few pages, too little content, too few links pointing at it — for Google to prioritise indexing it over higher-authority alternatives.
Each cause has a fix in the diagnose leaf. The pattern: walk through the list from top to bottom, fixing the first one that applies. The vast majority of "not showing" tickets resolve at step 1, 2, or 3 — the new-site timeline, the Search Console verification, or the crawlers toggle. Steps 4 and 5 are real but less common.
§03Sitemap
The Squarespace sitemap, what it includes and what it omits
Squarespace auto-generates /sitemap.xml from your indexable pages. The file lists every page that is published, not noindex, and not password-protected — including blog posts, product pages, collection items, and standard pages. It does not list draft pages, noindex pages, password-protected pages, or pages on a disabled site. The file refreshes in near-real-time when you publish, edit, or remove a page. You cannot edit the sitemap by hand.
Google's sitemap documentation1 describes the format requirements (XML, UTF-8, < 50,000 URLs per file, < 50 MB uncompressed) and the submission process via Search Console. Squarespace's auto-generated sitemap meets all the format requirements; the only thing you do is submit it once.
textHow to submit the Squarespace sitemap to Google Search Console
# Step 1: Verify the property in Search Console (DNS TXT, HTML meta, or HTML file)# — see the search-console leaf for Squarespace-specific paths.# Step 2: In Search Console, open Sitemaps in the left sidebar.# Step 3: Enter "sitemap.xml" in the input box. Click Submit.# Step 4: Wait. Google fetches the sitemap within hours, indexes pages over days to weeks.# Step 5: Re-check the Sitemaps report weekly. "Success" status means Google read the file.
§04Search Console
Google Search Console setup, three verification paths
Three verification methods work on a Squarespace site: DNS TXT (add a TXT record to your domain DNS — works for any domain, requires DNS access), HTML meta tag (paste a meta tag into Settings > Advanced > Code Injection > Header — works on Business plan and above), HTML file upload (Squarespace does not support root-level file uploads, so this method does not work on Squarespace). The DNS TXT method is the canonical recommendation because it survives template changes and Code Injection edits.
Google's verification documentation2 lists five methods total (DNS TXT, HTML meta, HTML file, Google Analytics, Google Tag Manager). Three work on Squarespace: DNS TXT, HTML meta, and the GA / GTM paths (if you have those installed already). The HTML-file-upload method does not work because Squarespace does not allow root-level file uploads — the same constraint that produces the llms.txt workaround in Pillar 1.
§05noindex
noindex on Squarespace, the right way
To hide a single page from Google, open Page Settings > SEO and check 'Hide this page from search results'. This emits a <meta name='robots' content='noindex'> tag in the page head and removes the page from /sitemap.xml. To hide the entire site, Settings > Crawlers > 'Block search engines from indexing this site' applies the same noindex sitewide. Page-level noindex is the right tool for draft pages, internal-use pages, thank-you pages, and content that should not surface in search.
Google's noindex documentation4 is unambiguous: the noindex meta tag is honoured by all major search engines and is the canonical way to keep a page out of the index. The page must remain crawlable for Google to read the noindex directive — blocking the page in robots.txt while also marking it noindex prevents Google from seeing the noindex, which is a common configuration mistake.
§06Crawl errors
Crawl errors in Search Console, what they actually mean
Search Console's Pages report groups indexing issues into named categories. The most common on a Squarespace site: 'Discovered - currently not indexed' (Google knows the URL but hasn't crawled it yet — usually a low-authority signal); 'Crawled - currently not indexed' (Google crawled but chose not to index — usually thin content or duplicate of another URL); 'Soft 404' (the page returns 200 OK but the content reads as 'not found' — rare on Squarespace); 'Server error (5xx)' (Squarespace returned a 500-class error — usually transient). The crawl-errors leaf decodes each one with the Squarespace-specific cause.
Each category in the Pages report has a "Learn more" link that opens Google's documentation5. The fix often is platform-specific — "Discovered - not indexed" on Squarespace often resolves once internal linking to the page improves, or once external links start pointing at the URL, which gives Google a reason to prioritise the crawl.
§07Pagination
Pagination on Squarespace blogs and store collections
Squarespace blogs paginate at a configurable per-page post count, usually 7 by default. Pagination URLs look like /blog?offset=... — these are technically separate URLs, indexable by default. Google retired rel=prev/rel=next in 2019, so pagination is now handled implicitly by Google's crawler. The owner action: keep the per-page count reasonable (10-15), ensure paginated pages have unique content (Squarespace handles this automatically — each paginated page shows different posts), and accept that paginated archives compete weakly with deep individual post URLs.
Squarespace's pagination documentation8 covers the per-page count setting and the URL pattern. For ecommerce collection pages, the same pagination pattern applies to product lists. The pagination leaf in this cluster walks through the configuration and the diagnostic for when paginated archives accidentally outrank the canonical landing page.
§08Summary
The full diagnose flow, summarised
Eight steps cover almost every 'not showing on Google' Squarespace ticket. (1) Site is published, live, and not password-protected. (2) Settings > Crawlers has search-engine crawling allowed. (3) Search Console property is verified. (4) Sitemap submitted via Search Console > Sitemaps. (5) Homepage URL Inspection in Search Console returns 'URL is on Google' or 'Indexing requested'. (6) Top pages don't have 'Hide this page from search results' checked. (7) Pages > Indexing report in Search Console shows expected page counts. (8) PageSpeed Insights returns no fatal errors on the homepage. The diagnose leaf walks through each step with screenshots.
The diagnose leaf is the most-read page in this cluster on field tests. Owners arrive there from the "my Squarespace site is not on Google" search query, and the eight-step pass usually identifies the cause inside ten minutes. Steps 1-4 take five minutes total. Steps 5-8 take longer but only when the first four passed.
§09FAQ
Five questions Squarespace owners ask about indexing
The five most-asked questions about Squarespace indexing, answered in the format AI engines prefer.
Why is my new Squarespace site not showing in Google?
The most common cause for a site under three weeks old is simply that Google has not crawled it yet. Verify the property in Google Search Console, submit your sitemap, and request indexing on the homepage. Google's documentation states a typical timeline of 1-21 days for a new domain to start appearing.
Where is the sitemap on Squarespace?
At yoursite.com/sitemap.xml. Squarespace generates the sitemap automatically from your indexable pages. You cannot edit it by hand. Pages marked 'Hide this page from search results' are omitted automatically.
Do I need to submit my Squarespace sitemap every time I add a page?
No. Squarespace updates /sitemap.xml in near-real-time when pages are added, edited, or removed. Google re-fetches the sitemap on its own cadence — typically every few days for active sites. Manual re-submission is rarely needed.
How long does it take for a new page to show up in Google?
On an established site with a verified Search Console property, new pages typically appear in Google within 1-7 days. On a brand-new site, 2-21 days. Using Search Console's URL Inspection tool to request indexing can accelerate the timeline by hours to days.
What does 'Discovered - currently not indexed' mean in Search Console?
Google knows the URL exists (usually via the sitemap) but has not crawled or indexed it yet. Most common causes: site authority is too low for Google to prioritise, the URL is buried deep in the site structure, or Google's crawl budget for the domain is fully allocated. Building internal links to the page and earning external links helps.
