Latest / 5 Minute UX / Keyword Research: What It Is and Why It Matters
Transcript
- 0:09This lesson is Keyword Research: What It Is and Why It Matters.
- 0:13Let's get started.
- 0:20Internal labels create a silent barrier. When you label a
- 0:22section “Catalog,” you’re speaking your own language, not
- 0:25the user’s. This jargon disconnect is the single biggest
- 0:28reason high-quality content remains hidden. Users don’t
- 0:30search for “Resources” or “Solutions.” They search for
- 0:33specific terms like “widgets” or “laptops.” If your taxonomy
- 0:36uses “notebooks” but users type “laptops,” you are invisible to
- 0:39them. It’s not just about SEO ranking; it’s about structural
- 0:42clarity. You just spent three sprints building a feature
- 0:44nobody can find because the label didn’t match their query.
- 0:47That’s the cost of ignoring keyword research. When you
- 0:50align your navigation with actual user vocabulary,
- 0:52discoverability skyrockets. You stop guessing what users want
- 0:55and start showing them what they’re already looking for.
- 0:58That’s your Fix on The Jargon Problem!
- 1:06By the end of this lesson, you’ll be able to apply keyword
- 1:09research principles to align site taxonomy and naming
- 1:11conventions with actual user search vocabulary. It’s about
- 1:14bridging the gap between internal jargon and external
- 1:16intent. Think of a time you struggled to find content
- 1:19because the navigation labels made no sense. Maybe you looked
- 1:22for “Laptop Guides” but found only a vague “Resources”
- 1:24section. That friction happens when teams label things based on
- 1:27their own mental models, not the user’s. Consider how your own
- 1:30organization uses internal terms that outsiders might not
- 1:33understand. A company might call its product list a “Catalog,”
- 1:36but users search for “widgets.” If the label doesn’t match the
- 1:38query, the content is invisible. This disconnect is exactly why
- 1:41we do keyword research. It’s not just SEO; it’s Information
- 1:44Architecture. We use it to identify the distinction between
- 1:47IA-focused keyword research and general SEO or user research.
- 1:50The goal is structural clarity, not just ranking. When teams
- 1:53apply keyword targets to navigation labels and metadata
- 1:55to enhance discoverability, the site becomes intuitive. We
- 1:58replace internal terminology with the actual language users
- 2:01employ. This ensures your structure reflects real search
- 2:03behavior, making content worthy of attention and easy to find.
- 2:13The sequence begins by identifying the specific
- 2:15language users employ to find content. This is the definition
- 2:18of keyword research in Information Architecture. It’s
- 2:20not merely an SEO tactic for ranking. It’s a core component
- 2:23of developing your site’s taxonomy. We use this data to
- 2:25inform structural and labeling decisions. The primary problem
- 2:28this solves is the disconnect between internal business jargon
- 2:31and external user language. Practitioners often label
- 2:33content based on organizational structures. This obscures
- 2:36content from both users and search engines. If you sell
- 2:38widgets, labeling the section "Catalog" might be internally
- 2:41accurate. But it fails to communicate relevance to a user
- 2:44searching for "widgets." Experienced IA practitioners
- 2:46notice that jargon creates invisibility. High-quality
- 2:48content remains hidden if the system’s language doesn’t match
- 2:51the query. Keyword research ensures your site is worthy of
- 2:54attention. It aligns your taxonomy with the natural
- 2:56language users actually speak. You can apply keyword targets to
- 2:59navigation labels and metadata to enhance discoverability. This
- 3:02means replacing vague internal terms with specific user
- 3:04vocabulary. For instance, consider the difference between
- 3:07"notebooks" and "laptops." Users search for "laptops"
- 3:09significantly more frequently. Using "Laptop Guides" instead of
- 3:12a generic "Resources" label bridges that gap. It makes the
- 3:15structure intuitive for human visitors. It’s crucial to
- 3:17distinguish this from general user research. While interviews
- 3:20and surveys uncover user goals and behaviors, keyword research
- 3:23targets the vocabulary used in search queries. It’s a narrower,
- 3:25more linguistic focus. You’re looking at the words people
- 3:28type, not just the problems they face. This practice also
- 3:31differs from pure SEO optimization. SEO focuses on
- 3:33algorithmic ranking and traffic volume. IA-focused keyword
- 3:36research focuses on structural clarity and label accuracy. The
- 3:38goal is to reduce cognitive load and improve navigation. It’s
- 3:41about making the site map make sense to the human mind. When
- 3:44teams do this alignment well, discoverability improves across
- 3:47the board. The signal of strong work is a taxonomy that feels
- 3:49native to the user. They don’t have to translate business speak
- 3:52to find what they need. The labels match their mental model
- 3:55of the domain. This research belongs in the early phases of
- 3:58development. It should precede or run parallel to creating the
- 4:00site map. You need to define your naming conventions before
- 4:03you build the structure. This ensures that every section title
- 4:06and product category reflects actual search behavior. By
- 4:08grounding your structure in user vocabulary, you solve the
- 4:11problem of jargon-induced invisibility. You create a
- 4:13coherent taxonomy that serves both human usability and search
- 4:16engine relevance. The work becomes linkworthy because it
- 4:19presents content in a language everyone understands. We’ve
- 4:21defined what keyword research is and why it matters for
- 4:24structure. The next section walks through how to actually
- 4:26conduct this research.
- 4:33Here’s how this works in practice. Let’s say you’re
- 4:35building an e-commerce site. You’ve spent weeks designing a
- 4:37clean, logical navigation structure. It looks perfect on
- 4:40the wireframes. But when users arrive, they get lost
- 4:42immediately. Why? Because your internal labels don’t match
- 4:44their search intent. Start by auditing your current site
- 4:47labels against actual search data. Pull up your user query
- 4:49logs. Look for the gap between what you call things and what
- 4:52users type into the search bar. This step is critical for
- 4:54identifying where internal business jargon creates a
- 4:56disconnect with external user language. You’ll likely see
- 4:59terms like "Resources" or "Solutions" dominating your
- 5:01menu. These are safe, corporate choices. But they are invisible
- 5:04to users who are hunting for specific answers. The fix is to
- 5:06apply keyword targets to navigation labels and metadata
- 5:09to enhance discoverability. Swap that generic "Resources" folder
- 5:11for "Laptop Guides." Replace "Catalog" with "Widget Catalog."
- 5:14It feels specific, maybe even slightly verbose. But it matches
- 5:17the user’s mental model. When teams do this well, the
- 5:19navigation becomes intuitive. Users don’t have to translate
- 5:21your structure into their needs. They just find what they want.
- 5:24This work belongs in the early phases of Information
- 5:26Architecture development. Specifically, start when
- 5:28defining the site’s taxonomy and naming conventions. Don’t wait
- 5:31until the site map is built. If you wait, you’re retrofitting
- 5:34labels onto a structure that already assumes internal logic
- 5:36is correct. That’s a harder fix. By integrating keyword research
- 5:39early, you ensure the skeleton of your site is built from the
- 5:41user’s vocabulary, not the department head’s org chart.
- 5:44Experienced practitioners notice that this alignment reduces
- 5:46cognitive load significantly. The signal of strong work is
- 5:49when a new user can land on the homepage and immediately
- 5:51understand where to click without reading a single
- 5:53paragraph of copy. The labels themselves do the explaining.
- 5:56This is especially vital for content-heavy portals or any
- 5:58platform where discoverability is a primary user goal. We’ve
- 6:01covered the application strategy. Next, we’ll look at
- 6:03the common confusions around keyword research and how to
- 6:05distinguish it from general SEO efforts.
- 6:13In your next project, start by auditing your current site
- 6:16labels against actual search data or user query logs. You
- 6:18need to identify where internal jargon diverges from common user
- 6:21search terms. This is the critical step to align site
- 6:24taxonomy and naming conventions with actual user search
- 6:26vocabulary. Look for labels like "Resources," "Solutions,"
- 6:29or "Catalog." These terms often feel right to the team but fail
- 6:32users. Replace them with the specific keywords users employ.
- 6:34For instance, change a generic "Catalog" label to "Widget
- 6:37Catalog." Swap "Notebooks" for "Laptops" if that is what people
- 6:40type. This simple swap ensures your Information Architecture is
- 6:43both discoverable and intuitive. It enhances both human usability
- 6:46and search engine relevance through linguistic alignment. By
- 6:49applying keyword targets to navigation labels and metadata,
- 6:51you boost discoverability significantly. The signal of
- 6:54strong work is a taxonomy that feels 'worthy of attention.'
- 6:56Presenting content in user- understood language makes the
- 6:59site linkworthy and clear. That brings the lesson full circle,
- 7:02connecting user intent directly to system structure.
- 7:07Welcome to The Take. I'm joined by a fellow practitioner and
- 7:10together we're going to dig into Keyword Research: What It Is and
- 7:13Why It Matters — what it means in practice and what's worth
- 7:16remembering.
- 7:18[HOST] That bit about retrofitting labels felt
- 7:20painfully familiar. I just finished a project where we
- 7:23built the whole site map before checking search logs. [LEARNER]
- 7:27Exactly. We spent weeks debating if 'Solutions' was too
- 7:30corporate, but the data showed users were typing 'pricing
- 7:33calculator.' [HOST] And that gap is where the real friction
- 7:36lives. The structure was logical to us, but invisible to them.
- 7:39[LEARNER] It’s tricky because stakeholders hate specific
- 7:42labels. They want clean, abstract navigation menus that
- 7:45look good on the org chart. [HOST] True. But clean menus
- 7:48often mean high cognitive load for the user. You’re forcing
- 7:51them to translate your internal logic into their intent.
- 7:54[LEARNER] I wonder if AI changes how we handle that translation
- 7:58layer. Maybe we can keep the clean labels but use AI to
- 8:01interpret the intent behind them. [HOST] That’s a fair
- 8:04point, but it feels like a band- aid. If the underlying taxonomy
- 8:07is wrong, AI just masks the structural failure. [LEARNER] I
- 8:10see your point. But what if the AI generates the metadata
- 8:13dynamically based on the query? You keep the 'Solutions' label,
- 8:17but the system knows it maps to 'pricing.' [HOST] That works for
- 8:20search, but it doesn’t fix the navigation. Users still have to
- 8:23click through a vague menu to get there. [LEARNER] So the
- 8:26lesson remains: fix the structure first. Don’t rely on
- 8:29algorithms to bridge a vocabulary gap you created.
- 8:32[HOST] Precisely. Good IA makes the right path obvious without
- 8:35needing a smart engine to guess where you’re going.