Faragiri

Learn URLs Site structure

A Doncaster timber merchant renamed a directory to something tidier and lost eleven months of a page's standing, which is what a URL is actually for.

4Sections
4Min read
4Depth

Stability is worth more than tidiness, and it is the only property that compounds. Thorne Timber, a merchant in Doncaster, moved its decking pages from a products directory to a decking directory in September 2025 because the second one read better. A URL that changes without a redirect loses what the old one earned, and for six weeks nobody had put the redirect in.

The address took eleven months to recover, and it recovered because of one redirect, added late, pointing the old path at the new one. The page did not come back on its own. The old address had 30 internal links and 4 from outside pointing at it, and the tidier one bought nothing anybody has been able to name since.

What the three words actually mean

Readable means a person could type it from memory after hearing it. Not that it contains keywords. Thorne's decking pages are at a path with two words in it, and the test that settled the format was somebody reading an address down a phone to a builder, which is a thing that happens in this trade twice a week.

URL properties

What readable, shallow, and stable actually mean

Only one of the three properties is about how the address looks; the other two govern navigation and longevity.

An address you never have to change
  • ReadableEasy to type from memory after hearing it read down a phone to a builder, not stuffed with keywords.
  • ShallowMeasured in clicks from the home page via menus, not by counting slashes in the path.
  • StableLeft untouched once live, even when somebody thinks of a slightly tidier phrasing later.

Discipline over cosmetic tidiness

A four-segment address linked from the main menu is shallower than a two-segment page buried on page nine of a list.

Shallow means few clicks from the home page, not few slashes. This is the one most often misread. A page at a four segment address linked from the main menu is shallower than a two segment page reachable only from page nine of a list, and shortening the path does nothing for the second one.

Stable means nobody renames it because a better word occurred to them. That is the whole of it, and it is a discipline rather than a format.

The details worth deciding once

Lower case, hyphens between words, and no words that repeat the folder above. A path with decking twice in it is not stronger for the repetition, and it is one more thing to say out loud. Underscores work and hyphens are what everything documents, which is reason enough at this size.

Format rules

Four path choices worth settling once at the start

Clean conventions remove repetition and keep dates or shifting category names out of permanent addresses.

Decided once
  • Lower case and hyphensHyphens between words match standard documentation and read clearly out loud.
  • No repeated folder wordsPutting decking in both the folder and the slug adds length without helping anyone.
  • Leave out the yearHaving 2023 in a guide path forced an awkward choice in 2026 between a stale date and a risky rename.
  • Prefer flat pathsCategory folders turn every catalogue reorganisation into a batch of broken or renamed addresses.

Only pages tied to a specific year, such as annual price changes, belong at a dated address.

Keep the date out of the address unless the page is about a date. Thorne's guide to choosing decking boards had 2023 in its path, which meant that updating it in 2026 forced a choice between an address that lies and a rename that costs. A page about a specific year's price changes is a different case and the date belongs there.

A category name in the path is a promise the page will stay in that category. That is the hidden cost of a tidy hierarchy: the moment a product belongs in two categories, or the categories are reorganised, every address under them is a rename waiting to happen. Flat addresses are less elegant and they survive reorganisations, which is why a shop with a changeable catalogue is usually better off with them.

Where this stalls: the tidy-up nobody costs

The stall is that renaming an address is a twenty minute job and its cost arrives months later, in a report nobody connects to it. Thorne's rename was done by somebody being careful, on a Friday, as part of tidying the site, and the fall in October was attributed to the season.

Addresses

The same decking page at two addresses

Only one of the five rows is about how the address reads, and it is the one that caused the rename.

The tidy addressChosen in September 2025 because it read better.
The address it replacedFour years old, linked from 30 other pages.
How it readsClean, and one word shorterA products folder with everything in it
What linked to itNothing, on the first day30 internal links and 4 from outside
Clicks from the home pageTwoTwo
Survives a category changeNo, decking is a categoryYes, products is not
Standing on the day of the changeNoneEleven months of it

A twenty-minute tidy-up on a Friday caused an October drop blamed on the season; no address should change without a redirect written in the same hour.

The rule that prevents it does not need anybody to understand ranking: no address changes without a redirect written in the same hour. That is moving a page without losing what it earned, and it is the one technical habit worth insisting on in a firm with no technical staff.

Parameters, and the ones that leak

Never put a session or a sort parameter in a link. Thorne's category pages carried a sort parameter in every internal link, so the same twelve products existed at eight addresses, and every one of them was crawled and stored as a candidate. That is a structural problem with a technical fix, and choosing which of the eight is the real one is naming the real version of a duplicated page.

Index bloat

Thorne Timber addresses in Search Console vs real products

Sort parameters inside category links turned twelve products into eight crawled addresses per view.

  • 340Addresses stored in Search ConsoleFound via the page indexing report; longest paths sorted in Screaming Frog showed linked parameters.
  • 60Actual products in the shopEvery extra address above this count came from session or sort parameters in internal links.

Never place session or sort parameters inside crawlable internal links; inspect address length in Screaming Frog to catch leaks early.

Screaming Frog SEO Spider lists every address a site links to, free up to a few hundred, and it replaced clicking through the site with a notepad. The column to sort by is address length: the longest ones are almost always parameters that were never meant to be linked.

Search Console's page indexing report shows which addresses were actually stored, free, replacing counting pages by hand and believing the total. Where it lists more addresses than the shop has products, the difference is parameters, and at Thorne it was 340 against 60.

How deep those addresses sit in clicks rather than in slashes is menus as the clearest statement of your hierarchy, and the eight versions of one category are also pages that dilute the ones that matter. Both belong to how pages relate, which decides what a site is about.

Alongside this

Above this