The Keyword Mismatch Trap: When Derrick Means Football, Not Drilling Equipment

Last quarter, I reviewed a keyword list for an energy equipment manufacturer. The first term made sense: "derrick." The task looked straightforward—or rather, it did until I reached the third row. Then came "derrick groves mother." Then "derrick perkins." Then "eddie dixon." Then "how many yards does henry have."

On its own, that list is almost funny. But when your business sells drilling derricks and mine hoisting equipment, those keywords aren't a joke. They're an emergency. In my role coordinating urgent content audits for industrial clients, I've reviewed over 60 keyword sets in the past three years—and this pattern comes up more often than it should.

What Looks Like a Content Problem Is Actually an Intent Problem

The surface problem is obvious: someone pulled a list of search queries containing "derrick" without checking who was searching. "Derrick Perkins" and "Eddie Dixon" are people, not industrial equipment. "Derrick Groves' mother" is a personal query. And "how many yards does Henry have" is about Derrick Henry, the NFL running back—not about a mast on an oil rig.

Why does this happen? Because keyword tools see strings, not entities. The tool takes "derrick," adds autocomplete suggestions, and exports everything that shares the name. It doesn't know or care that your domain is about rock drills and headframes. The result is 90% irrelevant queries that look like traffic potential in a spreadsheet.

But the deeper issue isn't the tool. It's the absence of a defined search entity. Before you choose keywords, you have to decide exactly which segment of the search world your site wants to own. Without that decision, any word with multiple meanings can pull you in the wrong direction.

Why the Wrong Keywords Are a Structural Threat

Search engines don't simply match strings. They try to understand relationships between terms. When a searcher types "how many yards does henry have," the algorithm sees "Henry," "yards," and a sports-stats pattern. It knows the intent is athletic performance, not inventory capacity. If you publish that phrase on an industrial page, you create confusion at the entity level.

What I mean is that every headline, every paragraph, and every internal link is an association signal. Publish "Derrick Perkins" on a drilling equipment site, and Google has to work harder to decide whether your page is about an oil derrick, a person, or something else. You may still rank for your product terms if your domain is strong, but you're wasting the one thing SEO cannot buy: clear topical authority.

The most frustrating part is that this is preventable. I can trace most keyword mismatches back to an editorial calendar that runs ahead of research. A blank slot is filled with "whatever has volume," and the list arrives without a filter. You'd think someone would stop at "derrick groves mother" and ask if a mining engineer would ever type that. They don't.

The Cost: More Than a Wasted Article

Let me be direct about what this costs. First, there's the obvious time: writing, editing, design, review, publishing. A 1,200-word article that never reaches a buyer still takes hours to produce.

Then there's a subtler cost. When Google associates your domain with ambiguous, sports-adjacent queries, you may start to rank for terms you never wanted while your real product terms slip. You'll see impressions for "derrick" but no clicks, because the searcher was looking for Derrick Henry's rushing totals. That looks like brand awareness, but it's irrelevant exposure.

In March 2024, a manufacturer called me with exactly this problem. Their SEO list had scheduled a paid article about "how many yards does Henry have" because the search volume was high. The piece was well written—it correctly explained the player's stats. But it generated zero inquiries from drilling companies. The client spent about $2,000 on the article and another week explaining to leadership why it didn't convert. We killed the piece, replaced it with a technical guide to derrick maintenance, and that guide produced three RFQs in its first month.

The damage went beyond money. The team lost confidence in its own editorial judgment. That's harder to fix than a bad keyword list.

What to Do Instead: Build a Search-Intent Filter

The fix is not to "write better." It's to redesign the keyword selection process around likely buyer intent.

• Start with product categories. Use "drilling derrick," "derrick mast," "mine headframe," or "hoisting equipment"—terms your engineers and procurement people actually use.
• Ask your sales team for the language in RFQs. That first-party data is more reliable than any autocomplete export.
• Never target a single ambiguous word like "derrick" without a context modifier. The intent under "derrick" is too divided between sports names, people, and equipment.
• Delete every query that references a person unless that person plays a decision-making role in your industry. "Derrick Perkins" and "Eddie Dixon" may be fine writers or athletes, but they are not mining specifications.

I also want to be honest about limitations. My experience is based on roughly 60 B2B keyword audits with industrial clients. If you're in consumer goods or local services, your patterns may differ. And search engines change: as of Q1 2025, entity recognition is central to how Google interprets content, but that can shift. Verify what your own Search Console data shows before betting a full editorial calendar on one strategy.

There's something satisfying about the cleanup phase. Once the bad queries are gone, the next article begins to rank for "drilling derrick mast," and the leads start coming from people who actually want to buy equipment. That's the payoff—not a dashboard with irrelevant traffic, but a pipeline with conversations.

So the next time a keyword list contains "how many yards does henry have" beside "derrick," don't ask how to write around it. Ask who built the list and why nobody filtered by intent. That's the actual crisis—and it's fixable.