“Japanese noise cassette” could be a request for a format definition, help identifying a tape with an unreadable spine, or a place to buy one. A broad history is unlikely to settle any of those questions. Before drafting, decide which task the searcher is trying to complete and whether the journal has the evidence to help.
Search intent is the purpose behind a query, not a fixed property of its words. Short phrases leave more room for interpretation. “Japanese drone” might call for an introduction to sustained sound; “Japanese drone cassette hiss or instrument” points to a particular listening problem. Working out the likely task helps an editor choose the scope, structure and sources before settling on a headline.
Separate the subject from the task
A subject is what the page concerns; a task is what someone needs the page to do. “Field recordings in Japanese experimental music” names a subject. “How can I tell whether a sound is a field recording?” asks for a method. A knowledgeable essay can still fail that reader if it offers no criteria they can apply while listening.
Conventional intent labels—informational, navigational, commercial and transactional—are a start. A search for a named label’s official page is navigational; a request for current cassette availability may be transactional. But “informational” can mean a definition, a listening method, historical context, a comparison or help with uncertain evidence. Those are different assignments.
One reader may move through several tasks in minutes: look up what a drone is, search for ways to hear changes within a sustained tone, then investigate an unfamiliar name printed on a tape. Treat those as separate moments rather than assigning the reader a permanent “beginner” or “expert” identity. A specialist journal can serve both levels when each page makes its purpose clear.
Read the wording for evidence, not certainty
Query wording offers clues. “What is,” “how to listen,” “difference between,” “discography,” “track list” and “where to buy” suggest different outcomes. A named release with a catalog number points to a narrower identification task than a genre term alone. An unexplained code might be a filename, a label reference, an error or something unrelated; its appearance alone cannot establish what it means.
Before outlining, make a short intent note:
- Likely task: What would count as a useful answer?
- Reader’s starting knowledge: Which terms need defining?
- Required evidence: Would the answer need audio, packaging, documentation or firsthand reporting?
- Uncertainty: What cannot be established from the available material?
- Out-of-scope needs: Is the searcher asking for live inventory, downloads or a definitive identification the journal cannot provide?
That note is a working hypothesis, not a claim to know every searcher’s mind. For an ambiguous query, set down two plausible tasks and test both against the evidence. If neither can be answered responsibly, the phrase may not warrant its own article.
Check what existing results answer—and leave unanswered
A search results page shows how a query is currently being interpreted. Look at the titles and page types, then open the results rather than relying on snippets. Are they explainers, shop listings, forum discussions, artist pages or archives? Do they answer the apparent question? A product page appearing for a broad phrase does not mean every reader wants to buy something.
Results change with time, location and wording. They show how a search system handles a query, not what the journal ought to publish. An archive entry may appear prominently yet leave provenance unexplained; a discussion thread may raise a useful question without supporting its proposed answer. Describe the gap exactly. “Available pages list the cassette but do not explain how the catalog number was verified” is more useful than “no one covers this.”
Choose a page type that fits the need
Intent should determine the form of an article, not just the terms it uses. Each task calls for a different presentation of evidence.
| Reader task | Useful article form | Evidence to prioritize |
|---|---|---|
| Understand a term | Definition with boundaries and examples | Clear descriptions of audible or documented features |
| Learn to listen | Step-by-step listening guide | Observable changes in sound, with limits on interpretation |
| Identify an item | Careful identification note | Spine text, catalog number, packaging and provenance |
| Compare approaches | Focused comparison | Consistent criteria applied to both subjects |
| Find current availability | Time-sensitive listing, if maintained | Fresh, directly verified information |
A listening guide could begin with the first seconds of a sustained sound, then follow changes in pitch, texture and room noise. An identification note should put the marks on the object near the top and separate printed information from later inference. Availability is different again: an undated article that nobody maintains is a poor answer to “where can I buy it now?”
Some queries carry more than one possible task. “What is Japanese ambient music?” could invite a definition, a historical overview or listening recommendations. Choose the primary question and include only the context needed to answer it. Give another question its own brief if it deserves depth; otherwise the journal may end up repeating an existing piece under a slightly different headline.
Match the promise of the title to the answer
A title makes a promise. “How to Identify an Unmarked Noise Cassette” calls for checks a reader can use, not an atmospheric account of collecting. “What Is a Field Recording?” owes the reader a definition before extended interpretation. If documentation is missing, the title must not suggest a settled attribution.
Try writing the first factual paragraph and the first two section headings under a proposed headline. If the paragraph takes several detours before addressing it, narrow the title or reconsider the task. Put the immediate answer early; a reader seeking a definition should not have to work through a long cultural preface first.
Precision keeps an article from claiming more authority than it has. “Signs that a sound may come from a field recording” allows for ambiguity. “How to prove a sound is a field recording by ear” promises more than listening alone can usually establish: processing, synthesis and recording conditions can obscure a sound’s origins. The headline should be no more certain than the strongest evidence beneath it.
Let intent determine research and safeguards
The task changes where research begins. For a listening question, return to the audio and separate observation from interpretation: a repeated scrape is audible, but its source may not be identifiable. For an identification question, inspect reliable documentation and record whether a name appears on the physical object, in an archive description or only in an unsourced repost. When discussing DIY circulation, distinguish a documented practice from a general possibility.
A search query cannot make a thin record conclusive. Material on poorly documented tapes may contain copied errors, inconsistent romanization or codes detached from their original context. The journal’s discussions of the unresolved “wasted f520” entry in Japanese noise archives and the undocumented tapes associated with the “z2 3” code show why an obscure string needs provenance checks, not a confident story built around it.
When evidence runs out, say where. “The printed text is legible, but the performer credit is not verified” tells readers what they can use. Absence of evidence is not evidence of absence: failing to find a release in the sources consulted does not establish that it never existed. That distinction matters most when the reader has come to resolve an attribution.
Decide when one article is not the answer
Sometimes the right answer is a direct resource, not another essay. A venue address needs current venue information. Someone searching for an artist’s official page does not need a journal post placed in the way. A named release may need a catalog record before it needs interpretation. Respecting the task can mean deciding not to publish a page.
Even a query that merits an article needs limits. A piece on “how to listen to Japanese noise” could address volume safety, texture, duration and playback context. Label histories, collecting advice and festival etiquette belong to other questions. Leaving them out makes room for concrete examples and careful qualifications.
Put the boundary in the brief: one sentence for the reader’s primary task, one for the answer the article can substantiate, and one for what it will not attempt. Then list the observations or documents each section needs. That is firmer ground than starting with a genre-sized heading and filling it with whatever research turns up.
Take a proposed piece on “how to tell room sound from tape hiss in a drone recording.” It could offer audible clues without promising certainty about the source: compare steady broadband noise with changes that seem to follow the recording space, and acknowledge that processing can blur the distinction. During editing, mark every sentence that identifies a sound source. Can the recording—or its documentation—support each one?