Using Generic Images Without Showing Real Tree Work
Observable evidence: Service and project pages rely mainly on stock photos, while the site provides little visual evidence of the company's actual crews, equipment, job conditions, completed removals, pruning work, stump work, or storm cleanup.
Consequence: Prospective customers may have less evidence for judging whether the company handles the type and scale of work they need. The problem is evidentiary and conversion-related; do not assume that stock imagery by itself causes a search penalty.
Correction: Replace or supplement generic imagery with accurate photographs from real jobs when the company has permission to publish them. Use descriptive filenames and alt text that explain what the image shows for accessibility and context, without forcing neighborhood names or keywords into every image description.
Owner: Operations or field staff should supply approved job-site media; the website or content owner should select, compress, caption, and publish it.
Verification: Review priority service pages and confirm that published images represent real services, load efficiently, have appropriate text alternatives, and do not make unsupported claims about staff, equipment, credentials, or locations.
Example: A company promotes large removals but shows only generic landscape imagery, giving a customer no way to assess whether the business has documented experience with comparable work.
Severity: high
Publishing Location Pages Without Genuine Local Value
Observable evidence: The site targets surrounding towns by cloning the same tree removal, pruning, stump, or emergency text and changing only the place name. Other sites make the opposite mistake and provide useful information only for the office location even though the company genuinely serves additional areas.
Consequence: Repetitive pages can create a weak user experience and make it difficult to decide which page best answers a local search. The source previously described a reach of 3 to 5 miles from the office, but no supporting source URL or methodology is supplied, so that range should not be treated as a verified visibility boundary.
Correction: Create a dedicated location page only for a genuine location or service-area need where the company can add useful local information, such as services actually offered there, access or scheduling details, relevant project examples, local contact expectations, and service limitations. Consolidate pages that cannot be meaningfully differentiated.
Owner: The SEO or content owner should map location intent; operations should confirm where crews actually work and what can be said accurately about each area.
Verification: Confirm that every retained location page corresponds to a real operating need, contains distinct useful information, is internally linked where appropriate, and does not exist solely to repeat a town name.
Example: A company serves several suburbs but publishes interchangeable pages with no local proof, project context, or service differences.
Severity: critical
Leaving Emergency Service Intent Unclear
Observable evidence: A company that genuinely offers urgent storm or hazard response has no clear emergency-service page, availability statement, service boundaries, or prominent mobile contact path. The source also used phrases such as 24 hour tree removal as examples of urgent wording, but the company should publish such availability only when it is true.
Consequence: People dealing with a fallen, damaged, or hazardous tree may not be able to confirm quickly whether the company handles the situation, which can reduce qualified enquiries even when the site receives relevant visits.
Correction: Build or improve an emergency tree service page that states the real service, current availability model, geographic limits, what information callers should provide, and how to contact the company. Keep the page fast and usable on mobile devices.
Owner: Operations must approve service and availability claims; the website owner should implement the page and contact path.
Verification: Test the page on a mobile device, confirm that the contact action works, check that claims match actual dispatch capability, and review search queries for relevant urgent intent without assuming a fixed ranking outcome.
Example: A site discusses general tree care but gives no clear route for a customer dealing with storm damage or a fallen tree.
Severity: high
Letting Business Details Drift Across Listings
Observable evidence: The business name, address, phone information, hours, or service details differ between the website, Google Business Profile, social profiles, and directories, or old listings still represent a previous business identity or location.
Consequence: Customers can encounter conflicting information and may call an outdated number or travel to the wrong location. The source previously stated that 40-60% of tree service clicks originate from the Map Pack, but it supplies no supporting URL or methodology for that range, so preserve it only as an unreconciled historical claim rather than a verified benchmark.
Correction: Audit important profiles and directories, choose the current authoritative business details, update controllable listings, and document any exceptions such as approved call tracking so staff understand why a number differs.
Owner: The person responsible for local listings should coordinate with operations or management, which must confirm the authoritative contact and location information.
Verification: Recheck the website and priority profiles after edits, verify that customers see accurate information, and maintain a record of listings that could not be changed.
Example: An older directory entry displays a former office number while the current website and Google Business Profile use the main dispatch line.
Severity: critical
Treating Credentials or Schema as a Shortcut to Trust
Observable evidence: A site shows certification logos or insurance language without enough context to verify who holds the credential, or it adds structured data fields that do not accurately represent visible page content. The source also linked readers to its tree service overview.
Consequence: Unsupported or ambiguous credential claims can reduce customer confidence and create inaccurate machine-readable information. The source included an example involving 20 years of experience, but longevity alone does not prove expertise or determine ranking.
Correction: State only credentials, memberships, insurance information, and professional qualifications the company can substantiate. Use supported structured data only when it accurately describes visible content and the represented entity; do not imply that certification markup creates a special ranking category.
Owner: Management or the credential holder should verify the facts; the technical owner should ensure any structured data matches those approved facts.
Verification: Compare visible credential statements with current documentation, validate implemented structured data for syntax and consistency, and remove fields or claims that cannot be supported.
Example: A credential logo appears in the footer but the site does not explain who holds it or whether it is current.
Severity: medium
Using Thin Service Pages That Do Not Answer the Job Question
Observable evidence: A single services page lists removal, pruning, stump grinding, plant health work, or other offerings in short bullets, while customers cannot find service-specific information about scope, process, access, equipment, limitations, preparation, or what happens next.
Consequence: Searchers may land on a page that does not answer the decision they are trying to make, and the site has less useful content for distinct service intents. The source previously recommended 500-800 words for each page, but no supporting evidence is supplied for that threshold, so word count should not be used as a quality rule.
Correction: Create individual service pages where the company genuinely offers a distinct service and where a separate page helps the customer. Write enough accurate information to answer the service decision, then connect related services with useful internal links.
Owner: The content owner should structure the page; arborists, estimators, or operations staff should review technical and service claims for accuracy.
Verification: Confirm that each service page has a clear purpose, matches an actual offering, answers recurring customer questions, and avoids duplication with neighboring pages.
Example: A company expects visibility for a specialized tree care service even though the only reference to that service is a short item in a general list.
Severity: high
Allowing Heavy Media or Mobile Friction to Block Urgent Enquiries
Observable evidence: Large hero images, autoplay video, third-party scripts, layout shifts, or delayed buttons make important service and contact information difficult to use on a phone. The source example described a 10MB video and a contact control becoming interactive after 15 seconds; those values are illustrative rather than a universal threshold.
Consequence: A visitor dealing with a damaged tree may abandon the page before reaching the phone number, request form, service details, or safety guidance. Performance can also affect page experience, but no single speed metric should be presented as a guaranteed ranking switch.
Correction: Compress and appropriately size images, avoid unnecessary heavy media, lazy-load noncritical assets when suitable, reduce blocking scripts, and keep primary contact paths usable early in the page experience.
Owner: The developer or site owner should implement performance changes; marketing and operations should define which contact and emergency information must remain immediately accessible.
Verification: Test priority pages on representative mobile connections and devices, confirm that navigation and contact actions work, and use diagnostic tools such as Google PageSpeed Insights as evidence for specific bottlenecks rather than as a substitute for user testing.
Example: A dramatic background video delays the emergency contact path even though the video contributes little to the customer's immediate decision.
Severity: critical
