url slugs get treated as an afterthought by most small business sites — whatever the cms auto-generates from the title is usually what ships. that's a missed opportunity: google's guidance on url structure treats a clear, descriptive url as a real signal of what a page is about, not a cosmetic detail.

why a vague slug hurts you specifically because you're small

if your slug is something generic like /seo or /services, you're competing directly against every major publication, agency, and enterprise site that also uses some version of that exact phrase near their url. those sites have decades of accumulated authority. a small business has no realistic path to outrank them on a term that broad and that contested.

make the slug more specific — /local-seo-checklist-for-ottawa-restaurants instead of /seo — and you've effectively moved into a much smaller, less crowded category. fewer sites are competing for that exact phrase, which means the bar to rank is dramatically lower.

the trade-off you need to manage

specificity isn't free. go too narrow and you can rank #1 for a phrase nobody searches. a slug like /how-to-fix-a-leaking-faucet-in-a-1987-condo-in-nepean might have zero competition and also zero search volume.

the target is the middle: specific enough that you're not fighting national brands for a generic term, broad enough that real people are actually typing something close to that phrase into google. a quick check in google's keyword planner or even the autocomplete suggestions in a normal search bar will tell you whether a phrase has any search volume before you build a page around it.

practical slug guidelines

match the slug to the actual query, not the internal name for the service. a customer searches "commercial lease review ottawa," not "biz-legal-svc-2."
keep it readable. /kitchen-renovation-cost-ottawa beats /kitchen-renovation-cost-ottawa-2026-guide-pricing-info — extra keywords in a slug past a certain point add no additional benefit and hurt readability.
avoid dates in the slug unless the content is genuinely date-specific. a slug with a year baked in ages badly and either needs constant updating or starts looking stale.
use hyphens, not underscores, and skip stop words like "a," "the," and "of" where you can drop them without losing clarity.

the same logic applies past the slug

url specificity is one lever. the title tag attached to that url is another, and the two interact — see brand name in title tags: help or hurt for how to spend the limited character budget you get there. and if you're building single-question pages rather than broad category pages, the same "narrow and focused beats broad and diluted" logic shows up again in one faq page vs. many.

one thing this doesn't fix

a well-built slug gets you into a smaller, more winnable category. it doesn't substitute for the page actually answering the query well once someone lands on it. treat the slug as the first filter that determines which race you're even entered in — the content still has to win that race.

the takeaway

slugs aren't cosmetic. a generic url puts a small site in direct competition with the biggest names on the internet; a specific one moves you into a category sized for your actual authority. the fix costs nothing and takes five minutes per page — there's no reason not to do it on every new page you publish.

nanushi builds sites with url structure and seo baked in from the start, not bolted on afterward. if your existing site is full of generic slugs, we can help you plan a cleanup that doesn't tank your existing rankings.

url slugs and seo: how specific should yours be?