SEO for Musicians: Your Own Name Is the Hard Query

Search advice written for musicians has a strange gap in it. It will tell you to add MusicAlbum markup so Google shows your album art, and it will not tell you that Google's own list of supported structured data features, updated on 15 June 2026, contains twenty-five entries and not one of them is music.

That is not a small correction. It is the difference between an afternoon spent on markup that does something and an afternoon spent on markup that Google has never used to build a search feature.

This article covers the parts of search that a working musician can actually change, with every claim about Google's behaviour quoted from Google's own documentation and the source named. Where a thing cannot be verified, it says so. No one can guarantee a ranking, and nothing here promises a position or a date.

The query you most need to win is your own name

Every other business starts with a category query. A dentist wants "dentist near me". A photographer wants "wedding photographer austin". You are different, and it is the reason generic SEO advice misfires on musicians.

Your highest-intent query is your name. Someone hears a track on a playlist, in a bar, in a friend's car, and types the artist name into a search box. That is a person who has already decided they are interested. There is no cheaper visitor in existence.

The problem is that you are not the only page about you. Spotify, Apple Music, YouTube, Bandcamp, Genius, Songkick, Last.fm, Discogs and often Wikipedia all hold a page carrying your name, on domains with vastly more authority than yours. Ranking first for your own name is not automatic. It is a competition against platforms that syndicate you.

This is structurally the same fight an agent has with Zillow and Realtor.com, which we worked through in SEO for real estate agents. The lesson transfers: you will not out-authority the platform, so you win by being the page that answers the parts of the query the platform cannot.

There are two shapes of name collision, and they need different work.

• You share a name with something common. A band called Mercury, Palace or Wild Honey is competing with a planet, a building type and a food. Here the fix is entity disambiguation, and it is the schema section below.
• Your name is unique but the platforms outrank you. Here the fix is having pages the platforms do not have: tour dates, press, licensing, booking, lyrics you actually own, a mailing list.

Check which one you have before doing anything. Search your own name in a private window, write down the first ten results, and note how many belong to you. That list is your actual to-do list, and it costs nothing to produce.

Two demand curves, and only one of them pays this month

Here are real numbers, measured with Ahrefs for the United States on 4 September 2026. seo for musicians gets 360 searches a month at a difficulty of 0, with an estimated traffic potential of 200 and a cost per click of $3.00.

Now the part that matters more than the volume. On that same query the pages holding the first page of results earn, by Ahrefs' estimate, between 23 and 194 organic visits a month across all their keywords. A query with 360 monthly searches does not produce 360 clicks, and it does not produce 100.

That gap is the whole reason to model search as arithmetic rather than as hope, which is the exercise in Is SEO worth it?. Volume is an upper bound that nobody reaches.

So split your demand into two curves and treat them separately.

The discovery curve is your name, your song titles, your lyrics, your genre plus a mood. It is high intent, low commercial value per visit, and it accumulates. These queries are how a listener becomes a subscriber.

The booking curve is where the money is: "wedding band manchester", "jazz trio for hire chicago", "session guitarist remote", "guitar lessons brooklyn", "studio drummer for hire". This is a local services market with a search volume, a competitor set and a map pack, and it behaves nothing like the discovery curve.

Most musician SEO guides only cover the first curve. If you make any part of your living playing at events, teaching, or doing session work, the second curve is the one that pays rent, and it is governed by the rules in the next section.

Google Business Profile: which musicians actually qualify

A Business Profile is a separate index from web search, with its own ranking inputs, and a large share of musicians are eligible without realising it.

Google's eligibility guidance is direct: "If your business either has a physical location that customers can visit, or travels to customers where they are, you can create a Business Profile on Google."

Read that clause twice. A gigging musician travels to customers where they are. A private teacher who visits students travels to customers. A teacher who runs lessons from a home studio has a physical location that customers visit. All three qualify.

