Squarespace Blog SEO, the 2026 Way

The platform-level baseline is reasonable. What Squarespace ships is enough to run a blog with adequate technical SEO out of the box, which is more than can be said for some platforms a year ago. What it does not ship is the layer that matters in 2026: the supplemental Article + Person + Publisher schema that lifts E-E-A-T, the 134-167 word passage discipline that lifts AI citation, the topic-cluster internal-linking pattern that lifts whole-cluster rank, and the editorial discipline (named sources, dated claims, specific numbers) that separates a post AI engines quote from a post AI engines skim past.

The good news is that none of those gaps require leaving Squarespace. The supplemental schema goes in via Code Injection. The passage discipline is a writing pattern that any author can adopt. The topic-cluster pattern is internal linking discipline. The editorial polish is an editor's job and travels between platforms. The work is real, but it is not platform-locked.

Each of the six has a leaf or section that goes deep on the mechanics. The pattern across them is the same: Squarespace's defaults are mostly correct, but the editorial habits authors carry from 2018-era blogging guidance are systematically wrong for the 2026 ranking and citation surfaces. The leaves below cover taxonomies, URL structure, the noindex archive question, excerpt/meta separation, and the diagnostic when a post that used to rank quietly disappears.

The 134-167 word band⁷ is not a rigid target. It is the centre of a distribution. Sections with leads at 110 words still extract; sections with leads at 220 words still extract; sections with leads at 50 words and 400 words extract noticeably less often. The band describes the most-reliable middle, and the editorial discipline is to open every section with a lead in roughly that range, then expand with the why and how.

Squarespace's blog editor renders Markdown blocks and Text blocks identically as far as Google and AI engines are concerned. Use either. The pattern that does need attention is the H2 hierarchy: 7.1 templates sometimes render an H1 for the post title and then start the body at H2 — but section templates occasionally re-use H1 for design reasons. Run a quick browser View Source on any post and verify there is exactly one H1 (the post title) and that body sections use H2. The HTML hierarchy fix lives in the H1 fix leaf in the Code Injection cluster.

 <!-- one Squarespace Markdown block per H2 section --> <h2 id="the-question-this-section-answers">The question this section answers</h2> <p> <strong>The 134-167 word lead answer that stands alone.</strong> </p> <p>Expansion paragraph 1 — the why, with a named source: "According to ...".</p> <p>Expansion paragraph 2 — the how, with a specific data point.</p> 

The blog URL pattern³ is the single setting that has the highest cost when changed. Picking 'blog' versus 'journal' versus 'field-notes' as the slug is purely a brand choice — none of them helps or hurts SEO. What does cost rank is changing the slug after posts are published: every post URL changes, every backlink needs redirecting, every existing rank takes a temporary dip while Google reindexes. The full URL-structure leaf is at /blogging-seo/blog-url/.

The tags-versus-categories question¹ is one of the most-asked Squarespace blog questions in forums and remains under-answered. The short answer: pick categories as your primary grouping, ignore tags entirely, and let the noindex default protect you from any tag archive you accidentally create. The full reasoning lives in the tags vs categories leaf; the noindex behaviour verification is in the tag page noindex leaf.

The fabricated meta description Google generates from a post body is usually correct but rarely optimal. It picks the first reasonable paragraph, which on a Squarespace post is often the opening line — fine for short conversational posts, ineffective for long-form posts where the actual answer sits a few paragraphs in. The fix is one-time: write a 150-160 character meta description on the SEO panel for every post, ideally including the primary keyword once. The full pattern, the keyword-density rule, and the excerpt-versus-meta-description copy distinction are all in the excerpt SEO leaf.

The contrast with the homepage-link pattern most Squarespace blogs default to is stark. Linking every post back to the homepage in the author bio gives the homepage one more link's worth of authority and gives the blog post zero contextual link signal. Linking every post to two or three peer posts in the same cluster gives Google a clear topic graph to read, gives readers a path through related content, and gives AI engines the cross-citation structure they treat as a confidence signal.

The Squarespace-specific implementation note is straightforward: links inside Text or Markdown blocks count. Links inside Summary blocks (the auto-generated recent-post widgets) count less because they are auto-generated and Google detects the pattern. Editorial links inside the prose of related posts compound; widget links to "you may also like" do not.

The Squarespace-specific addition to the generic 'why did my post drop' checklist is the template-shift question. Squarespace occasionally updates 7.1 section templates in ways that change rendered HTML. A post that ranked under one template version can underperform after a section is rebuilt with a different block layout — usually because the H1/H2 hierarchy shifted or because the post text moved inside a different semantic wrapper. The diagnostic, including the View Source one-liner that detects the shift, lives in the post not ranking leaf.