People first
If a page does not help a user make sense of a postcode or verify a claim, it should not be positioned as a primary entry page.
Editorial policy
How PLZHub decides what to publish
PLZHub uses structured data heavily, but it still has to read like a responsible information product. This policy explains which pages deserve indexing, which pages stay utility-only, and why sponsored placements remain separate from the informational layer.
Manual review
Page templates, trust sections, article content, and indexation choices are manually reviewed before release.
Correction workflow
Reported issues are checked against the cited source, corrected in code or content, and then republished with updated metadata.
What is manual and what is generated
Core postcode metrics are rendered from structured data. Trust pages, articles, content rules, source notes, and page-priority decisions are written and maintained manually.
We do not treat every possible route as a search target. Some routes exist because they help users navigate, not because they should be indexed.
Review standard for indexable pages
Indexable pages should explain the source of the data, the main limitation of the page, and the next official place a user should verify the claim. They should also make sense without ads and without requiring a user to click several other pages first.
- Clear source attribution
- Meaningful explanatory copy
- Useful internal links to deeper context
- No misleading claims of official status
Corrections, removals, and monetization
If a route is mainly navigational, repetitive, or too thin to stand on its own, it should remain browseable but non-indexable. That matters especially for machine-scaled location views that add little beyond a label and a map.
Sponsored placements stay visually separate from the main content. Ads should never decide which pages are indexed or how facts are phrased.