A festival listing may have the right date and lineup, yet still tell readers a Finnish thrash band is “playing this summer” years after the show. The listing belongs in an archive; the invitation does not. A content audit catches that difference by asking what a page claims, what supports it, and whether its wording still makes sense when someone reads it later.
For an archive of Finnish thrash metal from the late 2000s through the mid-2010s, old does not mean irrelevant. A disbanded group, a sold-out independent release, or a past European tour may be central to the record. The work is to keep that history accessible without making it sound current—or tidying away genuine uncertainty.
What an audit actually examines
A content audit reviews published pages and the records behind them as a group. It goes beyond fixing a typo or adding a photograph. Across a site, an editor might find conflicting release dates, missing source notes, duplicate band entries, outdated availability claims, or event titles that fail to name the year.
The unit of review is usually a page or a defined group, such as every release by one band. For each, record its purpose, the claims most likely to change or be challenged, the available evidence, and the action needed. The result should be a set of decisions, not merely a URL count.
Relevance takes different forms. A release entry helps collectors identify an edition. A concert account gives a date and venue while making the limits of its evidence clear. An introduction lets newcomers find deeper records without hitting dead ends. None requires pretending the scene stood still.
Set a review schedule based on the claim, not the page count
Reviewing every page each month wastes time; leaving them untouched for years lets avoidable errors accumulate. Sort pages by how quickly their claims can go stale. An event announcement needs attention soon after the show. A historical release entry may need only an occasional source check, unless a new edition or reliable document sheds light on a disputed detail.
- Time-sensitive pages: announcements, submission instructions, contact details, and statements about where recordings are available. Check them frequently, especially after a stated deadline or event.
- Core reference pages: band histories, discographies, festival histories, and tour accounts. Plan a deeper review at a manageable interval, and reopen them when substantial evidence appears.
- Interpretive pieces: articles on sound, aesthetics, or local context. Check that their examples still support the argument and their links lead to the records named in the prose.
- Low-traffic records: obscure releases and small shows. Give them a review path too. Few readers does not mean less care is needed.
Keep the schedule small enough to follow. An archive might review one batch of related records each month while leaving room for urgent corrections. More important than the precise interval is a record of when a page was last reviewed and why it is due again.
Start with an inventory that answers editorial questions
A spreadsheet or editorial database is enough. List each page’s title, URL, type, historical period, last substantive review, reviewer, and proposed action. Add a brief evidence note: “physical sleeve checked,” “venue archive consulted,” or “date awaiting confirmation.” “Updated” says little about what was checked.
Group entries by relationship, not just format. A band profile, demo listing, interview, and festival appearance may all repeat the same lineup or release claim. Reviewing them together brings disagreements into view. If the discography calls a recording a demo and the band history calls it an album, inspect the evidence before making the labels match.
Use a decision column with distinct outcomes
“Needs work” will not help much at the next editing session. Give each item a usable action:
- Keep: the page serves its purpose and its important claims have been checked.
- Correct: a statement is wrong or needs qualification.
- Expand: a meaningful gap can be filled with supported material.
- Consolidate: overlapping pages would work better as one record, with their references preserved.
- Retire or archive: an obsolete utility page has no continuing editorial role, while historically useful material remains identifiable.
Traffic alone should not decide the outcome. A little-read account of an independent release may be the only carefully documented entry for that edition. A popular introduction, meanwhile, may need urgent correction if it spreads an unsupported date across the archive.
Check evidence before polishing prose
When pages conflict, it is tempting to make their wording consistent and move on. That gives the site a smoother surface without improving the record. Start with the claim. For a release date, inspect the copy or contemporary documents the archive has, and separate the recording date, first issue, later pressing, and digital reissue. For a performance, separate an advertised booking from evidence that the show took place.
A flyer records how a concert was announced, not necessarily its final lineup. A sleeve shows the credits printed on that edition, but may not settle who played on the recording. Contemporary interviews add context, though memory and promotional language can affect them. Where it matters, tell readers what kind of evidence supports a claim.
If credible records disagree, preserve the discrepancy rather than pick a winner without support. A release entry can explain that one edition prints one year while a contemporary announcement gives another. That helps a collector more than a date silently changed by successive editors. Keep private notes on what was checked, so the next review does not have to begin again.
Source review also guards against accidental copying. Verify the facts, then describe a record’s sound, packaging, and place in the scene in the archive’s own words. Promotional phrasing has a way of making distinct bands sound alike.
Separate historical relevance from current availability
“Available now” ages badly in coverage of independent music. Small pressings sell out, official stores change, and bands remove uploads. None of that makes the release itself irrelevant. Keep lasting details—format, track listing, credits, artwork, edition information—separate from purchase or streaming claims that need frequent checks.
Describe former offers and events in the past tense, with dates. If an official source no longer carries a recording, do not substitute an unauthorized copy. The archive can identify the release and specify which edition it examined without pointing readers toward illicit distribution. A past festival announcement can likewise remain online, provided its title and opening lines make the year unmistakable.
Audit the paths between related records
Pages can be accurate individually and still fail readers together. A band profile may lead to a discography missing a demo; a festival history may mention a performance without connecting it to the band record. During a topical audit, follow a few likely paths: band to releases, release to edition notes, and festival appearance back to the artist.
Check link text along with destinations. “The 2012 cassette edition” is more useful than “more information” when two versions exist. After consolidating pages, update their references so readers are not left guessing whether two titles describe the same recording. For a separate look at structural problems before publication, Before Launching a Finnish Thrash Metal Archive covers mistakes at the launch stage; a recurring audit checks whether similar problems have appeared in the live archive.
Give each page type its own checklist
A universal checklist misses details that matter in music records. Start with a shared baseline—clear title, accurate dates, supported claims, readable text, and working internal references—then ask questions suited to each page type.
| Page type | Questions to ask during review |
|---|---|
| Band profile | Are active years qualified? Are lineup changes tied to evidence and specific periods rather than presented as one permanent roster? |
| Release entry | Does the page distinguish the recording from its editions? Are format, label, and credits attributed to the copy or documentation checked? |
| Concert or festival record | Is the event date unmistakable? Does the page distinguish the advertised bill from a confirmed performance? |
| Tour account | Are locations and dates supported? Does the prose avoid presenting an incomplete itinerary as a complete tour history? |
| Scene essay | Do named examples support claims about sound or aesthetics? Are broad statements limited to the period and community examined? |
Leave room for interpretation. A description of thrash guitar tone or drumming can make a strong case without pretending to be a measurable fact. The question is whether the writer names the recordings at issue and avoids treating one band’s approach as typical of the whole local scene.
Prioritize corrections without erasing the trail
With limited review time, address errors by their likely effect on readers. A wrong year in a release title can make a collector confuse editions; that matters more than an awkward sentence. A claim that a band played a show it was only booked to play should come before minor formatting. Broken contact instructions also matter: they may stop someone submitting a correction.
Distinguish routine maintenance from a material correction. Punctuation rarely needs a public note. A changed release date, lineup credit, or account of a performance may warrant one. Keep the note brief: say what changed and why, without publishing the whole research log. Retain the earlier wording in the site’s revision history so editors can trace how the claim entered the archive.
Do not wait for a full audit to make a well-supported correction. Fix the affected page, flag related pages for inspection, and add the issue to the audit queue. That stops the error spreading while keeping the wider check in view.
Use reader behavior as a clue, not a verdict
Search terms, navigation patterns, and reader questions can point to confusing pages. Repeated searches for a release’s format may mean the listing buries its cassette or CD details. If readers often leave an introductory band page, the discography may be hard to find. These are prompts to inspect a page, not proof that its historical material should be removed or rewritten.
Handle direct corrections with care. Ask which edition, document, or other evidence supports the proposed change, then compare it with the archive’s records. A firsthand account may open a useful line of research, but recollection alone should not automatically overrule a contemporary document. Aim for a more precise claim, not the most confident version of it.
Keep the audit manageable and reproducible
Set the boundaries before starting a batch: all release entries linked from one band profile, say, or every page about a particular festival year. Record who reviewed them, which evidence they examined, what changed, and what remains unresolved. “Checked” is misleading if the reviewer only tested broken links.
A workable sequence is to export the inventory, choose a related batch, inspect claims likely to mislead, check connected pages, make supported edits, and log open questions separately. Add a review trigger where useful: a physical edition arriving, a verified correction, or an availability notice ending. Such a trigger may tell the editor more than an arbitrary calendar date.
At the next session, take one release entry and identify the exact edition it describes before touching the prose. If its sleeve, label details, and page title point to different versions, hold the listing back or qualify it clearly until the discrepancy is resolved.