What does not qualify is a recording project with no in-person component. If you release music online and never perform, teach or record for clients in person, there is no profile for you, and every guide telling you to make one is wasting your evening.

Two clauses in Google's guidance trip people up, and both are worth quoting exactly:

• "If your business rents a physical mailing address but doesn't operate out of that location, also known as a virtual office, that location isn't eligible for a Business Profile."
• "Service-area businesses can't list a 'virtual' office unless that office is staffed during business hours."

So a mailbox at a co-working space is not an address. Your home is a legitimate base for a service-area business, and Google's documented behaviour for service-area businesses is to hide the address rather than publish it. The same pattern applies to any practitioner working from home, which we covered in SEO for therapists.

Pick your primary category from the booking curve, not from your identity. "Musician" is a category. So are "Live music venue", "Music instructor" and "Recording studio". The category you pick decides which searches you are eligible to appear in, and picking the artistic one over the commercial one is the most common mistake here.

The music schema everyone recommends is not a Google feature

This is the claim that sent me to the documentation, and it holds up.

Google publishes one canonical list of the search features that structured data can produce, at developers.google.com/search/docs/appearance/structured-data/search-gallery. As of its last update on 15 June 2026, it names these twenty-five: Article, Breadcrumb, Carousel, Course list, Dataset, Discussion forum, Education Q&A, Employer aggregate rating, Event, Image metadata, Job posting, Local business, Math solver, Movie, Organization, Product, Profile page, Q&A, Recipe, Review snippet, Software app, Speakable, Subscription and paywalled content, Vacation rental, Video.

There is no music entry. Not MusicGroup, not MusicAlbum, not MusicRecording, not MusicRelease.

Compare that against the advice actually ranking for this keyword today. One page in the top ten for seo for musicians recommends MusicGroup, MusicAlbum, MusicRecording and MusicRelease, and tells the reader that as a result "search listings might display upcoming tour dates, album covers, or preview snippets of your music". Google does not document a search feature that does that.

Two honest qualifications, because this is where the correction usually overshoots.

The types exist at schema.org and are valid. MusicGroup is a real schema.org type, a subtype of PerformingGroup and therefore of Organization. Writing it is not an error and will not get you penalised. It simply does not produce a rich result, because Google has not built one.

Using MusicGroup as your organization type is defensible. Google's Organization documentation, updated 15 April 2026, asks you to use the most specific subtype that matches. If you are a band, MusicGroup is more specific than Organization, and that specificity helps disambiguation even with no rich result attached.

What is not defensible is marking up every track on your site as a MusicRecording in the belief that Google will render something. Budget your time accordingly, the way we argue for triaging technical work in SEO for contractors.

What Google does support, and what to ship instead

Three of the twenty-five features are directly useful to a musician. Here is what each one actually asks for.

Organization, on your home page. Google's documentation says "There are no required properties; instead, we recommend adding as many properties that are relevant to your organization", and asks you to place it "on your home page, or a single page that describes your organization". The property that earns its keep is sameAs, which Google describes as URLs "to pages on other websites with additional information about the organization, such as social media or review site profiles".

That sameAs array is your entity disambiguation, and it is the direct answer to the shared-name problem from the first section. You are telling Google that the Spotify artist, the YouTube channel, the Bandcamp page and the Wikipedia entry are all one thing, and that your domain is its home.

{
  "@context": "https://schema.org",
  "@type": "MusicGroup",
  "name": "Wild Honey",
  "url": "https://wildhoney.band",
  "logo": "https://wildhoney.band/logo.png",
  "description": "Four-piece soul band based in Bristol, UK.",
  "sameAs": [
    "https://open.spotify.com/artist/XXXXXXXX",
    "https://music.apple.com/artist/XXXXXXXX",
    "https://www.youtube.com/@wildhoney",
    "https://wildhoney.bandcamp.com",
    "https://musicbrainz.org/artist/XXXXXXXX",
    "https://www.instagram.com/wildhoney"
  ]
}

