340 Posts, 47 Cannibalization Issues, Zero Unified Strategy

The Audit: Facing the Full Scope of the Problem

A content audit at this scale is not a spreadsheet exercise. Auditing 340 blog posts and 854 landing pages — 1,194 URLs in total — requires a systematic framework before you open a single document. You need consistent criteria, a clear decision taxonomy, and agreement across stakeholders on what "good" looks like before you evaluate a single piece of content against it.

The audit covered five dimensions for every piece of content: search performance (impressions, clicks, average position, click-through rate), content quality (depth, accuracy, alignment with current product positioning), keyword alignment (what term is this page actually targeting, and is that term worth targeting), buyer journey stage (awareness, consideration, or decision), and overlap analysis (what other pages on the site are targeting the same or adjacent terms).

The cannibalization analysis alone was a significant undertaking. Identifying 47 instances meant mapping every meaningful keyword cluster across the site and flagging every case where two or more pages were competing for the same primary or secondary terms. At that point you have to make decisions: which page is the canonical version? Which page gets the organic signals consolidated to it? What happens to the others?

What the four-team structure had produced was a textbook self-competition problem. The CRM team had written extensively about "contact management." The Marketing Automation team had written about "contact management workflows." The Support team had a piece on "managing customer contacts." From Google's perspective, these were not distinct topics serving distinct audiences. They were three pages competing for the same searcher, splitting signals three ways, and collectively ranking below where a single, authoritative piece would have landed.

Multiply that across four product lines and five years of independent content production, and you have 47 documented instances — and an unknown number of softer overlaps creating drag on performance across the entire content library.

The Content Architecture: Building a Taxonomy That Actually Works

The solution to fragmented content isn't a style guide. It's architecture. Topic clusters — a framework where one authoritative pillar page covers a broad topic and a set of supporting cluster pages cover related subtopics, all internally linked back to the pillar — are the structural answer to the silo problem. But implementing topic clusters at enterprise scale, across four product lines with distinct audiences and messaging, requires more than just a template. It requires a unified taxonomy.

A taxonomy in content strategy terms is a shared classification system. It answers: What are the core topic areas for this company? What subtopics live under each one? What's the relationship between topics across product lines? Who owns each topic cluster? At what stage of the buyer journey does each piece of content serve?

For Nexova, building a unified taxonomy meant getting all four content teams — who had previously operated entirely independently — to agree on a single source of truth for how content was categorized, labeled, and connected. That's as much an organizational challenge as a strategic one. Content teams are territorial about their topics. When the Marketing Automation team has been writing about "lead nurturing" for two years and is then told that "lead nurturing" belongs to a pillar page owned by the CRM team, that conversation requires careful framing.

The taxonomy we built mapped every meaningful topic cluster across all four product lines, identified the single authoritative page that would serve as the pillar for each cluster, and explicitly documented where cross-product content would live and who owned it. The result was a shared content map that every team was working from — the first time that had existed in the company's content history.

With the taxonomy established, every piece of existing content needed a decision. There were five options: merge two pieces of overlapping content into a single, more authoritative piece; consolidate a cluster of thin posts into one comprehensive guide; rewrite a piece that had the right topic but the wrong treatment; 301 redirect a page that no longer served a strategic purpose to the correct canonical URL; or delete content that had no traffic, no links, and no path to ranking for anything meaningful.

Each of those decisions requires judgment. You can't run content through a spreadsheet formula and get the right answer. A page with low traffic might still be worth keeping because it's the only piece targeting an important long-tail keyword. A page with decent traffic might need to be deleted because it's drawing in entirely the wrong audience. The audit framework gives you the data. The strategy is what tells you what to do with it.

Schema Markup at Scale: Making 854 Pages Legible to Google

Schema markup is structured data embedded in a page's HTML that tells search engines exactly what type of content they're looking at, who wrote it, what it's about, and how the pieces relate to each other. For a small site, schema is a nice-to-have. For an enterprise B2B software company with 854 landing pages across four product categories, schema is infrastructure.

When Nexova's engagement began, schema coverage was near zero. Not a few missing implementations — nearly the entire site was sending unstructured signals to Google. In practical terms this meant the site was leaving significant search real estate on the table. Featured snippets, knowledge panel entries, FAQ-style result expansions, and rich results for software and product pages all require schema to trigger. None of them were available to Nexova.

