Creating Near-Duplicate Service-Area Pages
Observable evidence: Several city or suburb pages target the same service, use the same headings, proof points, calls to action, and body copy, and change little beyond the place name. The source example described pages keeping 95% of their copy identical, one repeated description containing 300 words, and the same template reused across 20 suburbs. Treat those figures as examples from the supplied material, not as thresholds that automatically determine search performance.
Consequence: Visitors may learn little about why a page is relevant to their location, while crawlers must choose among several URLs that answer nearly the same need. The maintenance burden also grows because updates, service details, and business information must be kept consistent across many weak pages.
Correction: Keep a dedicated location page only when the business genuinely serves that market and can publish useful location-specific information. Differentiate the page with accurate service availability, locally relevant project examples when approved, practical travel or scheduling context when useful, and links to the correct service pages. Consolidate pages that do not serve a distinct user need, and avoid creating pages for nominal markets solely to capture place-name queries.
Owner: The SEO or content lead should define page purpose with operations input so published locations match actual service coverage.
Verification: Compare page intent, query overlap, internal links, indexation, and lead quality after the change. The intended location page should be clearly useful on its own, not merely a city-name variation of another page.
Severity: critical
Treating Google Business Profile Services as a Keyword List
Observable evidence: The profile uses broad or inaccurate categories, lists services the business does not actually provide, omits important real services, or contains descriptions that do not match the website. The original source referenced service descriptions up to 300 characters; verify any current field limit in the product interface before treating that historical wording as a requirement.
Consequence: Inaccurate or inconsistent profile information can confuse prospective customers and weaken the coherence between the profile, service pages, and other business references. Routine profile edits should not be described as a guaranteed path to local pack gains.
Correction: Use the most accurate eligible primary category, add legitimate secondary categories where they fit, keep services aligned with the real offering, and make contact, hours, and service-area details consistent with the business. Write descriptions for people first rather than forcing query variants into every field.
Owner: The local SEO owner should manage the profile with operations or leadership approval for business facts and service scope.
Verification: Check that profile details match the real business and the corresponding website pages, resolve duplicates or stale information where the platform allows, and review the queries and actions associated with the profile without assuming a single edit caused a ranking change.
Severity: high
Using Project Images Without Performance or Decision Context
Observable evidence: Service and gallery pages depend on large files, weak captions, repeated stock imagery, or photos that show work without explaining the service, location context, or stage of the project. The source used an example in which the same stock image might appear across 500 contractor sites. That is an illustrative duplication scenario, not evidence of a documented image-based ranking penalty.
Consequence: Heavy media can slow important pages, while generic or unexplained imagery gives customers less evidence for judging the contractor's actual work. Missing or poor alternative text also creates accessibility problems.
Correction: Use original, approved job photography when available, size files for their rendered use, compress them appropriately, and provide concise alternative text for informative images. Add nearby project context that explains what the image demonstrates. Do not rely on EXIF geotags, hidden metadata, or stock-photo avoidance as a substitute for useful page content.
Owner: The web team owns image delivery and page performance; marketing or operations owns the accuracy and approval of project descriptions.
Verification: Test representative mobile pages, inspect layout stability and load behavior, confirm alternative text describes visible content, and check that project captions do not invent locations, credentials, or outcomes.
Severity: medium
Adding Structured Data That Overpromises Search Appearance
Observable evidence: The site publishes LocalBusiness, Service, Review, or other structured data that conflicts with visible content, describes unsupported properties, copies review information that is not eligible for the intended use, or is added primarily in the hope of forcing a special search result. The source included an example of a competitor appearing with a 4.9-star rating. Without a supporting source URL and with search appearance varying by query and eligibility, that example should not be treated as proof that adding markup will produce stars or a richer snippet.
Consequence: Incorrect markup creates maintenance risk and can make the machine-readable representation of the business inconsistent with the page. Even valid structured data does not guarantee a rich result, local ranking improvement, or a particular display treatment.
Correction: Use only schema types and properties that accurately describe content users can verify on the page. Keep business identity information consistent, validate syntax, and remove unsupported claims rather than encoding them in JSON-LD. FAQ content can still answer customer questions, but do not plan the page around FAQPage rich-result eligibility.
Owner: The SEO or structured-data specialist owns implementation, while the business owner or appropriate operational reviewer confirms factual service and business information.
Verification: Validate the rendered markup, compare it with visible page content, monitor for parsing or eligibility issues, and judge success by clarity and technical correctness rather than by expecting a specific search feature.
Severity: high
Leaving Helpful Content Disconnected From Service Pages
Observable evidence: Articles answer homeowner questions but do not link to the service page that resolves the underlying need, service pages have few contextual links from related content, or navigation sends users through generic category pages instead of a direct relevant path. The source included a hypothetical article attracting 1,000 visits while offering no clear path to the related service; treat that as an example of conversion-path friction, not a traffic benchmark.
Consequence: Readers may consume useful information and leave without understanding what service is available, while crawlers receive weaker signals about how informational topics relate to commercial pages. Internal linking problems can also leave important pages deeper in the site than necessary.
Correction: Add descriptive, natural internal links from relevant guides to the best matching service page and from service pages to supporting resources where those links help the reader. Keep the architecture understandable from the home services SEO overview, major service themes, location content that is genuinely warranted, and supporting informational pages.
Owner: The content strategist owns link intent, with the web team responsible for template or navigation changes that affect the wider site.
Verification: Crawl the site to confirm important service pages have relevant internal paths, inspect anchor text for clarity, and compare engaged visits, service-page entrances, and lead actions without assuming that traffic alone equals business value.
Severity: medium
Writing for a Special Voice-Search Formula Instead of Immediate Customer Intent
Observable evidence: Emergency-service pages are written around awkward keyword strings, voice-search folklore, or stale query examples instead of the questions a customer needs answered quickly. The source contrasted urgent searches with a phrase ending in 2024. The useful lesson is not to chase a special voice-search mechanism, but to keep time-sensitive service information current and natural.
Consequence: A homeowner facing a leak, electrical issue, failed heating or cooling system, lockout, storm damage, or other urgent problem may not find clear information about service scope, availability, location coverage, or the next contact step.
Correction: Write concise answers to real pre-contact questions, explain what the business can and cannot handle, keep hours and emergency availability accurate, and make the primary contact action easy to find. Use conversational language where it improves clarity, not because a separate voice-search ranking system is assumed.
Owner: Operations owns accuracy around availability and service limits; content and UX owners translate that information into clear page copy and actions.
Verification: Review urgent-service pages on a phone, test the call or enquiry path, compare search queries with the language on the page, and verify that time-sensitive claims still match operations.
Severity: high
Ignoring Mobile Performance and Contact Friction on High-Intent Pages
Observable evidence: Important service pages load slowly, media delays the main content, tap targets are difficult to use, forms ask for unnecessary information, or the phone and enquiry actions are hard to find. The source previously stated that over 70% of home service leads came from mobile devices, but no supporting source URL is present here, so that figure requires reconciliation rather than being treated as a verified benchmark. It also used a 4G connection as a test scenario, a 5MB background video as an example of an oversized asset, and a case where the request button appeared only after 10 seconds.
Consequence: Customers with urgent needs can abandon the page before they understand the service or reach the contact step. Page performance can also affect search experience, but slow pages should be diagnosed with actual field and lab data rather than described as an automatic penalty.
Correction: Reduce unnecessary media weight, reserve space for key elements, simplify forms, make phone and enquiry actions prominent, and test the path on representative mobile devices and network conditions. Keep accessibility and error handling in the review so speed improvements do not create new usability problems.
Owner: The web or product owner is responsible for performance and form behavior, while operations confirms that contact options route to the correct team and reflect real availability.
Verification: Re-test the same templates after deployment, compare real-user performance where available, complete the contact journey on mobile, and track whether qualified users reach and use the intended actions more reliably.
Severity: critical
