Common SEO mistakes—and how to correct them
An architecture site usually underperforms when its visual work is difficult to discover or evaluate, its service and location pages do not reflect distinct client needs, or the firm cannot tell whether search visits lead to suitable conversations. Use this symptom-to-fix table to identify where to start.
| Symptom | Likely root cause | Corrective action |
|---|---|---|
| Project pages show a few photos and a project name, but little else | Portfolio content is designed as a visual gallery, with no written project context | Add an accurate project description covering type, region where appropriate, client brief, the firm’s role, design challenge, and response. Link to the relevant service page. |
| Portfolio images do not appear in image search or convey little to visitors using assistive technology | Images use unclear filenames, missing or unhelpful alt text, or are rendered only as CSS backgrounds; the page also lacks surrounding text | Use accessible HTML image elements, descriptive filenames, meaningful alt text, and nearby captions or project copy. Do not stuff alt text with keywords. |
| Several city pages have almost identical copy and all send visitors to the same generic contact page | Pages were created to target place names rather than to explain a genuine local offer | Consolidate thin pages or make each retained page genuinely useful with distinct local projects, services, and coverage. Do not simply replace one city name with another. |
| Many pages have titles such as “Projects,” “Services,” or the firm name only | Titles do not distinguish the page’s subject or match its purpose | Write a concise, accurate, unique title for each important service, location, and project page. Avoid repeating phrases unnaturally. |
| The firm sees website visits but cannot identify suitable enquiries or where they came from | Forms, calls, and enquiry quality are not tracked consistently | Establish a baseline, record meaningful form submissions and calls where practical, and ask new enquiries how they found the firm. Review search data with enquiry records. |
Thin project descriptions leave the portfolio hard to understand
A portfolio project needs enough context for a prospective client to understand what the firm did and whether that experience is relevant. A title such as “House 07” plus a row of photographs may look polished, but it does not explain whether the work involved a new build, renovation, extension, commercial fit-out, or another service.
A useful project page can state the project type, general location if disclosure is appropriate, brief, constraints, the studio’s role, design response, and services involved. Use facts the firm can verify. Do not disclose a client’s address, budget, or project details without permission.
This context helps people assess fit, and it gives the page clearer subject matter. It does not guarantee a ranking. The goal is to make the work genuinely informative rather than adding prose solely to reach a word count.
For example, instead of listing only “Oak House,” a firm might explain that it redesigned a permitted residential renovation in a particular region, describe the design challenge the client authorized it to share, and link the project to the firm’s renovation service. Keep the description specific to the project and avoid claims such as “award-winning” unless they are accurate and substantiated.
A stronger portfolio structure can also help visitors move between related projects and services. See the guide to architecture portfolio SEO for more on making project work easier to explore.
Image-only portfolios can hide important information
Large images can be central to an architecture website, but a portfolio should not depend on images alone to explain the firm’s work. People may need captions or text to understand the design, and search engines need accessible page content to interpret the subject.
Use standard image elements that can be discovered, provide useful alt text that describes the meaningful content of the image, and place images near relevant project text. A filename such as IMG_4832.jpg gives little context, while a short descriptive filename is more useful for the team and may help clarify the subject. Alt text should describe what matters in the image—for example, “timber-clad rear extension beside the original brick house”—only if that description is accurate. Do not turn alt text into a list of search phrases.
Also check how the portfolio works on mobile and whether images load at a practical size. Oversized galleries can make pages cumbersome, while a design that hides all useful content behind an interaction may make project details difficult for some visitors to reach.
If the website relies heavily on visual work, a review of architecture website SEO can help the firm examine structure, image delivery, and the route from a project page to an enquiry.
Duplicate location pages can confuse prospects and weaken local relevance
Location pages are useful when they reflect where a practice genuinely works and provide distinct information for that market. They become a problem when a firm creates a series of near-identical pages that change only the city name, add little value, and funnel visitors to the same generic destination.
A practice with several offices or meaningful service areas can explain the services available in each place, show relevant local work, and clarify who the local team is. If there is no distinct local experience or service information to share, one clear service-area page may be better than a dozen thin city pages.
Do not claim an office or local presence the firm does not have. Before adding pages, ask whether a prospective client in that location would learn something materially useful that is not already covered elsewhere. The local SEO for architects guide covers local pages and genuine regional relevance in more detail.
Weak page titles make important services and projects harder to distinguish
A page title should tell a prospective client what the page is about. Generic labels such as “Portfolio,” repeated titles across multiple service pages, or a long list of keywords can make pages less clear in search results and browser tabs.
Give each important page a concise title that accurately reflects its specific subject. A residential extensions page might use a title naming the service and the firm; a project page should distinguish that project from other portfolio entries. Add a location only when it is genuinely relevant to the page. Avoid stuffing several cities or services into one title.
Search engines may generate or adjust the title shown in results, so the firm cannot guarantee that its exact wording will appear. Still, clear titles help people understand the page before clicking and make a site easier to manage. Review titles alongside headings and visible copy to ensure they agree.
Tracking gaps make SEO decisions harder
A firm needs more than a traffic total to know whether its website is supporting business goals. If contact forms fail to record successful submissions, phone enquiries are not noted, or staff do not ask how a prospect found the studio, it is difficult to tell whether a page is attracting relevant attention.
Start with a simple measurement setup. Record which service and project pages receive search visits, track successful enquiries where possible, and add a consistent “How did you hear about us?” question to the intake process. Keep the record focused on business-relevant details such as project type, service area, and fit. Follow applicable privacy and consent requirements for analytics and lead tracking.
Search reporting can show impressions, clicks, click-through rate, and average position for queries and pages. These measures describe visibility and search visits; they do not prove that a search visit caused a signed commission. Architecture clients may discover a firm through a referral, return through search, and contact it after reviewing the portfolio. Keep attribution cautious and use enquiry notes to add context.
A practical correction example for a small architecture practice
Hypothetical illustration—not a client case study or performance claim: Imagine a residential practice serving three neighboring cities. Its website has a single portfolio grid, several project photos with filenames copied from a camera, three location pages with nearly identical copy, and a contact form that does not record which service the visitor is asking about.
A practical first pass would not be to publish ten more city pages. The firm could select a few projects it has permission to feature, create useful individual project descriptions, and link them to the relevant renovation or new-home service. It could review whether its existing location pages each provide distinct local information, consolidate pages that do not, and rewrite important titles to describe their actual content. Finally, it could test the enquiry form and add a way to record project type and how the prospect found the firm.
The practice can then check whether the pages are accessible, whether search impressions and clicks relate to the services it wants, and whether enquiries are suitable. No particular ranking or increase in leads can be promised from these steps. The example shows how to address the root causes before expanding the site.
Which fixes should an architecture firm prioritize?
Fix issues that block access or undermine important client journeys before polishing minor metadata across the entire site. A broken service page, a portfolio that cannot be explored, or an unusable enquiry form can matter more to the business than a small wording change on a low-priority page.
A sensible order is:
- Confirm that core service, location, and project pages load and can be reached through normal links.
- Resolve obvious indexing or navigation problems affecting those pages.
- Improve project descriptions and imagery context for the work the firm most wants to show.
- Consolidate or substantively improve duplicate location pages.
- Clarify page titles and headings for priority services and projects.
- Test enquiry forms and establish a simple record of relevant search visits and enquiries.
If the site has many issues and the team is unsure where to start, an architecture SEO audit can help turn technical, page, portfolio, local, and tracking findings into a prioritized plan. A useful audit should explain why a fix matters and what the firm should do next—not promise a first-page ranking. To map priority services, locations, and project types to distinct pages, see the SEO keywords for architects guide.
Conclusion
The most common SEO mistakes for architecture firms are usually fixable content, structure, and measurement problems: thin project pages, inaccessible portfolios, duplicate location content, vague titles, and missing enquiry tracking. Start with pages that represent the firm’s priority services and strongest work. Make each page useful to prospective clients, then measure whether relevant visits lead to suitable conversations. For a wider planning framework, see the architecture SEO strategy guide, then explore the [SEO for Architects service page](https://www.seoforarchitects.net/) and connect recommendations to the practice’s actual services and capacity.
FAQs
Why do architecture sites underperform?
Architecture sites can underperform when important services and projects are difficult to find, galleries have little descriptive context, local pages repeat one another, or visitors cannot easily enquire. A visual portfolio may communicate design quality but still leave prospective clients unsure about project type, location, or the firm’s role. Diagnose those issues before adding more pages.
Are image-only portfolios bad for SEO?
Not automatically, but an image-only portfolio can make it harder for people and search engines to understand what each project represents. Add accurate project text, useful captions, descriptive image alternatives, and clear links to relevant services. Ensure images are accessible in the page markup and do not rely only on text embedded in graphics or inaccessible gallery controls.
Which fixes matter first?
Start with issues that prevent important pages from being reached or understood, then improve the priority project and service pages, consolidate location pages that add no distinct value, clarify titles, and fix enquiry tracking. Priorities depend on the firm’s site and goals. A technical barrier or broken contact path should usually come before cosmetic changes on low-value pages.
FIX THE RIGHT PROBLEMS FIRST
Turn architecture SEO issues into a prioritized plan.
Identify the technical, portfolio, local, and measurement improvements that matter most to your firm.