What is URL structure?
URL structure is the system behind a site's addresses: how the domain, subdomains, folders and slugs are arranged, and the rules that keep them consistent. riot.nyc/glossary/url-structure/ has a structure. The domain is the brand, the folder says what kind of page this is, and the slug names the specific page. A visitor who has never seen the site can guess that riot.nyc/glossary/ lists all the terms, and a search engine can see that every page under that folder belongs to the same section.
Structure covers more than folders. It includes whether URLs use trailing slashes, whether they are lowercase, how words are separated, how parameters are handled, whether dates appear in paths, and how subdomains are used. Each decision is small; together they decide whether the site has one address per page or several.
Why it matters
Why URL structure matters
URLs are read. They appear in search results, in the browser, in shared links and in citations, and a readable address earns trust before the page loads. Search engines use the path as context: pages grouped under a folder are understood as related, and the words in the path confirm the subject. A structured site also makes technical SEO easier, because rules can be written per folder (index these, block those, apply this template) rather than per page.
Structure matters most when it goes wrong. Inconsistent URLs create duplicates, migrations without a plan break thousands of links, and a site that encodes the content management system's internals in its addresses is stuck with them forever.
In practice
How URL structure works in practice
- 01
Structure is designed with the site architecture, before the first page is built. The top-level folders mirror the main sections, the depth is kept shallow, and the conventions are fixed: lowercase, hyphens between words, trailing slash or not, no parameters in canonical addresses, no dates unless content is genuinely time-bound. Subdomains are reserved for genuinely separate properties, because search engines treat them as semi-independent sites; everything that belongs to the main brand lives under the main domain in folders.
- 02
Once live, the structure is enforced: the server redirects non-canonical forms, the content management system generates addresses by the rules, and any change to the pattern is treated as a migration with a full redirect map. When a site is rebuilt, preserving the URL structure, or redirecting every old address to its new equivalent, is the single most important task.
At RIOT
URL structure at RIOT
riot.nyc follows a few folders and no surprises. Client pages live under /our-friends/, industry pages under /our-creations/, and every glossary term under /glossary/, each ending in a slash and named by its slug. The pattern is deliberately boring, because an address a person can predict is an address a search engine can trust.
Watch out
What people get wrong about URL structure
Changing it casually. A redesign that moves every page to a new pattern without redirects throws away the authority of every old address at once, and it happens far more often than it should. The other mistake is depth for its own sake, nesting pages five folders down to mirror an internal hierarchy nobody searches for. And subdomains are overused: a blog at blog.example.com splits authority that a folder at example.com/blog/ would have kept.
