Almost all SEO advice is written for businesses with high search volume and low transaction value. Architecture is the opposite: very few people are searching, and each one is worth at least a year of work.
That inversion changes nearly every recommendation. Traffic is the wrong goal. Ranking for “modern home design” would be a disaster — thousands of visitors, none of them within two hundred miles or three years of hiring anyone. What you want is a handful of people a month who are looking for exactly what you do, where you do it.
Here’s what that actually takes.
Most of it is local
For a residential practice, the map pack — the three businesses Google shows above the regular results for a local query — is most of the prize. It's above everything else on the page, it's where "architect near me" resolves, and a firm that isn't in it is competing for scraps underneath it.
Getting there is unglamorous, and mostly it isn't about your website at all. It starts with a complete, actively maintained Google Business Profile — the correct category (Architect, not Architectural Designer or General Contractor), real hours, a service area, and photographs of finished work added regularly rather than once. Reviews help, too. Architects are squeamish about asking, and it costs them — a project handoff is a natural moment to do so and the request just needs to be built into it rather than left as a favor someone has to remember. Keep your name, address, and phone number consistent everywhere you appear, from AIA chapter listings to Houzz to the local chamber to old directory entries you forgot existed, since inconsistency there is a silent, common drag. And use a real address if you have one — service-area-only listings compete badly in this category.
If you do one thing from this entire guide, do the profile.
Your project pages are the SEO asset you’re not using
An architecture site's project pages are usually its most numerous pages and the least written. Photographs, a town, maybe a square footage. From a search engine's point of view, that page is close to empty.
Which is a shame, because a project page is naturally a perfect match for how people actually search. Somebody looking to build in Cape Elizabeth on a sloped waterfront lot is going to type something close to that. If you have a project page that says Cape Elizabeth · sloped waterfront site · shoreland zoning setbacks · year-round house for a family of five, you are the only result that exists.
Five things earn their place on every project page, roughly in order of return: a paragraph on the site and its constraints — the actual problem the design solved; the location stated plainly, town and state in the text itself and not only in a photo caption; the project type and scope, whether that's new construction, a historic renovation, an addition, or a camp; a drawing or sketch set alongside the photography; and real alt text on every image, describing what's actually shown.
This is the best return available to an architecture firm doing SEO, and it doesn't look like SEO work. It looks like finally writing up all those projects you’ve completed.
Go after the specific query
“Architect” and “architecture firm” plus a city are contested, expensive to rank for, and pull in everyone from students to someone pricing a shed. The queries worth owning are narrower than that, and they sound almost too specific to bother with: site conditions like waterfront, steep slope, island, or an in-town lot; regulatory realities like shoreland zoning, historic district review, or coastal setbacks; project types like a camp renovation, a carriage house conversion, a passive house, an ADU; and the questions a client asks before they ever call — what an architect costs, what schematic design actually produces, how long a custom house takes, whether they need an architect at all.
Each of these might bring five people a month. Those five are pre-qualified in a way that volume never is. And that last group — the pre-inquiry questions — is where most sites have nothing, because answering them can feel like giving away the consultation for free. It isn't. It's the page that makes you the firm they call.
The technical part is shorter than you think
Two things matter, and almost nothing else does.
The first is image weight. Architecture sites are heavy sites by nature, and speed is a ranking factor and a bounce factor at once. Images need to be properly compressed, correctly sized, saved in a modern format, and lazy-loaded below the fold. This is one of the most common technical problems on architecture sites.
The second is a crawlable, sensible structure — every project page reachable in a couple of clicks, one clear URL per page, a working sitemap, no orphaned pages. If your portfolio is a JavaScript gallery with no individual URLs, Google can't see your best content at all.
Structured data is worth adding — LocalBusiness on the contact page, Article on posts — but treat it as a finishing touch rather than a strategy in its own right. Anyone selling you schema before they've looked at your images has the order wrong.
Publish less, and better
The industry standard advice is a blog post a week. For an architecture practice that is both impossible and counterproductive — you'll produce thin posts that compete with each other for the same query and split your own rankings between them.
We know this one from the inside. This site's own previous blog ran to roughly 130 posts targeting overlapping terms, and the result was three and four versions of the same article fighting each other into positions in the thirties. It's being consolidated down for exactly that reason as you read this.
Six substantial pieces a year, each aimed at a question a client actually asks, will outperform fifty. And when in doubt, improve the page you have rather than adding a new one beside it.
What to expect, and when
Search for a small firm in a small market is a six-to-twelve-month proposition. Local profile work can move within weeks; content and authority take a couple of quarters to compound.
Track three things and let the rest go. Watch your map pack position for your core local queries. Watch qualified inquiries too — the ones that actually met your criteria, rather than every raw form fill. And watch which pages people arrive on; if it's all the homepage, your project pages aren't working yet.
Rankings for their own sake are a vanity number in a market this small. The whole game is whether the right five people found you.
If you're evaluating help
Whether you do this in-house or hire it out, the same three questions sort the serious from the rest: What are you going to change in the first ninety days? How will we know if it worked? What happens to the work if we stop? An answer that leads with content volume rather than the profile and the project pages is an answer aimed at a different kind of business.
For how search fits alongside everything else, see the one-page architecture marketing plan and our note on lead generation for architects. Search and website work is one of the things we run for shelter clients — architects, builders, interior designers, landscape architects and realtors. It's slow work, and the results we're proudest of took years rather than a quarter.
Tell us what you're not ranking for and we'll tell you whether it's actually worth ranking for.