On the logo, Google's documentation is specific: the minimum size is 112x112px, the URL must be crawlable and indexable, and "Adding this property can help Google better understand which logo you want to show, for example in Search results and knowledge panels". That is the closest documented path to a knowledge panel, and it is a good deal weaker than the guarantee most musician SEO posts imply.

Profile page, for a solo artist. This one is newer and under-used. Google's documentation, updated 10 December 2025, says "The primary focus of the page must be a single person or organization that is affiliated with the overall website", and lists it as being for creators. It requires only mainEntity and a name, and it feeds the Discussions and Forums treatment in search.

If you are a solo artist with an About page that is genuinely about you, this markup describes it accurately. If your About page is really a band bio, use Organization instead. Do not ship both on the same page.

Local business, if and only if you qualified in the previous section. It is the markup counterpart of the Business Profile, and the pattern is the same one used in SEO for restaurants.

Here is a fifteen-line script to check what you are currently serving. It needs Node 18 or later and no dependencies.

// node check-schema.mjs https://yourband.com
const url = process.argv[2]
const html = await (await fetch(url)).text()
const blocks = [...html.matchAll(/<script[^>]+application\/ld\+json[^>]*>([\s\S]*?)<\/script>/gi)]

if (blocks.length === 0) {
  console.log('No JSON-LD found on', url)
} else {
  for (const [, raw] of blocks) {
    try {
      const data = JSON.parse(raw.trim())
      const nodes = [].concat(data['@graph'] ?? data)
      for (const node of nodes) {
        const sameAs = [].concat(node.sameAs ?? [])
        console.log(node['@type'], '|', node.name ?? '(no name)', '|', sameAs.length, 'sameAs links')
      }
    } catch (err) {
      console.log('Invalid JSON-LD block:', err.message)
    }
  }
}

Run it against your site and against two artists you consider peers. Most website builders emit a generic WebSite node and nothing else, which tells you exactly how much room you have.

Event markup, and the clause that disqualifies most gigs

Event is a supported feature, it is the one musicians have the strongest claim to, and it carries an eligibility clause that almost nobody quotes.

Google's Event documentation, updated 10 December 2025, states: "Events must be bookable to the general public. Events that require a membership, or invitation prior to purchasing the ticket or attending the event are ineligible."

That single sentence removes a large slice of a working musician's calendar. A wedding is not bookable by the general public. A private corporate party is not. A members-only club night is not. Marking those up as events is not a clever edge, it is markup that does not qualify.

Google adds a second exclusion: "Virtual experiences that have no real-world component aren't supported. Events must take place in a physical location." A livestream-only show is out.

What is left is the ticketed public show, and for that the markup is worth shipping. Four properties are required: name, startDate, and a location carrying both location.name and location.address.

{
  "@context": "https://schema.org",
  "@type": "MusicEvent",
  "name": "Wild Honey at The Louisiana",
  "startDate": "2026-10-17T20:00:00+01:00",
  "eventStatus": "https://schema.org/EventScheduled",
  "location": {
    "@type": "MusicVenue",
    "name": "The Louisiana",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "Wapping Road",
      "addressLocality": "Bristol",
      "postalCode": "BS1 4RB",
      "addressCountry": "GB"
    }
  },
  "performer": { "@type": "MusicGroup", "name": "Wild Honey" },
  "offers": {
    "@type": "Offer",
    "url": "https://wildhoney.band/tickets/louisiana-2026",
    "price": "14.00",
    "priceCurrency": "GBP",
    "availability": "https://schema.org/InStock",
    "validFrom": "2026-08-01T09:00:00+01:00"
  }
}

MusicEvent is a subtype of Event, so it satisfies the requirement while being more specific. Note the offers.url pointing at your own ticket page rather than at the platform. That is the one place in this whole article where you get to compete with the aggregators on their own turf, because you are the source.

