What Is A URL Slug In Squarespace (And How To Edit One Without Breaking Your Site)

The URL slug is the part of a web address that comes after your domain name and forward slash. On sitekik.com/blog/squarespace-url-slugs-guide, the slug is squarespace-url-slugs-guide. That's it. Squarespace calls it the "URL Slug" in the page settings panel, and it starts life as whatever you typed into the page title, lowercased, with hyphens jammed between the words.

Which means if you named a page "Services & Pricing (New!!)", Squarespace handed you something like services-pricing-new and you probably never looked. This post covers what a URL slug does, how to edit one in Squarespace without knocking your rankings sideways, and the best practices for them I'd apply to a live client site.

URL slug is the house number on your site's address

Every page and blog post on your site has an address. The domain is the street, the slug is the house number. Google reads it. Your visitors read it, even when they think they aren't. And unlike almost everything else in your Squarespace back end, it's a permanent-feeling string that other people copy, paste, and text to each other.

Here's the anatomy of a typical Squarespace blog URL:

• Protocol:https://
• Domain:www.sitekik.com
• Collection path:/blog (the blog page's own slug)
• Post slug:/what-is-a-url-slug-squarespace

Blog posts inherit the parent collection's slug, so a post sitting inside a blog page called "Journal" lands at /journal/post-name. Change the blog page slug from journal to blog and every post underneath it moves too. That single click is how people accidentally orphan two years of content in one afternoon.

Standard pages sit at the root: /about, /contact, /pricing. Products live under your shop page. Events live under your events page. The pattern holds everywhere in Squarespace, which is one of the platform's quieter strengths compared to systems where you have to build the URL structure by hand.

Slugs build trust and signal quality to Google and visitors

Three reasons, and only one of them is Google.

1. The first is comprehension. A slug is a preview. When someone sees /squarespace-nonprofit-website-design in a search result or hovering in the corner of their browser, they know what they're about to get before they click. When they see /page-2-copy-final, they know something sloppy is happening behind the curtain. That's a small trust tax, paid on every impression.
2. The second is search. Google has said for years that words in the URL are a weak ranking signal, and I believe the "weak" part. But the slug also feeds the breadcrumb display in search results, gets used as anchor text when people paste a bare link into a forum, and tells a crawler roughly where this page sits in your pre-launch SEO checks hierarchy. Weak signals stacked across two hundred pages stop being weak.
3. The third is durability. Slugs get printed on business cards, baked into email footers, shared in group chats, and cited in other people's articles. A clean slug survives a redesign. A messy one gets rewritten during the redesign, and then someone has to remember to set up the redirect.

It's the one piece of your site design that other people type out by hand. Treat it like a phone number, not a filename.

Editing a URL slug takes seconds; deciding whether to takes longer

The mechanics take about eight seconds. Deciding whether to do it takes longer.

Standard pages: open settings and find the slug field

1. Open Pages in the left sidebar.
2. Hover the page name and click the gear icon to open page settings.
3. Find the URL Slug field under the General tab.
4. Type your new slug. Squarespace strips illegal characters as you go and adds the leading slash for you.
5. Save.

Blog posts store slugs in settings alongside title and excerpt

Open the post, click the settings gear or the Options tab, and look for the URL Slug field alongside the post title, excerpt, and thumbnail. Same field, different panel. On newer Squarespace versions it sits inside the post's settings drawer rather than a separate tab, so if you can't find it, check the tab labels at the top of that panel before assuming it's missing.

Products and events inherit parent paths; changing slugs kills old links

Product slugs live in the product editor's settings, event slugs in the event editor. Both inherit the parent page path. Worth knowing: changing a product slug after you've sent a campaign linking to it is one of the more expensive small mistakes available to you.

Now the important part. Squarespace does not automatically redirect the old slug. The moment you save a new one, the old address returns a 404. If that page had traffic, links, or a spot in Google's index, you've just cut the wire. Every slug change on a published page needs a matching 301 redirect, and my guide to Squarespace redirects and 404s walks through the syntax. The short version lives in Settings under Developer Tools, and looks like this:

/old-slug -> /new-slug 301

One rule per line. Arrow, then the status code. Write the redirect first, then change the slug, then load the old URL in a private window to confirm it lands where it should.

Short, readable, stable slugs perform best across all metrics

Short, readable, stable. If you only remember three words, remember those.

Beyond that, here's how I'd handle each decision on a real build:

Decision	Do this	Skip this	Why
Length	Three to five meaningful words	Full sentence titles	Long slugs truncate in search results and look broken when pasted
Separators	Hyphens	Highlights, spaces, plus signs	Hyphens read as word breaks to crawlers; highlights glue words together
Case	All lowercase	Title Case or camelCase	Some servers treat case differently, which creates duplicate paths
Stop words	Cut a, the, of, for, to	Keeping every connector	They add characters and no meaning, unless removing them breaks the phrase
Dates and numbers	Leave them out	/2026-spring-sale-v2	Dated slugs age your content and force a rewrite when you update the post
Keywords	One primary phrase, naturally	/dentist-dentistry-dental-clinic	Stuffed slugs read as spam to humans, which is the audience that matters

A few extras that don't fit the grid. Avoid special characters entirely, including ampersands and apostrophes, because Squarespace will either strip them or encode them into something unreadable like %26. Keep accented characters out if your audience is English-speaking, since they encode badly and break when copied between apps. And don't mirror your navigation labels blindly: a nav item reading "Work" can point to a slug of /squarespace-web-design-portfolio, which is what my own portfolio page does. The label is for humans scanning a menu. The slug is for everything else.

Renaming without redirects and bulk collection changes cause permanent traffic loss

Some slug problems are cosmetic. These four aren't.

• Renaming a page and forgetting the redirect. Already covered, still the number one cause of avoidable traffic loss on a Squarespace site. If you're doing a bulk cleanup, export your current URL list first so you have something to map from.
• Changing a blog collection slug mid-life. Moving /journal to /blog rewrites every child post's address at once. You'd need a wildcard redirect rule to catch them all, and even then you've reset whatever authority those individual URLs had accumulated. If the collection slug is merely ugly rather than actively wrong, leave it.
• Publishing with the Squarespace default. Duplicating a page gives you /about-1 or /services-copy. These go live more often than anyone admits. Before launch, click through every page in the Pages panel and read the slug field. It takes ten minutes.
• Letting client-side naming leak into public URLs. Internal shorthand like /v3-final-approved or /landing-fb-ads tells a visitor how the sausage is made. Name the page for the person reading it.

One more, smaller: don't put your brand name in every slug. /acme-about, /acme-services, /acme-contact. Your domain already conveys the brand. The repetition just pushes the useful words further right.

Map your entire slug structure before publishing anything

The cheapest time to get slugs right is before anything is published, because there's nothing to redirect and nothing indexed. I'd sketch the whole URL map alongside the sitemap, in a plain document, before a single page exists in Squarespace.

That map does two jobs. It forces you to notice when you've got three pages that could all reasonably be called /services, which usually means your information architecture needs a decision rather than a naming trick. And it gives you a reference for internal linking later, so you're not hunting through the Pages panel every time you want to point one article at another. The same principle runs through designing a site around user research: structure decisions come before surface decisions.

If you're migrating rather than building new, the URL map is non-negotiable. You need the old addresses and the new ones side by side, with a redirect rule for every row where they differ. My pre-migration checklist covers the export-and-map sequence in detail, and the slug column is the one people skip and regret.

Well, sort of non-negotiable. If the old site had no real traffic and no backlinks, you can start clean and let the old URLs die. That's rarer than people hope.

Slugs matter less than content quality but more than most fixes

Slugs sit in the same tier as alt text and heading tags: individually minor, collectively the difference between a site Google understands and one it has to guess about. The page title tag does heavier lifting. Content quality does heavier lifting still. But the slug is the one you can fix across an entire site in an afternoon, and it never needs touching again if you get it right.

The practical order I'd work in on an existing site:

• Audit every slug against the table above, noting which ones are wrong versus merely imperfect
• Fix the unpublished and no-traffic pages freely, since there's no redirect debt
• For published pages with traffic, only change a slug when the current one is misleading or broken, not when it's slightly suboptimal
• Write the redirect rule before you save the change, every time
• Check your 404 log a week later to catch what you missed

That last step is the one nobody does. Squarespace won't email you when a URL starts failing. You find out from a client asking why the link in their newsletter goes nowhere. If you want the rest of the no-code layer covered too, the SEO basics walkthrough handles titles, headings, and sitemaps in the built-in panel.

What is a URL slug, exactly?

What is a URL slug, exactly?

It's the part of a web address that identifies one specific page, sitting after your domain name and any parent folder. On Squarespace it lives in a field called URL Slug inside page or post settings, and it's generated automatically from your title unless you overwrite it.

Does changing a URL slug in Squarespace hurt SEO?

It can, and it will if you don't add a 301 redirect from the old address to the new one. With the redirect in place, most of the page's accumulated authority carries over and search results update within a few weeks. Without it, the old URL returns a 404 and any links pointing at it stop working.

Can two pages share the same slug on Squarespace?

No. Squarespace enforces uniqueness within a path and will append a number if you try, which is exactly how you end up with /services-1. If a slug you want is taken, check whether the page holding it is still needed before you settle for the numbered version.

Should the URL slug match the page title?

Usually close, rarely identical. Titles can run long and include punctuation; slugs should be trimmed to the three to five words that carry the meaning. "How To Bring Your Brand Into A Squarespace Website Design" becomes /branding-and-squarespace-website-design. Same subject, half the characters.

Do slugs matter for products and event pages?

Yes, and they're the ones most often left on autopilot. Product URLs get shared directly far more than category pages do, and a product slug reading /product-sku-4471 is a worse thing to text to a friend than /lavender-honey-soap.

---

Pick five pages on your site right now and read their URL slug fields. If any of them contain a number you didn't choose, a date you'll regret, or a word like "copy", you've found your afternoon's work. Start with the unpublished ones, where you can change anything without owing a redirect. And if the audit turns up more broken paths than you want to untangle alone, I'm reachable through the contact page and happy to look at what's going on under your URL structure.