Mistake: One Generic Page Covers Distinct Gutter Services
Observable evidence: Installation, repair, cleaning, guards, downspouts, materials, and problem-specific queries all resolve to the same broad services URL, while Search Console shows different intents competing for one page or multiple pages overlapping without a clear purpose.
Consequence: Customers may land on a page that does not answer the job they need, and search engines receive a less precise description of which page is most useful for each service intent. That can create weak relevance, internal competition, or poor conversion even when the site is indexed.
Correction: The SEO or content owner should separate a service only when it deserves materially distinct content, proof, scope, FAQs, and conversion actions. The existing source suggested 800-plus word pages, but word count is not a quality threshold; depth should follow the information needed to make the page useful.
Verification: Confirm that each retained page has a unique primary purpose, internal links point to the correct service, duplicate sections have been removed, and query-to-page mapping is clearer in crawl and Search Console data.
Severity: critical
Mistake: Seasonal Demand Is Treated as Static
Observable evidence: The site answers the same gutter questions all year while lead records, local weather patterns, or historical search data show changing homeowner concerns such as runoff, leaf accumulation, ice-related damage, storm repair, or preventive maintenance.
Consequence: Useful pages can appear too late for planning-oriented searches, or the business can promote work it cannot operationally support during peak periods. The SEO risk is mismatch between real customer intent and available information, not failure to satisfy a secret freshness rule.
Correction: The content owner should use first-party lead history and credible local seasonality data to update relevant pages before demand changes. The source used 60 days as an operating example; treat it as a planning lead time, not an official search-engine cadence.
Verification: Compare seasonal query coverage, entrances, calls, and quote requests against prior periods and confirm that the published advice matches the contractor's actual services and availability.
Severity: high
Mistake: Project Imagery Is Generic or Misrepresented as a Ranking Hack
Observable evidence: Core service pages rely mostly on stock imagery, project photos lack useful captions or context, or the workflow adds location metadata solely because the team believes it guarantees Google Maps visibility.
Consequence: Customers receive less proof of real gutter work, and accessibility or content context can suffer. There is no basis in the supplied source to claim that geo-coordinates in image files guarantee local image or Map Pack rankings.
Correction: The field or content owner should capture authentic project images where permission allows, explain the service shown, use accurate alt text for the image's purpose, optimize file delivery, and avoid invented location details.
Verification: Check that important pages contain relevant original project evidence, images load efficiently on mobile, captions and alt text are accurate, and no metadata is being fabricated to simulate local work.
Severity: medium
Mistake: Structured Data Is Missing, Inaccurate, or Oversold
Observable evidence: Markup conflicts with visible business details, names services or locations the contractor does not actually offer, fails validation, or is described internally as a mechanism that forces local rankings or review stars.
Consequence: Search engines can receive inconsistent machine-readable information, and unsupported markup can create maintenance or eligibility problems. Structured data can clarify eligible content, but it does not guarantee Map Pack placement or a rich result.
Correction: The technical SEO or developer should implement only schema types and properties that truthfully match visible page content and business facts, then test the generated JSON-LD with appropriate validation tools.
Verification: Confirm that markup parses without material errors, matches the page and business records, and does not claim reviews, service areas, or other facts that are absent or unsupported. The source example used a 30-mile radius; preserve it only as an example, not as a recommendation for every contractor.
Severity: critical
Mistake: Location Pages Exist Without Genuine Local Value
Observable evidence: Many area pages differ mainly by place name, use the same project claims or testimonials, or target markets where the contractor has little useful location-specific information.
Consequence: Customers encounter repetitive pages that add little help, while the site creates unnecessary duplication and index-management overhead. A location page is not automatically required for every neighborhood or nominal service area.
Correction: The SEO and operations owners should retain a dedicated location page only where the business genuinely serves the area and can add useful details such as applicable services, real project evidence, travel or scheduling context, local conditions, and accurate contact paths.
Verification: Review each page for distinct usefulness, confirm the location is actually served, inspect query and conversion data, and consolidate pages that exist only to swap geographic terms.
Severity: high
Mistake: Mobile Friction Blocks Urgent Gutter Inquiries
Observable evidence: Mobile testing shows slow rendering, oversized media, unstable layouts, hard-to-tap controls, obscured phone or quote actions, or forms that are difficult to complete during an urgent repair search.
Consequence: Prospects may abandon the page before calling or requesting a quote. Do not assume a particular bounce pattern directly causes a ranking loss; first verify the usability problem and its relationship to user behavior.
Correction: The developer should optimize images and video, simplify templates and scripts where practical, make primary contact actions easy to use, and address Core Web Vitals or other measured performance problems without treating a single test score as the business outcome.
Verification: Retest representative service pages on real mobile devices and performance tools, then compare completed calls, forms, and engagement before and after the change.
Severity: high
Mistake: Business Information Is Inconsistent Across Important Properties
Observable evidence: The website, Google Business Profile, major directories, or owned profiles show conflicting business names, old phone numbers, outdated addresses, or hours that no longer match operations.
Consequence: Customers can call the wrong number or travel using outdated information, and the team must reconcile conflicting entity data. Avoid claiming that minor formatting differences alone are a proven ranking killer.
Correction: The local SEO or operations owner should create a current source-of-truth record and correct materially inaccurate listings, prioritizing properties customers actually use. Formatting does not need to be mechanically identical when the underlying business information is unambiguous.
Verification: Recheck the website, Google Business Profile, and priority citations against the source-of-truth record. The source's 100% formatting standard is better interpreted as a data-quality goal: essential business facts should agree everywhere.
Severity: critical