One structural note: the tour dates page needs each event as a separate entity, and it needs past events removed or clearly marked. A page still advertising last spring's tour is the single most common stale page on a musician's site.

The FAQ rich result is gone, and the advice has not caught up

If a guide published before this summer tells you to add FAQ schema for extra space in the results, that advice expired on a specific date.

Google's documentation changelog records the sequence. On 8 May 2026 it "Added a deprecation notice to the FAQ rich result documentation" stating "This feature will no longer appear in Google Search starting May 7, 2026." On 15 June 2026 it "Removed documentation for the FAQ rich result feature", noting the feature "is no longer shown in Google Search results".

It is not an isolated pruning either. The same changelog records that on 6 January 2026 the practice problem type was removed because it "is no longer shown in Google Search results". Google has been shrinking the feature surface, not growing it.

The practical consequence is narrow but real. Keep writing FAQ sections when readers genuinely ask those questions, because the content still answers a searcher and still gets read by assistants. Delete the FAQPage JSON-LD, because it now buys nothing. And treat this as the general rule it is: before implementing any markup, check that the feature still exists, because the guide recommending it will not have been updated.

Streaming platforms are a different index with different rules

Your name is searched on Spotify and YouTube more than it is searched on Google, and neither of those is search engine optimisation in the sense the rest of this article uses.

That distinction matters because the two are constantly conflated. Optimising a Spotify profile is metadata work inside a closed catalogue. There is no crawler, no index you can inspect, no equivalent of Search Console, and no documented ranking guidance you can quote. Anyone stating Spotify's ranking factors as fact is guessing.

What is verifiable and worth doing is consistency. Your artist name, spelled and capitalised identically everywhere. The same short bio across profiles. Genre tags that a human would use. Correct credits and ISRCs delivered by your distributor, because that metadata is what links a track to you across services.

The useful connection back to Google is that those platform profiles are the sameAs targets from the schema above. They are also, in practice, what AI assistants read when someone asks about you, which is the next section.

One thing not to do: do not build your site as a thin wrapper around embedded players. A page whose only unique content is an iframe has nothing for a search engine to rank, and it is a variant of the mistake we describe in DIY SEO for small business.

Getting named by an AI assistant

This is where musician-facing advice gets the most speculative, so start with what Google actually documents.

Google's page on AI features, last updated 10 December 2025, states: "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary." It continues: "You don't need to create new machine readable files, AI text files, or markup to appear in these features. There's also no special schema.org structured data that you need to add."

So there is no special file, no music-specific markup and no trick. What there is, is a source-selection problem: assistants name entities they can find described in text, on pages they can read, corroborated in more than one place.

For a musician that means a few specific, unglamorous things:

• A plain HTML bio page that states in sentences who you are, where you are based, what you play, and what you are available for. Not a hero image with the text baked in.
• Consistent facts across your site, your platform profiles and any press coverage. Contradictions are what make an assistant hedge or pick someone else.
• Presence in the databases these systems draw on. MusicBrainz and Wikidata are open, editable and frequently ingested, and a correct MusicBrainz entry is the cheapest structured fact about you that exists.

There is a measurable version of this, and it is worth doing rather than guessing: ask the assistants the questions your potential audience would ask, on a schedule, and record which domains get cited. We describe the method in LLM brand visibility, the mechanics of citation in how to rank on ChatGPT, and what genuinely changed versus what did not in AI answer engine optimization.

Worth noting from this run's own measurement: the AI Overview for seo for musicians on 4 September 2026 carried sitelinks to seven sources, and one of them was a page about SEO for tour operators. Source selection is looser than the confident tone of these answers suggests, which cuts both ways.

Measuring it without buying a tool

You need one free tool and one habit. The tool is Google Search Console. The habit is splitting brand from non-brand.

Verify the domain, submit a sitemap, then open the Performance report and add a query filter excluding your artist name. Everything left is non-brand demand: people who found you without knowing you existed. That number, tracked monthly, is the only honest measure of whether any of this work is compounding.

