Research · Published
Duplicate Topic Screening Routine
A duplicate-topic screen protects the Research library from near-identical titles, slugs, search intent, and reader promises.
On this page
Headline signal
4 screening views: slug, title, intent, promise (Google Search Central: SEO starter guide). Treat this as context for planning, not a guarantee about a particular assistant or operating result.
Analysis and operating context
Methodology: screening compares candidates against the Research and Blog inventories, indexes, sitemap inputs, and candidates already accepted in the current run.
Normalize slugs and titles, then compare the underlying question and reader promise. A new wording is not a new topic when the decision and evidence path are the same.
Reject overlap, stale candidates, unsupported claims, and topics with no useful service or workflow connection. Record the reason so replacements are auditable.
Generate replacements from audience, workflow, pain point, comparison, use-case, and source gaps until the selected target is met.
Sources
- NIST Cybersecurity Framework 2.0
- NIST Digital Identity Guidelines
- CISA Secure Our World
- FTC Data Security Guidance
- Google Search Central: Creating helpful content
- Google Search Central: SEO starter guide
- OWASP Top 10
- ILO: Decent work and the care economy
- World Bank: Digital economy
- Philippine Statistics Authority
- W3C Web Content Accessibility Guidelines
Frequently asked questions
What should a manager verify first?
Verify the work definition, source record, reviewer, access limit, and escalation path before assigning the queue.
What belongs with the internal owner?
Keep final approvals, unusual exceptions, payment decisions, and changes to the control rules with the internal owner.