Clean URLs for a Cafe Website: Locations and Blog Posts
Look at your own site's address bar right now. If what follows your domain name is a random string of letters and numbers, rather than something a person could actually read and guess, you are not alone, and it is not automatically hurting you either.
Short answer: a clean URL is short, readable, lowercase, and stable, meaning it does not change once it is published. The shape of a URL is a usability question more than a ranking question. The real risk sits somewhere else entirely: changing an old URL without setting up a redirect, which breaks every link and every bookmark pointed at that page. Get the structure sensible from the start, and treat any future change as something that needs a redirect, not a fresh start.
This post gives a path structure for locations, menu, events, and blog posts that reads well and survives growth as your cafe adds a second location or years of posts, answers whether the city belongs in the URL, and walks through changing an old URL safely on the major site builders.
What Google Actually Says About URL Structure
Google's own Search Central guidance on keeping a simple URL structure describes organizing site content logically and using URLs that are readable and understandable to both people and crawlers, rather than long strings of parameters or session identifiers a visitor could never make sense of at a glance. The documentation frames this primarily as an aid to crawling, organization, and human usability, not as a stated ranking signal tied to specific words appearing inside a URL.
That distinction matters, because it is common to hear that stuffing keywords into a URL will help a page rank. Google's documentation does not make that claim. What it does support is a URL a person could read aloud and understand, one that reflects where a page actually sits in a site's structure, and one that stays stable once published rather than shifting every time a page gets reorganized.
The practical takeaway is simple: build URLs for the humans clicking them and the crawlers indexing them, not to game a keyword count, and treat stability as more valuable than any particular word choice inside the path itself.
Rules for a Readable URL
A few plain rules cover most of what makes a URL genuinely readable. Keep it short, favoring a handful of clear words over a long descriptive phrase. Use lowercase letters consistently, since mixed case in a URL can create confusion about whether two addresses are the same page. Separate words with a single consistent character rather than mixing separators or using none at all. Avoid dates, version numbers, or internal tracking codes in a path meant to be permanent, since those are exactly the kind of detail that makes a URL feel disposable rather than stable.
Structure matters as much as wording. A path should generally reflect where a page lives in your site: a blog post sits under a blog section, a location page sits under a locations section, a menu page sits at or near the top level since it is core content most visitors look for directly. This is less about pleasing a crawler and more about a visitor, or you six months from now, being able to guess roughly where a link will lead just by reading it.
None of this needs to be perfect to be useful. A URL that is short, lowercase, and stable clears the real bar. Chasing an ideal beyond that, at the cost of changing URLs repeatedly to optimize wording, creates exactly the instability this post is warning against.
A Path Structure That Survives Growth
For a cafe with one location today that might open a second tomorrow, plan the path structure now rather than after the second lease is signed. A sensible pattern looks like this: the homepage at the root, a menu page at a simple top level path, a locations section that can hold one page today and expand to hold several without restructuring anything, an events section for cuppings and classes, and a blog section for posts, each with its own clear top level path.
Inside the locations section, each individual location gets its own short path, ideally built around the neighborhood or a simple identifier rather than a long descriptive phrase. This is where the city question comes up directly: should the city appear in the URL. The honest answer is sometimes, specifically once there is more than one location to distinguish between. A single location cafe generally does not need its own city baked into a location page's path, since there is nothing to distinguish it from. A multi location cafe benefits from a clear, distinguishing word, often the neighborhood or the city, in each location's own path, precisely so a visitor or a search result snippet can tell the locations apart at a glance.
Inside the blog section, each post gets its own path built from the post's own short, descriptive title, not a publish date and not a numeric identifier. Dates in blog URLs create a specific long term problem: a genuinely evergreen post about a brewing method looks stale forever once its URL carries a year that keeps receding into the past, even though the actual content might still be entirely current. A title based path avoids that problem and also tends to read more naturally to a visitor scanning a list of links.
This kind of structure is meant to be planned once and then left alone. The point of thinking it through now, before a second location or a hundredth blog post exists, is precisely so you are not stuck reorganizing a live, linked, indexed site later.
What Platform Editors Actually Look Like
The three major site builders each handle this differently, and it is worth knowing your own platform's specific editing path before you need it. On Wix, an individual page or post's URL slug is edited directly from the page settings panel inside the site editor, where the SEO or URL section lets an owner type a custom path before publishing. On Squarespace, the URL slug for a page lives in that page's own settings, accessible from the page menu in the site editor, and can be edited at any point after a page is created. On Shopify, product, collection, page, and blog post URLs are each edited from that specific item's own edit screen inside the admin, under a search engine listing preview section that shows and allows editing of the exact path.
All three platforms let an owner set a custom, readable slug rather than accepting whatever default the system generates from a title. The practical habit worth building is checking that field every time you publish something new, a location page, an event, a blog post, before it goes live, since setting it correctly at publish time is far simpler than changing it after the page has been live, linked, and possibly indexed for a while.
Changing an Old URL Safely
Sometimes a URL needs to change: a location page's path was built badly the first time, a blog post's slug had a typo, or a page is being moved into a better organized section. The single most important step in any of these situations is setting up a redirect from the old URL to the new one, so that anyone, or anything, following the old link, a customer's old bookmark, a shared social post, a search result that has not refreshed yet, still lands somewhere useful instead of hitting a broken page.
Each of the three platforms has documented guidance on this. Wix's help documentation covers adding a manual URL redirect from the site's dashboard SEO tools when a page's URL changes. Squarespace's help documentation on URL mapping explains adding manual redirect rules that map an old path to a new one. Shopify automatically creates a redirect in many cases when a URL is changed directly through the admin, and also provides a manual URL redirect tool under its online store navigation settings for cases the automatic version does not cover.
The check after any URL change is simple and should not be skipped: visit the old URL directly in a browser after the change and confirm it forwards to the new page rather than showing an error. This takes under a minute and catches the single most common, most avoidable mistake in URL changes, an old link that quietly goes nowhere.
A Few Pitfalls Worth Naming
A handful of specific mistakes show up often enough on cafe sites to call out directly. The first is letting a site builder's default slug stand unedited, which on some platforms produces a path built from an internal identifier or the full, unshortened title including every filler word, rather than the short, clean version an owner would choose if they simply looked at that one field before publishing. This is the single easiest fix on this entire list, since it requires nothing more than checking the URL field at the moment of publishing.
The second is inconsistent capitalization or separator characters across a site, one section using all lowercase with a single consistent separator and another section using mixed case or a different separator entirely. This does not necessarily break anything technically, since most platforms handle it without errors, but it undermines the basic readability goal this whole post is built around, and it makes a site feel less deliberately built than it is.
The third, and the costliest, is treating a URL as disposable simply because changing it is technically easy on most modern site builders. A URL that has been live for months or years accumulates real value attached to that exact address: search engines that have indexed it, other sites that have linked to it, customers who have bookmarked it, social posts that reference it. None of that value transfers automatically to a new address without a redirect in place, which is why the redirect step in the previous section is not optional once a URL has been live for any meaningful length of time.
What the Audited Data Shows About Cafe URLs Generally
The nationwide census tracks each shop's homepage URL and platform, though it does not track a detailed inventory of every inner page path across all 1,109 shops, so this post cannot report a precise national count of how many cafe location or blog post URLs are readable versus long, cryptic strings. That limit is worth spelling out rather than filling the gap with an invented number.
What the census does show, useful context for this topic even without inner path detail, is that the shops in this dataset sit across a real mix of platforms, Shopify with 318 shops, Squarespace with 267, Square Online with 131, WordPress with 122, and Wix with 97, as of the September 15, 2026 snapshot. Each of these platforms handles slugs and redirects in its own specific way, which is exactly why this post covers all three of the largest builders' editing paths directly rather than assuming one universal workflow applies everywhere.
This is also a fair place to be clear about scope. This post is not a study claiming to measure how many of the more than 1,000 audited cafes follow clean URL practices today, because that specific inner path data is not part of the census. It is instead a practical guide built from documented platform behavior and Google's own published guidance, meant to give any owner, regardless of platform, a concrete plan they can apply this week rather than a statistic about how common the problem is nationally.
Related Reading
More from Hillcane on this topic, plus the pages on the site that sit next to the work.
Frequently Asked Questions
Should URLs include the city?
Sometimes, and mainly once there is more than one location to tell apart. A single location cafe generally does not need its city in a location page's path, since nothing else needs distinguishing. A multi location cafe benefits from a short neighborhood or city word in each location's own path under a locations section, so visitors and search result snippets can tell the shops apart at a glance. Plan that structure before a second lease is signed.
Can I change URLs?
Yes, but only with a redirect from the old URL to the new one. Changing a live URL without one breaks every bookmark, shared social post, and search result still pointing at it. Wix covers manual redirects in its dashboard SEO tools, Squarespace handles them through URL mapping rules, and Shopify often creates one automatically when a URL changes in the admin. Afterward, visit the old address in a browser and confirm it forwards.
Does putting keywords in a URL help it rank?
No documented evidence says it does. Google's Search Central guidance on keeping a simple URL structure focuses on logical organization and URLs that people and crawlers can read, rather than long strings of parameters or session identifiers. It frames this as an aid to crawling and usability, not a ranking signal tied to words in the path. A short, lowercase, stable URL is what the guidance supports, and stability matters more than any particular word choice.
Should blog post URLs include the publish date?
Generally, no. An evergreen post about a brewing method looks stale forever once its URL carries a year that keeps receding, even when the content is still current. Build the path from the post's own short, descriptive title under a blog section instead of a publish date or numeric identifier. On Wix, Squarespace, or Shopify, set that slug before publishing, since changing it later means adding a redirect from the old address.
What happens automatically when I change a URL on Shopify?
Shopify automatically creates a redirect in many cases when a product, collection, page, or blog post URL is changed directly through its admin. For cases the automatic version does not cover, it also provides a manual URL redirect tool under the online store navigation settings. Either way, test the result: open the old URL in a browser and confirm it forwards to the new page. Shopify is the most common platform in the census, with 318 shops.
How do I edit a page's URL slug on Wix?
Open the page or post's settings panel inside the Wix site editor and use its SEO or URL section, where you can type a custom path before publishing. Check that field every time you publish a location page, event, or blog post, because an unedited default can carry filler words. If you change a live slug later, add a manual redirect from the dashboard SEO tools. The census counted 97 shops on Wix as of September 15, 2026.
How do I edit a page's URL slug on Squarespace?
Open the page menu inside the Squarespace site editor, go to that page's own settings, and edit the URL slug there; it can be changed at any point after the page is created. Changing it after the page has gone live, though, needs a manual redirect rule added through Squarespace's URL mapping, which maps the old path to the new one. Squarespace was the second most common platform in the census, with 267 shops.
What should I check after changing a URL?
Visit the old URL directly in a browser and confirm it forwards to the new page instead of showing an error. It takes under a minute and catches the most common, most avoidable URL mistake, an old link that quietly goes nowhere. Test a few addresses across page types if several changed. On Wix and Squarespace a missed redirect is added manually, while Shopify's manual redirect tool lives under online store navigation settings.
Does the census show how many cafes have readable versus cryptic URLs?
No. The census tracks each shop's homepage URL and platform but has no inventory of inner page paths across its 1,109 shops, so a national count of readable versus cryptic URLs is not available. What it does show, as of the September 15, 2026 snapshot, is the platform mix: Shopify with 318 shops, Squarespace with 267, Square Online with 131, WordPress with 122, and Wix with 97. That mix is why this guide covers several builders.
What is the single biggest URL mistake to avoid?
Changing an existing, live URL without a redirect is the costliest mistake. A URL live for months or years builds value tied to that exact address: indexed search results, links from other sites, customer bookmarks, and shared social posts. None of it transfers to a new address automatically. Wix, Squarespace, and Shopify all document redirect tools for this, and a quick browser visit to the old URL after any change confirms it still forwards correctly.
Work with Hillcane
A clean URL is short, readable and stable. The real risk isn't the shape of your links, it's changing an old one without a redirect.
If you want help planning a URL structure that survives a second location or years of blog posts, reach Hillcane at hillcane.co/contact or call (256) 384-2449.
Comments