bing-duplicate-content-fix

Bing Duplicate Content Fix

Use Bing Webmaster, public-page audits, and a connected WordPress tool as one guarded workflow. Treat body similarity as evidence, not a deletion decision. Detect search-intent overlap even when the wording is different.

Read references/decision-rules.md before classifying pages or choosing a fix.

Required workflow

1. Establish the exact inventory

• Resolve the canonical URLs in scope.
• For a WordPress category, use category membership or the category ID as the authority. Do not treat a broad text search as complete membership.
• Separate languages and translated equivalents. A translation is not a duplicate merely because it conveys the same information.
• Record failed, blocked, redirected, non-indexable, and canonicalized URLs.
• For more than 30 URLs, divide the inventory into coherent topic groups. Include likely cross-group competitors in both relevant checks.

2. Collect duplication and search evidence

Run aeo_internal_duplicate_check on each URL group:

• Use 0.82 first to find strong body duplication.
• Use 0.50 as a second review pass for heavy templates and partial reuse.
• Do not assume a pair below 0.50 is safe. Intent cannibalization can exist with very low body similarity.

For every plausible competing pair:

• Compare the SEO title, H1, introduction, headings, tables, FAQs, conclusion, schema, and internal-link anchors.
• Identify each page's primary user question in one sentence.
• Use bing_get_page_query_stats or available GSC query-by-page data to see whether the same queries surface both URLs.
• Use seo_scan_page and aeo_audit_page to check HTTP status, canonical, robots, H1s, metadata, structured data, freshness, internal links, extractability, and intent coverage.
• Read the latest stored WordPress body and SEO fields before proposing any edit.
• Treat cached public HTML and authenticated WordPress content as different evidence. State when the public cache is stale or Cloudflare blocks verification.