Disclosing AI does not get tracks pulled. Farm-shaped metadata does. The 14 fields we check before upload, DDEX AI credit mapping and spam-filter patterns.
Honest AI disclosure has not cost us a single stream. Bad metadata has cost us releases. Since 16 April 2026 Spotify has shown AI credits in the song-info panel whenever a distributor passes the DDEX AI disclosure field, and DistroKid was the first partner wired to it. Spotify's stated position since September 2025 is that disclosed AI involvement is not penalised or down-ranked. In the same breath it reported removing more than 75 million spam tracks in a year through a filter that targets mass uploads, duplicated titles, artificially short tracks and SEO stuffing in metadata. Two systems, two outcomes, and the thing that decides which one you meet is the form you fill in before you press upload.
Short answer: treat release metadata as part of the product, not paperwork. Fourteen fields decide whether a track matches to its writers, clears distributor AI declarations, survives spam filters and gets paid on every store that still pays. The checklist below is the gate every release passes in the catalogues we run. Build it around one track that once failed, and you will never skip it again.
The two-system map
| System | What it reads | What it does |
|---|---|---|
| Spotify AI Credits (via DDEX) | Per-component AI disclosure passed by your distributor | Shows credits on the track. No ranking penalty. |
| Spotify spam filter | Upload volume, title duplication, track length, metadata stuffing | Stops recommending tracks and uploaders that match farm patterns |
| Spotify AI Persona review | Artist profile identity | Badge plus exclusion from recommendations by default |
| Distributor AI declaration (DistroKid, TuneCore, others) | Your answers at upload, sometimes including the generator used | False declarations are a contract breach; Believe and TuneCore block tracks from unlicensed generators |
| TIDAL detection | Audio analysis via a detection partner | Wholly AI-generated tracks earn no royalties since 15 July 2026 |
| Deezer fraud detection | Stream patterns | Fraudulent streams removed from the royalty pool |
Read the left column again. Only one of those six systems cares whether you used AI. The other five care whether you are honest, whether you are a person, and whether your upload behaviour looks like a farm. Metadata is how you answer all three before anyone asks.
The 14-field pre-upload gate
- Primary artist name matches the profile exactly, including case and diacritics. Variants create duplicate profiles, and duplicate profiles look like a farm.
- Featured artists listed as separate credits, never baked into the title with "feat." in brackets.
- Title is a title. No keywords, no "(Lofi Chill Beats to Study)", no version tags unless it is a version. Title stuffing is named in Spotify's spam criteria.
- Version field used for edits, instrumentals and remixes, so the title stays clean and the version is machine-readable.
- ISRC assigned by the distributor per recording and copied into your works sheet the same day.
- ISWC and writer splits for the composition, registered with your performing rights society. The distributor does not do this for you; see the two royalty pipes.
- Writer and composer credits as real names with roles: lyricist, composer, producer. "Various" and blank fields are how income disappears into the unmatched pool.
- Performer credits including the vocalist, and if the vocal is a disclosed clone of your voice, you.
- AI disclosure per component: vocals, instrumentation, lyrics, post-production. This is the field that becomes the Spotify AI credit. Tick what is true. Do not tick "fully AI-generated" for a track you wrote and sang over; that is the TIDAL zero-royalty category.
- Generator disclosure where the distributor asks. Since April 2026, Believe and TuneCore block tracks from generators they treat as unlicensed and have since opened distribution to tracks from Suno's new industry partner model while older-model tracks stay blocked. Record the model version in your provenance file so you can answer precisely.
- Language and explicit flags correct per track. Wrong language tags break editorial placement and lyric matching; wrong explicit flags get tracks pulled.
- Genre and sub-genre chosen from the taxonomy, not invented. Two levels is enough; five genres on one track is a stuffing pattern.
- Artwork that is not a photoreal generated face presented as the artist, carries no text that duplicates the title, and meets the store's size rules. Faces are the AI Persona trigger covered in the identity stack.
- Release date and cadence that a human could plausibly sustain. One account releasing daily is the shape in UMG's complaint against DistroKid, which cites 4,562 tracks from a single "Lofi Chill" act in twelve months.
Comments · 0
Beta: comments are stored locally on your device and not visible to other readers.
No comments yet. Be the first to share your thoughts.