Build a Gig-Synced Musician Website in a Weekend

The Independent Musician's Library · AI guide

Build a Gig-Synced Musician Website in a Weekend

Your website still showing last month's gigs?

A musician's website that updates itself — it pulls in your gigs, costs about £10 a year, and you can build it in a weekend. No monthly fees, no web designer, no code.

Aaron Norton

By Aaron Norton — independent solo artist, gigging for a living since 2006.

Every guide I found ended with a builder asking me for £20 a month — forever — for a site that'd be out of date the week after I built it. So I built my own with AI for the price of a domain, and made it update itself: I add a gig to my calendar on my phone, and by morning it's live on the site. No designer, no monthly rent, no dead 'last spring's tour dates' page. This is exactly how I did it — it's the site you're on right now.

£19.99 · instant download

UK VAT included · instant PDF download · yours to keep

Secure checkout · instant PDF download · UK VAT included · also on Etsy

Also in the AI Musician Bundle and the Ultimate Library — both save you money.

What's inside

How to Build a Musician Website That Updates Itself (Without Renting a Template)

I'm a full-time acoustic musician, and for years I did the thing you're probably about to do: I searched "how to build a musician website," found a dozen guides, and every one ended with me staring at a builder asking for £20 a month — forever — before I'd played a note on it. So let me be straight up front, because most of these guides won't be: you don't need to pay a designer, you don't need £240 a year, and you definitely don't need the kind of site that's already out of date the week after you build it. The site I use updates itself — it pulls my gigs in automatically — and it costs me roughly £10 a year. This is the honest guide to building one like it. (Two honest caveats kept throughout: it's an investment, not "free" — a weekend of your time plus the £10 domain — and tool prices and menus move fast, so anything dated here is a mid-2026 snapshot.)

Why most musician websites die

This is the most important sentence on the page: most musician websites die because there's no reason to come back. Someone pays £180–£360 a year for a Bandzoogle/Wix/Squarespace template, gets one wave of family-and-friends visits, and then it goes stale. The "Live Dates" page still shows a gig from last spring. A promoter clicks through, sees a dead date, and assumes you're not gigging — which is worse than having no site at all.

The reason isn't laziness. It's that the site was built as a brochure — a thing with a job to do once — instead of an instrument you pick up regularly. The fix isn't "remember to update your website." Nobody remembers to update their website. The fix is to build one that updates itself from the things you're already doing: adding gigs to your calendar, taking photos at gigs, sending the Sunday newsletter. Build a site you don't have to remember.

The magic trick: a gig list that updates itself

This is the feature that justifies the whole book. You add a gig to your Google Calendar on your phone; by the next morning, it's live on your website. You never touch the site. Add the booking once, in the one place you already keep your gigs, and the homepage's "next gigs" block is always current — a promoter glancing at it sees a packed, up-to-date calendar and instantly knows: this person works.

The obvious way to do this is to paste Google's embed code — and that's what every tutorial online tells you. Don't. An embedded Google Calendar is a clunky grey widget that looks nothing like your site and breaks when the quota runs out. The book teaches the better pattern: your site fetches the calendar once a day, saves it as a fast static file, and shows it as a gig list styled to look like your site — quick, reliable, and yours. The trade is that a gig added today appears tomorrow morning (plenty of lead time for a working musician). The full wiring is in the book; the concept is the thing to take away — the calendar is the source of truth, and the site reads from it.

(And here's where it compounds: that exact same gigs calendar is the spine of the auto-poster in The Automated Musician — one calendar entry feeds your website AND your social posts. Build the website's sync and you're most of the way to the whole engine.)

Can AI really build your website?

Yes — but be careful which kind of "AI website builder" you mean. The one-shot tools (the "describe it, get a site in 60 seconds" builders) are impressive demos, but they're optimised for a pretty one-shot result you then rent and can barely change. This book teaches the other path: you direct a conversational AI (Claude, ChatGPT or Gemini) to build a real site, in a real project, that you own and can edit for years. You don't write code — you describe what you want, paste the errors back when something breaks, and ask why until it works. The patience is the only real prerequisite; the skills come along the way. The difference matters: a one-shot builder gives you a site you're locked into; this gives you a site you understand and control. The book has the exact prompts; the mindset is "own it, don't rent it."

What it actually costs (~£10 vs £240 a year)

The honest economics no builder comparison shows you. A template builder is £141–£360 a year, every year (Wix ~£141, Bandzoogle ~£190, Squarespace ~£221 — 2026 pricing). The DIY path in this book is the £10 domain — because the hosting is free, the storage is free, and if you already pay for an AI tool for songwriting, admin or lyric help, the marginal cost of "and now I also have a website" is zero. The subscription's already on your card; the website is a side-effect. Two honest caveats: your weekend isn't free, and the free hosting tier (Vercel) has a non-commercial clause — for most musicians it's a non-issue, and if it ever bites, the paid tier is ~$20/mo, still less than Squarespace. The maths swings hard toward owning it.

Do you even need a website in 2026?

Honestly — only if it's an instrument, not a brochure. If you're going to build a dead three-page site that lists last year's tour dates, you're better off with a good link-in-bio. But a living site — one with a self-updating gig list, a fan scrapbook, your strongest track on autoplay — is the one door to your fanbase that no platform can lock, throttle, or delete. Instagram can change its algorithm tomorrow; your site is yours. The question isn't "do I need a website," it's "will I build one that's alive." If yes, it's the most durable asset you've got.

Your website IS your EPK

A contrarian one, and I'll back it with hard experience: don't build a separate EPK (electronic press kit) page. I've never used a dedicated EPK in my career and I get booking enquiries every single day — none of them off the back of an EPK. Your website already does everything an EPK tries to: it looks professional, the scrapbook is social proof no press quote can match, the live gig dates prove you're busy, and a clear /contact makes a booker's life easy. That's the entire EPK design brief, and a good homepage covers it in ten seconds. The one concession: some bookers will type "yourname EPK," so make /epk a one-line redirect to your homepage. Build the site well and the EPK builds itself.

What's wrong with the template you're paying for

Nothing, exactly — Bandzoogle, Wix and Squarespace are genuinely good products, and if yours is working, don't switch. The honest critique is narrower: templates are built for setup, not for return visits. They make it easy to open the box and hard to answer the only question that matters — will anyone come back next month? They also lock your time inside the template (every hour tuning a theme is an hour you can't transfer), and the casual visitor's eye is now trained to spot a stock template. Owning your own site costs more hours up front and compounds forever after.

You don't need a shop — outsource the checkout

A practical one that saves you weeks: don't build a store on your site. Selling music or merch means payment processing, tax, fraud, delivery — a whole maintenance burden. Link out to Bandcamp, Etsy or Gumroad instead, where the checkout, the tax and the delivery are someone else's problem, and put a strong Bandcamp embed on your /music page so a visitor can press play immediately. Your site's job is to send a warm fan to a place that already handles selling well. Simpler, safer, and it works.

Common questions

How do I make my musician website update its gigs automatically?

Keep your gigs in a Google Calendar, and have the site read from it — fetching once a day, saving a fast static copy, and showing a gig list styled to look like your site (not a clunky embedded Google widget). You add a gig on your phone; it's live on the site by next morning. The calendar is the source of truth; the site reads from it. The book has the full wiring.

Can AI build my website for me?

Yes — but choose the right kind. One-shot AI builders give you a pretty site you rent and can barely change. The better path is directing a conversational AI (Claude, ChatGPT or Gemini) to build a real site you own and can edit for years. You don't write code; you describe what you want and paste errors back when something breaks. The patience is the only prerequisite.

How much does a musician website actually cost?

About £10 a year — the domain — if you build it yourself with AI. Hosting and storage are free at this scale, and if you already pay for an AI tool for other things, the website's marginal cost is zero. Compare that to £141–£360 a year for a template builder, forever. Honest caveats: your time isn't free, and the free hosting tier has a non-commercial clause (the paid tier is ~$20/mo if you ever need it).

Do musicians really need a website in 2026?

Only if it's a living instrument, not a dead brochure. A site that lists last year's gigs is worse than none. But a self-updating site — live gig dates, a fan scrapbook, your best track on autoplay — is the one channel you own outright, that no algorithm can throttle. If you'll build one that stays alive, it's the most durable asset you have.

Is it better to build my own site or use Wix / Bandzoogle / Squarespace?

The builders are genuinely good and commission-free on sales — if one's working for you, keep it. But they're built for setup, not return visits; they lock your time inside the template; and they cost £141–£360 a year forever. Building your own with AI costs more hours up front and a £10 domain, and you own it and can add any feature you want. It's a trade: convenience vs control.

Do I need an EPK (electronic press kit) as a musician?

Not a separate page. Your website is your EPK — it looks professional, the scrapbook is social proof, the live gig dates prove you're busy, and /contact makes a booker's life easy. That's everything an EPK tries to do. Make /epk a one-line redirect to your homepage (some bookers type that phrase), and put your energy into the homepage instead.

What's the best free website builder for musicians?

"Free" builders usually aren't — the real cost arrives at renewal, or when you want a custom domain or to remove their branding. The genuinely cheap path is owning your own: a £10/year domain on free hosting, built with an AI subscription you already have. You're not renting someone's template; you own the site. That's the honest version of "free."

Why does my website keep going out of date?

Because it was built as a brochure you have to remember to update — and nobody remembers. The fix isn't discipline, it's architecture: build a site that updates itself from things you already do (adding gigs to your calendar, taking photos at gigs). A self-updating gig list and a fan scrapbook keep the site alive between your sessions, with no "update the website" task on your list.

Do I need a shop on my website to sell my music?

No — and you probably shouldn't build one. A store means payments, tax, fraud and delivery to maintain. Link out to Bandcamp, Etsy or Gumroad, where all that is handled, and embed a Bandcamp player on your music page so visitors can listen immediately. Your site sends a warm fan to a place that sells well; it doesn't have to be the checkout.

How long does it take to build a musician website with AI?

A weekend is the right ballpark for someone non-technical following a clear guide — and a first deploy can happen in about 90 minutes. The gig-calendar sync is a few more hours including the API setup. Budget more if you're learning as you go; the point is it's a one-time build, after which the site largely runs itself.

Do I need to know how to code?

No. You direct an AI to write the code; your job is to know what you want and to keep asking why when something doesn't work, rather than giving up on the third try. Every musician I know who can run a backing-track playlist at a gig is technically capable of this. The patience is the real skill; the rest comes along the way.

Not ready to buy?

Grab Music First free, or join The Soundcheck — one short email a week from the road, plus new guides as they land.