Blog Writing for Architects: Why Most Practice Blogs Produce Nothing — and What Changes When You Write for the Clients You Don't Have Yet

Blog writing for architecture practices works when it's structured around the questions prospective clients are already searching — not the project updates and award announcements that populate most practice websites. That applies whether your practice works on residential projects, commercial fit-outs, or a mix of both. The blog most firms have was built for people who already know them. This article is about the version that reaches the people who don't.

Why most architecture blogs generate no enquiries

The blog your practice has — if you have one — was probably built around what felt natural to publish: completed projects, award listings, a note about a new team member, a case study of a house that went well. This content is fine. It is not the problem. The problem is who it reaches.

Project updates and portfolio pieces are interesting to people who already know your practice. They validate the choice for a client who's considering you. They give former colleagues something to share. But they are not what a prospective client types into Google when they're trying to find an architect for a house extension, understand whether their commercial premises conversion needs a full planning application, or work out what an architect actually costs on a project of their scale.

RIBA's research on the future of architectural practice found that almost two-thirds of new commissions come from the reputation a practice develops through referrals and repeat business — specifically, 38% from repeat clients and 24% from word-of-mouth referrals, according to RIBA Business Benchmarking 2023. That network is real, but it only reaches as far as the people who already know you. And the referral network has a ceiling and a clock attached to it — it depends on the people who currently pass your name along still being active and still doing so.

Blog content that generates enquiries works differently. It reaches people at the moment they are searching for something your practice can help with — before they've engaged anyone. That is a structurally different audience, and it requires structurally different content to reach it.

The practices that get enquiries from their blog have figured this out. The ones that don't are still publishing project updates to an audience that already knows them.

What prospective clients are actually searching for

The specific queries vary by project type and sector, but the pattern is consistent: prospective clients search for orientation before they search for a provider. They want to understand the process, the cost, the risk — before they commit to picking up the phone.

Some of the queries that bring architectural practices into consideration — across both residential and commercial projects:

• "How much does an architect charge for a house extension UK?"
• "Do I need an architect for a loft conversion or just a draughtsman?"
• "Architect fees for office refurbishment UK"
• "Do I need planning permission for change of use from retail to office?"
• "What is permitted development for a rear extension?"
• "How long does a commercial building project take with an architect?"
• "What does an architect do on a small commercial project?"
• "What are the RIBA stages and what do they mean for my project?"
• "What questions should I ask an architect before hiring them?"

None of these searches mention a practice's name. None of them care about your last project. They are intent-driven searches from people who have a problem and are trying to understand it. An article that answers one of these questions well — written for the right search query, at the right depth — puts your practice in front of someone actively looking for the service you provide.

The content marketing for architecture firms guide covers the full strategic picture — clusters, topical authority, compounding. This article is about the more specific question: what does a blog post that actually ranks and converts look like when you sit down to write one?

What an architecture blog post that generates enquiries actually looks like

The gap between a post that produces nothing and one that generates enquiries is usually visible at the structural level before a word of the body is written. These are the elements that separate them.

1. A title matched to a real search query

Most architecture blog post titles are written from the inside: "Our Approach to Sustainable Design," "Behind the Scenes at a Planning Application," "What Makes a Good Brief?" These are interesting framings if you already know the practice. They are invisible to search because nobody types them.

A title matched to a real search query looks different: "How Long Does Planning Permission Take for a House Extension in Bristol?" or "Do I Need an Architect for a Change of Use Application — or Can I Do It Without?" The title contains the phrase someone is actually typing. It signals immediately to both the search engine and the reader that this article answers that specific question.

Getting this right requires keyword research — not guesswork. Tools like KWFinder and Ahrefs show you what people are actually typing and how competitive the existing results are. Google's own autocomplete reflects trending searches, though it doesn't show volumes on its own. A practice that picks topics by instinct will occasionally get lucky. A practice with a keyword map has a systematic view of which questions are worth answering and which aren't worth the effort.

2. An opening that answers the question directly

The first paragraph of an effective architecture blog post answers the search query. Not "in this article, we'll explore..." — the actual answer, in the first 100 words.

This serves two audiences simultaneously. The human reader, who arrived from a search result and needs to confirm quickly that this article delivers what the title promised. And AI search systems — Google's AI Overviews, ChatGPT, Perplexity — which often favour content that is clearly structured and easy to extract. A direct answer near the top can make the page easier for both readers and automated systems to understand; a post that opens with scene-setting prose is harder to parse either way.

Directly below the opening answer, a well-structured architecture blog post includes a Quick Summary block: three or four declarative bullets that capture the article's core findings. This gives AI systems and human readers a concise, self-contained summary to work with, although inclusion in AI results is never guaranteed. It also gives the human reader a fast orientation before they commit to reading 1,800 words.

