A rival practice may have ten pages on completed buildings but nothing about what a client needs to decide before a planning application. That omission is worth investigating, not automatically worth an article. Do clients face the decision often? Is dependable guidance hard to find? Can your team explain it from project experience?
Competitor research is most useful when it compares the answers a prospective client can find. For an architecture practice, those answers may concern site feasibility, approval routes, construction costs, accessibility, building operation or design trade-offs. The point is not to copy another firm's editorial plan. It is to find decisions that remain poorly explained and help clients make them.
Set the comparison boundary first
For this purpose, a competitor is any source a client might consult instead of your website at a given project stage. That includes other architecture practices, but may also include engineering consultancies, planning advisers, public agencies and developers publishing detailed guidance. A luxury-house specialist is a weak comparison for a practice serving municipal schools, even if both websites feature the word “architecture.”
Choose a small group of sources based on the services and locations you actually serve. Five to eight is often enough for a first review. Include close competitors and authoritative sources that shape readers' expectations for accuracy. Note each source's audience, building types and geographic scope, so a gap in one market is not mistaken for an opportunity in another.
Use publicly available material: articles, project pages, FAQs and navigation menus all show what a source explains. You do not need private client documents, restricted portals or copied project drawings. Save the page address, its publication or update date if shown, and the date of your review. The page may change later.
Map subjects to decisions, not just keywords
Categories such as “sustainability” or “commercial design” are too broad to reveal much. Break them into questions linked to decisions. A prospective clinic owner may need to compare refurbishment with a new building, understand how clinical adjacencies affect the plan, or establish who coordinates specialist equipment requirements. A homeowner may need to know when to commission a site survey or which choices must be fixed before pricing.
In a research sheet, give each distinct question its own row rather than creating a row for every competing page:
| Field | What to record |
|---|---|
| Client decision | The choice or action the reader is trying to make |
| Project context | Building type, project stage and jurisdiction, if relevant |
| Existing coverage | Which sources answer the question and how specifically |
| Evidence needed | Drawings, cost assumptions, regulations or specialist review |
| Practice fit | Whether your team has relevant, publishable experience |
Group questions that differ only in wording. “What does a feasibility study include?” and “What happens in early-stage feasibility?” could be answered in one piece. “How does a flood constraint change the feasibility study?” may need separate treatment because it calls for different evidence and decisions.
Read competing pages for usefulness
Titles and search results tell you which subjects competitors mention. Read the pages to see what they actually answer. Does the content state its assumptions, distinguish common cases from exceptions, and give the reader a practical next step? An article titled “How Much Does a School Cost?” may offer a generic price range without explaining how site works, gross floor area, servicing, phasing and local procurement affect an estimate.
Look for missing depth and missing perspective
A gap need not mean that no page exists. A page may be too general, written for the wrong reader or disconnected from the stage at which the decision arises. A project page might show a finished façade without explaining why the design changed after a daylight assessment. A technically accurate article about a regulation might still leave a client unsure what to give the design team.
Record strong coverage, too. If a public authority provides clear, current application instructions, rewriting them adds little and may quickly become inaccurate. An architecture practice can instead explain how those requirements affect the design programme and direct clients to the authority for current rules. The opportunity lies in applying your expertise, not duplicating official guidance.
Test the opportunity against real client evidence
A subject missing from rival websites is only a weak signal. Check candidate topics against questions raised in inquiries, briefing meetings and post-project reviews. Ask project leads which misunderstandings repeatedly delay decisions. Does the concern recur across projects, or did it arise from one unusual site?
Suppose several firms discuss net-zero ambitions but say little about maintaining building systems after handover. If facilities managers regularly ask your team about equipment replacement access, controls documentation or metering, there is more reason to address the subject. An article could explain which operational decisions belong in the brief and which need input from the future operator.
Separate publishable insights from project-specific claims
Architecture content often touches regulated, contractual and financially consequential matters. Sometimes competitors leave a question unanswered because it cannot responsibly be generalized. Approval requirements vary by jurisdiction and site; construction estimates depend on scope, procurement, market conditions and the available design information. Explain the variables and the decision process without suggesting that one cost or timeline applies everywhere.
Before drafting, establish what your practice can disclose. An anonymized example may show how a site constraint changed a layout, but check that combined details cannot identify the client or project. Do not publish confidential budgets, tender information or drawings without permission. Ask the relevant architect, engineer, cost consultant or planning specialist to review technical statements within their remit.
For regulatory subjects, name the jurisdiction and check the rules at publication. A comparison of routes to permission should make clear that the applicable route depends on the proposed works and local authority requirements. If those limits cannot be explained clearly, narrow the article's scope rather than relying on a vague disclaimer at the end.
Rank gaps by value and feasibility
Prioritizing topics helps prevent “no competitor has written about it” from becoming the sole selection test. Give each candidate a score from one to three for relevance to client decisions, frequency of the question, strength of your evidence and the consequences of misunderstanding it. Also note the technical review and future updates it would need. The scores support a discussion; they do not predict readership or inquiries.
- High priority: A recurring client question with meaningful design or cost implications that the practice can answer with clear examples.
- Investigate: A plausible gap supported by competitor review but not yet by client conversations or project records.
- Defer: A topic outside the practice's expertise, too dependent on unpublished information, or better answered by a current official source.
For example, a practice might find little useful coverage of loading and servicing at mixed-use sites. If its teams regularly resolve conflicts between delivery access, pedestrian routes and ground-floor uses, they have both practical evidence and an audience for the explanation. A gap concerning specialist laboratory ventilation is different: without relevant experience or a qualified reviewer, that practice should not take it on.
Choose a format that closes the gap
Match the format to the question. A staged checklist can show what a client should gather before a feasibility review. A comparison table can distinguish refurbishment constraints from new-build opportunities without claiming either is always better. A diagram may explain site circulation more clearly than prose. A project account can trace a decision if it includes the constraint, options considered and reason for the chosen approach, rather than only the finished result.
Not every gap needs a new blog post. If visitors cannot tell whether you undertake occupied-building refurbishments, a clear service-page description may be more useful. If an existing article already answers most of the question, add the missing section and check the whole piece for accuracy instead of publishing a second page on the same subject.
Link related material when it helps a reader make the decision. An article on early-stage site access could explain how entrances relate to surrounding streets, while the discussion of building design and urban mobility at the street edge provides context for assessing that interface.
Review results without treating traffic as the only test
After publication, look at the questions the piece brings in. Inquiry notes may show that clients better understand the scope of feasibility work; a project lead may spend less time correcting a recurring misconception. Website data can show whether readers arrive through relevant service pages and move to useful next steps. A specialist article can still be valuable with modest traffic if it supports a consequential decision.
Set a review date for material affected by regulations, pricing assumptions or changes in practice. Keep the research sheet with the article brief so the next editor can see why the piece was commissioned and which claims need checking. At the next research session, pick one recurring question—who supplies existing-building survey information before concept design, for instance. Record which competing pages answer it, what remains unclear and who on your team can verify the answer.