Industry-specific web design

Architecture Firm Website Design

Clients, developers and competition juries judge an architecture practice by its work first: at what scale, for which building types, in what context. We build architect websites around that look, with credits on every project, large images that load quickly even on a phone, and awards and publications archived with their sources. With practices in the UK and elsewhere, we work fully online.

Project portfolioProject creditsFast large imagesAwards and publicationsProject enquiry form
  • Google Partner
  • Talha Aslan and team
  • English, German, Turkish

Open the live demoA demo design we built for a fictional brand

In short

An architecture firm website presents the practice's projects by typology, scale and status, shows large images without losing speed, and archives awards, competitions and publications in a verifiable way. Each project has its own page and credits, and images are served in modern formats sized to the screen. In the UK, only persons on the ARB register may practise or carry on business under a title containing the word architect.

Talha Aslan and teamLast updated:

Why it needs its own approach

The problems we see most often on architecture firm websites

An architecture website is a portfolio: image heavy but never slow, striking but never short of facts. Generic business templates rarely strike that balance.

Heavy images that load slowly

Photos and renders are often uploaded at the size they leave the camera or visualisation software. On a phone the first project image takes seconds to appear, visitors leave before they reach the portfolio, and weak speed scores hold back search visibility too.

Projects without credits

A project page with a title and a few images does not say where, when, how big, for whom, at what stage or by which team. A client cannot tell whether you have worked at their scale, and search engines cannot tell what the page is about.

Awards and press scattered or missing

Competition results, awards and magazine features are left out or sit in an unsourced list, often only on social media. What should be the practice's strongest trust signal becomes something nobody can check.

Every project in one grid

Housing, workplaces, public buildings, conservation work and competition entries share one gallery. A client looking for a particular building type cannot find the relevant work, and the practice's focus disappears.

No people, no approach

Founders, partners and team are missing, and so are the design approach and the work stages the practice covers. Clients meet the people for the first time at the first meeting.

Protected title used loosely

In the UK, section 20 of the Architects Act 1997 reserves practising or carrying on business under a name, style or title containing the word architect for registered persons, with narrow exceptions such as landscape architect. Wording on the site and in the firm name has to match the actual registration.

Sources: Architects Act 1997, section 20, legislation.gov.uk · Architects Registration Board: The Architects Code

Our approach

A site that shows your work with its facts, quickly and in the right order

We plan an architecture website like a portfolio book: visitors see selected work first, narrow it down by typology, then go into the credits and story of a single project. Every project page opens with location, year, floor area, client, status, team and photo credit, and the same credits are marked up for search engines.

Keeping speed without sacrificing image quality is the technical core of the job. We convert photos and renders to WebP or AVIF, generate a size for each screen, and load the first image with priority and the rest as visitors scroll. For practices entering international competitions or working abroad, we plan a multilingual structure from day one.

Design, development and content sit in one team. Talha Aslan sets the strategy and an experienced team handles delivery. We prepare project texts and credits with you, and after launch you add new projects, awards and publications yourself from your own panel.

  • A portfolio filtered by typology and status
  • A credited page for every project
  • Images in modern formats, sized to the screen
  • Awards, competitions and publications archived with sources
  • An enquiry form that asks for project type and scale
Recommended sitemap

Home

  • ProjectsResidentialWorkplace and retailCivic and culturalConservationCompetitions
  • PracticeApproachFounders and teamServices by work stage
  • Awards and pressAwards and competitionsPublications and pressExhibitions and talks
  • CareersVacanciesStudent placements
  • ContactProject enquiry formPhone and emailMap and directions
  • LegalPrivacy noticeCookie notice

Each project appears in its typology list and in any related award or press entry, and every page leads to the same project enquiry form.

The right setup

Small studio or large practice?

The foundation stays the same; what changes is the size of the portfolio, how the team is presented and which clients the site speaks to.

Founding architect

Small studio site

