“Publish twice a week” sounds modest until each post requires listening, fact-checking, image permission, and an edit. For a new experimental-music site, start with the work behind each page rather than the number of pages you hope to publish. If a substantial piece takes eight hours and you have four editorial hours a week, even a weekly feature is out of reach.
Useful website goals say what the site is for, what its maintainers can control, and when they will review the results. Visitor counts matter, but they come after decisions about scope, accessibility, publishing rhythm, and trust. A small archive of dependable writing may serve listeners and musicians better than a busy site whose credits and updates nobody can keep straight.
Decide what the website must do first
A new site might be a listening guide, a publication, a label archive, a record of live events, or a musician’s portfolio. Each needs a different first milestone. A cassette label may need a clear catalog and ordering information before it needs a journal. An editorial site may need a few well-edited articles and clear navigation before it needs a newsletter.
Write a one-sentence purpose statement that names the audience and what they need to do: “Help listeners find and understand documented releases in a small experimental-music catalog,” for example. It is a test, not a slogan. If a proposed feature does not help with that task, it can wait.
Pick one primary objective for the first three months. Secondary aims are fine, provided they do not compete for the same limited hours. Possible objectives include:
- Make essential information findable: publish accurate artist, release, and contact pages.
- Establish an editorial practice: publish a few original, fact-checked pieces at a pace you can maintain.
- Preserve a project’s record: document past work with consistent credits, verified dates where available, and readable descriptions.
- Support an existing community: give contributors and readers a dependable place to find submission details, event information, or updates.
A site may eventually do all four. Requiring all four at launch creates a backlog before anyone has used it.
Build goals from capacity, not ambition
Count the hours genuinely available after paid work, rehearsals, shipping, caregiving, and other commitments. Then list the recurring jobs: research, writing, editing, securing permissions, preparing audio or images, adding alt text, checking links, answering messages, and updating software. The time spent pressing “publish” is only a fraction of the work.
Say two people can give a site six hours a week between them. Maintenance and correspondence take two, leaving four for new material. A feature that needs ten hours from research to publication will take at least two and a half weeks at that pace, assuming nothing else comes up. One such feature a month leaves space for corrections and delays.
Leave some hours unallocated. A buffer of roughly a quarter of the schedule is a planning allowance, not a rule for every site. It gives you room when an interview needs another edit, an embed breaks, or a contributor replies late. Without it, a small interruption becomes a missed promise.
Separate launch work from recurring work
Choosing a domain, setting up page templates, writing an about page, and testing the contact form are launch tasks. Research, correspondence, publishing, and maintenance keep coming back. Put them on separate lists. A long launch checklist does not mean every week will be that demanding; a quick launch does not prove you can keep publishing at the same pace.
For each goal, ask who owns it and what happens if that person is unavailable. “Post updates regularly” has no owner, frequency, or finish line. “The editor checks release-page corrections on the first Monday of each month” can go on a calendar and be handed over.
Set a small launch baseline
Before setting growth targets, decide what a functioning site must offer. Readers should be able to tell who is responsible, what they will find, and how to report a problem. For an independent music publication, that may mean an about page, contact information, clear topic categories, and a handful of complete pieces. The site need not pretend to have years of history.
Test the experience, not just the page count. Can someone read a long piece on a phone without scrolling sideways? Are links and controls easy to identify? Does an audio post offer enough text for someone who cannot play it? Have you checked names and credits against the material you actually have? Five pages that pass those tests are more useful than fifty thin entries.
Keep unfinished sections out of the menu. An empty “reviews” category or a coming-soon page promises something the site cannot yet provide. Save future ideas privately until there is material worth visiting.
Distinguish work targets from audience targets
There are two kinds of website goal. Work targets cover actions the team controls: publishing three verified catalog entries, revising navigation, or testing contact forms on mobile. Audience targets cover responses the team can influence but not guarantee: visits, sign-ups, inquiries, and returning readers.
At first, lean toward work targets. A new site has little evidence on which to predict traffic, and a niche subject may draw a small, attentive readership. An arbitrary visitor target can push editors toward rushed posts or misleading headlines. Gather a baseline instead, and check whether the intended readers can use the site.
Audience measures help more when tied to the site’s purpose. For a release archive, visitors moving from a catalog page to an individual entry may tell you more than total page views. A long-form publication might watch whether readers return for a second piece, though analytics cannot show how carefully anyone read. If the aim is contact with musicians or contributors, relevant messages matter more than raw traffic.
Measurement is not the same as a target. You can track monthly visits without setting a number to hit. In the first few months, where readers arrive, which pages they use, and where they find errors may be more instructive than whether a small traffic figure rises.
Write goals that can survive a real schedule
A useful goal names an outcome, a deadline or review date, an owner, and a standard for completion. It also serves the site’s purpose. “Become a leading source for underground music” gives nobody a task for Tuesday. “By the end of month two, publish four release entries with verified credits, descriptive text, and working audio controls” does.
A short goal sheet might look like this:
| Area | First goal | How to check it |
|---|---|---|
| Core pages | Publish an about page and a working contact route before launch | Ask someone unfamiliar with the project to find both |
| Editorial work | Publish one carefully edited feature each month for three months | Check credits, sources, permissions, and publication dates |
| Usability | Test key pages on a phone and with keyboard navigation | Record and fix obstacles found in the tests |
| Maintenance | Review links, forms, and outdated details monthly | Keep a dated log of checks and corrections |
These are examples, not standards every site must meet. A solo artist updating an archive may publish less often; a small label with a catalog ready may launch with more entries. Choose numbers after estimating the work, and define “done” by quality as well as quantity.
Use a range when the work is uncertain
Research and permissions rarely obey a tidy calendar. When a format is untested, set a minimum and an optional stretch: one complete interview by the review date, with a second only if transcription and approval take less time than expected. The minimum must be worthwhile on its own. Do not let the stretch goal become a public promise by accident.
You can also limit the initial research phase. Once that time is up, decide whether there is enough verifiable material to proceed. With obscure recordings or short-lived events, scattered references can suggest a story without supporting its claims. Narrow the piece rather than filling gaps with confident prose.
Define quality safeguards for music coverage
Coverage of noise, ambient, drone, electroacoustic work, or field recordings needs time for accurate attribution. Keep an artist’s description distinct from your interpretation. Confirm release titles rather than trusting ambiguous file names, and say when a date or location cannot be verified. Speed is no substitute for those checks.
Make room for rights and consent, too. Owning a cassette does not grant permission to upload its audio or artwork. Recording an event does not establish that everyone involved wants the performance posted. Keep a record of what you may use and who supplied it. If approval is pending, publish without the asset or hold the page.
Accessibility belongs in the workflow. Alt text can describe meaningful details in artwork or performance images without pretending to describe the sound. A short written account beside an audio excerpt helps someone who cannot listen at that moment decide whether the page is relevant. Include this work when you estimate your publishing pace.
Review the goals without chasing every signal
Choose review dates before launch. Monthly checks suit operational problems such as broken pages and unanswered messages. An editorial schedule may need three months before you can judge whether it is manageable. Changing course after every quiet week makes it hard to learn anything.
At each review, compare the plan with the work done. Note finished pieces, actual hours, recurring delays, requested corrections, and problems readers reported. Look for causes, not someone to blame. If interviews consistently need more editing than expected, revise the estimate or the format. If readers keep asking for information that is already there, revisit the navigation or wording.
Analytics can help, but collect only what you need and explain your data practices plainly. Figures for small audiences are noisy: a mention in a message thread may bring a brief spike without indicating lasting demand. Look at longer patterns alongside direct evidence, such as a reader finding a release credit or a musician reporting an error you can correct.
Sometimes the right move is to retire a goal. A news section needing daily attention may not suit a two-person archive. Keeping it alive at the expense of verified entries helps neither the project nor its readers. Record why you stopped, remove stale promises, and put those hours toward the primary objective.
A first-quarter plan with room to change
For a site starting from nothing, month one might cover the minimum useful structure: a purpose statement, core pages, one tested content template, and a short list of publishable material. Month two can test the production pace with one or two complete entries. In month three, use what you learned to set a repeatable schedule and fix what slowed you down. This is an example, not a required timetable.
Keep a simple document with columns for goal, owner, next action, due date, and evidence of completion. For unfamiliar tasks, add “hours spent.” Once the first feature is live, record research, editing, permissions, and uploading time separately. Use those figures—not the original guess—to set the next publication date.