The single most damaging thing you can do to a new Squarespace site takes about four seconds: leave the search engine visibility toggle switched off after launch day. It sits under Settings, buried behind a couple of clicks, and it tells Google to stay away. This Squarespace SEO checklist is a pre-launch pass you run in one sitting, and that toggle is item one for a reason.
What follows is organized by where the work lives inside Squarespace: site-wide settings, page-level metadata, images and speed, structure and internal linking, then the post-launch confirmations. Each item includes what it's for and what breaks if you skip it. Most of it takes an afternoon.
Enable search engine visibility and set your primary domain first
These are the global switches. Get them wrong and every page inherits the problem, which is why they come first in any Squarespace SEO checklist worth running.
- Search engine visibility. Squarespace hides new sites from crawlers while you build, and it does not un-hide them for you. Turn it on the moment you go live, then verify by loading yoursite.com/robots.txt in a browser tab.
- Primary domain. Pick one canonical domain and set it as primary. If your site answers on both a Squarespace-built-in address and your custom domain without one designated as primary, you're splitting signals across two versions of the same content.
- SSL setting. Set it to secure with HTTPS preferred, not the permissive option. You want every request landing on the encrypted version, not bouncing between two.
- Site title and tagline. Squarespace pulls these into your title tag format by default. Write the tagline as a real description of what you do, not a mood ("Custom Squarespace design for nonprofits and service businesses" beats "Where ideas take shape").
- Squarespace Analytics plus Google Search Console. Connect both. Analytics tells you what happened on your site; Search Console tells you what happened before people got there. You need the second one to catch indexing errors, and you want it verified before launch so the data starts clean.
One thing that trips people up: the title tag format Squarespace applies site-wide can be overridden per page, but the default format applies to any page you don't touch. If you leave it, every page reads as Page Name — Site Title, which is fine for a Contact page and wasteful on your main service page.
Write metadata individually for each page before launch
This is the slow part. There's no bulk editor in Squarespace, so you open each page's SEO panel and write the fields by hand. Budget ten minutes per page and do it before launch, because retrofitting metadata across a live site is the sort of task that stays on a list for months.
Keep title tags between 50 and 60 characters, keyword first
Aim for roughly 50 to 60 characters so Google doesn't truncate it. Lead with the phrase someone would type, then the brand. A home page reading "Freelance Squarespace Designer | Sitekik" does more work than "Home." Every page gets its own; no duplicates.
Meta descriptions should pitch the page, not summarize it
Around 150 to 160 characters, written as a pitch rather than a summary. Google may rewrite it, but a good one earns clicks when it survives. Skip the keyword stuffing and write the sentence you'd say out loud to someone asking what the page is about.
Clean URL slugs are short, lowercase, and hyphenated
Short, lowercase, hyphenated, no stop words. Squarespace auto-generates slugs from page titles, which produces things like /our-services-and-what-we-offer when /services would do. Clean them before launch, because changing a slug after indexing means setting up a redirect, and there's a whole approach to writing slugs that give Google context worth reading if you're unsure where to cut.
Enforce one H1 per page by demoting auto-generated duplicates
One H1 per page, and it should describe the page, not welcome the visitor. Squarespace's text blocks default to Heading 1 in some layouts, so a page can ship with three H1s without anyone noticing if nobody checks. Open each page, scan the heading levels, demote the extras to H2.
Social sharing images prevent grey rectangles and lost clicks
Set a social sharing image per page or at least site-wide. Without one, a link pasted into Slack or LinkedIn renders as a grey rectangle, and that grey rectangle costs you clicks that Google never sees but your traffic does.
Compress and resize images before upload to boost page speed
Squarespace serves responsive image sizes automatically, which handles a lot. It does not handle a 6MB hero photo you exported straight out of Lightroom. Compression is on you.
Resize before upload. A full-width banner rarely needs more than 2500px wide; a portrait in a two-column layout needs half that. Export as JPG at around 70 to 80 percent quality, run it through a compression tool, and check the file size before it goes near the media library. Under 500KB for a hero, well under 200KB for everything else, is a sane target.
Then write alt text. Real alt text, describing what's in the frame: "Volunteer sorting donated coats at a folding table" rather than "image1" or a keyword dump. It's an accessibility requirement first and an image search signal second, and Squarespace makes it easy to skip because the field is tucked behind the image editor's content tab.
A few other speed items that matter on Squarespace specifically:
- Font loading. Every custom font family and weight you add is another request. Two families and three weights total is plenty. If you've uploaded your own font files, trim the weights you never use.
- Third-party embeds. Chat widgets, booking tools, analytics scripts, social feeds. Each one loads external JavaScript. Audit what's in Code Injection and delete anything you added during the build and forgot about.
- Video backgrounds. They look great and they're heavy, especially on mobile over a weak connection. If you use one, make sure a static poster image shows first.
- Mobile check on a real phone. Not the browser preview. Pull the site up on an actual device, on cellular data, and watch how long the hero takes to paint. That's what a visitor experiences.
If you only do two things from this entire list, compress your images and turn search visibility on. Everything else is refinement on top of those.
Limit primary navigation to five or six items
Search engines read your navigation as a map of what you consider important. A site with fourteen top-level nav items has told Google that nothing is important.
Keep the primary nav to five or six items. Push everything else into footer navigation or subpages. Then check that every page you care about is reachable within two clicks of the home page, because a page linked from nowhere is a page that gets crawled last and ranked worst.
Internal linking is where most new Squarespace sites leave value sitting on the floor. Your service pages should link to relevant blog posts, and those posts should link back to the service page they support. Use descriptive anchor text. Write the sentence first and drop the link into it, so the link reads as part of the thought rather than a signpost bolted to the end of the paragraph.
Check your 404 handling too. Squarespace ships a default 404 page that's functional and forgettable. If you're launching a rebuild rather than a brand-new domain, mapping old URLs to new ones matters far more than the design of the error page, and setting up 301 redirects properly is the difference between keeping your existing rankings and starting over.
Migrating from another platform makes this urgent rather than optional. The importer brings your posts across and leaves your URL structure, title tags, and redirects behind, which is covered in more detail in this straight-talking accounting of what transfers in a Squarespace migration. Build the redirect map before you switch the domain over, not after traffic drops.
Every page needs enough substance to rank for its target query
Thin pages are the quiet failure of new Squarespace sites. A service page with a headline, a stock photo, and two sentences gives Google almost nothing to rank. Each page that you want found should carry enough substance to answer the question someone typed to get there — typically a few hundred words minimum, structured with real subheadings.
Run through this before launch:
- Every page has a unique title tag and meta description. No duplicates, no blanks.
- Location is stated in plain text somewhere on the site if you serve a geographic area. City and region in the footer, plus on the contact page.
- Contact information is real text, not baked into an image. Phone numbers and addresses in images are invisible to crawlers.
- Every page has one clear next action. A page that ranks and converts nobody was still a wasted ranking.
- No lorem ipsum. Search a live preview for "lorem" before you launch. It happens more than anyone admits.
Some of this you can eyeball. Some of it needs a browser tab open with each page's source, checking that the title tag renders what you typed. Ten minutes of paranoia here saves a month of wondering why nothing indexed.
Submit your sitemap to Search Console and request indexing manually
Launching isn't the end of the checklist; it's the point where you can finally verify half of it.
Submit your sitemap to Google Search Console. Squarespace generates one automatically at yoursite.com/sitemap.xml, and submitting it prompts a crawl instead of waiting for Google to notice you exist. Then request indexing on your three or four most important pages individually through the URL Inspection tool.
Give it a week, then check the Coverage report for pages excluded from indexing. Common culprits: pages set to hidden or password-protected in Squarespace, pages you disabled from the sitemap in the page settings, and canonical tag confusion on product or collection pages. Fix what shows up.
Watch the Core Web Vitals report as data accumulates. It needs real visitor traffic before it reports anything meaningful, so expect a few weeks of silence. When it does populate, Largest Contentful Paint is usually the metric that flags first on Squarespace sites, and it's almost always an uncompressed hero image or a font loading late.
Finally, set a calendar reminder for 30 days out to look at which queries Search Console shows you appearing for. They're rarely the ones you planned for, and that gap is the most useful piece of information you'll get in your first month.
Technical setup cannot replace thin or irrelevant content
None of the above will rank a site with nothing to say. Technical setup removes the obstacles between your content and Google; it doesn't manufacture reasons to rank. If your competitors have forty pages answering buyer questions and you have five pages of brand language, no amount of alt text closes that gap.
Nor does this address competitive analysis, keyword research, or the ongoing work of publishing. Those are separate disciplines and they matter more over a two-year horizon than anything on this list. What a pre-launch pass buys you is a clean starting line. If you're weighing whether your current site needs a full rebuild before any of this is worth doing, there are signals that a redesign is truly overdue versus ones that look urgent and aren't.
Frequently asked questions
How long does it take to work through a Squarespace SEO checklist like this?
Working through a Squarespace SEO checklist takes roughly four to six hours for a ten-page site, spread over two sittings. Site-wide settings take twenty minutes. Page metadata is the bulk of it at around ten minutes per page, and image compression depends entirely on how many photos you're shipping. Do the settings first so the rest of the work isn't invisible to crawlers while you finish.
Is Squarespace bad for SEO compared to WordPress?
No, though it's less flexible. Squarespace handles sitemaps, mobile responsiveness, SSL, and clean markup without configuration, which removes several categories of problem WordPress users spend plugins solving. What you give up is granular control: you can't edit robots.txt directly, schema options are limited without custom code, and there's no bulk metadata editing. For most service businesses and nonprofits, that trade is fine.
Do I need to add schema markup to my Squarespace site?
Squarespace adds basic structured data on its own for blog posts, events, and products. Local business schema is the one worth adding manually if you serve a specific area, since it feeds the information Google uses for local results. It goes into Code Injection as a JSON-LD script block, and it's a reasonable job to hand to whoever handles your custom code work rather than pasting something you found and hoping it validates.
Should I launch with a blog or add one later?
Launch with at least three published posts if you plan to have a blog at all. An empty blog page linked in your navigation reads as abandoned to a visitor and as a thin page to Google. If you're not ready to publish, leave the blog off the nav until you are.
What breaks most often after launch?
Redirects from a previous site, and images that were never compressed. Redirects fail silently: your old pages start returning 404s, rankings drift down over weeks, and nothing on your dashboard announces it. Check Search Console's Coverage report at the two-week mark specifically for a spike in not-found errors.
Follow a Squarespace SEO Checklist: Start With Site-Wide Settings, Then Handle Page Metadata Before Telling Anyone You're Live
Open Settings, confirm search engine visibility is on, then work down the site-wide list. That's twenty minutes and it unblocks everything else. The page-by-page metadata pass can wait until the weekend if it has to, but do it before you start telling people the site is live.
If you'd rather have this handled as part of a build than run the Squarespace SEO checklist yourself, that's the sort of thing that gets baked into a project rather than bolted on afterward — you can see how it shows up in finished work across the Squarespace design portfolio. Either way, run the checks. A site nobody can find is an expensive brochure.
