How to find duplicate search intent before publishing
Compare reader, question, decision, and answer across existing URLs before drafting. Merge close variants when the same searcher would choose either page for the same task.
Written for an editor planning a new article on a site that already covers related SEO, product, or industry questions.
Key facts
- Shared words do not prove duplicate intent; shared reader decisions provide the stronger signal.
- The opening answer and section coverage reveal overlap that titles can hide.
- A new URL needs a distinct promise, evidence set, and internal-link role.
A useful rule: make each important claim understandable and verifiable without requiring the reader to reconstruct your meaning from the rest of the page.
The direct answer
Write the proposed article's reader, primary question, decision, and promised result in four lines. Search the existing content inventory for pages that match three or four of those fields. Compare their openings and headings, not their keywords alone. Consolidate the idea into the strongest existing page when the same reader would get the same decision support from both URLs; publish a new page only when it has a distinct job and evidence set. The finished work should let a reader or reviewer identify the subject, the intended result, the evidence behind the recommendation, and the next action without reconstructing your reasoning. Keep material conditions in the same passage as the claim they limit. Use the canonical public page as the source of truth, since search engines and answer systems retrieve pages rather than private briefs. Google describes useful, reliable, people-first content and ordinary search eligibility as the foundation for both search results and its AI features. No heading pattern or schema type can compensate for a page that gives a vague answer, hides its evidence, or serves a different intent from its title. Complete the task for one named reader first, then check how the result appears to crawlers and extraction tools.
- Shared words do not prove duplicate intent; shared reader decisions provide the stronger signal.
- The opening answer and section coverage reveal overlap that titles can hide.
- A new URL needs a distinct promise, evidence set, and internal-link role.
Prepare the page and evidence before editing
Export the public article catalog with slug, title, primary question, category, and related links. Add a one-sentence reader decision for each likely neighbour. Search the site and the content files for the main entity and close wording used in the proposed brief. Save a baseline before you change anything: the public URL, response status, canonical, visible title, main heading, opening answer, source links, and the date you checked them. Record the target question in the reader's words and write one sentence describing the decision the page supports. This baseline prevents a common measurement error where several edits ship together and nobody can tell which one improved the result. It also gives editors a compact source ledger. A reviewer can compare each material statement with the cited page, its jurisdiction or product version, and its checked date. If the task affects a generated template, inspect several representative URLs rather than assuming one record proves the template works for every content shape.
- Write the new idea as one question with one named reader.
- Collect the five closest existing titles and read their full opening summaries.
- Mark the action each existing page asks the reader to take next.
Complete the process in five controlled steps
Work through the five steps in order and keep one output from each step. The order protects you from polishing copy while a crawl, canonical, intent, or evidence problem still blocks the page. Each output should be small enough for another person to verify from the public URL. Use plain labels and stable entity names throughout the page. When a changing fact controls the answer, cite the primary source beside that fact and include the relevant date or version. After each step, compare the output with the primary question. Remove any section that serves a different reader decision, and link to a separate guide when the adjacent task deserves its own page. This creates a focused answer instead of a broad page assembled from loosely related keywords.
- 1. Define the job: State the reader, trigger, question, decision, and useful output without using a keyword list. Evidence of completion: The brief fits in five specific lines.
- 2. Find neighbours: Search titles, questions, headings, and body copy for the same entity and problem. Evidence of completion: The comparison includes every plausible internal competitor.
- 3. Compare coverage: Place each page's direct answer, major sections, examples, and sources in adjacent columns. Evidence of completion: The team can see where two pages solve the same task.
- 4. Choose a home: Expand the stronger page, narrow the new brief, or create a separate page with a different decision. Evidence of completion: One canonical URL owns each reader job.
- 5. Repair links: Update hub links and related guides so their anchor text points readers to the chosen answer. Evidence of completion: Navigation reinforces the final topic map without dead or competing routes.
A worked example
An editor proposes “How to fix a page with no traffic” while the site already publishes “Why an indexed page can have zero Google impressions.” The broad draft targets the same new-site owner, repeats the same eligibility and intent checks, and ends at the same SEO audit tool. It adds no separate dataset or decision. The editor folds the useful traffic-diagnosis example into the existing article and reserves a new URL for “How to improve an article with impressions but no clicks,” which serves a different observed state and a different set of fixes. Treat the example as a model of the reasoning, not as a universal benchmark. The useful part is the chain from question to evidence to action. Preserve the exact entity names, scope, and conditions that a reader would need if an answer engine quoted the passage outside the page. If a number comes from a report, state the reporting window. If a result comes from a test, state the URL type, device or crawler, and date. A compact example earns its space when it helps the reader make the same decision on another page. Remove invented precision, anonymous authority, and conclusions that reach beyond the recorded evidence.
- The performance state can separate two articles that share an entity.
- The next action exposes overlap when titles use different words.
- Consolidation preserves links and gives the reader one stronger answer.
Avoid the mistakes that weaken the result
Teams often rely on keyword similarity scores, which miss conceptual overlap and flag harmless shared terminology. Read the pages as a user choosing where to click. Fix the first mistake that changes eligibility or meaning before editing smaller presentation details. Keep source boundaries visible: one citation should support the nearby claim, while a separate claim should receive its own source. Do not repeat the target phrase to manufacture relevance. Search systems can use titles, headings, visible text, links, structured data, and other signals, so those elements should agree on the subject without copying one sentence across the page. Check the public result after deployment because a correct content record can still produce the wrong page through caching, layout inheritance, JavaScript failure, or a stale build.
- Publishing singular and plural versions creates two weak destinations. Correction: Choose one natural title and cover the close wording inside it.
- Changing only the audience label leaves the same decision and answer. Correction: Require a different constraint, workflow, or outcome for a new page.
- Deleting an older URL discards its history and links. Correction: Merge useful material and redirect only when a precise replacement exists.
Verify the result and choose the next action
Crawl the published inventory and confirm that each primary question maps to one canonical URL. Review Search Console page-query pairs for signs that two internal pages alternate for the same narrow query group, then inspect the content before declaring cannibalization. Use a fixed observation window and compare like with like. Record the query set, country, device, page version, and publication or change date. Search impressions can show discovery and query matching; clicks and useful sessions show whether the result attracted the intended reader. Observed AI citations add a separate retrieval signal, but a citation count does not prove traffic or revenue. Review the cited passage when you can and check whether the answer preserved its subject, scope, conditions, and source. Keep the page stable long enough to collect evidence unless you find a factual error, broken route, security problem, or misleading claim. The next edit should respond to the strongest observed failure instead of a generic scoring recommendation.
- Flag exact duplicate primary questions and near-identical opening answers.
- Review competing URLs for the same query, country, and date range.
- Track consolidation effects on the surviving URL rather than total page count.
Put it to work
Find the highest-impact fix on your site.
Compare question intent and choose a single destination before creating another URL.
Map each query to one pageSources
- 1.Google Search Central: Creating helpful, reliable, people-first contentChecked 2026-07-26
- 2.Google Search Central: What canonicalization meansChecked 2026-07-26
- 3.Google Search Central: SEO Starter GuideChecked 2026-07-26