Letting Portfolio Images Overwhelm Site Performance
Observable evidence: Project pages ship with original photography or render exports near 10MB, filenames such as IMG_456.jpg, delayed hero media, layout instability, or mobile pages that remain difficult to use while assets load.
Consequence: Prospective clients may abandon project research before reaching the evidence that matters, while search systems and browsers must process heavier pages than necessary. Performance should be evaluated from real page behavior rather than assumed to explain every ranking change.
Correction: Resize media for its rendered use, choose efficient formats where supported, compress files toward an operational target under 200KB when visual quality permits, load noncritical assets later, and write useful alternative text for informative images. Treat the previously published example of 15 uncompressed 4K renders and a 12-second load as a historical scenario requiring source reconciliation, not as a universal threshold.
Owner: Web or digital design owner with the project marketing, accessibility, development, and SEO teams.
Verification: Re-test representative portfolio pages on mobile and desktop, compare field and lab performance where available, inspect rendered image dimensions, and confirm that visual quality remains appropriate for architectural work.
Decision rule: Preserve the design standard, but make each asset earn its transfer cost and remove technical waste that does not improve the client decision.
Publishing Silent Portfolio Pages
Observable evidence: A major project page contains a gallery and a short caption but does not explain the commission, project type, constraints, location context, design response, collaborators, or the firm's role.
Consequence: Searchers and prospective clients receive little first-party evidence connecting the project to the specific service or building type they are researching. The page can also be difficult to distinguish from visually similar work elsewhere in the portfolio.
Correction: Add substantive project narrative based on facts the firm can verify. The source previously suggested 300 to 500 words for every major project, but no supporting source URL is provided, so treat that range as a historical editorial benchmark rather than a ranking requirement. Write enough to explain the brief, relevant constraints, design decisions, project team, and relationship to the service area without padding.
Owner: Project marketing or communications owner with the project architect, principal, and SEO editor.
Verification: Ask whether a prospective client can understand why the project demonstrates relevant experience without relying on images alone. Then review query coverage, internal links, indexability, and whether project facts remain accurate.
Decision rule: Use project text to document real expertise, not to manufacture keyword density.
Creating Local Visibility Without Real Geographic Evidence
Observable evidence: Office information is incomplete or inconsistent, service pages name places the practice does not meaningfully serve, or the site creates multiple location pages that differ only by city name.
Consequence: Prospective clients may not understand where the practice is based, where it can realistically work, or which team has relevant local knowledge. Thin geographic pages also create maintenance and duplication problems.
Correction: Keep office name, address, phone, and other public contact information accurate across owned properties. Create a dedicated location page only for a genuine office or location with useful location-specific information, such as team, services, relevant projects, access, and regional context. Use structured data only when it accurately describes visible content and do not present it as a guaranteed ranking factor.
Owner: Marketing operations or local search owner with office leadership and web publishing.
Verification: Compare published office details across the site and relevant business listings, inspect whether location pages contain unique decision-useful information, and remove or consolidate pages that exist only to target a place name.
Decision rule: Let actual practice geography and project evidence determine local content, not a desire to cover every nearby market.
Targeting Broad Terms Instead of the Work the Practice Wants
Observable evidence: Reporting celebrates generic traffic while high-value service and project-type pages receive little qualified search demand, or broad keywords attract job seekers, students, suppliers, and research traffic that does not match prospective-client intent.
Consequence: The firm may appear busy in analytics while the website provides weak support for the commissions it actually wants to win.
Correction: Map search demand to real services, project types, sectors, locations, and client questions. The source's earlier 5x example lacks an immutable supporting URL, so it should remain a historical anecdote requiring reconciliation rather than evidence that one phrase will produce more qualified enquiries. Prioritize relevance, specificity, and proof over raw search volume.
Owner: SEO strategist with business development and sector leadership.
Verification: Segment organic entries and enquiries by landing page and intent, review the queries that surface each service page, and confirm that the page supports the type of commission being targeted.
Decision rule: Prefer search demand that maps to a real offering and credible project evidence over generic visibility that does not support business development.
Treating Structured Data as a Substitute for Clear Architecture Content
Observable evidence: Markup is extensive while service descriptions, office facts, project credits, or visible page relationships remain vague, inconsistent, or incomplete.
Consequence: Search systems still have weak source content to interpret, and the firm may spend time maintaining markup that does not improve the underlying client information.
Correction: Start with clear visible content and a coherent site structure. Add supported JSON-LD only when it truthfully describes the page and follows documented eligibility guidance. Do not invent special schema types, promise rich results, or assume markup alone improves rankings.
Owner: Technical SEO or web engineering owner with content governance.
Verification: Validate syntax, compare marked-up facts with the rendered page, monitor Search Console where relevant, and confirm that deleting the markup would not leave the page itself ambiguous.
Decision rule: Use structured data to describe strong content, not to compensate for weak content.
Leaving Service Pages Isolated From Relevant Projects
Observable evidence: Service pages do not link to representative work, project pages do not connect back to the service or sector they evidence, and important pages are reachable only through search or a deep navigation path.
Consequence: Prospective clients must assemble the practice's capability story themselves, while crawlers receive fewer contextual signals about how services and completed work relate.
Correction: Build contextual links between services, sectors, locations, people, and projects where the relationship is genuine. The source's example of 50 project pages and a service page reaching page 4 is an unsupported historical scenario, so use it only as a reminder to inspect internal structure rather than as proof of causality.
Owner: SEO or content architecture owner with the practice's project marketing team.
Verification: Crawl the site, inspect orphaned or weakly linked pages, test navigation as a prospective client, and confirm that priority services are supported by relevant project evidence without forcing repetitive anchor text.
Decision rule: Link pages when the relationship helps a person understand capability, not merely to circulate ranking signals.
Designing Mobile Pages as Scaled-Down Desktop Portfolios
Observable evidence: Navigation, image carousels, filters, forms, or motion effects that work on a large 32-inch display become difficult to use on a phone. The source's reported 40% traffic loss after a redesign has no supporting URL, so treat it as a historical claim requiring reconciliation.
Consequence: Prospective clients researching between meetings, on site, or while travelling may struggle to compare work, find credentials, understand services, or make contact.
Correction: Design mobile journeys around the decisions a client needs to make: identify fit, review relevant projects, understand the practice, and contact the right person. Test touch targets, navigation, media behavior, form completion, and reading order on real devices. Address mobile performance issues when evidence shows they materially affect use.
Owner: UX or digital design owner with development, accessibility, analytics, and SEO.
Verification: Run representative client tasks on multiple mobile devices, compare behavior before and after changes, and check that the mobile rendering contains the same essential project and service information as desktop.
Decision rule: Preserve visual sophistication only when it remains usable and informative on the device a prospective client actually has in hand.
