A Finnish thrash demo can have the right title in an archive post and still carry the wrong year: the date may belong to a later reissue. An audit needs to catch that distinction, but also the unsupported festival appearance, the dead reference, and the page that is hard to read on a phone. Begin by listing the published posts. Then check what each one actually tells its reader.
Build an inventory before judging the writing
Give each post a row in a spreadsheet or database. Record its URL, title, publication date, last substantive update, author or editor, category, format, and main subject. In a music archive, note the band, release, venue, festival, or period covered. A detailed release history and a short concert recollection should not be judged against identical expectations.
Include a status field for live, draft, redirected, or removed pages, and note which URLs receive internal links. If you have analytics, record page views and entry pages over a consistent period. Low traffic does not mean a post lacks archival value; a careful account of a scarce independent release may serve a small readership well.
Keep observations apart from decisions. “Needs verification” describes the post as it stands; “request a scan of the original insert” names the next action. That separation makes the audit easier to revisit.
Check the page as a historical record
Claims, dates, and editions
Mark statements a reader might take as settled fact: lineup, recording location, release sequence, label, tour route, or festival billing. Record the evidence for each. A dated flyer supports an advertised concert, but does not prove the band performed. A contemporary review may document a show yet get the lineup wrong. Note contradictions rather than quietly choosing the neater account.
For physical releases, separate the original issue from later pressings, compilations, and digital listings. Does a year refer to the recording, the first release, or a reissue? The discography overview on Wikipedia explains the general distinction between release types; a particular band’s history still needs evidence from its own primary materials.
Check the wording, too. “The band played across Europe” overstates the case if only a few dates are documented. “A surviving flyer advertises a show in Germany” makes clear what the evidence establishes. Do not turn fan recollections into certainty or repeat rumors about musicians.
Sources and permissions
For each quotation, photograph, scan, and audio excerpt, record where it came from, how it is attributed, and whether you have permission to use it. Citation and permission are separate: a source may support your description of a sleeve without giving you the right to publish a full scan. Check that external references still lead to the intended material. If a page has disappeared, keep a clear citation to its identifiable title, author, and date where possible.
Flag links offering unauthorized recordings rather than treating them as archival resources. When audio matters to a post, describe the release and, where appropriate, direct readers only to legitimate listening or purchasing options.
Assess what each post does for its reader
Write down the question each post answers. “When did this band first release these tracks?” needs a different treatment from “What did its live sound draw from classic thrash?” If the answer is buried beneath several paragraphs of background, revise the opening. If a headline promises a complete discography but the post covers only studio albums, narrow the headline or document the missing formats.
Explain terminology where a reader needs it. Someone unfamiliar with tape trading may need a brief definition. A collector comparing editions may need matrix or catalog-number information, but only if it can be verified and helps distinguish the releases. Check for posts that tell the same story twice: one well-supported account can serve as the main reference, while the other tackles a different question.
Record gaps in coverage without assuming each one calls for a new post. Compare the inventory by band, period, release type, and live activity. Several album reviews and almost no accounts of independent demos suggest an imbalance, but available evidence should guide coverage—not a target number of pages per category. For a closer look at what public accounts can leave out, Finnish Thrash and the Limits of Mainstream Media Coverage addresses that problem.
Inspect structure and technical condition
Read each page on a narrow screen and on a desktop. Do headings describe the sections beneath them? Are paragraphs manageable, images given meaningful alternative text, and tables understandable without horizontal guesswork? A table may make a documented chronology easier to check. An uncertain sequence usually needs prose explaining where the evidence runs out.
Record missing images, broken internal links, redirects to unrelated pages, and references whose anchor text no longer matches the destination. Check for a descriptive title and useful excerpt or meta description, but put historical accuracy first. A polished search result cannot fix an unsupported release date.
A compact audit row can hold the checks together:
- Identity: URL, title, subject, format, and dates.
- Evidence: key claims, supporting sources, contradictions, and permission questions.
- Reader value: the question answered, missing context, overlap, and coverage gaps.
- Usability: headings, images, mobile layout, and link condition.
- Decision: retain, correct, expand, combine, redirect, or remove, with a named next action.
Prioritize repairs without erasing the record
Rank problems by consequence, not just by how quickly you can fix them. Wrong attribution in a widely cited post matters more than an awkward heading. A dead citation for a disputed concert date matters more than a dead link in a general reading list. Note both the seriousness of the problem and the work needed to resolve it. While research continues, an unresolved claim may need a visible qualification.
Combining similar posts may help readers, but keep distinct firsthand accounts and their dates rather than folding them into one anonymous narrative. Before redirecting or removing a page, check for unique citations, photographs, or comments that need a documented home. Keep an internal record of what changed and why, especially if a corrected release chronology appears in other posts.
Set a review trigger for claims that new evidence could change: a newly found flyer, an authenticated sleeve, or a documented correction from someone directly involved. For a disputed demo date, an audit entry might say: “Post says 2010; insert scan appears to say 2009; verify whether the dates describe recording and release separately; leave both attributed until resolved.”
