Audit objective: confirm that important tree service pages can be discovered, rendered, indexed where appropriate, measured, and used on mobile devices. Technical findings should be tied to observable evidence rather than assumed ranking effects.
Crawlability and Indexing
Evidence: compare expected important URLs with indexed and discovered URLs in Google Search Console, inspect robots directives, canonical signals, sitemap entries, internal links, and page responses. Preserve the source example site:yourdomain.com only as a quick spot check, not as a complete indexation audit.
Severity: critical when core service or location pages are blocked, redirected incorrectly, canonicalized elsewhere without intent, or consistently unavailable to crawlers; lower when the affected pages are nonessential.
Owner: developer or technical site owner.
Corrective action: remove unintended blocks, repair status codes and canonicals, restore useful internal links, update the sitemap where appropriate, and make sure only intended URLs are indexable.
Validation: recrawl the affected URLs, inspect them in Search Console, and confirm that the implemented technical state matches the intended indexation state.
Page Speed and Media Weight
Evidence: test priority mobile landing pages with Google PageSpeed Insights and direct device checks. Large photographs and video can create avoidable delays; the source previously used a 4MB image and a score above 60 as working examples, not as universal pass rules.
Severity: high when visitors cannot reach contact or service information promptly, interactions are delayed, or pages fail repeatedly under representative mobile conditions.
Owner: developer, site administrator, or performance engineer.
Corrective action: resize and compress media, remove unnecessary scripts, optimize loading order, lazy-load noncritical assets when appropriate, and keep important contact elements usable early.
Validation: retest representative pages and confirm that the actual customer path is faster and stable, not merely that a tool score changed.
Mobile Usability
Evidence: test navigation, phone links, forms, estimate requests, emergency contact paths, text readability, consent overlays, and interactive controls on representative mobile devices.
Severity: high when a searcher can find the page but cannot complete a useful action.
Owner: developer and whoever owns enquiry-flow requirements.
Corrective action: repair layout, interaction, form, and contact-path defects and remove elements that obstruct essential content.
Validation: complete the real enquiry flow on mobile from landing page to submitted or initiated contact action.
HTTPS and Transport Security
Evidence: confirm that intended public pages load through https:// with a valid certificate and without avoidable mixed-content or redirect problems.
Severity: critical when browsers warn users, pages fail to load securely, or redirects create loops and broken navigation.
Owner: hosting or technical site owner.
Corrective action: repair certificate, redirect, and mixed-content issues while preserving intended canonical URLs.
Validation: load representative URLs in a browser, inspect the final response path, and confirm that secure versions resolve consistently without warnings.