Cover song metadata follows specific conventions that streaming platforms and distributors expect: the track title should match the song being covered (not the original artist’s name), your artist name goes in the artist field only, and any reference to the original performer belongs in a designated ‘cover of’ or version field, never appended directly to the title. Getting this wrong is one of the most common reasons cover submissions get flagged during moderation, and it has nothing to do with licensing eligibility — it’s a formatting problem that’s entirely avoidable.

For a solo artist releasing covers regularly, naming conventions aren’t a bureaucratic detail. They determine whether your release passes moderation on the first attempt, whether streaming platforms display it correctly next to the original, and whether your catalog stays searchable as it grows.

What should the track title actually say?

The track title should be the plain song title, exactly as commonly known — nothing more. If you’re covering «Hallelujah,» the title field should read «Hallelujah.» It should not read «Hallelujah (Leonard Cohen Cover),» «Hallelujah — Acoustic Version by [Your Name],» or «Hallelujah (Originally by Leonard Cohen).» Platforms treat the title field as the song’s actual name, and stuffing it with descriptors or the original artist’s name is one of the most consistent moderation triggers across every major distributor.

If you’ve made a specific arrangement choice worth noting — an acoustic version, a slowed-down version, a different key — that belongs in a subtitle or version field, formatted as «Hallelujah (Acoustic Version).» That’s a legitimate use of parentheses. Naming the original artist inside the title field is not.

Where does the original artist’s name go, if not the title?

The original artist’s name goes in the metadata field specifically designated for it during submission — typically labeled «original artist,» «composer,» or «cover of» — not in the title, and not in your own artist name field. Most distributors, including Globex Music, prompt for this information separately precisely so platforms can display «Hallelujah (originally performed by Leonard Cohen)» as a subtext line under your version, without it cluttering the title itself.

This distinction matters for search behavior too. Listeners searching «Hallelujah cover» find your track through platform search and metadata tagging, not because you wrote «cover» into the title. Titles that over-explain often rank worse in platform search because the algorithm is parsing an unusual string instead of matching a clean, recognized song title.

Should your artist name include the word ‘covers’ or similar?

Generally, no — your artist name should be the same consistent name across every release, cover or original, unless you’ve deliberately built a separate cover-specific project. Appending «(Covers)» to your artist name on every release creates two problems: it fragments your search presence if you ever release original material under a cleaner version of the name, and it reads as amateur to listeners who are used to seeing artist names presented plainly.

The exception is intentional branding — some solo artists run a dedicated cover channel under a name like «Acoustic Sessions by [Name]» as a distinct project from their original-music artist profile. That’s a legitimate strategy, but it should be a deliberate choice made once, not a naming habit applied inconsistently release to release.

What about featuring credits on collaborative covers?

If you recorded the cover with a collaborator, their name belongs in the featured artist field, not stitched into the title with «ft.» or «feat.» unless that’s how you want it displayed on the platform’s canonical title line. Most platforms will auto-format a properly tagged featured artist as «Song Title (feat. Collaborator Name)» in the display title, pulling directly from the metadata field rather than requiring you to type it manually into the title box. Typing it manually into both places creates duplicate or malformed titles that moderators are more likely to reject.

Why does formatting affect moderation speed specifically?

Moderation teams are checking two separate things at once: licensing eligibility for the cover and metadata compliance with platform standards. A well-formatted submission — plain song title, correct original-artist field, consistent artist name — lets a moderator confirm licensing and move on. A submission with the original artist’s name jammed into the title, or a title full of promotional language («BEST Hallelujah Cover 2026!!»), adds a second review layer that slows the whole release down.

Because Globex Music processes cover licensing automatically and reviews submissions quickly, most of the delay a solo artist experiences on a rejected cover comes from fixable metadata issues, not licensing problems. Fixing the title format and resubmitting is usually faster than waiting out a licensing dispute would be, because there typically isn’t one — the issue is the naming, not the rights.

A quick reference for solo artists releasing covers

  • Track title: the plain song name only, with arrangement details (acoustic, live, slowed) in a version subfield if applicable.
  • Artist name: consistent across your entire catalog, not modified per release.
  • Original artist: entered in the dedicated metadata field, never typed into the title.
  • Featured collaborators: entered in the featured artist field, not manually appended to the title text.
  • No promotional language, emojis, or all-caps in either the title or artist name fields.

None of this affects your royalty rate or your licensing cost — a single cover release still runs about $1 through Globex Music with mechanical licensing included, and payouts still start once you cross the $10 threshold on a given platform. What clean naming buys you is speed: fewer rejected submissions, fewer resubmission cycles, and a catalog that stays organized as it grows past ten or twenty cover releases. For a solo artist building a release schedule around covers, that organizational discipline compounds — a catalog with fifty consistently formatted tracks is far easier to track, promote, and license correctly than one with fifty variations on how a title should be written.

Sign up or log in to your dashboard and upload your release now

Latest from the blog

Share This Story, Choose Your Platform!