What Google Search Console is, and why verification matters
Google Search Console is Google's free, official tool for site owners — the place to submit sitemaps, see indexed-page counts, diagnose crawl errors, monitor Core Web Vitals, see which queries drive traffic, and request indexing of new pages. Verification proves to Google that you own the property; without it, Search Console returns no data for the domain. Verification is one-time per property. Every Squarespace site that wants Google visibility starts with a verified Search Console property.
Domain property vs URL prefix property
Search Console lets you create two property types. Domain property covers your entire domain — all subdomains, all protocols (http/https), all paths. Verification is via DNS TXT only. URL prefix property covers exactly one origin (e.g. https://www.yoursite.com but not https://yoursite.com). Verification works via any of the methods. Choose Domain unless you have a specific reason not to: it's more comprehensive, consolidates data across subdomains, and survives DNS-level changes.
Method 1: DNS TXT (recommended)
Google generates a TXT record like 'google-site-verification=abcd1234...'. You add it to your domain's DNS as a TXT record at the root (@). Within minutes, Google confirms the record and verifies ownership. The method works regardless of Squarespace plan, regardless of template, regardless of any Code Injection state. It survives template changes, plan changes, and Code Injection edits.
Method 2: HTML meta tag (the URL prefix fallback)
Google generates a meta tag like <meta name='google-site-verification' content='...'>. You paste it into Squarespace's site-wide Code Injection header. The page now renders the meta tag on every page. Google fetches the homepage, sees the tag, and verifies ownership. The method requires Code Injection access — Core plan and above per Squarespace's documentation.
Why HTML file upload does not work on Squarespace
Google's third verification method asks you to download a small HTML file (google[token].html) and upload it to your site's root. Squarespace does not allow root-level file uploads — there is no FTP, no SFTP, no /public folder, no developer mode field for adding files to the document root. The same constraint produces the llms.txt workaround pattern in Pillar 1. For Search Console verification, the cleaner path is to skip the HTML file method entirely and use DNS TXT or HTML meta tag.
Method 3: Google Analytics or Google Tag Manager
If you already have Google Analytics or Google Tag Manager installed on your Squarespace site, Search Console can verify via the existing tag. The Analytics method requires the gtag.js or analytics.js code is loaded on the page Google verifies against. The Tag Manager method requires the GTM container is loaded. Both are fast (near-instant verification) and don't require touching Squarespace's settings. Useful when DNS and Code Injection are inconvenient.
What to do immediately after verification
Three steps after the property verifies green. (1) Submit /sitemap.xml under Sitemaps in the left sidebar. (2) Open URL Inspection (search bar at top) and inspect your homepage URL — if it returns 'URL is on Google', you're indexed; if not, click 'Request indexing'. (3) Set up the Performance report — within a few days, you'll see queries driving traffic, clicks, impressions, and average position. Search Console's data is delayed by 2-3 days; expect the dashboard to populate over the first week.