Music Metadata Corrections: Edit or Takedown?
Music metadata identifies and describes a release: titles, artist roles, credits, version labels, copyright lines, ISRCs, UPC, dates, territories, and explicit status. Correct a live release through the distributor when the product and recordings remain the same. Use a takedown and new delivery only when the provider or rights problem requires a new product or recording.
Lead visual
Release metadata preflight
Title casing
Check before delivery, not after stores ingest the release.
Featured artist role
Check before delivery, not after stores ingest the release.
ISRC format
Check before delivery, not after stores ingest the release.
P line owner
Check before delivery, not after stores ingest the release.
Explicit tag
Check before delivery, not after stores ingest the release.
Fix before deliver
After delivery, corrections move through store updates, cache delays, and royalty systems that may already have recorded the wrong data.
Release · Metadata
Release data map
Decision
Fix release information before stores, societies, and royalty systems ingest it.
Evidence
Titles, artist roles, ISRCs, UPCs, ownership lines, explicit flags, files, and artwork specs.
Risk
Bad metadata travels into stores and takes longer to correct than it would have taken to preflight.
Good outcome
A release record that is easier to deliver, match, pitch, and pay correctly.
Key takeaways
- Metadata is a field-level record. Put titles, roles, versions, identifiers, dates, and rights data in their proper fields.
- Spotify displays supplier-delivered metadata, so most corrections start with the label or distributor.
- Edit when the product and recordings are unchanged and the provider supports the field.
- Takedown and redelivery are for changes the provider cannot edit, new products or recordings, and unresolved rights problems.
- Track-linking is conditional, not guaranteed. Preserve identifiers and verify the public result after every correction.
Which metadata fields should you verify before delivery?
Verify the release title and version, track titles and versions, primary and featured artist roles, songwriters and other credits, explicit status, language, territories, live and original dates, copyright lines, one UPC for the product, and one correct ISRC for each recording. Store the submitted export beside the final audio and artwork so the delivered record can be reconstructed later.
| What it identifies | Correction question | |
|---|---|---|
| UPC | The release product | Is this still the same product? |
| ISRC | One sound recording | Is the audio still the same recording? |
| Live date | When the product becomes available | Can the supplier update the future date in time? |
| Original release date | Historical first availability | Does the provider expose a separate historical field? |
| Artist role | How a contributor is displayed | Was the person delivered in the correct structured role? |
Should you correct a release or take it down?
Correct it in place when the release and recordings remain the same and the supplier supports the field. Spotify directs artists to the label or distributor for artist name, release title, artwork, dates, track order, territory, explicit tags, roles, and credits because Spotify displays the metadata that supplier sends.
| Try a supplier correction | Confirm whether a new delivery is required | |
|---|---|---|
| Display data | Spelling, credits, roles, artwork, explicit status | Provider rejects or cannot edit the field |
| Product structure | The tracklist and product remain the same | Tracks are added, removed, or reordered |
| Recording | The same recording needs a permitted minor fix | A different mix, edit, performance, or song replaces it |
| Rights | A correctable mandate or territory field | The release lacks authority and must stop being exploited |
| Identifiers | Existing UPC and ISRCs remain valid | The product or recording requires a new identifier |
Provider capability matters. TuneCore currently says adding, deleting, or reordering songs, changing UPCs or ISRCs, and changing its Original Release Date field require a takedown and new product. DistroKid lists a broader set of editable fields and a plan-specific minor Audio Swap. Neither provider's controls are a universal store rule.
A rights takedown is not a metadata experiment
If the release contains unauthorized audio, artwork, composition, performer, or territory rights, stop exploitation and get qualified advice. Do not keep a release live merely to preserve play counts.
How do you submit a clean metadata correction?
Export the current delivery, identify one exact field and replacement value, confirm that the underlying product and recording identity do not change, and submit through the original supplier. Keep the ticket, timestamps, and store acceptance messages. Verify every selected store because updates can arrive on different schedules.
If a new delivery is necessary, preserve the old identifiers and ask which can legitimately be reused. Spotify says track-linking requires the same audio and metadata, including duration, title, and artist. That is an eligibility condition, not a guarantee that streams, playlists, saves, reviews, or links will carry over.
How do you prepare compilation album metadata?
Build the compilation as one product record plus one recording record per track. Keep each track's real primary artists, contributors, ISRC, original release date, rights, and version fields. Apple's current style guide uses Various Artists at album level when five or more primary artists are listed, makes it the only album-level primary artist, and prohibits Various Artists as a track-level artist.
| Album-level record | Track-level record | |
|---|---|---|
| Artist | Actual album primary artist or provider-valid Various Artists rule | Every recording's actual primary and featured artists |
| Date | Date the compilation product was released | First release date of that recording where the provider requests it |
| Identifier | A product UPC supplied or assigned for this compilation | Reuse an ISRC only for the same unchanged recording; never invent or recycle one |
| Rights | Compilation product label, territories, and artwork permissions | Recording, composition, contributor, explicit, and territory data for that track |
Current owner evidence
This metadata pillar recorded 67 impressions at average position 9.66 from June 19 through July 16, 2026. No exact compilation-metadata query appeared, so this product and track boundary consolidates the idea into the established owner.
What does Velveteen's search evidence say?
This metadata pillar received 67 impressions and no clicks in Velveteen's Google Search Console export for June 19 through July 16, 2026, at an average position of 9.66. No exact correction-versus- takedown query appeared. The decision starts with field and identifier ownership, so the metadata pillar is the strongest existing owner. Query absence is not a market-volume estimate.
Where do the correction rules come from?
Frequently asked questions
Can Spotify fix my release metadata directly?+
Usually not. Spotify says it displays the metadata delivered by the label or distributor and cannot manually change fields such as release title, artwork, date, track order, roles, and credits for the artist. Send the correction through the supplier that delivered the release.
When is a metadata edit better than a takedown?+
Use an edit when the release and recordings are still the same and the provider supports the field: a spelling, role, credit, artwork, explicit tag, territory, or similar supplier update. Keeping the product live avoids an unnecessary second delivery and reduces the risk of split listings.
When does a release need to be taken down and re-uploaded?+
When the provider cannot edit the required field, the tracklist or product identity changes, a fundamentally different recording replaces the old one, or the release lacks the necessary rights. Rules vary. TuneCore currently requires a new product for adding, deleting, or reordering songs and for changing UPCs, ISRCs, or its Original Release Date field.
Will a re-upload keep streams and playlists?+
Do not promise it. Spotify says track-linking depends on the old and new versions having the same audio and metadata, including duration, title, and artist name. Check the public play count after delivery. A new or materially changed recording should not be presented as identical just to preserve history.
What should I save before requesting a correction?+
Save the UPC, every ISRC, current store URLs, delivered metadata export, artwork, audio checksums if available, screenshots, release date, territories, and distributor submission receipt. Record the exact before-and-after value and the supplier ticket number so you can verify each store separately.
Get better release strategy in your inbox
Release planning checklists, royalty explainers, and artist strategy notes from Velveteen. No daily noise.
Was this useful? Send a signal or flag a correction.
Keep reading
Related guide
What is an ISRC
What an ISRC code is: the 12-character ID for one recording, why a remix needs a new one, and how to carry it across distributors so you don't split your streams.
Related guide
UPC vs ISRC
UPC vs ISRC, plain: the UPC names the release, the ISRC names each recording, and swapping the two fields is the error that costs you.
Related guide
P line vs C line
The ℗ line covers your master, the © line covers the song and artwork. The format, the right owner, and the mistakes that misroute your royalties.
Related guide
Audio file prep
What audio to deliver, when a released file can be swapped, and where minor technical repair becomes a new creative recording.
Pillar guide
Album artwork guide
The complete artwork workflow: one cross-platform digital master, the rules that trigger rejections, explicit-content notices, AI rights, and separate print files.
Check your metadata before your distributor does
Run your titles, credits, copyright lines, and ISRC and UPC codes through the free checker and catch the rejection-bait errors before you upload. It all runs in your browser.