Blox Strike Sources

Code trackers consistently surface this query; update the existing codes page instead of splitting variants.

Alias spelling for the Roblox title maps to the same active-code intent.

Reverse-order phrasing leads to the same active-code and redemption answer on the primary codes page.

Fresh code discovery is consolidated on the codes page with needs-check labels.

Reverse-order new-code intent maps to the same checked codes route.

NEBULA is a current title/update and reported code signal; the update watch page handles claim boundaries.

Reverse-order NEBULA code intent maps to the same source-watch page.

Roblox metadata confirms the NEBULA title tag, while patch details remain unverified.

Reverse-order update phrasing needs the same checked status notes and update context.

YouTube and public guide wording connect knives to the NEBULA cluster, but item details still need confirmation.

Reverse-order knife query maps to the NEBULA/update source-watch page until named knife details are verified.

Older tracker conflict appears around SUPERSOAKED; keep it in archive/watch context until live-verified.

Reverse-order older-code query belongs in expired/archive context, not the active list.

Newer July 2026 code tracker wording creates a code-intent alias, but it does not need a separate page.

Reverse-order KNICKS query maps to the same reported-code watch list.

Current public tracker wording should be listed on the codes page as needs-check until source confirmation.

Reverse-order long birthday-code variant has the same code lookup intent.

Short birthday alias remains useful as a conflict note against BIRTHDAYBOYMALONI.

Reverse-order short birthday-code query maps to the codes page conflict note.

Conflicting public tracker presence should be handled in the reported-code watch list.

Reverse-order tracker code phrase has no separate page need.

FREEDOM is a current reported-code query; the codes page has visible needs-check coverage.

Reverse-order FREEDOM code intent maps to the reported-code watch table.

Current tracker discovery exposes TRADINGRELEASE as a reported code phrase, but it should stay needs-check on the consolidated codes page.

Reverse-order TRADINGRELEASE code query maps to the reported-code watch list.

Spaced-title alias for TRADINGRELEASE belongs on the codes page rather than a thin code-only route.

Reverse-order spaced-title alias maps to the same needs-check code coverage.

Medal-themed code wording appears as a discovery lead only, so it should remain in reported-code/source-watch context.

Reverse-order Medal code query maps to the consolidated codes page.

Public code-site wording exposes this as a code lookup, but it remains unverified and should stay on the reported-code watch surface.

Reverse-order exact code query belongs on the same codes page.

HELLENA overlaps code and map discovery; codes page covers code status while maps page covers map-name status.

Reverse-order HELLENA code query stays on the codes page to avoid a thin duplicate route.

Existing support route matches typo, expiry, level gate, and stale-server troubleshooting.

Reverse-order troubleshooting phrase maps to the code support route.

Existing redeem route covers the action phrase.

Reverse-order redeem phrase belongs on the same redeem instructions route.

Public guides and YouTube videos frame this as a broad role-first question, so it belongs on the existing tier list.

Alias spelling maps to the same ranking route.

Reverse-order query has no separate content need.

Trading, values, skins, cases, and safe-trade searches form a distinct publishable wiki topic.

Alias spelling belongs on the same exact trading route.

Reverse-order variant is covered by the trading route title and page body.

Value searches should land on a conservative trading page that refuses invented prices.

Reverse-order value searches map to the same trading/value status section.

Skin economy terms fit the trading/status page until item-specific sources support separate pages.

Case terms are relevant to trade/value research but not strong enough for a case-only route.

Reverse-order cases phrase is visibly covered on the consolidated trading route.

RAP/value demand is distinct enough for trading-page coverage, but exact price claims remain blocked.

Reverse-order RAP query maps to the same value-status section.

BS Float appears as a skin database/status surface; route coverage is useful but data ownership and exact values need checks.

Reverse-order BS Float query belongs on the trading/source-watch page.

Skin database intent is publishable as source-watch coverage without copying or inventing item data.

Reverse-order skin database intent maps to the same source-watch section.

Public guide coverage and official skin-economy wording justify this topic without item-level rarity claims.

Reverse-order skin rarity phrase belongs on the consolidated trading and skins source-watch page.

Rare-skin demand is publishable as a source-watch topic, but exact values remain blocked.

Reverse-order rare-skin phrase belongs on the same trading and skins route.

Skin market intent is the same trading/value topic and should not publish item prices without evidence.

Reverse-order skin market phrase belongs on the consolidated trading route.

Trading-update wording is better handled as a trading source-watch term until confirmed as a live code.

Reverse-order trading update phrase maps to trading/status context rather than a new code page.

Trading-release wording overlaps code and feature discovery, so trading status should cover the source context without confirming a reward.

Reverse-order trading-release phrase maps to the trading/source-watch route.

Item-level Stiletto wording needs live or creator-owned evidence before a dedicated skin page.

Reverse-order item-skin phrase should be covered only as a trading watch term for now.

Collection wording is not strong enough for an exact page without source agreement on items and availability.

Reverse-order collection phrase remains a trading/source-watch term until verified.

Searchers need an honest status page because no official Trello board was verified.

Alias spelling maps to the Trello status route.

Reverse-order support-status query uses the same route.

Discord status belongs with official/social source status rather than a thin Discord-only page.

Discord invite/status queries belong on the support-status route with official-link caveats.

Reverse-order Discord server query uses the same source-status route.

Existing wiki hub should clarify fan-site status and source standards.

Reverse-order official-wiki query should land on the wiki hub with fan-site status made clear.

Broad wiki intent should stay on the hub.

Reverse-order wiki phrase maps to the hub.

Weapon names/prices still need live source confirmation before individual weapon pages.

Reverse-order weapon phrasing maps to tier-list and buy-role coverage until exact weapon pages have current game details.

Settings questions support beginner setup guidance rather than a shallow standalone page.

Reverse-order settings query maps to the beginner guide and source-status links.

Official metadata confirms detailed maps and current public discovery exposes map-name demand, but layouts remain unverified.

Reverse-order map phrase maps to the source-watch maps page.

Helena/Hellena appears as a map-name lead, but spelling and layout need stronger source confirmation.

Alias/misspelling variant is covered on the maps source-watch page.

Oasis appears as a map-name lead and should be tracked without inventing callouts.

Dust II-style wording appears in public discovery; publish only as a watch term until confirmed in-game.

Reverse-order Dust II map query stays on the maps source-watch route.

Seaside appears in public discovery; route coverage is useful but layout claims remain blocked.

Reverse-order Seaside map query maps to the same source-watch route.

Map-name and code-name overlap requires a status page rather than separate unverified child routes.

Reverse-order map-code phrase is covered by the maps source-watch explanation.

The current public update cluster is NEBULA, so the update watch route is the best match.

Reverse-order update query maps to the current NEBULA source-watch route.

Group/social discovery supports source monitoring, not a standalone page.

Reverse-order group query belongs on source/status coverage rather than a group-only page.

X/Twitter source demand belongs with creator social and community status checks.

Reverse-order Twitter query maps to the source-status route.

X profile discovery is useful for source status but not enough for a standalone page.

Reverse-order X/social query maps to the same source-status route.

YouTube results are supporting discovery surfaces for updates, guides, and code leads, not an official source page.

Reverse-order YouTube query belongs on the source checklist.