Six Essential Pages for an Artist Website
Start an artist website with the six visitor jobs in this guide, then build only the destinations the project can maintain. The model does not require six URLs. Combine related jobs when the content remains useful and linkable; separate them when the audience, update rhythm, campaign, primary action, search intent, or need for a stable crawlable URL becomes distinct.
Lead visual
The smallest clear site map
Home
identity + priority
always visible
Music
release context
separate when catalog grows
Live
dates + tickets
separate when active
About
bio + proof
combine only when short
Press
assets + contact
separate for campaigns
Contact
inquiry + signup
separate actions
Audience · Owned web
Page architecture map
Use this for
Separate a website job when it needs its own audience, URL, content depth, update rhythm, or primary action.
Watch for
Combining everything can bury the next action, while splitting thin content can create empty pages no one can maintain.
Check
Home, music, live, about, press, and contact jobs; navigation labels; internal links; page owner; update trigger; and acceptance test.
Result
The smallest clear site map that helps fans, press, bookers, and search systems reach the right destination.
Key takeaways
- Design around visitor jobs before choosing a menu or template.
- Combine jobs only when clarity, URLs, and maintenance survive.
- Give releases and campaigns durable pages when they have durable context.
- Hide empty sections instead of publishing thin placeholder pages.
- Assign every page an owner, update trigger, and acceptance test.
When should each artist website job get its own page?
Combine-or-separate chooser
Split only when the job earns a destination
Home
Use when
Every site needs one canonical root for identity, orientation, and the current priority.
Avoid when
It becomes a duplicate of every other page instead of routing the visitor.
Music
Use when
Releases, credits, context, and actions need more depth or durable URLs.
Avoid when
There is one embedded player and no visible information beyond the home page.
Live
Use when
Dates, ticket links, venue details, or booking context change independently.
Avoid when
No shows or useful booking material exists; hide the menu item or combine a brief note.
About
Use when
The identity, verified story, credits, image, and profiles need a stable reference.
Avoid when
A two-sentence project can be explained clearly on Home without burying the current action.
Press
Use when
A release campaign requires a shareable, crawlable page with approved assets and direct media contact.
Avoid when
The only content is the same short bio and image already visible elsewhere.
Contact/signup
Use when
Inquiry and fan-consent actions need separate promises, owners, confirmations, or data handling.
Avoid when
One form mixes booking, press, support, and marketing consent without routing.
What acceptance test should every page pass?
Six-page acceptance audit
Content, action, discovery, and ownership
Home
Preferred artist name, current priority, one primary action, and paths to core jobs
A new visitor can orient without reading the complete site.
Music
Visible release context, accurate credits/dates, playable or outbound action, and durable link
The catalog has owned meaning beyond an embed.
Live
Current status, accurate date/place, working ticket path, timezone/context, and update owner
Fans do not act on stale or ambiguous show information.
About
Verified bio, consistent name, meaningful context, image credit, and official profiles
People and machines receive one defensible identity source.
Press
Current angle, proof, selected media, labelled assets, details, contact, and update date
A press contact can evaluate and use the campaign without another request.
Contact/signup
Purpose, recipient, response expectation, consent language, confirmation, and failure path
Inquiries and fan permission are routed and recorded correctly.
How should the page map change when the project grows?
Architecture review
Grow from jobs, not template features
- 01
Inventory
Name the active jobs
List the visitors, questions, content, actions, URLs, and owners the artist actually has now.
- 02
Combine
Keep thin jobs together
Use sections and anchored links while the content remains clear, current, and easy to share.
- 03
Separate
Create the durable destination
Split when the job needs its own audience, campaign URL, content depth, search intent, or update rhythm.
- 04
Retire
Redirect or remove stale paths
Preserve useful URLs with an appropriate destination instead of leaving empty menu items and dead pages.
Six jobs do not mean six compulsory URLs
The architecture is a Velveteen operating model, not a Google page-count rule. A smaller site is better than a larger site full of duplicate bios, empty calendars, broken forms, and unmaintained assets.
Which sources should guide page architecture and discovery?
Frequently asked questions
What pages are essential on a musician website?+
Cover the six visitor jobs defined below rather than copying a template menu. They are functions, not mandated URLs. Add store, video, lyrics, teaching, services, or other pages only when the artist has useful content, an audience need, an owner, and a reason to maintain a separate destination.
Can a musician website be one page?+
Yes, when the project is small and every job remains visible, linkable, usable on mobile, and easy to update. Separate content when press needs a stable shareable URL, a catalog needs durable release pages, live dates change independently, or contact and fan signup require distinct promises and handling.
Should every release have its own page?+
A durable page is useful when the release has unique context, credits, artwork, dates, links, video, press, or continuing search value. Do not create thin release pages that only repeat a player. A compact catalog can begin on one Music page and split into release URLs as the material earns depth.
What should appear in an artist website menu?+
Use short labels visitors understand, ordered by the project's current jobs. Home can be the logo or artist name; Music, Live, About, Press, and Contact are legible defaults. Do not expose empty sections, internal jargon, or several labels that lead to the same undifferentiated destination.
How often should an artist website be updated?+
Assign updates to events rather than a universal calendar: a release announcement changes Home and Music; a confirmed show changes Live; a new campaign changes Press; credits or team changes update About and contact. Review critical links, dates, forms, assets, titles, and structured data before every public campaign.
Get better release strategy in your inbox
Release planning checklists, royalty explainers, and artist strategy notes from Velveteen. No daily noise.
Was this useful? Send a signal or flag a correction.
Keep reading
Pillar guide
Artist websites and music SEO
A six-page owned-site system with a crawl and index gate, artist identity signals, press delivery, conversion evidence, and a 30-day launch loop.
Related guide
EPK page for music press
A seven-block press-page workflow that makes the current story, selected music, factual proof, approved downloads, details, and media contact easy to use.
Related guide
Track artist website conversions
A five-stage website evidence ladder that separates search visibility, on-site events, confirmed owned actions, and downstream outcomes in their source systems.
Build your one-sheet in minutes
Drop in your bio, links, and proof points and get a clean, copy-ready one-sheet for curators, blogs, bookers, and anyone else asking who you are.