The practice is known by its founder's name and stance; the site puts a few selected projects first.

  • A tight selection of projects with strong images
  • The founder's approach and background
  • A calm, image led layout

Multidisciplinary team

Large architecture practice site

On public, commercial and mixed use work, clients want to see capacity and process.

  • A large portfolio filtered by typology and status
  • Team, partner and collaborator pages
  • Work stages and project management explained

Competitions and press

Competition and research led practice

Reputation is built on competitions, awards and publications; the site organises them as an archive.

  • A separate section for competition entries and results
  • A press archive linked to its sources
  • Project pages in more than one language

Built for architecture practices

What an architecture firm website needs

This list starts from the questions clients and juries ask when they assess a practice.

Credited project pages

Location, year, floor area, client, status (design, on site, completed), team, collaborators and photo credit. We set the credits up as a template from the start, so every new project is added the same way and lists can be filtered by these fields.

Image performance

Photos and renders are served as WebP or AVIF in sizes matched to the screen; the first image loads with priority and the rest as visitors scroll. web.dev treats a Largest Contentful Paint of 2.5 seconds or less as good, and we fix image proportions in advance to prevent layout shift.

Awards, competitions and publications

Each entry carries the name, year, result and a link to the related project; publications list the magazine or site and, where possible, a link. A verifiable archive builds more trust than a row of unsourced logos.

Practice, team and approach

Founders, partners and team with accurate, current titles; for UK practices we describe as architects only people on the ARB register, all of whom are bound by the ARB Architects Code. We explain the design approach and the work stages the practice covers in plain words.

Project enquiry form

A short form asking for project type, location, approximate scale and timeline. Site details, drawings and documents are left for the first conversation, and a privacy notice sits next to the form.

Image rights and credits

Rights to architectural photographs and renders often stay with the photographer or visualisation studio. We show a credit for each image on its project page and check with you before launch that web and press use is agreed in writing.

Sources: Google Search Central: Google Images best practices · web.dev: Largest Contentful Paint (LCP)

Comparison

A generic template or a site built for an architecture practice?

TopicGeneric business templateSite built for an architecture practice
PortfolioAll work in one galleryProjects filtered by typology, scale and status
Project pageA title and a few imagesLocation, year, area, client, team and photo credit
ImagesHeavy files at original sizeWebP or AVIF, sized per screen, loaded in order
Awards and pressUnsourced badges or nothing at allAn archive linked by year, result and source
TeamOne group photoFounders, partners and accurate titles
ContactA general message boxA form asking for type, location, scale and timeline

Quick check

Architecture firm website feature list

Must haves: does your site have them?

0 of 6 in place Tick the boxes to see where your site stands.

Added as needed

  • Turkish or German project pages
  • Careers and placements page
  • Downloadable press image packs
  • Map of project locations
  • Email on your own domain with SPF, DKIM and DMARC
  • Content panel for adding projects

We choose which of these you need together during the scoping call.

Let's talk about your portfolio

Tell us how many projects you want to show, in which building types and languages; we will come back with a page structure and a written quote.

Process

From brief to launch in four steps

  1. Discovery and scope

    We define your business, your audience and the site’s one-sentence job: who it sells what to, through which action. Scope and timeline are written from that answer.

  2. Design approval

    The home page and key templates come to you as designs first; no code is written before your approval. We do not like surprises, and we do not cause them.

  3. Development

    The approved design becomes fast, secure, maintainable code. You follow progress in the CRM and see every page in a staging environment before launch.

  4. Launch and measurement

    The site goes live with analytics, Search Console and conversion tracking connected; panel training is given, first-year hosting and maintenance included.

Free tools

Check your practice's website for free today

Before planning a new site, resize your images and convert them to modern formats, test mobile usability and check how project links preview when shared. The tools are free and need no sign up.

Image

Image Converter

