Using One Generic Service Page for Distinct Residential and Commercial Decisions
Observable evidence: Search Console shows the same broad landing page appearing for driveway repair, parking lot resurfacing, maintenance, milling, and other materially different searches. The page gives each audience nearly the same explanation, while estimate notes show that prospects still have to ask basic questions about scope, access, crew capability, or the type of work the company actually wants. A B2B buyer cannot quickly tell whether the page addresses commercial requirements or simply repeats homeowner-oriented language.
Consequence: The page can generate visibility without helping the right prospect qualify the contractor. Sales staff then spend time sorting mismatched inquiries, and commercial buyers may leave before confirming that the company handles the needed scope. An earlier editorial example referenced a $50,000 commercial bid to show why inquiry quality matters. Because this JSON provides no supporting source URL for that amount, it remains an illustrative example rather than evidence of a normal paving contract value.
Correction: Build the page map from real services and buyer decisions. Where commercial work is genuinely distinct, explain the relevant scope, site conditions, access planning, phasing, drainage considerations, maintenance needs, coordination requirements, and estimate process. Keep residential pages centered on homeowner decisions. Merge keyword variants when one useful page can satisfy the same intent instead of multiplying pages for superficial wording differences.
Owner: The SEO lead owns query mapping and landing-page intent. The estimator or operations lead confirms that service terminology, qualification points, equipment references, and project constraints match the work the company actually performs.
Verification: Review the queries reaching each corrected page, inspect the inquiries generated from those pages, and compare sales notes with the intended audience. The test is whether a qualified prospect can confirm project fit without decoding generic copy. A previously published Ohio example cited a 40 percent increase in RFPs after separating intent. With no supporting source URL in this JSON, that figure must stay historical context requiring source reconciliation and must not be treated as an expected result.
Severity: critical
Scaling Location Pages by Swapping Place Names Instead of Adding Local Usefulness
Observable evidence: The site has 50 location pages across a 100-mile service area, but most of them repeat the same services, calls to action, and supporting text with little more than a place-name substitution. Some pages cannot show relevant project evidence, practical coverage details, or location-specific information that would help a prospect understand whether the company truly serves the market. A nominal service area alone is not enough reason to create a dedicated page.
Consequence: Thin local pages can split internal authority, create overlapping query targets, consume crawl attention, and disappoint users expecting information about the named market. Pages designed mainly to funnel users from many similar place-name variants toward the same destination can also create doorway-style quality concerns. Similarity by itself, however, is not proof of an automatic site-wide penalty.
Correction: Keep a location page when service coverage is real and the company can provide useful, accurate local substance. That may include completed work, relevant service constraints, coverage boundaries, estimate handling, or maintenance considerations that genuinely differ for the market. When several pages cannot justify distinct usefulness, consolidate them into a stronger regional or service resource and update internal links accordingly.
Owner: The SEO lead owns consolidation, canonical targeting where applicable, and internal-link updates. Operations confirms where crews actually work and approves any market-specific claims or project examples before publication.
Verification: Audit every retained page for a distinct purpose, accurate coverage, unique supporting evidence, and queries that make sense for that page. An older editorial illustration compared replacing 20 thin pages with 4 stronger regional hubs. Because the source contains no supporting URL for a traffic result, use that comparison only to explain consolidation logic and not to forecast performance.
Severity: high
Expecting Structured Data to Compensate for Weak Local and Service Content
Observable evidence: LocalBusiness or Service markup lists facts that users cannot confirm on the visible page, expands service areas beyond what operations supports, or is deployed with the expectation that schema alone will create local ranking gains. Structured data can make supported page facts easier for systems to interpret, but it should not be described as a special requirement for Google AI Overviews, a guaranteed rich result, or a direct path into the Maps 3-Pack.
Consequence: Unsupported markup creates a credibility gap between the code and the page, while attention spent chasing markup tricks can leave more important defects untouched. Weak service explanations, inconsistent business details, poor local evidence, and unclear project information still need to be corrected on the visible experience.
Correction: Use structured data to represent facts the business can substantiate. Keep names, contact details, services, and relevant visible claims consistent, choose appropriate types, and remove assertions that operations cannot verify. Do not invent certifications, ratings, service areas, or service capabilities in markup.
Owner: The developer or technical SEO lead owns implementation and validation. Business leadership or operations approves the underlying facts so technical deployment does not outrun what the company can support publicly.
Verification: Validate the live markup after deployment, compare each important property with visible content, retest templates after releases, and review Search Console issues where relevant. The pass condition is accurate, parseable representation of the page, not a ranking movement attributed to schema without evidence.
Severity: medium
Showing Project Photos Without Explaining What the Paving Work Demonstrates
Observable evidence: Gallery pages are dominated by large images with generic filenames such as 'IMG_4567.jpg', missing or repeated alt text, vague captions, and no explanation of the surface condition, preparation, repair, resurfacing, striping, drainage, or other work visible in the photos. A property manager or homeowner can see that a project happened but cannot determine what capability the gallery is meant to prove.
Consequence: Visual proof loses decision value when the reader cannot connect an image to a service or project constraint. Heavy assets can also delay the mobile experience, making it harder for a prospect in the field to evaluate the work and reach the estimate path.
Correction: Compress images appropriately, use descriptive filenames when practical, write concise alt text for meaningful images, leave decorative images with appropriate empty alt attributes, and add captions or nearby copy that explains the actual paving work. Avoid repeating city names mechanically in image fields. For site-wide service and content structure, use the paving company SEO guidance rather than treating filenames or alt text as an isolated ranking tactic.
Owner: The content or web team prepares the assets and accessible text. The project manager verifies that each caption, service reference, and scope description accurately reflects the completed work shown.
Verification: Inspect rendered quality, asset weight, accessibility, mobile loading behavior, and the surrounding project explanation. Then review whether prospects can identify the work shown and whether project pages support qualification. Image-search impressions may be observed, but they do not prove that a filename or alt-text edit caused commercial lead growth.
Severity: medium
Refreshing Seasonal Paving Content Only After Buyers Have Started Making Decisions
Observable evidence: Educational and service content is revised mainly when crews are already busy, even though commercial buyers may research maintenance, budgeting, access, phasing, or surface work earlier. The business also copies a generic publishing calendar without checking climate, service availability, local estimating patterns, or the questions that actually appear in sales conversations.
Consequence: Useful content can arrive after the research or estimating window it was meant to support. That is an operating and planning defect, not evidence that a specific publishing frequency is an official ranking factor.
Correction: Maintain a 12-month refresh plan tied to actual seasonality, weather constraints, estimating lead times, service availability, and recurring buyer questions. If Q1 is when local prospects begin researching a relevant service, prepare the page before that planning stage. If Q4 is when another maintenance concern becomes useful, refresh the material while buyers can still act on it.
Owner: Marketing owns the editorial calendar and page refresh workflow. Estimating and operations supply the real-world timing, scheduling constraints, service availability, and common questions that should shape the content.
Verification: Compare publication and refresh timing with query patterns, estimate requests, sales notes, and actual service availability. A prior editorial example reported a 25 percent lift in early-season bookings after winter-protection content was published. With no source URL supporting that result in this JSON, treat it as a historical observation awaiting source reconciliation rather than evidence that the same change will reproduce the outcome.
Severity: high
Buying or Accumulating Links Because the Count Looks Impressive
Observable evidence: New-link reports are filled with unrelated directories, generic blogs, repeated commercial anchors, or placements whose only obvious purpose is to influence rankings. The team may also treat third-party authority scores as if they were Google metrics. None of those signals answers the practical question: whether the mention is legitimate, contextually relevant, and useful to a real audience connected with the paving business.
Consequence: Volume-first outreach can consume budget while producing little referral value or defensible authority. Manipulative placements can also conflict with search-engine spam policies, and a large batch of low-quality links makes later diagnosis harder because the business cannot tell which relationships or mentions had genuine value.
Correction: Prioritize references that arise from real business activity: relevant suppliers or partners where editorially appropriate, organizations the company genuinely participates in, credible local or project coverage, and unlinked brand mentions that warrant a citation. Avoid generic packages and artificial sponsorship activity created solely to manufacture SEO links.
Owner: The SEO or communications lead owns prospecting, review, and outreach records. Business leadership approves relationships, paid arrangements, and disclosures so link acquisition stays aligned with actual company activity.
Verification: Review newly discovered links for legitimacy, audience fit, topical or local relevance, referral value, anchor context, and the reason the citation exists. Previous copy contrasted one relevant mention with 50 low-quality directory submissions. That comparison is not a documented ranking formula or equivalence, so it should only illustrate why raw counts are a weak decision metric.
Severity: high
Allowing Mobile Speed or Estimate Paths to Fail When Prospects Are on Site
Observable evidence: Mobile visitors encounter oversized galleries, delayed service copy, hard-to-use tap targets, inconsistent phone links, or estimate forms that do not complete reliably. Scripts may block the information needed to confirm service scope and coverage. Page speed and Core Web Vitals can inform user-experience work, but improving a score does not guarantee stronger rankings or more contracts.
Consequence: A prospect looking at a damaged lot, driveway, or active jobsite may leave if the page cannot quickly answer what the company does, where it works, what comparable work looks like, and how to request an estimate. That failure weakens the lead path regardless of the page's search position.
Correction: Size and compress images, remove unnecessary scripts, cache static assets, keep essential service information accessible without excessive interaction, and test the primary contact journey on representative mobile devices. Use Google PageSpeed Insights diagnostically, then pair lab findings with field data and direct testing of forms, calls, and estimate actions.
Owner: The developer owns performance and functional defects. Marketing or sales owns the practical lead-path check, including whether forms, phone actions, and estimate requests reach the correct destination.
Verification: Use a 5 seconds load example and a 2 seconds load example only as a diagnostic comparison, then inspect real-user performance, form completion, lawful call tracking where configured, and observed behavior before attributing an outcome. Older copy claimed a 15-20 percent increase in mobile form submissions after such an improvement. Since this JSON contains no supporting source URL, that figure remains historical and unverified and must not be presented as a promised result.
Severity: critical
