A band entry mentions a demo, but the reader has to search again to find its release page. Link the title at its first useful mention, and that detour disappears. The connection also shows how the band, the recording and the archive’s evidence fit together. In a Finnish thrash archive, internal links earn their place when they follow relationships a listener or researcher would want to trace.
Link the relationship, not just the keyword
An internal link joins two pages on the same site. A band profile can point to a release because the band made it; the release can point back for lineup context. A documented show might connect to the participating bands, festival or venue, if those entries exist. The sentence around each link should make the relationship clear.
In an archive covering the late 2000s through the mid-2010s, the same name might appear on a cassette sleeve, concert flyer, video credit or contemporary review. Links help readers move among those records without mistaking them for equivalent evidence. A flyer establishes that a band was advertised for a show; on its own, it cannot verify every detail of what happened onstage. The linked entry needs to keep that distinction intact.
Nor can a link replace a citation. If an entry gives a release year, it needs evidence for that date. Sending readers to another page that repeats it does not settle the question. Internal links make the archive’s work easier to inspect, but weak documentation remains weak documentation.
Give each page a clear place in the archive
Navigation menus and links in the text serve different purposes. A menu might offer steady routes to bands, releases, shows and features. An entry can be more specific, connecting a release to details of its format or a festival appearance to a documented festival history. Readers following a name in the text should not have to return to the home page to continue.
Build around useful page types
Decide what each page type is meant to record before adding links. One workable arrangement is:
- Band entries for verified names, documented personnel, recordings and performance history.
- Release entries for track lists, formats, credited contributors and evidence for dates or variants.
- Show entries for documented lineups, locations and surviving promotional material.
- Context features for subjects that need more room than a catalogue entry allows, such as festival circulation or musical influences.
That does not mean giving every passing mention its own page. If all you can verify is a name and one sentence, a note in an established entry may be more useful. Create a separate destination when there is enough documented material to answer a distinct question, then link to it where that answer belongs.
Apply the same restraint to broad features. A festival essay may explain the setting for a band’s documented appearance, but it cannot prove the band played an event the essay does not mention. For a passage specifically about festival exposure, [how festivals helped Finnish thrash bands find new listeners](/festivals-finnish-thrash-metal-bands/) provides context. A show record must carry the evidence for a particular appearance.
Write link text that names the destination
People often scan an entry before reading it closely. The linked words should give them a fair idea of the destination. A release title works when it leads to that release’s entry; elsewhere, “the cassette’s format and credits” may tell the reader more than a link on “cassette.” Choose the wording for the page at hand, rather than repeating a favourite phrase across the archive.
The rest of the sentence counts, too. “The recording later appeared in another format” offers little to check. “The release entry documents the formats named on surviving copies” says what the reader can verify without claiming a complete pressing history. Even a well-worded link misleads if it points to the wrong subject: a band name should not lead to a general thrash essay merely because both pages contain that name.
Descriptive link text also helps people using assistive technology, who may encounter links apart from their paragraphs. Keep labels short enough to read comfortably. If nearby links sound alike but lead to different entries, make the distinction clear in the linked words.
Make the route work in both directions
A search result may take someone straight to a release entry, bypassing the archive’s indexes. That entry should lead to the band responsible and, when relevant, to a show or contextual feature. A visitor starting at the band profile needs a route to the recording. Every pair of pages does not need reciprocal links, but important connections should be accessible from likely starting points.
Take a hypothetical profile mentioning a self-released demo, a later CD edition and a festival appearance. It could link to both release entries and a verified show entry. The release pages could point back to the profile; the show entry could identify its documented lineup and link to the participating bands. A feature on cassette formats belongs one step farther away. Readers can follow the recording’s history without finding a format essay tucked into every band biography.
Chronology calls for care. A newer feature can interpret an older source, but the link should not present that later reading as contemporary testimony. Say what each page does: the archival item records what a source said at the time, while the feature considers it in later context. If a release date is disputed, mark the uncertainty on the release page instead of linking as though one unsupported answer were settled.
Prevent useful links from turning into clutter
Linking every repeat of a band’s name makes a paragraph harder to read. Put the link where it helps someone pursue a question. Once you have linked a band profile in a short section, linking it again in the next sentence rarely helps. In a longer feature, a second link may make sense when a different relationship comes up.
Keep links beside the claims they clarify. If a paragraph compares rhythmic choices, [listening to the drums in Finnish thrash metal](/finnish-thrash-metal-drumming-speed-groove-control/) belongs there, not next to a sentence about cover art. Its discussion of speed, groove and control should match what the surrounding text leads readers to expect.
Related-page blocks and category indexes are useful for browsing, but they cannot do all the work of a link in the prose. An index groups entries; a contextual link explains why two particular entries belong together. When space is tight, favour a connection readers might otherwise miss, such as a release variant documented on another page, over another route to a familiar category index.
Keep the structure accurate as the archive grows
Entries get renamed, merged and corrected. A link may still open after such a change yet promise a subject the destination no longer covers. Deleted pages leave dead ends. Redirects can keep an old route working after a move, but important links should point directly to the current entry when possible.
A practical review of an entry
- Identify the main subject. Check that the title and opening distinguish it from similar bands, recordings or events.
- Mark documented relationships. Note releases, shows, people and contextual subjects that already have useful entries.
- Check each destination. Make sure it supports what the linking sentence implies without overstating the evidence.
- Read the linked words alone. A scanning reader should be able to tell the destinations apart.
- Test the route. Open the links; look for outdated titles, broken pages or a missing return path on an important entry.
Start with common entry points, especially band profiles and release pages. Revisit older features when new documentation gives them a more precise destination. After adding a cassette entry, for instance, find the first clear mention of that cassette in the band profile. Link its title only if the new entry identifies the recording and explains what the surviving copy can establish.