3. Enough depth to actually answer the question

Many practice blogs rely on short updates or light case-study posts, which often lack the depth needed to answer complex client questions. That is not enough for the queries that generate enquiries. A question like "how much does an architect charge for a house extension UK?" cannot be answered well in 400 words. There are too many variables, too many caveats, too much the reader needs to understand to act on the information.

The articles that rank for competitive, intent-driven queries are typically 1,500 words or more — not because length is rewarded for its own sake, but because the question requires depth to answer honestly. Shorter content tends to rank only for low-competition, low-intent queries. The queries that bring in enquiries require the kind of thorough treatment that a practice principal genuinely knows how to give — but rarely has the time to write out in full, at the pace required.

4. AEO signals embedded throughout — not bolted on at the end

AEO — answer engine optimisation — refers to structural choices that can improve the chances a blog post is machine-readable and useful in answer-led search experiences, not just ranked by Google in the traditional sense. AI citations depend on many factors and cannot be guaranteed, but a practice that appears in ChatGPT or Google's AI Overviews when someone asks "how much does an architect charge for a house extension?" is reaching a buyer who didn't search for the practice by name — which is why it's worth building for.

The signals aren't complicated, but they need to be built in from the brief stage, not added as an afterthought. Structured heading hierarchy (H2, H3) that AI can parse. Named, primary-source citations inline in the body — at the point the claim is made, not collected in a footer. A genuine FAQ section at the end answering specific sub-questions the article's main body doesn't cover. Schema markup in the HTML that helps search engines understand the page's structure and content.

These signals don't require a separate process — they're properties of a well-structured article. But they need to be deliberate. An article written without them in mind will usually satisfy none of them cleanly. For a full breakdown of how the technical, local and content layers of search interact for practices, see the guide to SEO for architecture practices.

5. A clear path from article to enquiry

An article that generates traffic but has no clear path to contact is a reading experience with no commercial value. Every effective architecture blog post has a natural transition — at least once mid-article and again at the close — that moves the reader from understanding a topic to taking the logical next step.

For an architecture practice, that step is usually an initial conversation. The framing needs to match what the reader knows at that point in the article. A reader who has just finished a thorough answer to "how much does an architect charge for an office refurbishment?" or "do I need planning permission for this conversion?" and is now working out whether their project is viable needs to be told that a short diagnostic conversation is the right next step — not handed a generic contact button. The reader's situation is the opening; the practice's offer is the close.

How you go from "what should we write about?" to an article that ranks

Deciding to blog is the easy part. The harder part is identifying the specific topics worth committing to — and building a production rhythm that survives busy project periods.

A proper topic-finding process for an architecture practice starts with mapping the questions prospective clients ask at different stages: before they know they need an architect, when they're trying to understand whether a project is viable, when they're actively selecting a firm. Each of these stages produces different queries — and different articles.

The questions that generate the most valuable enquiries are usually one level more specific than the obvious ones. "Do I need an architect?" is a real query but highly competitive and often answered by AI before anyone clicks through. "Do I need an architect for a change of use application, or can a planning consultant handle it?" or "Do I need an architect for a permitted development extension, or just a structural engineer?" are more specific, lower competition, and the person asking is closer to commissioning someone. The same principle applies across project types — residential and commercial clients both search with specificity once they've identified a real project.

Keyword research is what reveals which of these more specific questions are worth answering and which aren't searched often enough to bother with. Without it, content production is driven by what feels right rather than what the data supports. Some of those instinct-led decisions will land. Most won't.

After topic selection comes briefing: agreeing the specific angle, the internal links, the commercial destination, the authority citations — before writing begins. The brief is where the article either becomes a rankable, conversion-oriented piece or drifts into generic territory. Most practices skip the brief stage entirely and go straight to writing. That's the process problem that keeps most architecture blogs producing nothing, even when the writing itself is good.

How long before blog writing starts generating enquiries for an architecture practice

There's no clean answer to this, and any firm offering a specific guarantee isn't being straight with you. In our experience, practices typically begin to see early organic search traffic within three to six months of consistent, well-structured publishing — assuming the content is built around real search queries and the site has reasonable technical foundations. Enquiries tend to follow traffic by a further one to three months, as rankings stabilise and the practice's topical authority builds.

These timelines vary significantly depending on keyword competition, the practice's existing domain authority, how many articles are published, content quality, and the technical condition of the site. They are estimates, not guarantees.

The important thing is the clock: it only starts when the first article goes live. A practice that decides to start in October may begin to see real movement by the following spring. A practice that keeps deciding to start never does.

Frequently asked questions