An architecture firm website should bring you clients, not compliments

A large studio came to us with a simple complaint: their website brought them no clients. So we looked at it. It was beautiful. Serious projects, confident photography, the kind of site a good designer is proud of. And it was completely invisible. Not to people with taste, to machines. Google could barely read it, and the AI assistants that clients now ask, ChatGPT, Claude, Perplexity, could not see it at all.

The reason was underneath, where nobody looks. The design was finished to the last pixel, and the technical layer below it was empty or left on default values. Whoever built the site did the part you can see and skipped the part you cannot. We reworked that invisible half and relaunched. Within weeks the site was bringing in inquiries it had never produced before. One fix, and it paid for itself many times over.

I am telling you this because it is the most common website problem we see, and it is almost never the one firms think they have.

The problem is not that the site is bad

Most architects, when the website underperforms, assume the design is at fault and start thinking about a redesign. Usually the design is fine. The problem is that the site cannot be found, and a beautiful site nobody finds does nothing. It is not a bad website. It is an invisible one, and those are two completely different problems with two completely different fixes.

So before anything else, be clear about what a website is for. It is not a site for the sake of having a site. Its job is to bring you clients, prospects and leads, and for that, people have to find it first. The site should work for you, not you for the site. If it is not doing that, the beauty is beside the point.

Why a beautiful architecture website goes invisible

Architecture websites are built to be looked at. Large images, little text, a portfolio that unfolds as you scroll. That is exactly what makes them hard for a search engine or an AI assistant to use, because those systems read text, not atmosphere. The things that most often make a good-looking site invisible:

• The important facts live inside images. Project name, city, building type, client and year are baked into the picture, not written in text. A machine reading the page sees almost nothing it can repeat to a client.
• There is no plain description anywhere. A page that opens with a mood image and the word "Studio" tells a search engine nothing about what you do or who you do it for.
• No captions, no alt text. The photographs carry the whole story, and none of it is labelled, so none of it is readable.
• The basics that tell a machine what the page is are blank or left on default. No real page titles, no descriptions, no structured data, no proper sitemap. These are the unglamorous pieces that make a site legible, and on most architecture websites they were never filled in.

None of this is a design flaw. The site is doing the first job, looking right, and failing the second one, being found. The person who built it was a designer, not someone who thinks about how search works. That gap is the whole problem.

The plain SEO basics every page needs

When we say a site is unreadable, this is the concrete list that is usually missing. None of it is complicated, and most of it is just writing.

• A page title. The clickable headline that shows in Google and in the browser tab. Every page needs its own, written with the words a client would actually search, not "Home" and not your studio name alone.
• A page description. The sentence or two under that headline in a search result. It barely moves rankings, but it decides whether anyone clicks.
• Alt text on every image. A written line saying what the photo shows: the project, the city, the building type. Without it, a site made of pictures is nearly blank to a machine, and your whole portfolio goes unread.
• Real text on the page. A plain paragraph that says what you do and for whom, not a mood image and the word "Studio." If a person had to explain your practice in three sentences, those sentences should exist as text.
• A sitemap and a correct robots file. The sitemap is a list of all your pages so crawlers find every one. The robots file tells crawlers what they may read, and its most common failure is quietly blocking the very pages you want found.
• Structured data. A few lines of code that label the page in machine terms: this is a firm called X in this city, this is a project of this type, this is an article by this author. It removes the guesswork for Google and for the assistants, and it is cheap to add.

The first four you write. The last two a developer sets up once. Together they are the difference between a site a machine can repeat to a client and one it cannot see.

What a website that actually works does

A working architecture firm website does four things, and only one of them is about looking good.

1. It can be found. By Google, and by the assistant a prospect now asks for a shortlist. If you are not in the answer, you were not rejected, you were never in the room. We go through how those systems read a site in how architecture firms get recommended by ChatGPT and AI search.
2. It says plainly what you do and for whom. In text, in the first screen, in words a client would use. Not "we shape space" but the building types, the cities, the kind of work you want more of.
3. It shows the prospect what they came for and answers their questions. The things a client actually asks in a first call, answered on the page, so the site sells the service while you sleep.
4. It makes the next step obvious. One clear action, not a buried contact form at the bottom of a page nobody scrolls to.

Looking good supports all of this. It does not replace any of it.

The three things that most often kill an architecture website

If I had to name what goes wrong most, in order:

1. Not understanding how search and SEO actually work. The site is built as a gallery, by someone who never asked how a client would find it. Everything else follows from that.
2. No text and no labels. No written descriptions, no captions, no alt text on the images. The whole site is pictures, and pictures are invisible to the machines doing the finding.
3. Missing the technical SEO layer. No sitemap, no structured data, no real titles and descriptions, defaults left untouched. The plumbing that makes a site legible is simply not there.

Fix those three and most "my website brings no clients" problems disappear, usually without touching the design at all.

Common questions

Do I need a new website? Almost never. If the design looks right, the fix is the invisible layer underneath, not a redesign. Rebuilding a good-looking site from scratch is the expensive way to solve a problem the site does not have.

Why does my architecture firm website not show up on Google? Usually because the content lives in images instead of text, and the technical basics, titles, descriptions, a sitemap, structured data, were never set up. Google cannot rank what it cannot read.

Can ChatGPT and other AI assistants see my website? Only if it is readable as text and not blocked to their crawlers. Many beautiful architecture sites are invisible to them, which matters more every month as clients ask an assistant for names. We explain the work in what is GEO optimization.

Does a beautiful website help win clients? Yes, but only once it can be found and read. Beauty closes the client who is already looking at it. It does nothing for the far larger number who never arrive because the site was invisible.

A site that works for you, not the other way around

Your website should be earning its keep: bringing in prospects, showing them what they want, and making it easy to say yes. If it looks good and still brings nothing, the problem is not the look. It is that nobody can find it, and that is fixable without starting over.

We do not redesign websites to make them prettier. We take a site that already looks right and make it found and read, by Google and by the assistants your clients now ask, either as a one-time rebuild of how the site is found or as part of running it for you. See how that work runs, or tell us about your firm and we will look at where your site is leaking.