Convert between JPG, PNG and WebP in one click or in batches; it detects the input format, lets you set quality and a background for transparency, and uploads nothing.

Image

Image Resizer

Resize + compress photos and cut the KB; never leaves your device.

Tech SEO

Mobile Friendly Test

Test whether a page works well on phones: viewport, font size, tap targets, a mobile screenshot and Core Web Vitals.

Sharing

Open Graph Checker & Link Preview

Preview how your link looks on WhatsApp, Facebook, X, LinkedIn and Telegram, and find missing Open Graph tags and image problems.

Tech SEO

Schema Markup

Generate rich-result JSON-LD for Article, Product, FAQ, Local Business.

Security

SSL Checker

Check an SSL certificate's validity, expiry date, issuer, hostname match, certificate chain and TLS versions in seconds.

All free tools

How we work

How we work with architecture practices

We do not yet have a live architecture practice project to show, so we show our approach on a live demo site and describe how we work below. Our other work is on the references page.

Live demo

See how your site could look

For this field we built a one page demo site for a fictional brand, made only to show our approach. You can explore the design, the copy structure and the mobile view live in three languages.

Open the live demo

Portfolio inventory first

Before design starts, we list your projects, images and credits together and decide which work leads and which building types the site opens with.

Speed without losing quality

We compress images while comparing them by eye, stop where detail starts to go, and reach the speed target through sizing and loading order instead.

Texts and credits approved by you

We prepare the structure and wording of project descriptions; credits, titles and award entries go live only after your approval.

Updates from your own panel

At handover we test the panel and the credits template with you, so you can add new projects, awards and publications yourself.

All references

FAQ

Architecture firm website questions

If your question is not here, write to us; we will send you an answer and a written quote.

Next step

Let's plan your practice's website together

In a free 15-minute call, in English, we will go through your projects, your image archive and the clients you want to reach, then send a written scope and quote.

In-depth guide

Architecture Firm Website: From Project Inventory to Enquiries

Talha Aslan and teamLast updated: 15 min read

An architecture firm website carries a decision that a stranger makes in the first few minutes: has this practice worked at my scale and on my building type, who has it worked with, and how do I reach the right person. Clients, developers, competition juries, editors and graduates looking for a job all arrive with different questions, and a well built site gives each of them a short path to an answer.

In this guide, we at Talha Aslan and team walk through the decisions we make, in order, when we build a site for an architecture firm: choosing the portfolio, structuring project pages, preparing images, presenting titles and registration, designing the enquiry form, earning search visibility and keeping the site current.

Build the project inventory before any design

The structure of the site comes from the projects you actually have, not from a design idea, so the first task is to put every project into one spreadsheet. Within a few hours it shows which building types are well represented, which projects lack good images and which ones are missing credits.

We suggest one row per project with these columns:

  • Basics: Project name, location, year, floor area and status (design, on site, completed).
  • Image status: Professional photography, renders only, or drawings that can be shared.
  • Rights: The photographer or visualization studio and whether web use is agreed in writing.
  • Client consent: Whether the client can be named and how precisely the location can be shown.
  • Strategic value: Whether the project represents the kind of commission you want next.

The last column causes the most debate. Early residential extensions may matter to the founders, but if the practice now targets schools or mixed use schemes, that work belongs in the archive rather than the front window. Scoring the inventory with the partners settles which ten or fifteen projects go on the home page, and it produces a to do list of missing photography and credits that can run in parallel with design.

Set up building type and status filters

Good filters take a visitor to their building type in two clicks; badly planned filters split the portfolio into near empty categories. The rule is simple: if a category does not hold at least three strong projects, do not open it yet, and group the work under a broader heading.

We think about filters along three axes:

  • Building type: Housing, workplace, civic and cultural, education, healthcare, conservation, named the way clients search, not the way the studio talks.
  • Status: In design, on site, completed, plus the result for competition entries.
  • Scale: A rough split into small, medium and large, or sorting by floor area, because clients compare your experience with the size of their own project.

