By Deep Digital Ventures. Reviewed for small-business site architecture and launch migrations.
A small-business URL structure should make pages easy to understand, easy to share, and hard to outgrow. The best rule is simple: use readable lowercase slugs, group pages under stable parent folders, avoid dates on evergreen pages, keep paths short, and use 301 redirects when a live page is permanently renamed or replaced.
The Default URL Rule Set
- Use human words:
/services/bookkeeping, not/page-7. - Use stable parent folders:
/services/,/locations/,/portfolio/,/guides/. - Use hyphens between words and lowercase every slug.
- Skip dates for evergreen pages unless the date is part of the promise.
One credibility note before the naming rules: if this article, or any URL-structure article, is live at an opaque address such as ?p=1357, fix that first. Publish the clean permalink, set it as the canonical URL, and 301 any old query-string or temporary version to the final address. A page teaching clean URLs should not depend on a draft-looking URL.
This guide is for service businesses, local operators, consultants, restaurants, studios, and independent professionals planning a first serious website or cleaning up an older one. The goal is not to memorize platform documentation. It is to choose a URL system that still works when you add new services, locations, menus, case studies, booking pages, or guides.
Choose Slugs Customers Can Read Aloud
A useful slug tells someone what page they are about to open. /services/emergency-plumbing is clear. /best-affordable-licensed-emergency-plumbing-services-near-me is not stronger; it is just noisier.
Google’s URL guidance favors crawlable, readable URLs with words people can understand, and it recommends hyphens between words instead of underscores. That advice is enough for most small-business sites: lowercase words, hyphens, no special characters, and no CMS leftovers such as /new-page-copy-3.
| Weak slug | Better slug | Why it works |
|---|---|---|
/page-4 | /services/commercial-cleaning | The service is obvious before the click. |
/summer-menu-final | /menu/catering | The page can survive menu updates. |
/wedding-gallery-2023 | /portfolio/weddings | The portfolio can be refreshed without changing the URL. |
/about-us-company-information | /about | The extra words add no meaning. |
In site rebuilds, the most common slug problem is not bad SEO theory. It is unclear ownership. Nobody knows whether /consulting, /business-consulting, and /services/consulting are separate pages or old versions of the same idea. Before launch, pick one naming pattern and write it down.
Takeaway: if the slug needs more than five or six words, shorten the slug and let the page title carry the detail.
Use Parent Folders That Match Buying Decisions
Small-business URL structure should follow how customers choose, not how the owner thinks about the company internally. A plumber usually needs services and service areas. A photographer needs services and portfolio categories. A restaurant needs menu, catering, reservations, and events.
| Page type | Recommended path | Rule |
|---|---|---|
| Core service | /services/bookkeeping | Keep every durable service under one parent. |
| Location page | /locations/denver | Use the customer-facing place name, not an internal territory code. |
| Restaurant menu page | /menu/catering | Keep menu-related pages predictable for QR codes and printed materials. |
| Portfolio category | /portfolio/kitchens | Group proof by the way buyers evaluate your work. |
| Evergreen guide | /guides/prepare-for-tax-season | Use a topic path that can be updated every year. |
Avoid hiding important services behind fragments such as /#services when the content deserves its own page. Fragments are fine for jumping to a section, but they are a weak foundation for shareable service, location, booking, menu, and product pages. Google also notes that URLs are case-sensitive, so standardizing lowercase paths prevents accidental duplicates such as /Menu and /menu.
Takeaway: use one to three meaningful path segments in most cases. If the path reads like a folder maze, the hierarchy is serving the CMS instead of the customer.
Do Not Put Temporary Details in Permanent URLs
The fastest way to create future cleanup work is to put temporary facts in a permanent URL. Dates, campaign names, seasonal labels, staff names, and “new” language all age badly.
Use dates only when the date is part of the content promise: an event recap, release note, dated announcement, or annual report. For evergreen service pages and guides, dates make an updated page look stale before the content itself is stale.
| Instead of | Use |
|---|---|
/2026-tax-prep-guide | /guides/tax-prep-checklist |
/fall-mini-sessions | /services/family-photography |
/new-patio-menu | /menu/patio |
/sarah-brand-design | /services/brand-design |
Platform limits still matter. WordPress calls these permanent URLs permalinks and lets site owners choose structures such as post name, dates, numeric IDs, or custom patterns. Shopify, Squarespace, Wix, and other builders may reserve certain paths or enforce handle rules. Treat those constraints as guardrails, not as a reason to invent a complicated workaround.
Takeaway: a URL should describe the durable topic, not the current promotion, staff assignment, or publishing year.
Plan Redirects Before You Rename Anything
Most URL damage happens during small, rushed changes: a service gets renamed, a menu page is replaced, a gallery is merged, or a builder migration changes every path. The fix is not complicated, but it has to happen before the old page disappears.
Google treats 301 and 308 redirects as permanent signals, while 302, 303, and 307 redirects are temporary. For small-business sites, use a permanent redirect when the old URL has been replaced for good. Use a temporary redirect only for short-term inventory, seasonal campaigns, maintenance, or testing.
| Old URL | New URL | Redirect | Reason |
|---|---|---|---|
/wedding-gallery-2023 | /portfolio/weddings | 301 | The gallery became the permanent wedding portfolio. |
/families | /services/family-photography | 301 | The new service page replaces the old short page. |
/mini-sessions-fall | /services/family-photography | 302 during campaign, then decide | The offer may return, so do not make the final signal too early. |
/contact-me | /contact | 301 | The shorter contact path is the durable version. |
When we clean up older small-business sites, we usually find redirects that point to the homepage because nobody chose a closer destination. That is convenient for launch day and frustrating for everyone later. A retired catering page should point to the current catering or events page, not to the homepage. A discontinued product can point to its category or replacement product. A merged service should point to the new service page that explains the combined offer.
Takeaway: redirects are not just technical cleanup. They are customer-routing decisions.
Separate Slugs from Titles and Snippets
A URL does not need to carry every keyword. Search result titles, snippets, headings, copy, testimonials, service-area language, and internal links all do different jobs. Google’s guidance on title links and snippets focuses on clear, descriptive titles and useful page text, not overloaded URLs.
Use /services/commercial-cleaning for the path. Use the title, intro, proof, and calls to action to explain office cleaning, janitorial work, floor care, medical offices, service areas, and pricing factors. A clean slug gives the page a stable address; the page content earns the click and the conversion.
This also fits Google’s broader helpful-content direction: write for people first, make the purpose of the page obvious, and avoid producing pages that feel assembled only to match search variations. For AI answer surfaces, concise extractable structure can help systems understand the answer, but the underlying requirement is the same: useful content, clear organization, and pages that answer real user needs.
Takeaway: write the URL as if it might appear on a sign, then write the page as if it has to answer the next customer question.
Questions Worth Asking Before Launch
Should I change old URLs that already get traffic?
Usually no. Keep a working URL if customers, search results, ads, QR codes, or backlinks already use it. Change it only when the new structure fixes a real problem, then redirect the old URL to the closest new page.
Should every service have its own URL?
Only if the service deserves its own page. If customers search for it, ask about it, buy it separately, or need different proof, give it a durable URL. If it is just a small feature of a broader offer, keep it on the parent service page.
What if the builder reserves the slug I want?
Pick the closest plain alternative and document the decision. Fighting reserved paths usually creates more maintenance risk than choosing a clear second-best slug.
Should I add FAQ schema to this kind of post?
Only if the FAQ is genuinely useful on the page. Google limits FAQ rich results mostly to well-known government and health sites, so normal business blogs should not expect FAQ markup to produce enhanced search results.
Closing Checklist
- List every planned page and its final slug before launch.
- Choose one parent-folder pattern for services, locations, portfolio work, menus, products, and guides.
- Remove dates, campaign names, and temporary labels from evergreen URLs.
- Check for duplicate concepts with different paths.
- Map every old live URL to the closest new destination before publishing.
- Update navigation, internal links, QR codes, profiles, invoices, ads, and email templates after any URL change.
For a small-business website, the best URL structure is boring in the right way. Customers can read it, staff can remember it, search engines can crawl it, and the business can grow without renaming everything each time the offer changes.
Sources
- WordPress.org, permalinks documentation: https://wordpress.org/documentation/article/customize-permalinks/