The Blox Fruits editorial policy requires last verified, game version, source type, reviewed by and report an error fields on every important data page. It also keeps values, tier ratings and demand separate from official facts.
Required page fields
The Blox Fruits editorial policy requires every major entity page to show Last verified, Game version, Source type, Reviewed by and Report an error. The page edit date and data verification date are different fields and should not be merged.
Content states
Content should move through Draft, Fact Check, In-game Verification, Editorial Review, Published, Needs Reverification and Archived. A page can exist in the CMS before it appears in navigation, sitemap or homepage cards.
Corrections
Players should be able to report a wrong fruit price, stale stock entry, broken code, value issue, route mistake or source problem. The correction queue should record page, issue, evidence, status, editor response and resolution date.
Review labels
| Label | When to use it | What readers should assume |
|---|---|---|
| Official | The fact comes from the Roblox page or an official announcement. | Strongest source, but still date-stamped. |
| In-game Verified | An editor checked the fact directly in-game. | Practical evidence tied to a platform and date. |
| Community Confirmed | Multiple reliable community observations agree. | Useful but still weaker than official or direct testing. |
| Editorial Estimate | Used for values, demand, tier placement or subjective recommendations. | Not an official game fact. |
The Blox Fruits editorial policy requires these labels to appear near the data they qualify. A value estimate should not sit beside a fruit price as if both were the same type of fact.
Publishing gate
Before an entity page is indexed, it should have a direct answer, quick facts, how-to-get or use guidance, source notes, internal links and a change-history section. If a record has only a name, slug and one copied table, it belongs in the CMS as unpublished data, not in the public sitemap.
Thin-page prevention
The Blox Fruits editorial policy rejects mass pages that only contain a name and one table. A detail page must include unique explanation, useful advice, source notes, internal links and change history.