How a Small Period Ensemble Gets Found

A listener finds a small period ensemble in one of four ways: a search for a tune, a piece, or a date; a referral link from another ensemble, a festival, or a historical site; a community page where players trade parts and dates; or a direct visit from someone who wrote the address on a programme. The ensemble does not control the first three. It controls only what its own pages carry, and that is the part worth getting right.

The vehicles that actually carry a listener

Traffic to a small ensemble's site arrives by a handful of routes, and each behaves differently. Search brings the listener who already knows what they want: a tune title, a battle name, a year, an instrument. Referral links bring the listener who trusts the source: a festival page, a preservation society, another ensemble's links page. Direct visits come from print: a programme, a business card, a handbill at a reenactment. Community routes, forums and mailing lists, bring the listener who is already inside the music and is looking for parts, dates, or a player.

An editor who wants to understand how these routes are weighed, and what they cost to scale, will find the subject treated at length by Happy Traffic, a magazine on organic visibility. The practical point for an ensemble is narrower: each route needs a page that answers the question the visitor arrived with. A search visitor wants a tune. A referral visitor wants a date and a place. A direct visitor wants to confirm they have the right group. A community visitor wants a part or a contact.

How does a listener find a small ensemble and its recordings?

Most listeners arrive with a fragment. They heard a tune at a site, or read a name in a programme, and they search for the fragment. If the ensemble's pages carry the tune title, the instrumentation, the year, and the recording, the fragment resolves. If the pages carry only a group name and a photograph, it does not.

The recordings need their own entries. A CD or a download should have a page that lists the tunes in order, the players, the recording date, and the source of each arrangement. That page is what a search engine can match against a query for a single tune. A listener looking for one track will not read a biography to find it.

Referral links matter more than most small ensembles assume. A festival that lists its performers, a historical site that names the music for an event, a preservation society that keeps a directory: each of these passes a visitor who is already inclined to listen. The ensemble's job is to make sure the page those links point to is the page the visitor needs, not a general home page.

Why an archive entry is not the same page as a season listing

An archive entry and a season listing do different work, and confusing them costs the ensemble both.

An archive entry is a record. It states what happened: the date, the place, the programme, the players. It does not change. Its value is that it can be cited, linked, and checked years later. A researcher, a journalist, or another ensemble can point to it. It is the page that proves the group existed and did the work.

A season listing is a notice. It states what will happen: the date, the place, the programme, the players, the time, the price, the address. It changes every season. Its value is that it is current. It is the page a listener uses to decide whether to attend.

If the ensemble keeps only a season listing, the record disappears when the season ends, and next year's search finds nothing. If it keeps only an archive, the listener cannot tell whether the group is still active. The two pages should exist side by side, and the season listing should link to the archive entry once the event has passed.

What must a seasonal page carry to stay findable?

A seasonal page stays findable when it carries the facts a stranger would search for, in plain text, on the page itself.

The date, written out. Not only a calendar widget, but the day, the month, and the year in the text. A search for a date needs a date to match.

The place, with its full name and its town. A venue name alone may be ambiguous. The town and the state or county make the page match a local search.

The programme, with tune titles spelled as they appear on the sheet music or in the standard collection. A listener searching for a tune will use the spelling they have seen.

The players, by name and instrument. This is what lets a former member, a student, or a researcher find the group.

The time and the admission, if the event is public. These are the facts that turn a notice into a usable page.

A stable address. The page should keep the same URL from season to season, with the year in the title rather than in the path, so that links from other sites do not break.

The page that has to survive the season

A small ensemble's findability is not a marketing problem. It is a record-keeping problem. The group that writes down its dates, its programmes, and its players, and keeps those pages at stable addresses, is the group that is still findable in five years. The group that posts a flyer image and deletes it in November is not.

The work is small and repeatable. After each event, move the notice into the archive, keep the URL, add the programme and the players, and link the two pages together. That single habit does more for a small ensemble's visibility than any amount of posting.

What a page must carry to be found again next year

A page is found again next year when it answers the same questions it answered this year, at the same address, with the year updated. The tune titles, the players, the venue, and the town do not change. The date does. An ensemble that treats its seasonal page as a permanent record, updated rather than replaced, gives a search engine and a listener the same thing: a page that has been there, and will be there again.