A search for “school building cost” could come from someone setting a construction budget, looking for a cost-per-square-metre benchmark, or trying to understand design fees. Treat those as the same question and a prospective client may leave with the wrong number and no idea how to use it. Before drafting, work out what decision the searcher faces and what information would help them make it.
What search intent means for a building project
Search intent is the purpose behind a query. In architecture and property, it often reflects a project stage: testing feasibility, comparing options, seeking permission, procuring a team, or dealing with an existing building. The same phrase can mean different things at each stage. Someone searching “clinic design requirements” might want an introduction to patient flow; someone else may need to identify the rules that apply to a particular site and service.
A useful working distinction is between learning, comparing, and acting. Learning queries call for explanations and definitions. Comparing queries need criteria, trade-offs and, sometimes, cost ranges with their assumptions stated. Acting queries may need a sequence of steps, a list of documents or help identifying the relevant authority. These are not rigid labels: someone can compare design approaches while learning which approvals apply.
Intent is not the same as subject. “Fire strategy for an office conversion” names a subject, but the person searching may really need to know whether a conversion is feasible before buying the property. A definition of fire strategy would miss that decision. A better answer would set out what information a competent specialist needs, which existing-building constraints could matter, and why a generic article cannot settle the question.
Investigate the query before choosing the page
Start with the exact wording, including modifiers. “How much,” “requirements,” “examples,” “near me” and a named jurisdiction all suggest different answers. Then inspect the results for the query. Look beyond headings: are the pages guides, official requirements, project examples, calculators or service pages? What questions do they actually answer? Results offer clues about reader expectations, though they can change by location and over time.
For regulated building questions, establish the jurisdiction before settling on an interpretation. The answer to “planning permission for a garden studio” may depend on location, site designation, intended use and building size. Results from another country are a poor basis for a local article. If a blog serves several jurisdictions, make the scope clear in the title or opening rather than presenting local rules as universal.
Search results are only part of the evidence. Compare them with questions raised in project enquiries and planning meetings, and by facilities teams and building users. An enquiry about “office refurbishment costs,” for example, may turn out to be chiefly about whether tenants can remain in occupation during the work. That conversation clarifies one person's problem; it does not prove everyone using the query has the same concern.
Test an intent hypothesis
Before writing, put your hypothesis in one sentence: “A property owner searching this phrase needs to decide whether to commission a measured survey before briefing a designer.” Then look for evidence against it. Perhaps the results mostly serve owners who already have surveys and want to know which drawings accompany an application. It is easier to revise the hypothesis now than rebuild the article later.
These checks help separate a real information gap from a topic that merely sounds relevant:
- Decision: What can the reader do differently after reading?
- Stage: What information might the reader already have, and what remains unknown?
- Scope: Does the answer depend on building type, jurisdiction, site conditions or occupancy?
- Evidence: What can be supported by documents, technical requirements or relevant project experience?
- Format: Would a checklist, comparison or worked example serve the need better than a broad essay?
Match the answer to the decision
Take “new school ventilation requirements.” Someone seeking compliance information needs the applicable standards and an explanation that requirements depend on location and project scope. A school operator planning a renovation may be more concerned with survey findings, existing plant capacity, room occupancy and disruption during installation. A parent searching the same terms may want to understand how ventilation affects everyday classroom use. A page can acknowledge all three, but it needs a primary audience and purpose.
Choose the format accordingly. A comparison of design approaches should explain when each might suit a project, not declare a winner. A cost article should distinguish construction cost from professional fees, surveys, approvals, contingency and, where relevant, operating costs. A process article should show which tasks can run in parallel and which decisions must come first. That specificity helps readers without suggesting a general guide can replace project-specific advice.
Take particular care with healthcare buildings, accessibility, fire safety and structural alterations. Someone may be using the article to decide whether to buy a property or open a facility. Explain what affects the decision, identify the professionals or authorities who must verify the answer, and do not present an illustrative example as an approval route. A reader's need for certainty is not a reason to publish an unsupported conclusion.
Separate a broad query from its narrower variants
“Designing a community centre” could cover site selection, spatial planning, public consultation, permissions and long-term maintenance. If search results and enquiries suggest readers mainly want early feasibility guidance, give that question a focused page. Feedback from building users once the centre is occupied could warrant a separate article. Covering every project stage in one place can bury the answer the reader came for.
A narrow page still needs enough context. Feasibility guidance may need to explain how staffing, servicing and maintenance affect the viability of a layout; it does not need to become an operations manual. Include what the reader needs for the immediate decision, and make the limits of that decision clear.
Handle mixed or uncertain intent honestly
Some queries have several plausible meanings. Someone searching “architect drawings for an extension” might want examples, an explanation of drawing stages, or a list of documents needed for approval. If no interpretation clearly dominates, use the opening to state what the page covers—for instance, drawings typically used to develop and submit a proposal, while noting that exact submission requirements vary. Headings can help readers find the stage that concerns them.
Shared vocabulary is not always a reason to combine tasks. “Hospital masterplan” might mean a long-term estate strategy or visual examples of completed projects. Those readers need different evidence. Address the need the publication can cover credibly, and consider a distinct page for the other if there is enough substance.
Check existing content before commissioning anything new. If a current page already answers the question but has an unclear title or misses a necessary distinction, improve it rather than publish a competing version. A separate page makes more sense when the intended reader, decision and answer format are materially different.
Check the draft against the original need
Once the draft is ready, return to the intent hypothesis and read the page without relying on its title. Is the central answer easy to find near the start? Do qualifications sit close to the claims they limit? Does the page say what information a project-specific answer would require? Give a colleague the query and draft separately, then ask what decision the draft helps them make. If their answer differs from the one you intended, revisit the opening or the scope.
In an article on “office conversion feasibility,” that check might expose a missing question: can the existing structure and services support the proposed use? Address that dependency before polishing the prose, and say plainly that it requires investigation of the actual building. The reader will know what to examine next, rather than mistake a general guide for a verdict on their property.