An internal term like "collective living" may mean something precise to you, while a developer searches for "multi family housing" or "residential architect". A project can appear under several types, but each needs one primary type so that its title and internal links stay consistent.

Studios whose work is mostly interiors need a different structure, where furniture, materials and finished rooms lead. In that case the setup on our interior designer website page is likely a closer fit.

Balance credits and narrative on project pages

A project page serves two readers: the client who scans the credits to judge your capacity, and the juror or editor who wants to understand the idea. So the page needs a scannable credits block at the top and a short, structured narrative below it.

The credits list location, year, floor area, client, status, project team, collaborators and photo credit. For the narrative we recommend this order:

  1. Context: Site, surroundings, brief and the client's ambition in two or three sentences.
  2. Key move: The idea that drove the design and why it was the right answer.
  3. Making: Structure, facade or material decisions worth explaining.
  4. Use: How the building works today, with a link to any related award entry.

Together these four parts can stay between 250 and 500 words; much longer texts are rarely read to the end. Images sit next to the paragraph they illustrate: the facade detail beside the facade decision, a simplified plan beside the planning idea.

End each page with links to two or three projects of the same type to keep visitors in the portfolio. Build the credit fields as a fixed template from day one, so every new project is entered the same way and the filters draw on the same data.

Prepare photos and renders for the web

Image preparation decides both the quality and the speed of the site, and unless it becomes a written routine it breaks again with every new project. A file straight from the camera or the rendering software should never go onto the site as it is.

This is the sequence we follow on our projects:

  1. Select: Choose 8 to 15 strong frames per project including the cover, and drop near duplicate angles.
  2. Crop: Crop all cover images to one aspect ratio so that grids line up across the site.
  3. Resize: Produce versions at several widths for phones, tablets, laptops and large screens.
  4. Convert: Save the versions as WebP or AVIF and set quality by comparing results by eye.
  5. Name: Give each file a name that describes the project and the view, and write short alt text that describes the image.

Compression has a threshold: stop when board marked concrete, timber grain or an evening sky starts to break up. To see how much your current files shrink in each format, try a few of them in our image converter.

Whoever adds projects after launch needs the same routine, so we hand over a short written guide. Resizing and conversion happen automatically in the content panel; selection, cropping and naming remain decisions for the office.

Hit Core Web Vitals targets with large images

An image heavy site is fast when the first large image loads with priority, the rest wait their turn and nothing jumps while the page loads. Google measures this with Core Web Vitals: LCP is the time until the largest element on screen has loaded, and 2.5 seconds or less counts as good; CLS measures how much the layout shifts, with 0.1 or less as the target.

The third metric, INP, measures how quickly the page responds to taps and clicks, and 200 milliseconds or less is good; heavy galleries and filters push it up. These are the elements that most often hurt architecture sites:

  • Full screen opening slideshow: Five or six large images load at once; only the first should load with priority.
  • Autoplay video: A heavy file on a phone; use a poster image and play the video on tap.
  • Custom typefaces: Late loading fonts shift text; keep font files few and check that the license covers web use.
  • Heavy lightbox plugins: The code for the full screen viewer should load when someone taps an image, not with the page.

Declaring the width and height ratio of every image solves most layout shift problems. Test on a midrange phone over a mobile connection, not on the studio's desktop, because project links are often opened from a message.

Handle confidential projects, drawings and client consent

Not every project can be published in full, so decide on publication rules up front for private houses, work under confidentiality agreements and competitions whose results are pending.

Common situations and the approach we suggest:

  • Private house: Show the district or town instead of the address, and remove family photos and personal items from interior shots.
  • Confidential commission: Describe it generically, for example "corporate headquarters, London", without the client name, or leave it out.
  • Competition entry: Competition rules may restrict publication until results are announced, so check them before posting.
  • Drawings: Publish simplified plans, sections and diagrams rather than detailed construction drawings.

