Overlap Map: Find Similar Pages Before You Rewrite
SEO Slots
| Slot | Value |
|---|---|
| seo_title | Content Overlap Map for Thin Page Audits |
| meta_description | Build a content overlap map to identify duplicate intent, repeated outlines, cannibalization risk, weak differentiation, and consolidation actions. |
| slug | overlap-map |
| primary_query | content overlap map |
| secondary_queries | content overlap map, content overlap map checklist, content overlap map template |
| search_intent | operational checklist |
| canonical_path | /resources/content-thinness-lab/overlap-map/ |
| og_title | Content Overlap Map for Thin Page Audits |
| og_description | Build a content overlap map to identify duplicate intent, repeated outlines, cannibalization risk, weak differentiation, and consolidation actions. |
Search Intent
operational checklist. The article must answer the reader's operational question before any commercial route appears.
Reader Artifact
Reusable checklist, table, or runbook from the article body. This artifact is the reason the article can be saved, cited, or reused by an operator.
Internal Links
- Hub: /resources/content-thinness-lab/
- Related article: /resources/content-thinness-lab/thin-page-symptoms/
- Related article: /resources/content-thinness-lab/rewrite-matrix/
- Related article: /resources/content-thinness-lab/content-briefs/
- Related article: /resources/content-thinness-lab/qa-scoring/
- Tool/service route: /services/diagnostic-sprint/
Structured Data
Recommended schema: Article, BreadcrumbList. Keep BreadcrumbList aligned with /resources/content-thinness-lab/overlap-map/. Do not add Product, Offer, Review, Rating, or FAQPage schema for this wave unless a later approved public page visibly supports it.
CTA Route
Primary route: /services/diagnostic-sprint/.
CTA label: Use the related checklist or diagnostic route.
CTA family: diagnostic_sprint.
Use this route only after the article artifact has clarified the next operational step. Public forms, accounts, and payments are intentionally not part of this resource page.
The CTA stays measured and specific, with no public payment or account route on this page.
Measurement
| Event | Name |
|---|---|
| event_view_article | view_article_content_thinness_lab_overlap_map |
| event_click_artifact | click_artifact_content_thinness_lab_overlap_map |
| event_click_cta | click_cta_content_thinness_lab_overlap_map |
| utm_policy | No UTM on internal links; campaign UTMs only during approved external distribution. |
Public-Preflight NG Items
- Fake client proof, fake metrics, fake awards, or guaranteed outcomes.
- Public account, form, payment, repo, domain, or outreach route before checks pass.
- Unapproved cross-brand, unrelated monetization, or off-topic trust route.
- Unsupported claims about SEO, ranking, revenue, or tool behavior.
- Machine-like slug, broken internal link, missing schema plan, or missing measurement slot.Thinness often hides at the cluster level. One page may look acceptable alone, but when compared with nearby pages, it may repeat the same intent, examples, internal links, and CTA. That overlap makes it difficult for readers and search systems to understand why each page exists.
An overlap map makes the decision explicit before rewriting starts.
When to Build an Overlap Map
Build the map when:
- two or more pages target similar queries;
- multiple pages share the same title pattern;
- the same intro, examples, or CTA appears across a cluster;
- pages alternate rankings for similar terms;
- a rewrite request says "make this better" but cannot explain the page's unique role;
- a content brief was copied across several URLs.
Overlap Map Fields
| Field | Why it matters | Example entry |
|---|---|---|
| URL | Keeps decisions page-specific | /resources/example/topic-a/ |
| Primary query | Reveals intended search job | content audit checklist |
| Reader promise | Shows what the page claims to help with | Audit weak pages before rewrite |
| Unique job | States why this page should exist | Symptom diagnosis only |
| H2 pattern | Reveals outline duplication | Definition, benefits, checklist, CTA |
| Evidence layer | Shows proof, examples, screenshots, or sources | Internal QA table |
| Artifact | Identifies reusable value | Decision table |
| Internal links | Shows cluster route | Hub, rewrite matrix, scorecard |
| CTA | Reveals route fit or mismatch | D01 diagnostic |
| Similarity risk | Low, medium, high, critical | High |
| Recommended action | Keep, merge, differentiate, expand, noindex, retire | Differentiate |
Similarity Scoring
Use a simple 0 to 3 score for each dimension.
| Score | Meaning |
|---|---|
| 0 | No meaningful overlap |
| 1 | Some shared vocabulary, but different reader job |
| 2 | Similar intent or outline; needs differentiation |
| 3 | Same promise, same structure, or same artifact |
Total risk:
| Total score | Risk | Action |
|---|---|---|
| 0-4 | Low | Keep both pages; improve internal links |
| 5-8 | Medium | Differentiate titles, artifacts, and sections |
| 9-12 | High | Choose primary page; merge or rewrite weak sibling |
| 13-18 | Critical | Hold from publish review until consolidation plan is approved |
Example Overlap Map
| Page | Primary query | Unique job | Shared sections | Artifact | CTA | Similarity score | Action |
|---|---|---|---|---|---|---|---|
| Thin page symptoms | thin page symptoms | Diagnose visible weakness | Definitions, checklist | Symptom table | D01 diagnostic | 3 | Keep as triage page |
| Overlap map | content overlap map | Compare similar pages | Definitions, checklist | Similarity map | Worksheet | 4 | Keep as cluster page |
| Rewrite matrix | content rewrite matrix | Choose fix action | Checklist, CTA | Rewrite matrix | Implementation Sprint | 5 | Differentiate with action-owner fields |
| Content briefs | content brief template | Prevent repeat weakness | Checklist, template | Brief template | Worksheet | 6 | Tie to post-map brief creation |
| QA scoring | content QA scorecard | Gate readiness | Checklist, scoring | Scorecard | Content diagnostic | 5 | Keep as final gate |
Action Rules
| Action | Use when | Owner decision required |
|---|---|---|
| Keep | Pages have different reader jobs and artifacts | No, if links and metadata are clean |
| Differentiate | Pages overlap in sections but solve different tasks | Yes, assign unique promise and artifact |
| Merge | Two pages solve the same task and one is clearly stronger | Yes, choose canonical target and redirect plan |
| Expand | Page has unique intent but incomplete evidence or examples | No, if brief and acceptance criteria are clear |
| Noindex | Page is useful for users but not a search landing page | Yes, confirm route and measurement impact |
| Retire | Page has no unique value and no business or user route | Yes, confirm redirect, archive, or removal path |
How to Interpret the Map
Do not reward a page for having more sections. Reward it for owning a clear job. A strong cluster can have several pages about content quality if each page gives the reader a different artifact and next action.
The overlap map should produce a decision, not just a note. Each page should leave the map with one assigned action and one acceptance criterion.
Optional CTA
Use the content thinness worksheet placeholder to map similar URLs before rewriting. For larger clusters, the D01 diagnostic can convert the map into a prioritized fix queue for a content diagnostic review or Implementation Sprint. The local route does not authorize public publishing or external submission.