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.
Farm patterns to avoid on purpose
Near-duplicate titles across releases ("Rain Lofi 1", "Rain Lofi 2").
Tracks under about ninety seconds released in bulk. Short filler is an explicit spam signal.
Album art templates with only the number changed.
Ten aliases from one account uploading the same day.
Keyword strings in the title, artist name or album name.
Re-uploading an existing track under a new ISRC to reset its history.
Releasing more than you could describe from memory. If you cannot say what a track is, a reviewer cannot either.
None of these require AI to trigger a filter. All of them are more likely when a generator makes volume free.
Build the gate around one failed track
Checklists get skipped when they are abstract. Pick the release that went wrong for you: the one that matched to nobody, the one a store rejected, the one that sat outside recommendations for a reason you could not name. Write its metadata as it was next to how it should have been. That side-by-side is the training document for the gate; keep it at the top of the sheet. Ours is a devotional track whose lyricist credit read "Various" for eleven months while the performance income went to the unmatched pool.
Tooling for the gate
The gate is a spreadsheet and a folder, and it works best when the style sheet, the credits and the identifiers are the same document family. Our free Suno Prompt Builder produces the structured style sheet that becomes the first page of the provenance file, and the JSON to CSV converter flattens distributor statement exports into the works sheet for the quarterly audit. The Regional Indian Music Pack and EDM Festival Bangers packs ship the credits and identifier templates pre-filled for the common lyricist-plus-composer case.
The cadence rule
Volume was the 2024 strategy, and 2026 priced it out. Deezer sees roughly 90,000 AI tracks a day and strips fraud streams from payouts; Spotify's filter and persona review target the same shape; TIDAL pays wholly generated tracks nothing. A cadence of one or two releases a week, each with full credits, per-component disclosure and a video, survives every one of those systems. The market data behind that rule is in Fully AI music just peaked.
The ninety-second run
A gate nobody runs is decoration. Ours takes about ninety seconds per release because the fields are pre-filled from the provenance folder and the check is a scan, not a form. The order is deliberate: identifiers first, because they are the fields you cannot fix after delivery without a new release; disclosures second, because they are the fields a distributor will hold you to; presentation last, because titles and artwork can be corrected in place.
Open ids.json. Confirm ISRC present, ISWC present or registration queued with a date, writer splits summing to 100.
Open credits.json. Confirm each component (vocals, instrumentation, lyrics, post-production) has a value, the generator and model version are recorded, and the performer line names a human.
Read the title aloud. If it contains a keyword, a bracket or a number that is not part of the name, fix it and move the qualifier into the version field.
Look at the artwork at thumbnail size. If a stranger would assume the person on it is the singer and the person does not exist, change it.
Check the calendar. If this is the third release this week, hold it.
Two of those five will feel unnecessary on a good day. Run them anyway; the release that fails is never the one you expected.
Quick answers
Does disclosing AI use on Spotify hurt streams?
Spotify says disclosed AI involvement is not penalised or down-ranked. The AI credit is informational. Farm-shaped uploads and synthetic artist identities are what get restricted.
Which field becomes the Spotify AI credit?
The per-component AI disclosure your distributor passes through DDEX. DistroKid was the first distributor wired to it in April 2026.
Can a wrong AI declaration get my account closed?
False declarations are treated as a contract breach by distributors, and Believe and TuneCore block tracks from generators they consider unlicensed. Declare accurately and keep the model version in your provenance file.
Why does title formatting matter so much?
Keyword-stuffed and near-duplicate titles are named signals in Spotify's spam criteria. Clean titles plus a version field keep a release out of that pattern.
What is a safe release cadence?
Whatever you can fully credit and describe from memory. For most independent acts that is one or two releases a week, far below the daily cadence cited in the UMG complaint.
Disclaimer: This article describes the release practices we follow and is for informational purposes only. Platform and distributor policies change; verify current terms with your distributor and consult a qualified professional for legal questions.
Fourteen fields, one failed track as the teacher. Every product mentioned is available at wowhow.cloud — pay once, ship forever.
Originally published at wowhow.cloud
Top comments (0)