Checked against the current site data and kept only when the claim is stable enough to use in tools.
Use for code rewards, calculator thresholds, or page claims that should be safe for a player decision.
Wizard Alchemy updates and source log
Track how this site handles Wizard Alchemy data before it becomes a guide recommendation, calculator assumption, or long-tail page.
Codes, race passives, potion thresholds, material drops, and boss routes can change or conflict across public guides. This log keeps uncertainty visible so new pages do not publish unverified values as final facts.
1 Verified items
11 Tracked items
6 Watchlist items
2 Conflict items
Labels
How to read data confidence labels
These labels are not decoration. They decide whether a claim can be used in a calculator, written as a guide rule, or kept only as a watchlist note.
Useful data that appears in our pages, but still needs rechecking after major game updates.
Use for race odds, potion thresholds, material roles, and farming route advice.
A searched topic or reported claim that is worth monitoring before becoming a firm guide recommendation.
Use for new codes, newly reported drops, new bosses, or update rumors.
Sources disagree or the exact value is not safe enough to publish as a final fact.
Use when a reward, drop chance, passive value, or unlock path needs a visible warning.
Log
Current update and source notes
This log explains the current site assumptions and what needs to be rechecked before new claims are promoted.
Updated Trello and broom pages from current competitor patterns
PUBLIC_API keyword-site and browser-loaded HTML checks showed Trello, broom, and item-location pages winning with direct answers, tables, status wording, controls, locations, and FAQ sections. The Trello page now labels the discovered Trello board as reported instead of ignoring it, and the broom page exposes quick facts plus a reported location/stat table.
Verify the Trello board from Roblox, Discord, or the creator group, then confirm Apprentice Broom and Lava Broom prices, locations, and acceleration values in-game.Optimized broom, Dark Shard, and Trello pages from new GSC signals
The June 1 GSC export showed broom impressions with no clicks, Dark Shard queries ranking around the first page with low CTR, and Trello impressions with a weak click-through rate. The affected pages now answer exact search wording earlier in the page.
Watch CTR for /en/brooms/, /en/shards/, and /en/trello/ before splitting any separate Dark Shard or magical broom page.Added a conservative boss hub from boss keyword signals
PUBLIC_API related-keyword checks showed new demand around Wizard Alchemy new boss, bosses, boss dwarf, and World 2 boss searches. The new hub targets the prep intent while keeping exact new boss names, drops, timers, and mechanics out of the page until verified.
Watch GSC for /en/bosses/ impressions and only add full new-boss pages after current-version sources confirm exact mechanics.Separated all-spells guide intent from the best-spells blog
GSC showed impressions split between the spells page and the all-spells blog. The main spells page now targets all spells list, best spells, dark spells, and requirements, while the blog title is framed as an explanation of what to craft first.
Watch whether spell queries consolidate toward /en/spells/ before adding any narrower dark-spells page.Strengthened the stats guide from new GSC impressions
The stats guide started receiving impressions around best stats, stat guide, and what stats to upgrade. SimilarWeb related-keyword data also showed demand around what stats to upgrade and Wizard Alchemy stats, so the page now opens with clearer stats-search intent before the decision map.
Watch whether stats-guide CTR improves before creating any narrower best-stats page.Added a dedicated shards guide from GSC and SimilarWeb signals
GSC showed repeated shard queries and SimilarWeb related-keyword data showed demand around how to get shards, shards in Wizard Alchemy, and Dark Shard. The new page uses code rewards, tracked material roles, and route guidance without publishing unverified drop rates.
Watch whether shard impressions split cleanly from materials and potion-calculator intent, then expand only after stable query data or in-game verification.Added low-competition leveling and stats guides
SimilarWeb related-keyword checks showed edge demand around what stats to upgrade and fastest way to level up. The new pages answer these intents with conservative route, upgrade, and material-planning advice instead of unverified XP or stat formulas.
Watch Search Console impressions for stats-guide and leveling-guide, then expand only if queries separate from beginner and farming intent.Rechecked Wizard Alchemy codes against current competitors
The codes page was refreshed after checking current public code trackers and the Roblox game page. No new code was found; DELAY and the old RELEASE/WIZARD launch codes keep visible source-conflict notes.
Run an in-game redeem test for DELAY, RELEASE, and WIZARD before changing the final active or expired status.Adjusted page titles and sections from GSC query data
Homepage, Trello, spells, materials, and the all-spells blog were adjusted around queries that already showed impressions: Wizard Alchemy wiki, Trello, spells, shards, Dark Shard, and Copper Earring.
Request indexing for the updated pages and compare CTR after Google refreshes titles and snippets.Refreshed active and expired Wizard Alchemy codes
The codes page was updated from current public code tracker coverage after New Mainland-related updates, with old launch codes moved to expired instead of leaving stale rewards active.
Verify each active code in-game and move any failed code to expired immediately.Added New Mainland, enchantments, and chest route guides
Competitor pages began targeting New Mainland, wand rolls, and chest locations. These pages use route planning and verification notes instead of copying unconfirmed exact locations.
Confirm exact New Mainland access, chest spots, enchantment names, and broom unlock wording in-game before adding database tables.Added a potion recipes and thresholds page
The new potions page targets recipe and potion search intent with tracked Magic gates, element labels, calculator links, and a visible data note.
Recheck potion names, thresholds, and exact recipe behavior after major game updates.Added a safe selling guide
The new how-to-sell guide answers sell-intent searches without inventing an exact NPC or location.
Verify the current sell prompt, NPC, or shop location in-game before adding a step-by-step location claim.Added reported broom prices, locations, and stats
The broom guide now answers how-to-get queries with competitor-reported Apprentice Broom and Lava Broom data while keeping an in-game verification warning visible.
Confirm broom prices, locations, acceleration values, and New Mainland unlock wording in-game.Added Furnace Core and Copper Earring long-tail guides
The new material pages answer high-intent search questions with conservative route, use, and save advice instead of unverified drop rates.
Recheck exact drop sources and rates before adding database-style enemy tables.Added Source Log and data confidence labels
The site now explains how verified, tracked, watchlist, and conflict claims should be handled before they appear in player-facing guides.
Apply the same labels to future code, material, spell, and route updates.Spell page uses conservative potion threshold data
The spells page keeps Magic requirements and race-fit language as planning guidance instead of exact passive-stat claims.
Recheck potion names, Magic gates, and race compatibility after each major update.Race page focuses on keep-or-reroll decisions
Race odds and role notes are useful for reroll planning, but exact passive text can change after balance patches.
Confirm exact passive wording before adding stronger database-style claims.Material-specific long-tail pages are planned
Furnace Core and Copper Earring have strong search intent, but exact drops and rates should not be expanded until checked.
Build individual material pages only with cautious source notes or verified in-game evidence.Code rewards should keep visible notes when sources disagree
Some public guide pages can disagree on rewards or active status. Conflicting code data should stay labeled instead of being silently merged.
Add per-code confidence fields if new code conflicts appear. Watchlist
Next pages and checks to prioritize
These topics have search value, but they should be handled with clear verification notes before becoming database-style pages.
High New boss and World 2 boss data
PUBLIC_API shows rising boss-related demand, but exact boss names, locations, drops, timers, HP values, and mechanics are not verified on this site.
Keep the boss hub prep-focused until reliable current-game sources or in-game checks confirm the exact data. Medium Wings of Tree God and owl statue searches
GSC has started showing low-volume queries for Wings of Tree God, owl statue, owls, and Spirit of Nature, but SimilarWeb does not show stable keyword-site data yet.
Monitor for 2-3 more GSC exports and avoid publishing exact item or quest claims until reliable source data appears. High Shard drop sources
Search demand exists for how to get shards, but exact route drops and rates are not verified on this site.
Keep the shards page conservative until current-version in-game evidence confirms exact sources, drop rates, or NPC wording. High Leveling and stat formulas
Search demand exists for leveling speed and stat upgrades, but exact XP values and stat formulas are not verified on this site.
Keep pages decision-based until in-game screenshots or reliable current-version data confirm exact numbers. High New Mainland route data
Competitors are publishing New Mainland, brooms, enchantments, and chest location pages, but exact route claims still need in-game confirmation.
Verify access wording, chest landmarks, enchantment names, and travel unlocks before publishing exact coordinates or final best lists. High Selling location
Search demand exists for how to sell, but the exact current NPC or UI path is not confirmed on this site.
Confirm the sell prompt in the live game before publishing exact location wording. High Furnace Core guide
The first conservative guide is live, but exact drop sources still need confirmation.
Recheck source wording and add enemy-specific data only after reliable verification. High Copper Earring guide
The first conservative guide is live for potion planning and farming route queries.
Confirm singular/plural naming, drop sources, and exact rates before expanding the page. Medium Potion planner improvements
Players benefit from next-target and short-by-Magic feedback.
Add material filtering and next threshold feedback to the calculator. Medium Code conflict labels
Code pages can change quickly and copied lists often drift.
Store confidence status with each code when a conflict is found. Decision rules
What gets published as a fact?
Use cautious language first
New material drops, exact rates, and passive values stay conservative until checked.
Separate planning from database claims
A route can be useful even when exact drop rates are not ready for publication.
Keep conflicts visible
If sources disagree, the page should explain the conflict instead of hiding it.
Link tools to checked assumptions
Calculators should use the most stable values and point players to recheck notes.
FAQ
Source log FAQ
Why does Wizard Alchemy Tools use source labels?
Wizard Alchemy changes quickly, and copied guide data can drift. Source labels make it clear whether a claim is verified, tracked, on the watchlist, or conflicting.
Does tracked mean confirmed forever?
No. Tracked means the data is useful enough for the current site, but it should be rechecked after major game updates or balance changes.
When do you use a conflict label?
A conflict label is used when sources disagree about a code reward, drop value, passive effect, unlock path, or other player-facing detail.
What pages should be added next?
The current watchlist prioritizes Furnace Core, Copper Earring, potion planner improvements, and code conflict labels.