What a URL slug is, and why it matters
A URL slug is the visible, human-readable portion of a page's URL that lives after the domain — '/about' on yoursite.com/about, '/blog/coastal-palettes' on a blog post. Google's URL-structure guidance recommends descriptive, simple, hyphen-separated, lowercase URLs because they help users and search engines understand the page before clicking. The slug is one of the three SERP elements visible to users alongside the title and description, and it travels with every shared link, so it directly affects both click-through rate and link-sharing perception.
Squarespace's slug rules and the SEO-aligned pattern
Squarespace accepts lowercase letters, numbers, and hyphens in slugs. It rejects spaces, capital letters, and most special characters automatically — entering a space becomes a hyphen, an uppercase letter becomes lowercase. The platform also strips most punctuation. The SEO-aligned pattern: short (3-6 words), descriptive of the page's primary topic, hyphen-separated, no stop words like 'a', 'the', 'and' unless they materially aid readability, no dates.
Changing a slug after a page is published
Open Page Settings > General. Edit the URL Slug field. Save. The page now lives at the new path — but the old path returns 404 unless you add a URL Mappings 301 redirect. Squarespace does not automatically generate redirects from old slugs to new ones (with one exception: a tiny set of system pages like /shop). For every slug change on a published page, the workflow is: change the slug, immediately go to Settings > Advanced > URL Mappings, add 'old-slug -> /new-slug 301', save.
The URL Mappings redirect pattern, in code
URL Mappings live at Settings > Advanced > URL Mappings. The syntax is line-by-line: source path on the left, arrow, destination path on the right, status code on the far right. 301 is permanent; 302 is temporary (rarely the right choice for slug changes). Wildcards work with an asterisk for bulk patterns. Multiple lines for multiple redirects.
Blog and collection page slugs are different
Blog posts and collection items (products, events, portfolio entries) have their own URL slug field, separate from regular page slugs. The slug field on a blog post lives at the post's Settings > URL Slug. The collection itself (the parent page, e.g. /blog/) has its own slug at Page Settings > General. The two are concatenated: a blog at /blog/ with a post slug 'coastal-palettes' renders at /blog/coastal-palettes.
Four Squarespace-specific slug gotchas
First: the slug field has a maximum length, and Squarespace silently truncates very long slugs. Aim for under 60 characters. Second: changing a slug while logged in does not invalidate the live cache immediately — visitors sometimes hit the old URL for a few minutes. Third: Squarespace reserves certain path prefixes (/s/, /api/, /config/) for internal use; do not use them as slugs. Fourth: the homepage does not have a user-editable slug — it always lives at /, regardless of what you'd prefer.