Current target score
The wiki is now structured as a 90+ quality base for source hygiene, SEO readiness and maintenance transparency. Monetization is lower by design until ad files are installed.
Build A Boat For Treasure wiki quality scorecard
A public-facing quality snapshot for what is strong, what is cautious and what still needs real playtesting.
| Dimension | Score | Reason |
|---|---|---|
| Source hygiene | 9.1/10 | Official/API facts are separated from community leads; no fake working codes. |
| Wiki coverage | 8.7/10 | Core pages cover codes, guides, items, badges, secrets, glitches and mechs. |
| Human maintenance feel | 9.0/10 | Update log, editorial policy, testing notebook and submission templates are visible. |
| SEO readiness | 9.1/10 | Canonical, sitemap, robots, indexed core URLs and question-led pages are in place. |
| Technical launch | 9.0/10 | Apex and www serve Cloudflare Pages; Search Console has verified sitemap success. |
| Monetization readiness | 6.2/10 | Privacy and terms exist, but AdSense files and ad layout are intentionally not active yet. |
What keeps it honest
Unverified codes, hidden-room answers, strongest-item claims and video-only mech builds remain in testing queues instead of confirmed pages.
Next proof needed: real screenshots and test notes are the remaining difference between a polished launch wiki and a mature community reference.