Project Pages That Show Images Without Enough Project Context
Observable evidence: Review portfolio templates, rendered copy, image attributes, internal links, and crawl output. A weak project page may contain large image files but little information about project type, architectural style, materials, location context, scope, or the builder's role. The source used an example of ten 5MB images, but the correct diagnostic is the page's measured weight, rendering behavior, and usefulness.
Consequence: Buyers and search systems receive too little context to understand why the project is relevant to a particular service, style, or market. Thin visible information can also weaken query matching and the internal pathways that connect project proof to service pages.
Correction: Add substantive, project-specific copy only where the builder can verify the facts. The source suggested 300 to 500 words as an operating example, not a ranking threshold. Describe the brief, design decisions, materials, build scope, constraints, and genuine location context when those details are available.
Owner: Content owner with project-team review.
Verification: Re-crawl the page, inspect rendered text and media attributes, confirm factual accuracy, and test whether buyers can move from the project to the relevant service or inquiry path. The source example titled 'Project 1' and referenced a 4-Bedroom design only as an illustration; project naming should follow the actual build.
Severity: critical
Creating Local Coverage That Does Not Match the Builder's Real Markets
Observable evidence: Compare the firm's actual service footprint with location pages, navigation, Google Business Profile settings, and local business records. Look for duplicated pages, nominal city targeting, or locations that lack substantive local information. The source used a 50-mile radius as an example, but distance alone is not a page-creation rule.
Consequence: Near-duplicate location pages can confuse buyers, dilute useful market information, and create maintenance overhead without proving local relevance. The source cited 40 to 60 percent of localized search volume, but it provides no supporting methodology or URL; preserve that range only as historical source material requiring reconciliation.
Correction: Create a dedicated location page only for a genuine market the builder serves and where the firm can provide useful information about project types, process, local considerations, and contact options. Do not fabricate landmarks, codes, testimonials, or neighborhood experience.
Owner: SEO or content owner with operations verification.
Verification: Confirm every location page against real service records, check uniqueness, crawlability, internal links, and whether the content helps a buyer evaluate the builder in that market.
Severity: high
Letting High-Resolution Media Create Measurable Performance Problems
Observable evidence: Test representative galleries on mobile and desktop, review image dimensions, compression, format, request count, layout shifts, and Core Web Vitals data. The source described 10MB files and load times of 5 to 10 seconds as examples; measure the actual site rather than assuming those thresholds apply.
Consequence: Slow or unstable galleries can obstruct project evaluation, delay contact actions, and create poor user experience. Core Web Vitals are part of Google's page experience systems, but a single metric should not be presented as a guaranteed ranking cause.
Correction: Serve appropriately sized images, use efficient formats where supported, defer noncritical media, and keep visible quality suitable for architectural work. The source suggested keeping images under 200KB as an example, but file-size targets should follow image dimensions and visual requirements.
Owner: Developer or technical SEO owner.
Verification: Retest the same templates and devices after deployment. The source's gallery example contained 20 images, took 12 seconds on a 4G connection, and asserted a page-one outcome; retain those numbers only as the original illustration, not as a predictive rule.
Severity: critical
Publishing Trust Claims That Buyers Cannot Verify
Observable evidence: Inventory licenses, insurance statements, warranties, memberships, certifications, project awards, biographies, and third-party profiles. Check that every claim is current, belongs to the firm or named professional, and is stated within its actual scope.
Consequence: Missing trust information can leave buyers with unanswered due-diligence questions, while incorrect credentials can create a more serious credibility or legal problem. E-E-A-T is guidance for evaluating content quality, not a standalone ranking score that a builder can optimize mechanically.
Correction: Publish verifiable credentials, warranty terms, insurance information, affiliations, and experience where relevant. Avoid inventing memberships or certifications and avoid implying that a credential guarantees search visibility.
Owner: Marketing or compliance owner with business leadership review.
Verification: Check each published claim against current documentation and third-party records where applicable, then schedule review when credentials or policies change.
Severity: high
Targeting Search Volume Without Matching Buyer Intent
Observable evidence: Compare target queries, Search Console data, page purpose, form submissions, and sales qualification notes. Look for pages attracting broad research traffic while failing to answer the questions of buyers actively evaluating a custom build.
Consequence: Traffic can increase without improving qualified inquiry volume, making headline visit counts misleading for commercial decisions.
Correction: Map informational, comparison, cost, process, location, and service queries to pages that genuinely answer those intents. Avoid labels such as 'Money Keywords' as if they were an official search classification.
Owner: SEO and content owners with sales input.
Verification: Review query mix, landing pages, qualified inquiries, and sales notes after changes to see whether search intent and buyer stage are better aligned.
Severity: medium
Leaving Google Business Profile Information Inaccurate or Unmanaged
Observable evidence: Compare the live profile with the website and business records for name, address, phone, hours, categories, service areas, photos, and review process. Do not assume a particular posting cadence is required.
Consequence: Incorrect or conflicting information can create customer friction and weaken confidence in which business record is authoritative. The source's original copy overstated the certainty of local ranking effects.
Correction: Maintain accurate business information and ask eligible customers consistently for honest feedback without incentives, discouraging negative feedback, or selecting only satisfied customers. The source called for 100 percent NAP consistency, but the practical requirement is accurate, current information across records the business controls or can correct.
Owner: Local SEO or business-profile owner.
Verification: Audit the live profile and important listings after changes. The source compared a 4.2 rating with 5 reviews against a 4.8 rating with 50 reviews, but no supporting source establishes that one listing will always outrank the other; treat it as an unresolved historical example.
Severity: critical
Orphaning Projects and Supporting Content From the Main Site Architecture
Observable evidence: Crawl the site and identify project, service, location, and educational pages with no relevant internal links or with paths that require unnecessary navigation depth. Review whether important pages can be reached from contextually related content.
Consequence: Orphaned or poorly connected pages are harder for users and crawlers to discover, and buyers may miss the next logical step from education to project proof, service detail, or contact.
Correction: Add descriptive internal links where they help navigation and topic relationships. A blog post about 'Top 10 Kitchen Trends for 2026' should link naturally to relevant project or service content and to the main home builder resource when that connection serves the reader. Do not force a rigid silo if a clearer architecture works better.
Owner: SEO or content owner.
Verification: Re-crawl the site, confirm important pages have meaningful inbound internal links, test the links, and inspect whether the anchor text accurately describes the destination.
Severity: medium
