Answer-first guide

How to audit duplicate search intent before pages compete

Compare tasks, inputs, outputs and proof needs so overlapping queries become one strong page instead of several thin pages.

MCXAI Editorial · reviewed 2026-07-18 · for SEO editors, product teams and site architects planning tool or guide inventories

Short answer

Treat queries as one page when they require the same task, source input, finished output and evidence. Consolidate those variants into one canonical record. Keep separate pages only when a user would need a materially different workflow or result.

Colored query paths passing through a comparison lens, with three similar paths merging into one page and distinct paths remaining separate — Queries merge when the required task and evidence match; different outcomes retain separate destinations. Original MCXAI artwork.

Inventory routes and query variants together

Create one row per proposed or published route. Record its primary user task, likely query variants, required input, promised output and current evidence. An audit cannot find cannibalization when the keyword list and route list live in separate files.

Normalize trailing slashes and route aliases.
Include planned pages before they are published.
Attach every variant to a candidate canonical route.
Flag a query assigned to more than one candidate.

Compare four intent dimensions

Ask whether the user is trying to complete the same task, arrives with the same kind of source, expects the same finished result and needs the same proof to trust it. Shared vocabulary alone is weak evidence; matching all four dimensions is a strong consolidation signal.

Merge equivalents and separate real workflow differences

When all four dimensions align, choose one primary intent, store the other phrases as merged variants and build the strongest single page. When the source, workflow or result differs, retain separate pages and make that distinction visible in the title, H1, interface and example.

Verify the decision in routing and internal links

The canonical, sitemap entry, navigation labels and related links should all support the chosen page. Redirect retired duplicates when appropriate. Do not use a canonical tag as a substitute for removing two indexable pages that still make the same promise.

Worked example

Check the source against the result

convert JSON to CSV · JSON array to spreadsheet · flatten JSON

One /tools/json-to-csv page with a working converter, a nested-path example and all three phrases recorded as merged query variants.

The wording differs, but each query starts with JSON records and expects a flat spreadsheet-ready file, so three pages would repeat the same task and proof.

Use the same rule in publication review

MCXAI records one primary intent, merged query variants and evidence requirements before a route becomes indexable.

Read the evaluation methodology

Inventory routes and query variants together

Normalize trailing slashes and route aliases.

Include planned pages before they are published.

Attach every variant to a candidate canonical route.

Flag a query assigned to more than one candidate.

Check the source against the result

convert JSON to CSV · JSON array to spreadsheet · flatten JSON

One /tools/json-to-csv page with a working converter, a nested-path example and all three phrases recorded as merged query variants.

The wording differs, but each query starts with JSON records and expects a flat spreadsheet-ready file, so three pages would repeat the same task and proof.