Release Metadata Is Boring and It Decides Who Hears You
Genre tags, credits, ISRCs and release dates are unglamorous fields that determine placement and payment.
The least interesting part of releasing music is the form you fill in at the distributor, and it has a disproportionate effect on what happens next.
You can listen to our full playlist which contains the artist's music, and know more about the artist's work by scrolling down the page.

PLAYLIST
Unglamorous Fields That Decide Outcomes
Release metadata — genre tags, credits, identifiers, dates and contributor information — is the least interesting part of putting out a record and one of the most consequential.
These fields determine which playlists a track is eligible for, how recommendation systems classify it, whether royalties reach the right people, and whether the release can be identified at all across the systems that handle it.
Errors here are not cosmetic. They cause money to go missing and records to be invisible to the systems that would otherwise surface them.
Identifiers Are How Anything Is Tracked
Every recording needs a unique identifier, and every release needs a product identifier, because these are what all downstream systems key on.
An ISRC identifies a specific recording and follows it across every platform, every compilation and every future use. If the same recording is issued twice with different identifiers, its performance data is split and its royalties are tracked separately.
Conversely, reusing an identifier for a different recording merges two things that should be distinct. Both errors are common, both are difficult to unwind afterwards, and both directly affect payment.
Version identifiers matter as much as track identifiers. A radio edit, an extended mix and an instrumental are separate recordings needing separate codes, and conflating them merges their performance data permanently.

Credits Determine Who Gets Paid
Contributor metadata is where the largest sums go astray, because performance and mechanical royalties are distributed on the basis of registered credits.
Writers, publishers, performers and producers all need to be listed accurately and consistently, and the splits need to match what was actually agreed. A missing writer does not receive their share, and recovering it later requires the cooperation of everyone else.
Consistency of name spelling matters more than it should. The same person credited three different ways across a catalogue can end up as three entities in a royalty system, none of which receives the full amount.
Genre Tags Drive Placement
Genre and mood metadata feed directly into playlist eligibility and algorithmic classification, and they are frequently filled in carelessly.
A track tagged to a broad category competes with everything in it, while a more precise tag places it among a smaller, better-matched set. Getting this wrong can exclude a record from the editorial contexts where it would have performed.
Mislabelled genre also confuses recommendation, since the system uses it as an initial prior before behavioural data accumulates. A wrong prior means the first listeners are the wrong listeners, and the early signals are correspondingly poor.
Featured-artist fields are read by recommendation systems as a relationship signal, so omitting a guest costs both artists the algorithmic adjacency the collaboration was partly intended to create.

Dates and Territories Have Real Effects
Release date and territory metadata determine chart eligibility, editorial consideration windows and where the record can legally be sold.
A date entered incorrectly can push a release outside a chart week or cause it to appear before a coordinated campaign is ready. Territory restrictions applied by mistake make a record unavailable in markets where it was expected to sell.
These are simple fields with disproportionate consequences, and they are usually entered once, quickly, by whoever is operating the distribution tool.
Fix It Before Release, Not After
The general rule is that metadata is far easier to get right initially than to correct once a record is live across dozens of services.
Corrections propagate slowly and unevenly, some platforms do not accept them at all for certain fields, and royalty distributions already made on incorrect data are not automatically recalculated.
That makes an hour spent checking these fields before submission one of the highest-return uses of time in the entire release process, and it is almost always the part that gets least attention.
A pre-submission checklist takes ten minutes and catches nearly all of it: identifiers unique, writers and splits agreed in writing, genre specific rather than broad, date and territories correct, contributor names spelled consistently with previous releases.

