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

Blogging SEO · Tag Noindex · § 2.8.2

Squarespace Tag Archives Are Noindex by Default

Squarespace 7.1 tag and category archive pages render with a <meta name="robots" content="noindex"> tag in the head element by default1. This is the protection that has let owners use tags casually without producing the thin-archive penalty WordPress blogs ran into through the late 2010s. The verification is a 30-second View Source pass; the rare cases where the default is missing are template-specific and the fix is a single Code Injection snippet.

This page covers what noindex does on a tag archive, the verification one-liner, the cases where the default is missing, and the Code Injection override. Pair this with the tags vs categories leaf for the broader taxonomy decision.

What noindex does on a tag archive

The noindex meta tag tells search engines to read the page but not include it in search results<InlineCite n={2} sourceId='google-noindex' />. On a tag or category archive page, this prevents the auto-generated list of post excerpts from competing in search results against the original posts themselves. Without noindex, the archive page often shows up for the tag name as a query (because the page header explicitly is that tag) and outranks better-written individual posts on the same topic. With noindex, Google still crawls the archive (so internal links to and from the archive count), but the archive itself stays out of the index.

The thin-content risk noindex protects against is real and well-documented. Auto-generated archive pages with only post excerpts (no editorial introduction, no curated context, no original commentary) are the classic Google helpful-content failure case3. The pages have a clear topical signal (the tag name) but no substantive content to back it, and Google's algorithms have been consistent for years about filtering these out. The noindex default takes the entire question off the table — owners can use tags freely without producing competing archive URLs.

What the default protects

noindex

the meta robots value Squarespace 7.1 injects automatically on /tag/ and /category/ archive URLs.

Squarespace Help · 2026-Q1
Crawled

noindex pages are still crawled — internal links to and from them count, only indexation is blocked.

Google Search Central · 2026-Q1
Thin

the Google helpful-content classification the default avoids — auto-generated archives without context.

Google Search Central · 2026-Q1

Verify the default with View Source

The verification is a 30-second pass per blog. Open /tag/{any-tag}/ in the browser, run View Source (Cmd+Option+U or Ctrl+U), search the rendered HTML for 'robots'. The expected match in the head element is <meta name='robots' content='noindex'>. Repeat for /category/{any-category}/. If both archive types render the noindex meta, the default is working and no further action is needed. If either is missing, the template requires a Code Injection override.

The View Source check is preferable to the Inspect Element check because View Source shows the HTML Squarespace renders server-side, which is the HTML Google receives. Inspect Element occasionally shows DOM modified by JavaScript that runs after page load, which Google's renderer may or may not see depending on rendering budget. View Source is the conservative, reliable check.

When the noindex default is missing

The default can be missing in three scenarios. Heavily-customised 7.0 templates with template-file overrides that removed the auto-injected meta. Some legacy 7.0 cover-page templates that did not include the noindex behaviour. Custom-coded template injections that removed standard head elements during a brand redesign. In all three cases, the gap is template-level — the platform's default behaviour is to ship noindex; the gap exists because the template-level code has been modified.

The fix is a Code Injection override at the site level. Settings > Advanced > Code Injection > Header lets owners add HTML or JavaScript that loads on every page. A JavaScript snippet that detects /tag/ and /category/ URLs and injects a noindex meta tag dynamically resolves the gap without needing to edit the template directly.

Force noindex via page-level Code Injection

The override snippet checks the URL path on page load and injects a noindex meta tag into the document head if the URL matches /tag/ or /category/. Place the snippet in Settings > Advanced > Code Injection > Header. The snippet runs on every page but only takes effect on tag and category archive URLs. Google's renderer reads JavaScript-injected meta tags reliably in 2026, so the runtime injection is functionally equivalent to the server-rendered default.

HTML Site-level Code Injection (Header) to force noindex on tag and category archives 
 <script> if ( window.location.pathname.startsWith('/tag/') || window.location.pathname.startsWith('/category/') ) { const meta = document.createElement('meta'); meta.name = 'robots'; meta.content = 'noindex'; document.head.appendChild(meta); } </script>

The snippet is harmless on pages that already have noindex (the second meta tag does not contradict the first) and harmless on pages that are not tag or category archives (the URL check fails, no injection happens). It is safe to leave installed indefinitely as a belt-and-braces safeguard even on templates where the default works correctly.

Keep reading · § 2.8.2