Some practices want certain projects visible only to clients who receive a direct link, and blocking those pages in robots.txt does not work: Google cannot read a noindex tag on a page it is not allowed to crawl, and a URL shared elsewhere can still appear in results.

To keep a page out of search results, leave it crawlable and add noindex. For work that must stay genuinely private, password protection is the only safe option.

Run awards, publications and press as an archive

Awards and publications show that independent people have judged the practice's work, so they belong in an archive where every entry can be checked, not in a row of logos. Each entry should make sense on its own and link to the project it concerns.

We use these fields for every archive entry:

  • Name and organizer: The full name of the award or competition and the body that runs it.
  • Year and result: Winner, commendation, shortlist or entry, stated exactly as it was.
  • Project link: The entry links to the project page and the project page links back.
  • Source: Magazine, book or website, the issue or date, and a link where possible.

A press page answers a separate need. Editors want high resolution images, credits and a short practice description in one place, and a dedicated page with a press contact email address covers it. Confirm that every image in the pack is cleared for press use, and place the credit line next to each image as copyable text.

The preview that appears when a project link is shared on social media or in a message is part of the same shop window. Give every project page the right cover image and title, then check the result with our link preview checker.

Get titles, registration and team details right

The team page builds trust, but it also carries statements with legal weight: in the UK, section 20 of the Architects Act 1997 reserves practising or carrying on business under a name, style or title containing the word architect for people on the register, with narrow exceptions such as landscape architect. So treat the team page as a checked record, not as marketing copy.

Our checklist for the team and practice pages:

  • Titles: Call someone an architect only if they are on the ARB register; use "architectural designer" or "architectural assistant" where that is accurate.
  • Practice name: Make sure the firm name and the strapline match the registration of the people behind them.
  • Roles: Founder, partner, associate and project lead reflect real responsibility in the office.
  • Former staff: Remove them from the team page but keep their contribution in project credits.

Registered architects are bound by the ARB Architects Code, and your professional body may set its own rules for how you present the practice, so have those checked by the office. For a practice outside the UK, check the equivalent rules of your national register.

In the approach text, replace general claims with specifics: which work stages you cover, from concept and planning to technical design and site, which scales you take on and how you work with consultants. Clients then arrive at the first meeting already prepared.

Design the enquiry form around the first call

A good enquiry form for an architecture practice is a short pre meeting that turns a message into a lead you can assess; its job is not to collect everything but to let you ask the right questions on the first call. A long technical form loses clients, while a one line message box leaves the subject unclear.

Fields we suggest:

  • Project type: Options such as house, residential development, commercial, civic, conservation or interiors.
  • Location: Town or district; the exact site address can wait for the first conversation.
  • Approximate scale: A rough floor area or number of storeys.
  • Timing and stage: Whether the site is secured, whether planning has started and when the client wants to begin.
  • Contact preference: Phone or email and suitable times.

We recommend leaving file uploads out of the form; title documents, drawings and photos are requested through a secure channel after the first call. A link to the privacy notice sits next to the form and explains why the personal data is collected and how long it is kept.

Put job and internship applications on a separate careers page. Portfolios are large files, so asking for a sharing link instead of an upload protects both the server and your inbox.

Be found by practice name, project name and building type

An architecture firm is found in three ways: by its name, by the name of one of its projects and through building type searches such as "school architect Manchester"; the site structure has to serve all three separately.

The steps, in order:

  1. Project page titles: Project name, building type and town appear together in the title.
  2. Building type pages: Every filter page gets an introduction of two or three paragraphs about the practice's experience with that type.
  3. Structured data: Practice details and project credits are marked up so search engines can read them.
  4. Google Business Profile: The business name matches the real practice name exactly, with no added keywords; category and opening hours stay current.
  5. Image search: Descriptive file names and alt text help projects show up in image results.

