Turn Visitor Questions Into Better Music Pages

An editor sorts questions beside an event page

“Doors at 7” is on the event page, yet visitors keep asking when the music starts. The page may be accurate, but it still leaves out the detail they need to plan their evening. That repeated question is a cue to check the copy—not an automatic reason to add another item to an FAQ.

Collect questions without losing their context

Look beyond the contact inbox. Questions turn up in ticket-support messages, social comments, artist direct messages, venue calls and conversations at the door. Site searches may show different ways of asking the same thing. Record each question as closely as possible to the visitor’s wording, along with the page they saw and what they were trying to do.

For a music publication, “Who is playing?” might mean the lineup is missing, hard to find on a phone or unclear about which acts play on which day. For an independent artist, “Where can I hear the new release?” might point to an outdated profile link. Without that context, it is easy to mistake a broken path or an unclear page for a missing FAQ entry.

A simple working log is enough:

  • Exact wording: Keep the visitor’s language before editing it.
  • Page and task: Note whether they were reading, planning a visit, buying a ticket or seeking press information.
  • Current answer: Check whether it exists, is buried, conflicts with another page or has yet to be confirmed.
  • Owner and review date: Record who can verify the answer and when it needs another check.

Remove personal details from the log. A private message can reveal a gap without becoming public material or a quoted testimonial.

An editor sorts questions beside an event page

Decide what kind of change each question needs

Count repeated questions, but do not let frequency make the decision on its own. One question about step-free access may need attention sooner than several about a playlist. Group related questions, then consider how each gap affects someone trying to understand a story, make plans or use the site.

Fix the page before expanding the FAQ

Put essential answers where the task happens. Visitors should not have to open an FAQ to find an event’s location, age policy or confirmed performance times. If a festival sells both day tickets and passes, explain the difference beside the ticket information. The FAQ can handle exceptions; it should not hide the basic terms.

Sometimes the problem is not the answer but the page around it. If readers keep asking whether an artist profile is about a solo performer or a group, try a clearer heading or opening sentence. If they cannot find a review mentioned in a newsletter, check the link or the site navigation. Fix the obstacle rather than filing it under “Frequently Asked Questions.”

Use an FAQ for genuine exceptions

An FAQ makes sense for useful details that would interrupt the main page: whether re-entry is allowed, how a venue handles lost property or where to ask about an unusual access requirement. Keep standing policies separate from show-specific details. A venue-wide policy belongs on a maintained venue page; a change affecting one show also belongs on that show’s page.

Questions about stories and guides can point to reporting gaps, too. If readers ask how to tell whether a scene guide’s listings are current, explain how the guide is updated. Define an unfamiliar term where it first appears. Save a separate article for a question that needs more depth than the original piece can comfortably hold. Our guide to matching music coverage to search intent looks at the related task of working out what a visitor wants before writing a story.

Write answers that can survive a quick scan

Use words visitors recognize and answer the question first. “Can I leave and come back?” is easier to scan than “Information regarding re-entry.” If the policy changes by event, say that instead of offering a blanket yes or no. Someone checking access information needs the conditions and a contact route, not promotional copy about the atmosphere.

Be clear about what is confirmed and what is pending. “Set times have not been announced; this page will be updated when they are confirmed” is more helpful than an estimate that reads like a promise. Treat accessibility information with the same care: describe verified features precisely and provide a way to ask about needs the page does not cover. Do not infer a venue’s facilities from photographs or a previous event.

Match headings to the language readers use. A visitor may search for a “schedule” while an organizer calls it “set times.” Use the familiar word in the heading and introduce the specialist term in the answer if it helps. There is no need to publish several near-identical questions just to cover both phrases.

Check whether the change actually helped

After updating a page, watch for questions about the same task. Fewer repeat messages are encouraging, but silence is not proof: visitor numbers, event timing and contact habits may have changed. Check the page on a phone, ask someone unfamiliar with the event to find the answer, and see whether support staff still have to explain it. This fits with measuring what music readers actually need, rather than judging a page only by its views.

Keep the log tied to a review routine. Dates, ticket terms and performer details can change quickly; an answer that was accurate when published can mislead later. On longer-lived editorial pages, revisit definitions, links and references as the subject changes. According to Wikipedia’s overview of frequently asked questions, an FAQ pairs recurring questions with answers. On a live music site, each of those answers also needs a reliable source and someone responsible for keeping it current.

Start with one page and three questions from recent messages. For each, decide whether the answer belongs in the main copy, a short FAQ or a separate guide. If visitors ask “What time does the music start?” and the page lists only door time, put the confirmed performance time beside the schedule—or say plainly that it has not yet been announced.

Related posts