Exact duplication and semantic overlap: consolidated audit result
Audit executive summary
The consolidated diagnosis points to a positive scenario:
- exact duplication of titles: not found
- semantic overlap: found in a few blocks
- a good part of the perceived repetitions are part of intentional sets
- some groups deserve angle consolidation, not automatic exclusion
In other words: the backlog is more organized than it seemed.
1. Exact duplication of titles
Result
Not found.
This means that there are no literally repeated titles within the audited set.
Editorial implication
The problem is not in the same title. When it appears, it is in:
- very close theme
- similar promise
- risk of redundant content if the angle is not well differentiated
2. Semantic overlap
Result
Found in a few blocks and generally controllable.
Most cases can be maintained if there are:
- different angle
- different search intent
- different player stage
- different usage context
Practical conclusion
No need to cut in bulk. It is better to refine the positioning of some titles.
3. Intentional series that do not constitute duplicity
Three families were considered healthy and purposeful:
“Everything you need to know”
Works as a class or theme post-pillar.
“What no one tells you”
It works as a post for real expectations, friction and retention.
“Common mistakes”
It works as a practical correction post and quick gain.
These series can coexist because they fulfill different editorial roles.
4. Consolidation point 1: Skinning + Leatherworking
Diagnosis
There is strong thematic proximity, but no mandatory need for exclusion.
Recommended direction
Maintain:
- a title for beginners
- another title focusing on gold/endgame/optimization
Editorial rule
If both titles stay, each one needs to have:
- different promise
- different reader profile
- different context of use
5. Consolidation point 2: weekly checklist
Diagnosis
The series works very well when segmented by profile.
Recommended direction
Maintain:
- checklist for casual
- raid checklist
- checklist by role or context when it makes sense
Avoid:
- extra generic variants that just repeat the same structure with a different name
Editorial rule
Checklist needs to be:
- by profile
- by function
- or by phase Never just “another checklist” without a clear outline.
How to use this audit in practice
Keep
- intentional series
- post families with clear function
- comparisons with different angles
Adjust
- titles very close without explicit differentiation
- blocks in which the reader may not understand the difference just by name
Avoid
- create extra generic variants
- duplicate search intent just by changing the order of words
- consolidate too early what can still work by cutting
Post-audit editorial checklist
- [ ] Is there a title literally the same?
- [ ] Does search intent really change?
- [ ] Is the angle of the post clear in the title?
- [ ] Is the series intentional or has it become automatic repetition?
- [ ] does this new content expand coverage or just take up space?
Minimum recommendation
The consolidated result of the audit is:
- there is no relevant exact duplication
- semantic overlap exists at few points
- series such as “Everything you need to know”, “What no one tells you” and “Common mistakes” are still valid
- priority adjustments are angle, not rough cut
The audit shows that the backlog is not bloated with copy. It just needs some positioning refinements to become even stronger.
Posts Recomendados
Weekly checklist by player profile
Weekly checklist by player profile: WotLK progress improves when the week has structure. See routines for casual, raid and PvP, no endless spreadsheet.
Magtheridon: the pit lord of Hellfire Citadel
Who is Magtheridon: the pit lord who ruled Outland, lost the Black Temple to Illidan and became the blood source for fel orcs in Hellfire Citadel.
Saurfang and Dranosh: father and son of the Horde
Varok and Dranosh Saurfang: the son hidden in Nagrand, his death at the Wrathgate, the Deathbringer in ICC and the father who takes him home. Full arc.
Azeroth Legacy under construction: where we are
Where Azeroth Legacy stands: a WotLK 3.3.5a server in testing, a community being built and no launch date yet. See what exists and how to follow along.