Two more reports repay a monthly glance:

• Pages in the Performance report, sorted by impressions with zero clicks. High impressions and no clicks means Google shows the page and nobody chooses it, which is a title and description problem, not a content problem.
• Page indexing, to catch pages Google has decided not to index at all. On music sites the usual offenders are duplicate tour date pages and paginated galleries.

Set expectations from arithmetic rather than from anecdote. Take your non-brand clicks, your booking conversion rate, and your average gross profit per booking, and see what the channel is actually worth to you. The ads comparison, worked in full, is in SEO vs Google Ads. Results vary, and nobody can tell you a date.

What to publish, in order

Order matters more than volume, because the early items make the later ones findable.

1. A real home page with your name in the title tag, a text bio, and the Organization or MusicGroup JSON-LD with a full sameAs array. This is the entity foundation and everything else hangs off it.
2. A tour dates page with MusicEvent markup on public ticketed shows only, past dates removed.
3. A booking or hire page per service you sell, named the way clients search: "wedding band", "session guitarist", "guitar lessons", not "services".
4. A location page per city you genuinely work in, with real content about real venues and real past work. One thin page per city with the name swapped is doorway abuse, and it is the trap we documented in SEO for photographers.
5. Song and release pages you own, with lyrics you hold the rights to, credits, and the story. These are the pages that catch lyric searches, which is a large and permanently underserved query family.
6. A press page with your bio in a copyable form, high resolution photos and correct spellings. This exists so that journalists and assistants describe you consistently.

Only after those six does a blog make sense. When it does, the topics that work are the ones your booking curve asks about: what a wedding band costs, how long a set should be, what a venue needs from you in advance.

FAQ

What is SEO in music?

It is two separate jobs sharing a name. The first is making sure your own website, rather than a streaming platform, holds the top result for your artist name and your song titles. The second is ranking for the commercial queries around your work: bookings, lessons, session hire, in the cities where you work. The first builds an audience, the second books gigs.

Is SEO dead or evolving in 2026?

Evolving, and the evidence cuts against the panic. Google has been removing search features, not adding them: FAQ rich results stopped appearing on 7 May 2026 and the documentation was deleted on 15 June 2026. At the same time Google states plainly that no special files or markup are needed for AI Overviews or AI Mode. Fewer decorations, same fundamentals.

What schema markup should a musician use?

Organization (or its MusicGroup subtype) on the home page with a complete sameAs array, MusicEvent on publicly ticketed shows, ProfilePage on a solo artist's About page, and LocalBusiness only if you qualify for a Google Business Profile. Skip MusicAlbum and MusicRecording: they are valid schema.org types, but Google's list of supported structured data features contains no music entry, so they produce no search feature.

Do I need a website if I am already on Spotify and Instagram?

If you only release music, you can survive without one, though you are then a tenant on someone else's platform for every query about you. If you sell anything (gigs, lessons, session work, merch, licensing) you need one, because those searches happen on Google and platform profiles do not rank for "wedding band bristol". A domain you own is also the only entity anchor the schema above can point at, and the trade-off between feeds and search is measurable rather than a matter of taste (three tests here).

Can I do SEO for my music myself, or should I hire someone?

The work in this article is a weekend of setup and about an hour a month of upkeep, and none of it requires an agency. Hiring makes sense when the bottleneck becomes consistent publishing rather than configuration. Before paying anyone, read what the money buys in How much does SEO cost?.

How long does it take before search brings in bookings?

Nobody can give you a date, and anyone who does is selling. What you can do is watch the sequence: indexing first, then impressions on non-brand queries, then clicks, then enquiries. If impressions are not moving after a few months of publishing, the problem is the keyword choice rather than the patience, and the method for auditing that choice is in SEO keywords for photographers. Results vary by market, by city and by how many competitors got there first.