A SaaS company created a dedicated entity-optimized page for their product category, including comprehensive schema markup and entity co-occurrence patterns. Within six weeks, Google began ranking that new entity page for queries previously owned by the product’s main landing page, which had generated 40% of organic revenue. The entity optimization succeeded technically but created a cannibalization problem: Google associated the entity with the new page and reassigned query relevance away from the conversion-optimized page. Entity optimization and keyword targeting can work against each other when Google’s entity resolution assigns a different URL as the entity’s canonical representation than the URL you want to rank.
How Entity Association Creates URL-Level Cannibalization
Google’s entity recognition system assigns entity associations at the URL level. When the system identifies a page as the strongest representation of a specific entity on a domain, that page becomes the preferred result for entity-rich queries, queries where the search intent centers on understanding, evaluating, or learning about the entity rather than performing a specific action related to it.
The cannibalization occurs when this entity-preferred URL is different from the URL that was previously ranking for the same queries through keyword-level signals. The keyword-targeted landing page may have ranked because it contained the right keyword terms, had strong backlinks, and matched the query’s transactional intent. The new entity-optimized page displaces it because Google’s systems increasingly favor entity-level relevance for queries that map to Knowledge Graph entities.
The mechanism is asymmetric. The entity page gains ranking for entity-rich queries because of its stronger entity signals (more comprehensive schema markup, better entity co-occurrence, more complete entity coverage). The keyword page loses ranking for those same queries despite having stronger conversion optimization, better backlinks, and a longer ranking history. Google’s entity resolution does not evaluate which page is better for the user from a conversion perspective. It evaluates which page best represents the entity.
This creates a ranking conflict that traditional keyword cannibalization frameworks do not detect. Standard cannibalization diagnosis looks for two pages targeting the same keyword. Entity cannibalization involves two pages associated with the same entity through different signal types (keyword signals vs. entity signals), and the resolution favors the entity-signal page even when the keyword-signal page was performing well.
The Trigger Conditions That Cause Entity-Keyword Conflicts
Specific implementation patterns reliably trigger entity-keyword cannibalization. Recognizing these patterns before implementation prevents the problem.
Creating a separate entity hub page when the existing keyword page already has implicit entity signals. A product landing page that mentions the product category entity, uses the entity name in headings, and has accumulated backlinks with entity-relevant anchor text already carries entity signals. Creating a separate “What is [Product Category]” page with comprehensive entity markup competes directly with the existing page for entity association.
Adding comprehensive schema markup to a new page that duplicates the entity context of an existing page. When a new blog post about the product category includes Organization schema, Product schema with sameAs links, and entity co-occurrence patterns that the existing landing page lacks, Google may reassign entity association to the better-marked-up page. The markup creates an explicit entity signal that overrides the implicit signals accumulated by the existing page.
Publishing hub pages that compete with spoke pages for entity queries. In a hub-and-spoke content architecture, the hub page is typically designed as a comprehensive overview. If the hub page is heavily entity-optimized while spoke pages are keyword-optimized, Google may route entity-rich queries to the hub instead of to the relevant spoke page that was ranking and converting.
Launching a glossary or knowledge base that covers the same entities as product pages. A glossary entry for “CRM software” with rich entity markup can cannibalize the main CRM product page for informational queries that previously drove awareness traffic to the product page.
Diagnosing Entity Cannibalization in Search Console Data
Entity cannibalization produces a specific data pattern in Google Search Console that distinguishes it from standard keyword cannibalization.
Symptom 1: URL switching for entity-rich queries. In Search Console’s Performance report, filter by specific entity-rich queries and examine which URLs receive impressions over time. If the URL receiving impressions shifts from the keyword page to the entity page after the entity optimization was deployed, the cannibalization is confirmed. The shift may be gradual (over 2-4 weeks) or abrupt (within a single week).
Symptom 2: The keyword page retains rankings for transactional queries but loses them for informational and entity-rich queries. Filter queries by intent type. If the keyword page still ranks for “[Product Name] buy” or “[Product Name] pricing” but has lost rankings for “[Product Category]” or “what is [Product Category],” the entity page has captured the informational and entity-level queries.
Symptom 3: Total clicks and impressions for the query set decline during the transition period. When Google is deciding between two competing URLs for the same queries, it may alternate between them or temporarily demote both. This transitional volatility produces a net traffic decline even if one URL eventually stabilizes in the rankings.
Distinguishing entity cannibalization from keyword cannibalization: Standard keyword cannibalization involves two pages with the same target keyword competing for the same queries. Entity cannibalization involves two pages associated with the same entity through different signal types. The diagnostic difference is that entity cannibalization disproportionately affects entity-rich informational queries while leaving transactional keyword queries less affected.
Resolution Strategies for Entity-Keyword Cannibalization
Resolving entity cannibalization requires consolidating entity signals onto the URL you want to rank, rather than allowing competing entity associations across multiple URLs.
Strategy 1: Consolidate entity markup onto the existing high-performing page. Instead of maintaining a separate entity-optimized page, add the comprehensive schema markup, entity co-occurrence content, and structured data to the existing keyword-targeted page. This page then carries both keyword signals and entity signals, eliminating the competition. This is the preferred resolution when the keyword page has strong conversion performance.
Strategy 2: Use internal linking and canonical signals to direct entity association. If both pages serve legitimate purposes (the keyword page for conversion, the entity page for top-of-funnel awareness), establish a clear relationship between them. Link from the entity page to the keyword page as the primary action destination. Use the entity page’s structured data to reference the keyword page via mainEntityOfPage or similar properties. This creates a hierarchy where the entity page establishes the entity context and the keyword page is positioned as the canonical action page.
Strategy 3: Differentiate entity scope between pages. If both pages must exist, ensure they target different entity scopes. The keyword page targets the specific product entity. The entity page targets the broader category entity. Distinct @type declarations, different sameAs links, and non-overlapping entity co-occurrence patterns reduce the overlap that causes cannibalization.
Strategy 4: Merge the pages. If the entity page and keyword page address substantially the same topic, merging them into a single comprehensive page eliminates the cannibalization. Redirect the lower-performing URL to the consolidated page to preserve link equity.
Prevention Framework for Entity Optimization Projects
Preventing entity cannibalization requires an audit-first approach before creating any new entity-optimized content.
Step 1: Map existing entity associations. Before creating entity-optimized content, identify which URLs on the domain currently rank for entity-rich queries. Use Search Console data to determine which pages Google currently associates with the target entities. These pages are the existing entity anchors.
Step 2: Optimize existing anchors rather than creating new pages. Add entity markup, co-occurrence content, and structured data to the pages that already hold entity associations. Enhancing an existing page’s entity signals is safer than creating a competing page because it builds on established associations rather than creating new ones.
Step 3: When new pages are necessary, scope them to distinct entities. If a new page is needed for content strategy reasons, ensure it targets a different entity than existing pages. A new page about “CRM implementation methodology” targets a different entity scope than an existing page about “CRM software,” reducing cannibalization risk.
Step 4: Monitor entity query routing after deployment. After any entity optimization, track which URLs receive impressions for entity-rich queries in Search Console. Set up weekly monitoring for 6-8 weeks post-deployment. If the new optimization is pulling queries away from the preferred URL, the cannibalization pattern is emerging and requires immediate intervention before it stabilizes.
For the mechanism behind entity recognition and Knowledge Graph association, see Entity Recognition and Knowledge Graph Association. For related internal linking conflicts, see .
How quickly does entity cannibalization appear after deploying a new entity-optimized page?
Entity cannibalization typically becomes visible in Search Console data within 2-6 weeks after Google recrawls and reindexes the new entity-optimized page. The URL switching pattern for entity-rich queries may be gradual, with impressions shifting from the original keyword page to the entity page over multiple weeks, or abrupt within a single week. Setting up weekly monitoring immediately after deployment catches the pattern before it fully stabilizes and causes significant traffic loss.
Should entity schema markup be added to the existing high-performing page rather than creating a new entity page?
Adding entity markup to the existing high-performing page is the preferred approach when that page already carries implicit entity signals through its content and backlinks. Consolidating both keyword signals and entity signals onto a single URL eliminates the competition between pages that creates cannibalization. This approach is especially important when the existing page drives significant conversion revenue, because maintaining its ranking continuity takes priority over creating a structurally cleaner entity page.
Does entity cannibalization only affect informational queries, or can it impact transactional queries too?
Entity cannibalization disproportionately affects informational and entity-rich queries while leaving transactional queries less impacted. Google’s entity resolution system favors the page that best represents the entity, which tends to be comprehensive and informational in nature. Transactional queries (“buy X,” “X pricing”) are resolved more heavily through keyword matching and conversion intent signals, where the original keyword page retains its advantage. However, if the entity page accumulates enough broad relevance, it can begin displacing the keyword page for commercial investigation queries that bridge informational and transactional intent.
