Using Project Names That Do Not Explain the Design Work
Observable evidence: Portfolio titles rely only on internal labels, client surnames, or poetic names, while the page gives little indication of the style, room type, project category, or genuine location. The source's Project 102 example illustrates the problem: the title may work internally but does not explain the work to a prospective client.
Consequence: A visitor or search system may have difficulty connecting an otherwise strong project to the type of design service being researched.
Correction: Use a descriptive public-facing title or subtitle that accurately states the project type, design character, and location where location is genuinely relevant. Keep the wording natural instead of forcing a keyword pattern.
Owner: Portfolio editor with the design principal confirming that the description accurately represents the project.
Verification: Review the rendered title, page copy, internal links, and search query data. The source previously described a 40 percent traffic increase after a rename, but no supporting source URL or methodology is present, so preserve that figure only as an unreconciled historical example.
Severity: high
Publishing Oversized Portfolio Images Without Performance Controls
Observable evidence: Portfolio templates load very large originals, including files around 10MB in the source example, while mobile tests show slow rendering, delayed interaction, or excessive transfer size.
Consequence: Prospective clients can experience slow or unstable portfolio pages, especially on mobile connections. That is a user-experience problem and can also complicate page-performance diagnostics; it should not be presented as a single guaranteed ranking cause.
Correction: Generate appropriately sized derivatives, use efficient formats where suitable, preserve visual quality, lazy-load below-the-fold media where appropriate, and write useful alt text that describes the image rather than stuffing keywords.
Owner: Developer or web production owner, with the designer approving visual quality.
Verification: Compare real page weight, rendering behavior, and mobile performance before and after the change. The source example reduced a page from 8 seconds to 1.8 seconds; use those values only as a historical example, not a promised outcome.
Severity: critical
Treating Portfolio Pages as Image Galleries With Too Little Context
Observable evidence: A project page contains strong photography but does not explain the brief, project scope, rooms involved, constraints, design decisions, materials, or the studio's role.
Consequence: The page can be difficult for prospective clients to evaluate and gives search systems limited text for understanding what the project demonstrates.
Correction: Add substantive project information that is genuinely useful. The source prescribed 300 to 500 words per project; treat that as an old operating suggestion rather than a verified ranking threshold. The right length is the amount needed to explain the project accurately without filler.
Owner: Design or editorial lead with project-team input.
Verification: Confirm that the final case study answers what was designed, for whom, where relevant, what the studio handled, and why the decisions matter. The source also described a top 3 ranking outcome after case-study expansion; without supporting proof, keep that as a historical example rather than a causal claim.
Severity: high
Leaving Genuine Local Signals Incomplete or Inconsistent
Observable evidence: The studio has a real location, but the Google Business Profile, website, or legitimate directories show conflicting name, address, phone, hours, categories, or service information.
Consequence: Prospective clients can receive inconsistent business information, and the firm loses a clean basis for measuring local discovery.
Correction: Keep the Google Business Profile and legitimate listings accurate. Publish a dedicated location page only for a genuine location with useful local information. Do not rely on map embeds, posting cadence, or profile activity as guaranteed ranking factors.
Owner: Operations or local SEO owner, with the studio principal confirming business details.
Verification: Compare the live profile and directories against firm records. The source described a 25 percent phone-inquiry increase after profile activity; no supporting methodology is present, so treat that value as an unreconciled historical example. If reviews are requested, ask eligible clients consistently for honest feedback without incentives, gating, or selecting only satisfied clients.
Severity: critical
Letting Portfolio Pages End Without a Relevant Service Path
Observable evidence: Project pages attract visits but offer no contextual route to the service that produced the work or to the studio's main /industry/professional/interior-designer page.
Consequence: Visitors may admire a project without understanding whether the firm offers the relevant service, and important service pages can remain poorly connected within the site's own architecture.
Correction: Add a natural internal link or call to action where it helps the reader continue from the project to the relevant service. Do not add links only to meet a quota.
Owner: Content or SEO owner with the studio confirming the service relationship.
Verification: Crawl internal links and manually follow the user path. The source example describes 20 projects, a movement from position 15 to position 4, and a short observation period. Treat those values as historical source material, not evidence that internal linking alone caused the change.
Severity: medium
Building Traffic Around Inspiration Instead of Project Intent
Observable evidence: The editorial plan is dominated by broad inspiration topics while the firm's real services, project types, design specialties, locations, and qualification criteria are weakly covered.
Consequence: Traffic can increase without increasing the share of visitors who are evaluating professional design services.
Correction: Map queries to actual client decisions: service type, project scope, style, room, property type, genuine location, and other factors the studio can accurately address. Keep educational inspiration content where it serves a real audience, but measure it separately from inquiry-focused pages.
Owner: SEO or content strategist with the design principal defining project fit.
Verification: Compare query classes, landing pages, assisted journeys, and qualified inquiries. The source reports a 20 percent traffic decline alongside a lead increase after a targeting shift; without supporting source evidence, use that only as a historical observation.
Severity: high
Designing the Portfolio for Desktop While Mobile Interaction Breaks
Observable evidence: Navigation, galleries, text, hover interactions, animation, forms, or calls to action are difficult to use on a phone or small tablet.
Consequence: Mobile visitors can abandon the experience before understanding the studio's work or reaching the inquiry path. Mobile usability should be treated as a direct user-experience requirement, not as a fixed penalty claim.
Correction: Test representative pages on actual mobile devices, simplify interactions that depend on hover, reduce unnecessary animation, and make navigation, images, text, and contact actions easy to use by touch.
Owner: Designer and developer jointly.
Verification: Repeat key user tasks and compare mobile engagement after deployment. The source described a 50 percent increase in time-on-site after a navigation redesign; preserve that as an unverified historical example rather than a guaranteed result.
Severity: critical
