SEO for Architects: Turning Portfolios Into Search Traffic

Jul 27, 2026 · SEO for Industries

An architect I worked with had won two AIA chapter awards and had a website that looked like it deserved them — full-bleed photography, elegant type, a portfolio in a smooth JavaScript lightbox. Google's view of that site was four pages: Home, Studio, Contact, and a portfolio page whose entire text content was the word "Work." Twenty completed projects, zero pages describing any of them. That's the core problem with SEO for architects: the portfolio is the marketing asset, but it's usually built in a way search engines can't read.

How people actually hire an architect

Nobody impulse-buys architecture. A couple planning a custom home or an addition researches for months — they search "how much does an architect cost for a renovation," "architect vs design-build firm," "do I need an architect for an addition," and only later "residential architect in [their city]." Commercial clients behave similarly with longer committees. This research-heavy behavior is actually good news: it means informational content has a real audience in this niche, and whoever answers those early questions gets shortlisted before competitors know the project exists.

It also means you should expect and measure long lags. A visitor who reads your cost guide in March might submit an inquiry in September. That's a working funnel, not a broken one.

SEO for architects starts with project pages

Every completed project deserves its own page with an actual write-up: the location (neighborhood-level is fine if the client prefers privacy), the building type, the design problem, and how you solved it. "Hillside Modern Addition in Berkeley" as a page title, three paragraphs of narrative, and captioned photos will rank for searches like "hillside home architect Berkeley" — searches with almost no real competition because most firms publish galleries instead of pages.

Write the narrative you'd tell at a dinner party: the lot nobody could build on, the setback variance, the client who wanted the kitchen to face the oak tree. This is the content clients actually read on shortlisted firms' sites, and it's what differentiates you from the firm whose project page says "Residential. 2,400 sq ft. Completed 2024."

Living with Houzz instead of losing to it

Search almost any residential architecture term and Houzz occupies two or three results, with Architizer and local directories filling more. You won't displace them, so do both: maintain a complete Houzz profile (it's a legitimate referral source and a citation for your business details) while making sure your own site targets the specific searches Houzz answers generically. Houzz ranks for "modern architects near me"; your project page ranks for "mid-century renovation architect Pasadena." Specificity is the moat aggregators can't cross, because they don't have your projects.

The technical debt hiding in beautiful websites

Architecture sites carry a predictable set of technical problems, and they're worth taking seriously because this niche's sites are heavier than almost any other local business:

• Uncompressed images. Ten 8MB photos on a project page can push load time past ten seconds on a phone. Export web-sized versions — the visual difference is invisible, the speed difference isn't.
• Empty alt text. Every project photo needs a descriptive alt attribute ("cantilevered cedar deck over creek, Portland residence") — it's how Google Images indexes your portfolio, and image search is a genuine discovery channel for architecture.
• JavaScript-only galleries. If project content only exists inside a lightbox or a script-rendered carousel, verify Google can see it. Often it can't, and the fix is simply having real HTML pages behind the pretty grid.
• Portfolio PDFs. A downloadable portfolio is fine as an extra, terrible as the only version. PDFs rank poorly and convert worse.

These issues are exactly what a crawler catches in minutes — audit your site for free and you'll likely find slow pages and missing metadata clustered in the portfolio section.

The studio's map presence, briefly

Architects underinvest in Google Business Profiles because the work isn't walk-in — but "architect near me" and "residential architect [city]" produce map packs, and an empty profile forfeits them. Twenty minutes of setup covers most of the value: the right category (Architect, or Architecture firm), your project photos uploaded as the profile gallery, and a handful of reviews from past clients. Reviews are awkward to request in a relationship business that might span two years per client, so ask at the natural close — the final walkthrough or the photography session — and accept that eight thoughtful reviews describing real projects beat a volume play here. A profile whose reviews mention "our hillside lot everyone said was unbuildable" is doing sales work no brochure can.

Content that earns the shortlist

Three pieces outperform everything else in this niche. A genuinely detailed cost guide — "What an Architect Costs in [Your City], With Real Fee Structures" — because fee opacity is the single biggest anxiety in hiring an architect and almost nobody addresses it honestly. A process page that walks through schematic design to construction administration, because clients don't know what they're buying. And a permitting guide for your specific jurisdiction, because "ADU permit requirements [city]" searches are booming and city websites answer them miserably.

If your site runs on WordPress — most firm sites do — the WordPress SEO guide covers the plugin and template settings that make project pages indexable without a developer.

What winning looks like

Track inquiries and where they entered, not raw traffic. A healthy architecture pipeline from search looks like: cost guide and process pages pulling steady informational traffic, project pages winning specific local searches, and one or two qualified inquiries a month that mention "I read your page about..." Given typical project fees, that's a transformative channel. Work through the SEO checklist for architects to sequence it — project pages first, technical cleanup second, guides third.