Skip to content
50% OFF $299 $599
Lock in
§ 2.8.3 ARTICLE
Published VerifiedEvery 6 weeks Sources3 named Authored bySquareRank Team

Blogging SEO · Blog URL · § 2.8.3

Squarespace Blog URLs

Squarespace 7.1 blog post URLs follow /{blog-slug}/{post-slug}/1. The blog slug is set when you create the blog page and is shared across every post; the post slug is per-post. Pick the blog slug ('blog', 'journal', 'field-notes', 'writing') before publishing the first post and never change it. Every rename forces a redirect chain across every post and produces a small ranking dip while Google reindexes.

This page covers the 7.1 pattern, the legacy 7.0 patterns you might inherit on a migration, and the safe rename via URL Mappings when a rename is unavoidable.

The 7.1 blog URL pattern in 2026

Squarespace 7.1 blog posts live at /{blog-slug}/{post-slug}/. The blog slug is whatever you named the blog page when you created it ('blog', 'journal', 'field-notes', 'writing' are the most common). The post slug is set per-post on the post editor's SEO panel, defaulting to a lowercase-hyphenated version of the post title. Categories add a /category/{name}/ archive URL; tags add a /tag/{name}/ archive URL — both share the same noindex default. The pattern is consistent across all 7.1 templates and across every blog page on the same site.

The pattern means a typical blog post URL on a 2026 Squarespace site looks like /blog/how-to-optimize-product-descriptions/ or /journal/three-photographers-who-changed-my-mind/. The slugs are descriptive, lowercase, hyphenated, and stable — which is exactly what Google's URL guidance3 recommends for blog content.

The blog URL anatomy

{blog-slug}

the parent path — set once on the blog page, shared across every post. 'blog' is the most common default.

Squarespace Help · 2026-Q1
{post-slug}

the per-post identifier — set on the post SEO panel, lowercase-hyphenated, descriptive.

Squarespace Help · 2026-Q1
Stable

URL stability is a ranking signal — every rename costs a redirect chain and a small reindexing dip.

Google Search Central · 2026-Q1

Legacy 7.0 URL patterns you might inherit

Some 7.0 templates shipped date-based URL patterns: /blog/2018/03/15/post-slug/ or /blog/2018/march/post-slug/. These patterns have aged poorly — date prefixes look stale, force readers to re-evaluate the relevance of older posts before clicking, and create the impression that the content is dated when the underlying material may still be current. Migrations from these patterns to the 7.1 default require URL Mappings to redirect every historical URL to the new pattern.

The migration is straightforward in principle but tedious in execution. List every existing blog post URL, generate the new URL by stripping the date prefix, set up wildcard URL Mappings where possible (e.g. /blog/[year]/[month]/[name] -> /blog/[name] 301), verify a sample of redirects with the browser before deleting the old URLs. The transition typically takes one to four weeks for Google to fully consolidate the new pattern in its index, during which time some posts may rank below their pre-migration position.

Renaming the blog slug safely with URL Mappings

Renaming the blog slug — moving from /blog/ to /journal/, for instance — is a destructive operation. Every post URL changes the moment the rename saves. The safe approach: set up wildcard URL Mappings before saving the rename, save the rename, verify a sample of old URLs redirect cleanly to the new pattern, notify Google via Search Console. The wildcard mapping <code>/blog/[name] -> /journal/[name] 301</code> handles every post in a single line<InlineCite n={2} sourceId='sq-url-mappings' />.

The rename cost is real even with redirects. Google takes one to four weeks to fully consolidate the old and new URLs in its index. During that window, posts may rank below their pre-rename position. Inbound links to old URLs continue to work via the 301s but pass slightly less link equity than direct links to the new URLs would. The recommendation: rename only when there is a strong brand reason (the existing slug is materially confusing or misaligned with the current brand voice), and never rename more than once.

Keep reading · § 2.8.3