Cites Google

Content Cannibalization: When Nashville Law Firm Pages Clash

5 min read

  • 6 sections
  • 2 sources cited

Content cannibalization is the problem of two pages on the same site trying to answer the same search intent, so that the site has two weaker pages where one stronger page would serve. It is not the same as two pages showing up for one query. Google’s John Mueller made that distinction in September 2025: “If you have 3 different pages appearing in the same search result, that doesn’t seem problematic to me just because it’s ‘more than 1′”, and his advice was “Reduce unnecessary duplication and spend your energy on a fantastic page” (Search Engine Journal, September 22, 2025). For a law firm, the job is to tell real overlap from harmless overlap, and to fix the first kind without deleting pages that do separate work.

Three Signs That Point to a Real Problem

These three signs are evidence to weigh, not a checklist that must be complete before acting:

  1. Same intent. A person who would be satisfied by one page would be equally satisfied by the other. “Nashville car accident lawyer” (hire someone) and “what to do after a car accident in Tennessee” (learn something) are different intents, even though both mention car accidents. This is the central sign; without it, two pages on the same subject are doing different jobs.
  2. Overlapping content. The pages answer the same points for the same reader. They need not be word-for-word copies: two differently written pages that each try to be the firm’s answer to “do I have a car accident case” overlap in the way that matters.
  3. Evidence in the data. Search Console shows the two URLs for the same queries, and their positions or impressions trade back and forth instead of one page settling. Data like this shows the pages competing for a query; it does not by itself prove that the competition is what is holding either page back.

The stronger the first sign and the more of the others that hold, the stronger the case for acting. Where the pages share an intent only in theory and the data never shows them appearing for the same searches, Mueller’s comment that “it’s not really ‘cannibalization’ if it’s theoretical” applies.

How to Check in Search Console

In the Performance report, open the Queries tab, pick a high-value query, then switch to the Pages tab to see which URLs received impressions for it. Repeat for the firm’s main practice queries. The pairs worth investigating are those where:

  • a blog post receives more impressions than the practice page for a hiring query the practice page was built for;
  • two URLs alternate as the top-performing page for the same query from month to month;
  • a new post’s impressions rise in the same weeks the older page’s impressions fall for the same queries.

Mueller’s point that “Search Console shows data for when pages were actually shown” is the reason to work from that data rather than from a keyword list.

Consolidate or Differentiate

Before choosing, put the two pages side by side on the things a merge would put at risk: the queries each appears for, the clicks and contacts each brings, and the links each has from other sites. When the case for acting is clear, there are two fixes.

Consolidate when the pages do the same job. Merge the useful content into the stronger page, then point the weaker URL to it with a permanent redirect. Google’s documentation says that with a permanent redirect, “the indexing pipeline uses the redirect as a signal that the redirect target should be canonical,” and recommends “a permanent server-side redirect whenever possible” (Google’s redirect documentation). Update internal links to point at the surviving URL and remove the old URL from the sitemap so the site does not keep sending signals to a page that no longer exists.

Differentiate when the pages can do separate jobs. Rewrite each around one question it owns, and make the difference visible in the title and the first paragraph. Link the narrower page to the broader one so the relationship is clear to readers.

Leaving two near-identical pages in place is the option to avoid, because it keeps the duplication Mueller recommends reducing.

Practice Pages and Blog Posts: Where the Line Sits

A practice page serves the person deciding whom to hire: what the firm handles, how the process and fees work, where the firm practices, how to reach it. A blog post serves a narrower question, one a reader may have well before deciding to hire anyone. One way a collision starts is a post that drifts into the practice page’s job and ends with a full description of the firm’s services for the same practice. Keeping posts on their question and linking them to the practice page keeps the line clear. What a practice page needs to contain is covered in the post on why practice area pages fail to rank.

A truck crash page and a general motor vehicle accident page can look like duplicates on a keyword list, but a truck case is a specific kind of motor vehicle case with its own questions, starting with the commercial carrier and its insurer. The relationship is general page and specific page, not two names for the same thing.

The test is the same as for any pair. If the truck page only repeats the general page with “truck” substituted, it is a duplicate and should be merged or rebuilt. If it answers questions the general page does not, keep both, link the specific page from the general one, and make each title say which question it answers.

When the Pages Are Location Pages

Firms with offices in Nashville and its suburbs face a version of the same problem with city pages. Pages that differ only by a swapped city name raise a separate issue under Google’s spam policies, which list among doorway examples “pages targeted at specific regions or cities that funnel users to one page.” That case is covered in multi-location SEO for Nashville-area firms.

Before merging or deleting anything, confirm the two pages share an intent and check what Search Console and the firm’s own contact records show for each; where the intents differ, the better fix is to sharpen each page rather than remove one.