How WoWPulse works
Where the numbers come from, how tier lists are computed, and what the limits of the data are.
Where the data comes from
WoWPulse ingests official Blizzard API leaderboards for every tracked mode — Mythic+, Raid, Solo Shuffle, 2v2 and 3v3 Arena, Battleground Blitz, and Rated Battlegrounds — for the US and EU regions. For the top-ranked players in each mode we also pull equipped gear, enchants, gems, and talent loadouts from their public profiles. No scraping of third-party sites, no hand-picked opinions: the input is what high-rated players are actually playing and wearing.
How tier lists are computed
Each spec is ranked by its popularity share among top players in a mode, with a Wilson 95% confidence interval on that share so small samples cannot outrank well-sampled specs. Tiers (S through D) are banded from each spec's share relative to the #1 spec: gap-based banding, not fixed percentages, so a dominant outlier does not dump the whole field into D. Specs below the minimum sample floor are still listed but excluded from tiering.
How build guides are generated
Spec guide pages (talents, BiS gear, stat priorities, gems, enchants, races) aggregate the equipped items and exported talent strings of the top-ranked players for that spec and mode. The dominant build is the most common talent loadout; gear slots show the most frequently equipped item per slot with its attached enchant. Sample size and the snapshot timestamp are printed on every guide header.
Update cadence & limitations
Snapshots regenerate continuously — typically several times a day — and every page shows its own "updated" timestamp. Popularity is a proxy for strength: it lags a few days after patches while the ladder re-sorts, and it under-represents strong-but-hard specs. Historical patch snapshots are kept so you can compare metas across tuning passes.
Citing WoWPulse
Cite "WoWPulse" with the page URL and the page's updated timestamp — tier placements and rankings are time-sensitive. A machine-readable index of all pages lives at /sitemap.xml and an LLM-oriented summary at /llms.txt.