Implementing schema across 854 pages isn't a task you do page by page. Like the content audit, it requires a system. The schema plan we built for Nexova mapped every content type across the site — blog articles, product landing pages, feature comparison pages, case study pages, integration hub pages — and specified the appropriate schema type for each. Article schema for editorial content. SoftwareApplication schema for product pages. FAQPage schema for feature documentation. BreadcrumbList schema sitewide. Then, rather than making 854 individual edits, the implementation was done at the template level wherever possible, with CMS variables populating the structured data automatically.

The result: 100% schema coverage across the entire site, including properties for organization, author, date published, date modified, and primary topic classification for every content type. The practical outcomes showed up in search results within weeks — rich snippets appearing for high-priority product pages, structured results for FAQ content, and improved clarity for Google's understanding of the site's topical authority.

Schema is one of those investments that looks like overhead until you see a competitor's result appearing as a featured snippet for a term you'd been targeting for two years. Then it looks like a strategic gap.

The Results: What the Numbers Actually Mean for Business

Twelve months after implementation, the results were clear across every metric that mattered. But the numbers in isolation don't tell the full story. Here's what each one actually means in business terms.

+68% organic traffic. This is not 68% more random people landing on the site. Organic search traffic, by definition, is traffic from people actively searching for something your content addresses. A 68% increase means 68% more qualified prospects arriving at Nexova's pages — people in market for the exact problems Nexova solves. No ad spend. No outbound campaign. Just a better-organized content library doing its job.

+43% lead generation increase. This is the metric the business cares about most. More traffic is only valuable if it converts. A 43% increase in leads generated from organic means that the content improvements didn't just bring more people in — it brought them to the right pages, at the right stage of the buyer journey, with messaging that matched their intent. That's architecture working exactly as intended.

+112% blog traffic increase. Blog traffic more than doubled. This is worth highlighting separately because it reflects the successful resolution of the cannibalization problem. When 47 competing pages were consolidated, redirected, or eliminated, the surviving authoritative posts received all of the ranking signals that had previously been split across multiple weaker pages. Consolidating equity is not a theory. It shows up in rankings, and rankings show up in traffic.

47 cannibalization instances resolved to zero. Google now knows exactly which Nexova page should rank for every target keyword. There is no ambiguity, no signal-splitting, no self-competition. Each topic cluster has one pillar page. Each pillar page has one clear relationship to its supporting content. The content library is legible — to Google and to the sales teams who use it every day.

100% schema coverage. Starting from near zero, the entire site now speaks Google's language for structured data. Rich results, featured snippet eligibility, and entity clarity across all four product lines. This one doesn't have a single dramatic "before and after" number attached to it, but it is foundational to every other improvement listed here. Schema coverage doesn't just help with the current query — it builds the trust signals that compound over time.

What This Means If You Have 40 Posts Instead of 340

The scale in this case study is enterprise. The lesson is not.

Content cannibalization doesn't require 854 pages to happen. It can happen with 25. If you've been publishing content for more than a year without a deliberate topic cluster strategy, there's a reasonable chance your own pages are already competing against each other — diluting signals, confusing intent matching, and collectively underperforming relative to what a well-organized, smaller content library would achieve.

The question I ask when I look at any content library — large or small — is whether Google could explain your content strategy back to you. Not whether it could identify that your topic is "HVAC services in Atlanta" or "small business bookkeeping." Whether it could articulate the logical relationship between your posts, identify the authoritative page for each topic, and understand where each piece sits in the buyer journey. For most small business sites I've looked at, the answer is no.

And that's not a publishing problem. It's not a frequency problem or a word count problem. It's an architecture problem. Producing more content without a taxonomy doesn't fix it — it accelerates it. You get to the same broken state faster.

This is why the work I do with small businesses starts with strategy before it starts with content. Not because content doesn't matter — it matters enormously — but because content without architecture is just noise. It looks busy. It might even feel productive. But if it's not organized around how your audience searches and how Google reads topical authority, you're building on sand.

The Nexova engagement proves the same principle at the other end of the scale. A company with serious resources, an experienced team, and years of genuine content production still ended up with a library that was actively working against itself — because the foundation was never built. The fix wasn't more content. It was architecture. It always is.

If you've been producing content for a while and organic growth has plateaued — or if you've never been sure whether your posts are working with each other or against each other — the right first step is an honest content audit. Not a new content calendar. Not a higher publishing frequency. A clear-eyed look at what you already have, what it's doing, and what it needs to become.

That's the work. And it's worth doing before you write another word.