Data & Methodology
This page explains where PlaylistMap's data comes from, how often it updates, what our labels mean, and how the free integrity checker scores playlists. If you're a curator, the claim / update / removal form is at the bottom.
Where the data comes from
PlaylistMap indexes publicly available Spotify playlist data — playlist names, follower counts, track counts, genres and last-update dates — through Spotify's public interfaces. Our crawler revisits tracked playlists continuously and the public directory recomputes its statistics every night. We do not collect private listener data, and we never display personal contact information publicly anywhere on this site.
What our labels mean
How the integrity checker scores playlists
The free playlist checker (model v1.0) blends six public signals into a 0–100 score: engagement coherence (30%), curator activity (20%), artist diversity (15%), addition pattern (15%), description check (10%) and size sanity (10%). Score bands: 75+ looking healthy · 55–74 mostly healthy · 35–54 proceed with caution · below 35 high-risk signals.
Limitations, stated plainly: the checker reads public Spotify data only. It cannot see play counts, listener geography or follower history, so its output is a risk assessment, never an accusation. Legitimate playlists that were bulk-imported or rebuilt can score low; sophisticated manipulation can score high. When a playlist exposes too little data (under 20 readable tracks or under 1,000 followers) we lower our stated confidence rather than guess. Results are cached for 24 hours.
Corrections
If you believe any figure on this site is wrong, tell us at support@playlistmap.com — we'll investigate and correct verified errors, typically within a week.
Curators: claim, update or remove your listing
PlaylistMap lists playlists using publicly available information. If you curate a listed playlist you can claim your profile (and get pitches that match your rules), correct outdated details, or have your contact route removed from the members-only database entirely. We process these requests within 30 days, usually much faster.