We do not promise rankings; nobody can do that honestly. But any content work without this base stays weak.

For a wider search strategy with competitor analysis and a content plan, see our SEO services.

Plan languages for international competitions and clients

If the practice enters international competitions, works for clients abroad or is published in other countries, a second language is a structural decision to make at the start, not an add on. Languages added later usually stay half done: the home page is translated and the project pages are not.

What we look at when planning languages:

  • Separate URLs: Each language has its own address; a button that swaps text on the same address is not enough.
  • hreflang: Every language version references the others and itself; without reciprocal annotations Google may ignore them.
  • Credit terms: Terms such as gross internal area or work stage names are rendered in the professional language of the target country.
  • Selective translation: Start with the projects that matter to international clients instead of translating everything.

We do not leave project texts to machine translation; we review architectural terms with you, because a juror reads a wrong term as carelessness. Units and dates are part of the decision too: square meters or square feet, and date formats, must be consistent within each language.

For clients abroad, a short note on the countries where you can work and how you collaborate with local architects builds confidence. The technical side is covered on our multilingual website page.

Keep the site current and measure enquiries

An architecture firm website earns its keep not on launch day but two years later, when it is still current; that requires deciding who updates it, when and with which template. The pattern we see most often is a portfolio whose newest project was added years ago.

The routine we suggest:

  • Owner: One person in the office adds projects and awards, with a named deputy.
  • Triggers: Every completed photo shoot, competition result and publication goes on the site within the same month.
  • Annual review: Team page, registration details, featured projects and contact details are checked once a year.

On the measurement side, form submissions, calls and email clicks are tracked as conversions with consent; for visitors in the European Economic Area, Google requires consent mode for measurement and personalized advertising features. You then see which project pages and building types bring enquiries.

If visitors from conservation projects fill in the form more often, adding projects and text to that type is a sensible next step. A short monthly report answering three questions is enough for most practices: which pages were visited most, which pages produced enquiries, and how many enquiries matched the work you want.

Common mistakes on architecture firm websites

Most of the mistakes we see come from treating the site as a brochure that is made once and then left alone. Each item below pairs the mistake with a better alternative:

  • A logo and full screen video as the home page: Clients leave before they know what you do; put three featured projects and a one sentence description of the practice on the first screen.
  • Every project given equal weight: Strong work gets lost among weak images; lead with selected projects and move the rest to an archive.
  • Only renders for completed buildings: Clients want to see the real building; budget for professional photography on completion and keep renders for projects in design.
  • Text baked into images: A project name written over a photo can be read neither by search engines nor by screen readers; put it on the page as text.
  • A portfolio only as a PDF: A large PDF opens slowly on a phone and hides individual projects; give each project its own page and send the PDF to clients who ask for it.
  • Thin, small, pale gray type: Minimalism that makes text unreadable is a contrast problem; treat sufficient contrast and a readable type size as part of the design.

Choose a web partner and take the next step

The quickest way to choose a partner is to ask concrete questions about how they would build an architecture firm website; if the answers address your portfolio rather than a generic pitch, you are on the right track. We suggest asking every agency you talk to:

  • Images: Who prepares images, in which formats and sizes, and is that automated for new projects?
  • Panel: Can credit fields and filters be edited in the panel, or does a new building type need a developer?
  • Speed: Will Core Web Vitals be measured on a phone before launch and shared with you?
  • Ownership: In whose name are the domain, site and content registered, and what do you receive if you leave?
  • Content: Who helps write project texts and credits, and how does approval work?

The value of an architecture firm site lies less in its first impression than in carrying new projects at the same quality for years, so compare proposals with that in mind. To see our approach, this page links to a live demo we built for the field, and our other work is on our references page.

What a project includes is described on our web design service page, and fixed packages are listed under web design pricing. Share your number of projects, building types and languages through our contact form, and we will work out the page structure and a written proposal for your practice.