PublishedVerifiedEvery 6 monthsSources6 namedAuthored bySquareRank Team
Cluster 2C · the redirect spine
Squarespace 301 redirects
Squarespace 7.1 supports 301 and 302 redirects through one panel: Settings > Advanced > URL Mappings1. The syntax is exact — /old -> /new 301, one rule per line — and the panel rejects every other status code on save. Google treats a clean 301 as the permanent URL-change signal and passes full PageRank through it2.
This hub is the canonical install: the five syntax rules, a single-redirect walkthrough with curl verification, the four failures every Squarespace owner trips over, and four leaves that go deeper — bulk uploads, syntax reference, migration mapping, and the Google removal flow.
A 301 is an HTTP response code that tells a browser, a crawler, or an AI engine: this URL has permanently moved, fetch the new one instead. Google passes full PageRank through a clean 301 and treats it as the canonical permanent-move signal. A 302 is the temporary equivalent — the move is reversible, and Google may not consolidate the signal. On Squarespace 7.1, both are added through the same URL Mappings panel and both share the same arrow syntax. The status code at the end of each rule is the only thing that distinguishes them.
The behaviour matters because redirects are where SEO equity either survives or evaporates. A site that renames its services page from /services-list to /services without a 301 loses every backlink pointing at the old URL — the link still resolves to a 404, the inbound authority disappears, and the new URL starts from zero. With a clean 301 in place, the backlink resolves, the authority transfers, and ranking continues without interruption5.
Squarespace's documentation1 is explicit on the constraint: only 301 and 302 are accepted. The panel rejects 303 (See Other), 307 (Temporary Redirect), and 308 (Permanent Redirect) on save with no override. For the SEO use case this is fine — 301 is what Google wants for permanent moves2 — but it does mean Squarespace cannot do the things 307/308 enable on other platforms (preserving the HTTP method across the redirect, for example).
The hard limits
5,000
redirect rules Squarespace allows per site in URL Mappings as documented in the help reference.
One location: Settings > Advanced > URL Mappings. It is a single plain-text textarea, no row UI, no drag-to-reorder, no per-rule edit dialog. You paste rules in, one per line, and click Save. Squarespace validates each rule on save and surfaces a syntax error if any line fails — but the error message names the line number, not the rule, so a 500-line paste with a single typo can be slow to debug. There is no native CSV import as of Q2 2026, no row preview, and no test mode. What you see is what the server runs.
The panel itself is buried two clicks past the dashboard. The exact path: dashboard sidebar → Settings → Advanced → URL Mappings. The Advanced section also houses Code Injection, Developer Mode, and File Storage — adjacent panels that come up frequently in any redirect work. Bookmark the URL once and you stop hunting for it.
The textarea has a soft visual cap around 5,000 rules per the help reference1, but the harder cap is editor performance — pasting 4,000+ rules at once can lock the browser tab for several seconds while Squarespace validates the syntax. For larger migrations, paste in batches of 200-500. The bulk leaf covers the batching workflow in detail.
§03Syntax
The five syntax rules the panel enforces
Squarespace's URL Mappings panel enforces five hard rules and rejects rules that violate any of them on save. (1) Arrow must be a hyphen plus a greater-than with no space inside — `->`. (2) Status code is 301 or 302, nothing else. (3) Each rule on its own line. (4) Cannot redirect from `/` — the homepage root is off-limits. (5) External destinations must begin with `https://` and resolve to a real hostname. Get all five right and the rule saves; miss any one and the panel rejects on save with a line-number error.
The arrow is where most failures originate. Forum threads4 are full of =>, -->, and -> (with a space inside) syntax mistakes that fail silently or visibly. The correct token is exactly two characters: - immediately followed by >, with no whitespace between them. Squarespace is also strict about whitespace around the arrow — one space on each side, no more, no less.
URL MappingsThe five rule shapes Squarespace accepts (internal, external, wildcard, two slashes, query-string)
# 1. Simple internal redirect — most common/old-page->/new-page301# 2. External redirect — must use https:///booking->https://calendly.com/your-handle301# 3. Wildcard — match any value at [slug]/blog/old-section/[slug]->/blog/[slug]301# 4. Two-segment internal redirect/services/branding->/services/identity301# 5. Temporary redirect — 302 while a page is in draft/launch->/coming-soon302
The wildcard syntax — [slug] as a placeholder — is one of the panel's quieter strengths. It lets a single rule absorb thousands of legacy URLs that share a path prefix. For a blog migration where every post moved from /blog/old-section/post-name to /blog/post-name, a single wildcard rule replaces what would otherwise be hundreds of one-off mappings. The syntax leaf covers every wildcard pattern Squarespace recognises and the order-of-precedence rules when multiple wildcards could match the same incoming URL.
§04Install
Adding a single redirect, end to end
The whole sequence takes about 60 seconds once you know the path. Open URL Mappings. Paste one line in the textarea. Click Save. Then verify with curl — the verification step is the one most Squarespace owners skip, and it is the one that catches typos before they live on the production site for weeks. Below is the three-step walkthrough with the exact commands.
Two things to know before you paste: the source path is what users were typing in (the old URL), and the destination path is where you want them to land (the new URL). Both are relative to the domain — /old-page, not https://yoursite.com/old-page. The only time you use a full https:// URL is for external destinations.
01. Open URL Mappings
From the Squarespace dashboard: Settings > Advanced > URL Mappings. The panel opens to a plain textarea — if it already has rules in it from a previous edit, scroll to the bottom rather than typing in the middle of an existing block. Each rule should sit on its own line. A blank line between rule groups is fine and helps readability when you scan the panel later.
If you do not see the Advanced section, your Squarespace plan may be Personal-tier — URL Mappings is available on Business, Commerce Basic, and Commerce Advanced plans per the help docs1. Upgrade once and the panel appears. The plan upgrade is reversible, but losing the URL Mappings panel mid-migration is painful, so verify your plan before starting.
02. Paste the rule
One rule per line. Exact syntax. Use the format below. Click Save. Squarespace validates on save and rejects any line that violates the syntax rules — the error message names the failing line by number. If the save succeeds, the rule is live within seconds, no deploy step required.
URL MappingsThe single line — replace the paths with your own
/old-services->/services301
Common typos: => instead of ->, missing the status code, putting the status code first, using quotes around the paths. None of those work. The panel saves only when the syntax is exact.
03. Verify with curl
From any terminal — Mac, Linux, Windows PowerShell — run curl with the -IL flags to inspect headers and follow redirects. The expected response chain is a single 301 (or 302) at the old URL pointing to the new URL, followed by a 200 OK on the destination. If you see a 404, a 500, or a chain of multiple redirects, the rule is misconfigured or there is a conflicting earlier rule. Fix and re-save.
bashVerify the redirect — copy, paste, replace yoursite.com
# Inspect headers and follow the chain
curl -IL https://yoursite.com/old-services
# Expected output:# HTTP/2 301# location: /services# ...# HTTP/2 200
The double-check matters. A 301 chain (301 to 301 to 200) is technically valid but loses time and can cause some crawlers to give up early. A 302 where you meant 301 still works for users but may not consolidate ranking signals per Google's guidance2. Curl shows both problems in the response chain instantly.
§05Failures
What actually breaks redirects on Squarespace
Four failure modes account for most broken Squarespace redirects. Wrong arrow (=> or --> instead of ->) is the most common — the panel rejects on save. Trailing-slash mismatch is the quietest — the rule saves, but the redirect fires inconsistently because /old and /old/ are treated as distinct URLs. Conflict with an earlier rule is the trickiest — Squarespace matches top-down, so a wildcard rule near the top can absorb a URL that a more specific rule lower in the list was supposed to catch. And destination-page redirects create chains — the rule succeeds, but the destination page itself is set to forward, producing a 301-to-301-to-200 chain.
The conflict failure is the one that catches careful migrations. Squarespace evaluates URL Mappings top-down — the first matching rule wins. If you have a wildcard like /blog/[slug] -> /journal/[slug] 301 at the top of the panel and a specific rule like /blog/feature-launch -> /announcements/launch 301 further down, the wildcard absorbs the specific URL and the second rule never fires. Reorder: specific rules first, wildcards last.
The destination-chain failure is also worth a curl check. If the destination page itself has a redirect configured in its own page settings (Page Settings → SEO → Page Redirect), the URL Mapping points at a page that immediately re-redirects somewhere else. Net result: a redirect chain. Fix it by clearing the page-level redirect on the destination, or by pointing the URL Mapping directly at the final URL.
The four failures, ranked
#1
wrong arrow syntax — `=>` or `-->` instead of `->`. Rejected on save with a line-number error.
Four leaves go deeper than this hub. The bulk leaf covers the spreadsheet-to-textarea workflow for 50, 500, or 4,000 redirects at once. The syntax leaf is the full reference — every rule shape Squarespace accepts and rejects. The migration-map leaf covers the audit step every migration skips: a 1:1 spreadsheet from every old URL to a new URL before launch. The remove-old-URL leaf covers what to do after a redirect ships when Google still shows the old URL in search results.
Five questions Squarespace owners ask most about 301 redirects — answered in the format AI engines lift from.
Does Squarespace support 301 redirects?
Yes. Squarespace 7.1 supports 301 (permanent) and 302 (temporary) redirects through Settings > Advanced > URL Mappings. The panel accepts up to 5,000 rules per site according to the help docs. No other status codes (303, 307, 308) are accepted; the panel rejects them on save.
What is the correct redirect syntax on Squarespace?
/old-path -> /new-path 301 — one rule per line. The arrow is `->` (a hyphen and a greater-than with no space between them). External destinations must begin with `https://`. Wildcards use `[name]` syntax inside path segments. The order rules appear in matters: the panel matches top-down.
Why isn't my Squarespace redirect working?
Four common reasons: (1) the arrow is `=>` or `-->` instead of `->`; (2) there is a trailing-slash mismatch between the source and destination; (3) the rule conflicts with an earlier rule above it; (4) the destination page is itself set to redirect, creating a chain Squarespace serves as a final 200 after multiple hops. Use curl to inspect the response chain.
Can I bulk upload 301 redirects to Squarespace?
There is no native CSV import for URL Mappings as of Q2 2026. The panel is a plain textarea, so 'bulk' means pasting many lines at once — up to the 5,000-rule limit. The bulk leaf below covers the prep workflow: build the map in a spreadsheet, validate the syntax locally, paste in batches of 100-500.
Will Google follow Squarespace 301 redirects?
Yes. Google's official guidance is that 301 redirects pass full PageRank and are the correct signal for permanent URL moves. Recovery after a redirect rollout typically takes 4-12 weeks per Google's migration documentation, depending on site size and crawl frequency.
