Squarespace SEO: the settings that exist, the ones that do not

Squarespace covers the basics. It ships an automatic XML sitemap, automatic canonical tags, and built‑in structured data on blogs and products. You get per‑page fields for the title and the meta description. You can edit URL slugs. Images let you set alt text. You can create 301 redirects with URL mappings.

Squarespace does not let you edit robots.txt. There is no plugin system. If you need features outside these, you work with what is there, or you move parts to a different stack.

• Works out of the box: sitemap, canonicals, blog and product schema
• Editable per page: SEO title, meta description, URL slug, page visibility
• Media: alt text through image settings
• Site moves: 301 redirects with URL mappings
• Does not exist: editable robots.txt, plugins

Edit the title and meta description on every important page. These control the search snippet. Keep the title under about 60 characters to avoid truncation. Use the primary term near the start when it fits the line.

1. 1

   Set the SEO title

   Open the page settings, then SEO. Write a short line that matches the query. Example: for /pricing, use “Pricing and plans for YourProduct”.

2. 2

   Write a meta description

   One sentence of 120 to 155 characters that earns a click. Include one feature or outcome. Example: “Choose a plan, start a 14‑day trial, cancel any time.”

3. 3

   Check the URL slug

   Make it short and descriptive, like “pricing” or “guides/getting-started”. Avoid dates unless you publish news.

4. 4

   Set page visibility

   If the page should not appear in search, use the per‑page visibility controls to hide it. Do this before you publish.

On a fixed page, the title reads cleanly in about 60 characters, the description fits in one line on mobile, and the slug matches the nav label. The copy on the page then answers the search intent in the first screenful.

Squarespace generates robots.txt for you. You cannot change it. When you need to block or allow specific content, you must work per page or by redirecting. For sections you are not ready to ship, keep them out of your navigation and hide them from search at the page level.

• Hide single pages: use the page’s visibility setting to keep it out of search
• Remove thin variants: consolidate duplicate pages and 301 redirect the others
• Private areas: use password protection while you build, then remove it when live
• Parameter URLs: link only the clean canonical URL in your menus and content

Slugs are editable in Squarespace. Keep them short, lowercase, and human. Use clear folders for sections you plan to grow, like /guides/ or /blog/. Match the navigation labels. Avoid keyword stuffing. One or two words are enough for most top‑level pages.

1. 1

   Plan the top level

   Map the five to seven core pages: /, /pricing, /features, /guides, /about, /contact. Add /blog if you publish.

2. 2

   Name folders for scale

   Use /guides/topic or /blog/post-title for content. Keep product areas flat to reduce click depth.

3. 3

   Avoid slug churn

   Pick a slug and keep it. If you must change it, create a 301 redirect from the old path to the new one.

A clean structure helps users and crawlers. On a fixed site, /guides/getting-started links back to /guides and across to related guides. The breadcrumb in your design mirrors the folder path, even if the platform handles navigation without explicit breadcrumbs.

Squarespace supports 301 redirects through URL mappings. Use them for slug changes, deleted pages, and site moves. Plan redirects before you publish a restructure. Keep a map in a spreadsheet: one column for the old URL path, one for the new one.

• Change /blog/my-post to /guides/my-post: 301 the old to the new
• Remove /features/old-addon: 301 to /features or to the closest match
• Merge two guides: 301 the weaker to the stronger page
• Fix case and trailing slash variants: pick one form and 301 the others

After you add mappings, check a few with a redirect checker. In Search Console, watch the index coverage and the performance of the target pages over 28 days. Expect old URLs to drop and the targets to absorb clicks.

Add alt text through the image settings. Describe the image for a screen reader, not for robots. If the image is decorative, leave alt empty. On product images, write what the photo shows, like “Blue canvas backpack, front view”.

Large images slow Largest Contentful Paint. Aim for LCP at or under 2.5 seconds. Use the smallest image that looks good in your template. Prefer images that compress well. Test a heavy page in PageSpeed Insights and fix the biggest files first.

Squarespace sets canonical tags automatically. This handles most duplicate paths and query strings. You still need to avoid creating near‑duplicates in your content. Do not publish two pages that target the same term with the same offer. Fold thin content up into one page and redirect the rest.

• One page for each intent: “/pricing” for prices, not two variants
• Clean internal links: always link the canonical path, not a parameter variant
• Avoid print or preview URLs in links and sitemaps
• Consolidate tag or category pages if they add no value

Squarespace includes structured data for blog posts and products. This helps eligibility for rich results. You do not need to add a plugin. Write clear titles, dates, prices and availability in the editor. These fields feed the schema that ships with the theme.

1. 1

   For blog posts

   Set a clear title, a publish date, an author, and a summary. Add a featured image. Keep the URL slug short. Test a post in the Rich Results Test.

2. 2

   For products

   Enter name, description, price, currency, stock status and images. Use product options where needed. Test a product URL in the Rich Results Test.

If you need schema types outside blogs and products, check the platform’s current settings. There is no plugin system. You may be constrained by what is built in. Focus on clean content and internal links when you cannot add more schema.

Use this on each new page. It keeps you within Squarespace’s settings and avoids dead ends you cannot fix later.

1. 1

   Pick the intent

   Write down the exact query the page earns, like “squarespace seo settings”. If two pages would target the same query, merge the plan.

2. 2

   Name the slug

   Choose a short slug, like “seo-settings”. Do not ship a draft path that you will change later.

3. 3

   Write the title

   Stay under about 60 characters. Put the main term first when it reads well. Example: “SEO settings in Squarespace: what to change”.

4. 4

   Write the description

   One sentence, 120 to 155 characters. Promise the answer. Example: “Set titles, descriptions, slugs and redirects, and avoid pages you cannot index.”

5. 5

   Build the first screen

   In the editor, make the h1 say the topic, then answer it in two or three lines. Add a link to your /pricing or /signup if it fits.

6. 6

   Add internal links

   Link to two or three relevant pages, and add one or two links back from older pages to this one. Use short, literal anchor text.

7. 7

   Set image alt text

   Add alt text on key images. Keep it literal, like “Screenshot of URL mappings in Squarespace”.

8. 8

   Publish and test

   Load the page on mobile. Check LCP, CLS and INP in PageSpeed Insights. Fix any image or script that hurts the first paint.

9. 9

   Watch Search Console

   After indexing, check the Performance report over 28 days. If the page shows but never gets clicks, revisit the title and the intro.

You cannot edit robots.txt. If you plan large sections that need fine control, you will not be able to set crawl rules. Plan your information architecture so that only clean URLs are public. Use redirects to clean up stray paths.

There is no plugin ecosystem. Titles, descriptions, canonicals and schema outside blogs and products are not extensible through plugins. If you need custom schema for software, events, or FAQs at scale, you may be constrained. Decide if the feature is critical to growth before you commit content plans that depend on it.

Core Web Vitals still apply. Good LCP up to 2.5 s, CLS up to 0.1, and INP up to 200 ms. Heavy images and scripts in your design will penalise these, no matter the CMS. Keep templates lean, keep hero images small, and audit any embeds you add.

Squarespace generates an XML sitemap. Submit it in Search Console. When you add or remove pages, the sitemap updates. If a page must not be indexed, hide it from search so it is not sent in the sitemap or crawled through your menus. Keep orphan pages out of the build by removing links to them.

• After launch: add your domain to Search Console and submit the sitemap
• After a restructure: recheck the sitemap entry count and sample a few URLs
• When deprecating content: 301 redirect and ensure old URLs drop out of the sitemap