Content marketing for architects starts where the portfolio stops

A portfolio shows what you decided. It does not show how you decide, which is the part a prospective client is nervous about. Someone can spend twenty minutes on your project pages and still not know whether their 1950s house is worth keeping, what you need from them before the first sketch, or what happens when the builder’s price comes back over budget. Photographs cannot answer any of that.

A studio has four things it can publish: a guide that answers a question, a project story, a short explanation of one design decision, and practice news. Start with the guide. It is the only one of the four that gets found by someone who does not yet know you exist. Project stories back it up, short explanations feed Instagram and LinkedIn, and practice news is for people already watching you. You do not need all four in the same month.

The topics are already in your first-call notes

After every first meeting, write down the question that took you longest to answer, in the client’s words. “What happens if the builder comes back over budget?” is a better title than “Our collaborative design philosophy”. Do that for two months and you have a year of topics.

Search Console is the second source and it costs nothing. It lists every query your site has appeared for, including the page-three ones where nobody clicked. If you are sitting at position 34 for “raising a queenslander cost”, a proper page on that topic will rank faster than something you picked out of a keyword tool, because Google already associates you with it.

The third source is your enquiry form or fee estimator. If people keep stalling on the budget step, budget is your next guide. Before you commission anything, write down two things: the decision the reader is trying to make, and the page you want them on afterwards. If the only next step you can think of is “contact us”, choose a different topic.

Twenty architecture blog ideas, grouped by what the client is deciding

These are starting points for an Australian practice. Take the ones you can answer from completed work and drop the rest. The line after each title is the decision the reader is trying to make.

  • Renovation: should we renovate or knock down and rebuild? The first question every owner of a tired post-war house asks.
  • Renovation: what to bring to a first meeting with an architect. Turns a vague enquiry into a usable brief.
  • Renovation: how to get northern light into a house facing the wrong way. Options, and what each costs in floor area.
  • Renovation: can a Queenslander feel modern without losing its character? Shows how you handle old fabric and new.
  • Renovation: keeping a usable back yard when you extend. The trade-off nobody raises until the site plan appears.
  • Renovation: when should the builder join the conversation? Explains your process and why you run it that way.
  • Renovation: the early estimate came back high, so what now? The scope decisions you help clients make.
  • New home: how to write a brief for a custom house. Helps owners describe how they live, not how many bedrooms they want.
  • New home: what to check before buying a difficult block. Slope, easements, overlays, access, and who to ask.
  • New home: how orientation changes the plan. Explain it through a project where it obviously did.
  • New home: what is inside an architect’s fee proposal. Stages, deliverables, exclusions and the consultants you do not cover.
  • New home: why two houses of the same size cost different amounts. Scope and specification, without quoting a rate per square metre.
  • New home: what your architect does during construction. Most clients have no idea, and they are paying for it.
  • New home: how to compare two early design options. Gives a client a way to judge more than which one is prettier.
  • Development: what a preliminary site assessment actually tells you. Purpose, inputs and limits.
  • Development: what an architect needs before testing a concept on a site. Helps a developer turn up prepared.
  • Development: the difference between a concept and an approval. The stages, with no promised outcome.
  • Development: when to bring in a town planner. Where your advice stops and theirs starts.
  • Development: how a small infill project can sit well beside its neighbours. Design reasoning, using work you are allowed to publish.
  • Development: what makes a feasibility brief useful. Separates the objectives from the assumptions still to be tested.

Write one project story properly, then cut it up

Do not ask the project architect for an essay. Interview them for half an hour instead. What did the client need? What made the site or the brief hard? Which option did you reject, and why? What changed between the first sketch and the finished house? Someone else turns those answers into brief, constraint and response. The architect checks it for accuracy and signs it off.

One story then feeds everything else for the month. Instagram gets a single moment: the plan comparison, the reason the window moved, a photograph of a room being used the way it was designed to be used. LinkedIn gets the professional angle, usually the coordination with the builder or how the brief shifted. A short video is the architect talking beside a sketch for ninety seconds. No drone shot required.

Credit the builder, the engineer and the photographer. Get permission before posting a site in progress. Send every extract back to the full guide or project page. Pasting the whole article into a caption just makes a long caption.

What a month costs you in hours

Allow six to eight hours across the practice for one guide: thirty minutes of the architect’s time in the interview, thirty minutes checking the draft for accuracy, and three to five hours of writing, images and uploading by whoever owns the job. Anything touching cost or planning rules takes longer, so plan for that rather than discovering it in week three.

Book the interview before you commission the writing. Hand the writer the question, the reader, the service page it should lead to, the project they may reference and anything that cannot be said. Ask for an outline first if the topic is complicated.

Put a name against each stage: architect, writer, approver, publisher. If approval keeps stalling at the same desk, either the guide is too ambitious or that person is the wrong approver. A short piece that gets published beats a calendar full of drafts.

What to look at after six months

Three things. Which guides bring people in from search and for which queries. Whether those readers go on to a service page, a project or the enquiry. And whether new enquiries mention anything they read. Ask that last one on the first call, because people will tell you.

Roughly 70% of Invilla Architecture’s organic clicks land on guides rather than project or service pages: Queenslander renovations, knock-down rebuild costs, demolition costs, natural light. None of those pages sell anything. All of them lead to the studio’s fixed-fee estimator.

When a guide brings traffic but the wrong enquiries, the topic is the problem, not the writing. Push it towards the projects you want. When a guide is flat after six months, check whether anything on your own site links to it before you blame the topic.

Frequently asked questions

What should an architecture firm blog about? The questions clients ask before they commission you: briefs, budgets, process, site problems and the reasoning behind projects you have finished. Pick subjects you can answer from experience and have an opinion about. One honest answer to a real question is worth more than a piece on industry trends.

How often should an architecture firm post? Once a month on the website, sustained, is a rhythm a small practice can hold. Project stories go up as work completes, and social extracts come out of both. Publishing weekly and stopping in March is worse than twelve solid guides a year.

Is blogging worth it for architects? Yes, when the guides answer questions the right clients are already searching. They earn their keep twice: people find the studio through them, and your team stops explaining the same thing on every first call. If the writing attracts readers who will never commission you, change the topics rather than the frequency.

Where to start this month

  1. Ask the team for the five questions that come up before nearly every commission.
  2. Pick one, name the reader, and decide which service page or project it should lead to.
  3. Open Search Console and check whether the site already appears for that topic.
  4. Record a thirty-minute interview with the architect who knows the subject best.
  5. Draft it, get it approved, publish it, then pull two short extracts for Instagram and LinkedIn.
  6. Diarise a review before you choose next month’s topic.

Sources

MORE GUIDES

Marketing for architects: how a studio gets found without becoming a content machine

SEO for builders and architects: what actually moved the numbers for two Brisbane firms

Houzz Pro in Australia: is it worth it for builders and architects?