Redirect & HTTP Status Checker for Squarespace Users

Why Squarespace Users need this

Squarespace saves a blog post, product or event the moment you hit save, and if the title field was still empty, the slug it generates is a random string. You fix it later, the address changes, and every link pointing at the old one now depends on a redirect you have to add by hand. Miss one and visitors land on a 404. That is the quiet way Squarespace URL redirects go wrong: nothing looks broken inside the editor. The Redirect & HTTP Status Checker lets you test from the outside. Paste an old address and it follows each hop the server returns, up to ten, showing the status code and type at every step and where the chain ends. For a Squarespace user, the useful question is simple: does the old URL reach the new slug through a single 301 and finish on a 200? A URL typed without a scheme is tested as http://, so the HTTP-to-HTTPS step shows up in the same trace. It reports; it does not judge whether the destination is the right page.

Squarespace Users specific guidance

Start with the old address, not the new one

Open the Pages panel, find the page whose slug you changed, and write down the old path from your own records. Then paste the full old address, for example https://www.example.com/blog/a8f3k2, into the checker and run it once. Test the version people actually saved, with or without www. If you changed several slugs in one sitting, trace the three or four most linked ones first. A clean result does not prove that every old URL is covered, because the checker traces one address per run, and it says nothing about whether Google has already dropped the old page.

Read the hops, the types and the final status

Look at Redirect Summary first: it tells you whether there were no redirects or how many hops came before the final destination. Then read Redirect Path. A healthy old slug shows one hop labelled 301 permanent and a Final URL equal to the new slug. A 302 or 307 labelled temporary means the move was set up as temporary, which is worth correcting for a permanent slug change. In Chain Checks, a fail on Final status is 200 OK means the old address ends in a 404, 410 or server error, and a warning on Short redirect chain means three or more hops. Compare the Final URL with the page you meant, because a tidy 301 to the homepage still passes every check and is still the wrong answer.

What to fix, and in which order on Squarespace

Fix 404s first. Open the URL Mappings panel under Developer Tools in Settings and add one line per old address in the form /old-slug -> /new-slug 301. Save, then trace the old address again to confirm one permanent hop ending in 200. Next, shorten chains: if an old address redirects to another old address, point it straight at the final slug. Last, replace any 302 lines with 301 where the move is permanent. Redirects do not repair internal links, so also update menus, buttons and blocks that still use the old slug. The check confirms server answers only; it cannot say when the old URL will leave search results.

Example scenarios

Common mistakes

• Testing only the new slug. A new address that loads says nothing about the old one. Always paste the old URL, because that is the address other sites and bookmarks still use.
• Trusting the editor instead of the trace. Changing a slug in the page settings does not add a redirect for the old address. Without a URL mapping the old link simply returns a 404.
• Redirecting everything to the homepage. A blanket mapping to the homepage ends in a 200 and passes the checks, but visitors and crawlers lose the page they wanted. Compare the Final URL with the page you meant.
• Stacking mappings over time. Renaming a page a second time and adding a new line while leaving the first creates a chain. Edit the older line so it points at the current slug.
• Using a script for a redirect. A redirect pasted into Code Injection runs in the browser, so the server still answers with the old page or a 404. Use a URL mapping so the answer is a real 301.

Frequently asked questions

How do I set up squarespace url redirects after changing a slug?

Open the URL Mappings panel under Developer Tools in Settings and add one line for each old address, written as /old-slug -> /new-slug 301. Save it, then paste the old address into the checker. You want one hop labelled 301 permanent and a Final URL that matches the new slug with a 200 status. If the result still ends in a 404, check the line for typos, a missing leading slash, or a different spelling of the old path than the one you tested.

Is Squarespace good for SEO if old links keep returning 404?

Broken old links usually come from slug changes, not from the platform itself. Squarespace gives you URL redirects, so the fix is in your hands. Ahrefs notes you cannot edit robots.txt or the sitemap, but redirects remain editable. Run your changed slugs through the checker: if each one reaches a 200 in a single hop, the redirect side is sound. That does not say anything about rankings, titles, speed or content quality, which need other checks.

Why does my old Squarespace URL show two redirects instead of one?

Two hops usually mean the address passes through an extra step before reaching the final slug, for example an HTTP to HTTPS upgrade followed by your own mapping, or an old mapping that points at a slug you later changed again. Read Redirect Path row by row to see which step is which. The chain check only warns at three or more hops, so two is acceptable, but pointing the old line straight at the final slug removes the extra step.

Will the checker show a redirect I set up in Squarespace code injection?

Only if the server answers with it. The checker sends HEAD requests and follows Location headers, so it does not see meta-refresh or JavaScript redirects, which is what a script pasted into Code Injection would produce. If your old address loads the new page but the trace shows a 404 or a plain 200 on the old URL, the redirect is happening in the browser, not on the server. Switch to a URL mapping so crawlers get a real 301.

Does a 301 on my Squarespace SEO checklist guarantee the new URL keeps its rankings?

No. A 301 tells search engines the move is permanent and passes signals to the new address, but nothing is promised about positions or timing. The checker only confirms what the server answers today: the hops, their types and the final status. Whether Google has recrawled the old URL or indexed the new one is shown in Search Console, not here. Treat the clean trace as a precondition, then watch the new slug there over the following weeks.

Reference: Squarespace's SEO checklist in the Help Center warns that saving content before adding a title creates a random slug and advises creating redirects for the old URL after you change one.