Latest / 5 Minute UX / Structuring Keyword-Rich URLs
Transcript
- 0:08This lesson is Structuring Keyword-Rich URLs. Let's get
- 0:11started.
- 0:19When you build a URL, the first move is selecting keywords that
- 0:22match the specific section of the site. You are not just
- 0:24naming a file; you are declaring what that part of the site is
- 0:27about to the search engine. Take the example structure:
- 0:29sitename.com/widget- catalog/aquatic-
- 0:31widgets/underwater- submersible.html. Notice how
- 0:34each part of the path carries its own relevance. The domain
- 0:36sets the brand, the first directory names the broad
- 0:39category, and the filename identifies the specific product.
- 0:41This layered approach lets the engine understand the hierarchy
- 0:44instantly. The rule for separating these keywords is
- 0:46simple: always use hyphens. Whether you are dealing with a
- 0:49multi-keyword domain or a filename, the hyphen is the
- 0:51standard separator. It tells the parser where one word ends and
- 0:54the next begins, which underscores are not guaranteed
- 0:57to do. Keep the filename focused. Avoid stuffing too many
- 0:59keywords into a single name, as it dilutes the signal. A clear,
- 1:02concise filename like "underwater-submersible.html" is
- 1:05far more effective than a long, cluttered string. If you are
- 1:07starting from scratch and branding allows, try to get a
- 1:10domain with one or two relevant keywords. Even if you can't, the
- 1:13hyphenation rule still applies to any multi-word domain you
- 1:15choose. This foundation of keyword selection and
- 1:18hyphenation sets the stage for the directory structure that
- 1:20follows.
- 1:26Search engines map your site’s hierarchy directly from the
- 1:29directory structure, so the placement of folders dictates
- 1:31how they understand your content. You need to place the
- 1:34most important directories at the top of the architecture,
- 1:37ensuring that the primary categories sit closest to the
- 1:39domain root. Keep the structure simple, and avoid having
- 1:42extraneous files in the directory structure at all
- 1:44costs, because every unnecessary path adds noise to the signal.
- 1:47One major trap is the Content Management System automatically
- 1:49inserting sub-directories into your URLs. You must prevent the
- 1:52CMS from doing this if possible, as these hidden layers dilute
- 1:55the relevance of the entire site. The directory structure
- 1:58critically influences how link popularity is distributed
- 2:00throughout the site, meaning a clean, shallow hierarchy
- 2:03concentrates that authority where it matters most. With a
- 2:05streamlined, keyword-focused hierarchy established, the next
- 2:08step is ensuring that both the www and non-www versions of your
- 2:11site point to the same canonical address.
- 2:19The first concrete move is setting up a three-oh-one moved
- 2:22permanently redirect from the non-www address to the www
- 2:25version of your site. This step prevents accidental content
- 2:27duplication, which happens when a server resolves the same page
- 2:30with and without the www prefix. Search engines, particularly
- 2:33Yahoo, may index content at both URLs, treating them as distinct
- 2:36pages rather than duplicates. This duplication condition tends
- 2:39to propagate when a third party links to your site without the
- 2:42www, or when your internal architecture uses dynamic link
- 2:45structures that omit the prefix. You mitigate these risks by
- 2:48establishing a single canonical source. The three-oh-one
- 2:50redirect is the only acceptable redirect type for search engine
- 2:53purposes, ensuring that link equity flows to one specific
- 2:56location. When you implement this, you are applying the
- 2:58three-oh-one moved permanently status code to map old URLs to
- 3:01new ones on a one-to-one basis. This precise mapping preserves
- 3:04the relevance you built in your directory hierarchy.
- 3:13[0.00s] Think about the moment you swap out your content
- 3:15management system. That change almost always forces every
- 3:18single URL to shift, which puts your entire site architecture at
- 3:21risk. Your first move is to preserve as many old URLs as
- 3:24possible, because keeping the existing structure intact saves
- 3:26you from a massive cleanup later. [4.20s] But when URL
- 3:29changes are truly inevitable, you have to manage the
- 3:31transition carefully. You assign a status code of three-oh-one
- 3:34Moved permanently to every old URL, which tells search engines
- 3:37that the content has moved for good. This specific status code
- 3:40is the only acceptable redirect type for search engine purposes,
- 3:43so you never use temporary redirects here. [12.60s] The
- 3:45mapping itself demands strict discipline. You execute
- 3:48redirects on a strict one-to-one basis from old URLs to new URLs,
- 3:51ensuring that no single old link points to multiple new
- 3:53destinations. This precision prevents link popularity from
- 3:56getting diluted or lost in the shuffle. [20.40s] You also need
- 3:59to check your site’s taxonomy during this transition. Keyword
- 4:01targets must be reflected in the site's taxonomy, which means you
- 4:04avoid jargon that doesn’t match user search behavior. If you are
- 4:07selling widgets, you don’t call the product list just "catalog."
- 4:10You call it "Widget catalog." [32.20s] This naming choice
- 4:13makes the whole site more relevant for the products being
- 4:15sold. It ties directly back to the initial goal of building
- 4:18keyword-rich structures. When you combine careful URL
- 4:20preservation, proper three-oh- one redirects, and precise
- 4:23taxonomy, you create a stable foundation. This is how you
- 4:26ensure your site remains visible and relevant, even as the
- 4:28underlying technology changes. [48.00s] So the next time you
- 4:31plan a system migration, remember that the URLs are part
- 4:34of your strategy, not just technical details. Treat them
- 4:36with the same care you give to your content.
- 4:41Welcome to The Take. I'm joined by a fellow practitioner and
- 4:44together we're going to dig into Structuring Keyword-Rich URLs —
- 4:47what it means in practice and what's worth remembering.
- 4:51[HOST] I keep coming back to that warning about CMS auto-
- 4:54inserting sub-directories. It feels like a technical detail,
- 4:57but it actually breaks the relevance signal. [LEARNER] It
- 5:00does. We had a client where the platform added a date folder to
- 5:03every post URL. It buried their top-tier content three levels
- 5:06deep. [HOST] Exactly. That shallow hierarchy is what
- 5:09concentrates the link equity. If you let the software bloat the
- 5:12path, you dilute the authority you worked hard to build.
- 5:15[LEARNER] And the worst part is that the fix is often just a
- 5:18config change that the developers ignore. They see the
- 5:21site working, so they don't care about the path length. [HOST]
- 5:24That’s the gap. They see functionality, but we see the
- 5:27semantic structure. The URL is a declaration of intent, not just
- 5:30a file location. [LEARNER] Speaking of intent, I’m curious
- 5:33how you view AI agents interacting with these
- 5:35structures. They don’t click links like humans do. [HOST]
- 5:38Good point. If an agent is scraping your site, it might
- 5:41ignore the visual hierarchy and just parse the raw path. A messy
- 5:44URL is a direct hit to machine readability. [LEARNER] So clean,
- 5:47hyphenated paths aren’t just for search engines anymore. They’re
- 5:51for the bots that are actually doing the summarizing and
- 5:53retrieval. [HOST] Precisely. The machine needs the hierarchy to
- 5:57be explicit. If your URL is ambiguous, the agent has to
- 5:59guess your intent, and it usually guesses wrong. [LEARNER]
- 6:02That makes the 301 redirect discipline even more critical.
- 6:05If you've duplicate signals, the agent might index the wrong
- 6:08version as the canonical source. [HOST] Yes. And unlike a human
- 6:12user who might just close the tab, an agent might permanently
- 6:15store the wrong URL in its knowledge base. That’s a long-
- 6:18term brand issue. [LEARNER] So we’re not just preventing
- 6:20duplicate content for Google. We’re preventing data pollution
- 6:24for AI. [HOST] That’s a fair way to frame it. The redirect isn’t
- 6:27just a technical fix. It’s a data integrity measure for the
- 6:30entire digital ecosystem consuming your content.
- 6:32[LEARNER] I’ll have to check our redirect map again with that
- 6:35lens. It changes how I view the maintenance burden. [HOST] It
- 6:38should. Treat the URL as a permanent asset, not a temporary
- 6:41container. That mindset shift solves most of the migration
- 6:44headaches we see.