CA

What a band's website needs to cover

The four questions everyone asks on arrival, and how to answer them

19/11/2026

What a band's website must answer, what to leave out, and how to tell whether a template is enough. With a checklist to run through before hiring anyone.

The short answer

A band’s website is not a shop window: it is the place where someone who does not know you decides whether to listen to you, book you or move on. They do it in a few seconds with four questions: who you are, what you sound like, when you play and how to book you. If the site answers them without making people think, the rest is decoration.

The four questions

Who you are

A photo where everyone’s face shows, a ten-line biography explaining where you come from and what you do, and the line-up with names and instruments. You do not need the story since the first rehearsal: someone landing on the page needs to know what world they are in and whether it interests them.

What you sound like

Each record with its own page: cover, credits, year and links to the platforms where it already lives. That is not a quirk: it is what makes each record findable by its name in search engines, and what lets someone link to it from a review, a festival or an interview. Keeping them all in an embedded player is convenient, but it leaves the catalogue with no doors in.

When you play

The gig list has to be the one you already maintain, not another one that will be forgotten. If your dates live on Bandsintown or a shared calendar, the site should read them and publish them by itself, with the ticket link alongside. A copy typed in by hand lasts two weeks and then goes stale.

How to book you

A page aimed at venues, festivals and press: formats (solo, trio, big band), available line-up, guest artists, technical rider if you have one, and a downloadable press kit. It is not vanity: it saves three emails every time someone wants to book you.

What you do not need

  • Autoplaying video on the front page. It is heavy, eats mobile data and covers what people want to read.
  • A blog abandoned two years ago. Worse than having none: it makes the project look stopped.
  • Animations and effects that add nothing. If the site takes time to load, the record never plays.
  • Empty template sections: a gallery with two photos, a press page with no clippings, a shop with nothing to sell.
  • A cookie banner if you have no tracking cookies. Most band sites we build have none.
  • A visitor counter in the footer. The audience does not care and it gives you away.

If everything already lives on the platforms, why a website?

Because social networks reach the people who already follow you, and the website is the only piece that is yours: it does not depend on an algorithm, it does not vanish if a platform shuts down, and it is what someone finds when they search your name. They do not compete: the site reads Instagram, Spotify and YouTube and shows them next to what belongs to you.

When a template is still the right call

Be honest with yourself: if you play twice a year, have not released a record and your presence is mostly Instagram, a simple, well-edited template does the job and you do not need anything else. A custom site makes sense once there is a catalogue, a continuous gig list, booking or more than one language — that is, when the content repeats and goes out of date, and keeping it by hand already costs more than keeping it right.

A checklist to run before hiring anyone

  1. Who will update it, and how often.
  2. Whether the gig list updates itself or by hand.
  3. Whether records will have their own URL and platform links.
  4. How the migration of what you already have will be done, and whether addresses are kept.
  5. Whether it will work on a phone without zooming.
  6. Whether one day you can walk away with the texts and the images.
  7. Whether whoever builds it explains how it works. If they don’t, that is a sign.

How we solve it

We use a consolidated base with the same eight elements across every music project — they are explained in solutions for musicians — and we customise it thoroughly: aesthetics, structure, texts and integrations.

Three cases that show it:

  • Bratia — from a heavy WordPress to a light system the band can maintain on its own.
  • Ivan Kovačević — many projects and more than fifty records on one site, in four languages.
  • Barcelona Big Blues Band — automatic gig list, twelve records with their own page and a booking page.

Frequently asked questions

I am not technical. Will I be able to update it myself?

Yes. Texts, biography, press and photos are edited from a simple editor, without touching code. And what changes most often —the gig list and the videos— you do not even have to touch: the site reads Bandsintown or your calendar and your YouTube channels, and updates itself.

We are already on Instagram and Spotify. Do we still need a website?

Not always. If you play a handful of times a year and everything happens on social media, maybe not right now. A site becomes essential once there is a catalogue, a steady gig list or booking: it is the only piece that is yours, that does not depend on an algorithm, and that a festival programmer finds when they search your name.

How long does it take to get it live?

It depends on the content, not the technology: records, photos, press, texts in more than one language. Because we start from a proven base, the work goes into your music and your image. We give a concrete schedule before starting.

Does it work if I play in several projects at once?

Yes, and it is one of the cases where a custom site clearly wins: a single place bringing together projects, line-ups and records. That is what we did for Ivan Kovačević’s site, with more than fifty records and four languages in one place.

And if we want to leave later on?

The content and the images should be yours and should be portable. We do not lock anything in: it is all text, images and files in common formats, not tied to a platform that keeps you.

Keep reading

→ Contact · How we work

→ Websites for musicians and bands