Search the site · Ask Zorva

Results appear as you type. Press Enter and Zorva answers from this site’s own pages.

Public scan result · scored by the Zorva Labs website scan

wilhelmlandscapeandhardscape.com scored 87/100 on the website scan.

Solid

wilhelmlandscapeandhardscape.com · Scanned 2026-11-18

87 passed6 warnings4 failed

  • Technical SEO & indexability10 of 10 points
  • On-page SEO & content24 of 25 points
  • AI search / AEO / GEO readiness25 of 35 points
  • Local SEO & entity signals4 of 5 points
  • Speed, scripts & mobile19 of 20 points
  • Conversion & lead generation5 of 5 points

Why AI search is 35 of the 100 points

Google is sending fewer people to websites. When it answers with an AI Overview, the top-ranked page's click rate is 58% lower than it would otherwise be (Ahrefs, 300,000 keywords, December 2023 against December 2025), and 68% of Google searches now end without a click at all (SparkToro, January–April 2026). The answer comes more and more from Google's AI, ChatGPT, Gemini and Perplexity, and they name the businesses whose sites they can read and quote. That is what this part of the scan measures, so it carries the most points. Every area's points fall faster than its checks: a warning counts a quarter of a pass, and an area half done earns about a third of its points, because search and AI answers go to the sites that finish the work.

What to fix first

  • ✗

    FAQs on the inner pages +6 points

    The service page read carries no FAQ. The questions people ask about a service are what the answer engines quote.

    What we’d do: Every service, area and post page carries its own researched questions — four or more, the ones people ask about that subject, none repeated from another page — visible and in FAQPage schema.

  • !

    Specifics an engine can cite +3 points

    The service page (/services/): 359 words, 9 numbers, 1 name (Knoxville) — thin for a page an answer engine should quote. They quote prices, timelines, counts, and named places, products and people.

    What we’d do: Every page is written from the business's own facts: real prices or ranges, timelines, how many and how big, the products and brands used, the towns and neighborhoods worked in, the people by name — 300 words or more that no competitor could publish unchanged.

  • !

    The first paragraph answers +1 point

    The service page's first paragraph does not say what its headline is about.

    What we’d do: The first paragraph under the headline answers the question the page is for — what, where, for whom — in two or three sentences, so a searcher sees it without scrolling and an engine can lift it whole.

  • ✗

    Page weight +1 point

    3.6 MB downloaded to show the home page on a phone. On a cellular connection that is many seconds before the page settles.

    What we’d do: Our pages weigh 300–700 KB in all: 20–50 KB of HTML, two fonts, pictures sized to the box they fill in WebP or AVIF, and almost no JavaScript.

  • !

    A menu a thumb can use +1 point

    11 links in the header and menu.

    What we’d do: A menu of five to eight items a thumb can hit — the services, the area, about, contact — with the number beside it, and every service page one tap from the home page.

Every check, by category (103 checks)

Technical SEO & indexability 10 of 10 points

  • !

    Sitemap dates

    Every page in the sitemap carries the same date (2026-11-18) — a build stamp, not the day each page changed. Google ignores dates it has learned not to trust.

    What we’d do: Each page's lastmod is the day its own content last changed, written from the content's hash, never the build date.

  • •

    HTTPS certificate

    The certificate could not be read from this platform, but the page was fetched over HTTPS.

  • ✓

    Indexable by search engines

    No noindex on the page or in the headers, and robots.txt lets Googlebot in.

  • ✓

    Structured data Google accepts

    18 schema types on the 2 pages read, and nothing Google would reject: ratings only where they belong and shown on the page, every reference typed, every value filled.

  • ✓

    Canonical URL

    Canonical is https://wilhelmlandscapeandhardscape.com/.

  • ✓

    HSTS header

    Strict-Transport-Security is set — browsers remember to use HTTPS.

  • ✓

    Mixed content

    Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.

  • ✓

    Security headers

    All four baseline security headers are set.

  • ✓

    Sitemap

    Sitemap at https://wilhelmlandscapeandhardscape.com/sitemap.xml — 62 URLs.

  • ✓

    Missing pages return 404

    A made-up URL returns 404, so Google never indexes ghost pages.

  • ✓

    HTTP redirects to HTTPS

    http:// redirects (301) to https://wilhelmlandscapeandhardscape.com/.

  • ✓

    Internal links resolve

    All 40 internal links read (30 on the home page, 10 in llms.txt) answer.

  • ✓

    Language declared

    <html lang="en">.

  • ✓

    Redirect chain

    The URL answers directly, with no redirect.

  • ✓

    robots.txt

    robots.txt is served (5 groups, 1 sitemap line, the private paths repeated in each crawler's own group).

  • ✓

    Sitemap named in robots.txt

    robots.txt names the sitemap: https://wilhelmlandscapeandhardscape.com/sitemap.xml.

  • ✓

    www and apex agree

    www.wilhelmlandscapeandhardscape.com redirects (301) to wilhelmlandscapeandhardscape.com.

  • ✓

    Sitemap lists the live URLs

    The sitemap's 62 URLs are all on https://wilhelmlandscapeandhardscape.com, and the pages read from it answer directly and are open to indexing.

  • ✓

    Lighthouse SEO score

    Lighthouse SEO 100/100.

  • ✓

    Lighthouse best practices

    Lighthouse best practices 100/100.

On-page SEO & content 24 of 25 points

  • !

    A menu a thumb can use

    11 links in the header and menu.

    What we’d do: A menu of five to eight items a thumb can hit — the services, the area, about, contact — with the number beside it, and every service page one tap from the home page.

  • •

    Pages read

    Read with the home page: service page https://wilhelmlandscapeandhardscape.com/services/.

  • •

    Article schema on the post

    No post found in the sitemap to check.

  • ✓

    Page title

    “Landscaping & Hardscapes in Brentwood, TN | Wilhelm” — 51 characters, inside the 30–60 Google shows in full.

  • ✓

    Meta description

    155 characters — fills the space Google shows without being cut.

  • ✓

    Social share cards

    Open Graph title and image and a Twitter card with its own image. A share on any platform unfurls with a picture.

  • ✓

    Titles across the site

    Each page read has its own title of 30–60 characters.

  • ✓

    No stock phrases

    None of the phrases copy falls back on when it has no facts (“look no further”, “we pride ourselves”, “one-stop shop”, a run of “top-notch” and “peace of mind”) on the 2 pages read.

  • ✓

    No placeholder or template text

    No template or placeholder text on the 2 pages read — no lorem ipsum, sample address or number, “add your text here”, or “undefined” where a value should be.

  • ✓

    No stock or AI-marked pictures

    None of the 6 pictures on the pages read is marked as bought stock or AI-made — not by where it is served from, its name, its alt text, or the credits inside the 4 files opened.

  • ✓

    Not a stock template

    No builder or stock theme shows in the page: no template credit, demo pictures or sample text.

  • ✓

    Single H1

    One H1: “Patios, walls, drainage and planting, designed and built for Middle Tennessee ya…”.

  • ✓

    Image alt text

    All 7 images have an alt attribute.

  • ✓

    Readable content in the HTML

    1,308 words of readable text in the HTML.

  • ✓

    Share image loads

    The share image loads (image/jpeg, 85 KB).

  • ✓

    Descriptions across the site

    Each page read has its own description of 120–160 characters.

  • ✓

    Pages that repeat each other

    The pages read share few sentences: at most 2 of 18 (11%) between the service and home pages.

  • ✓

    Canonical and share card on every page

    The inner page read names itself as its canonical, carries a share image and a Twitter card, and has one H1.

  • ✓

    Pictures named and described for what they show

    4 of the 4 pictures on the pages read are named and described for what they show.

  • ✓

    A page for each service

    56 service pages in the sitemap (/landscaping-design-installation/, /brentwood-tn/, /oak-hill-tn/, …).

  • ✓

    Favicon

    A favicon is linked — it shows in the tab and beside the site in Google's results.

  • ✓

    Title and H1 differ

    The title and the H1 are different, each doing its own job.

  • ✓

    About and privacy pages

    The home page links an About page (/about/) and a privacy policy (/privacy/).

  • ✓

    Titles lead with the subject

    The inner pages' titles lead with their subject, not the business name.

  • ✓

    Service pages link each other

    The service page read links 7 other service pages in its copy (/landscaping-design-installation/, /hardscape-construction/, /outdoor-living-patios/).

AI search / AEO / GEO readiness 25 of 35 points

  • ✗

    FAQs on the inner pages

    The service page read carries no FAQ. The questions people ask about a service are what the answer engines quote.

    What we’d do: Every service, area and post page carries its own researched questions — four or more, the ones people ask about that subject, none repeated from another page — visible and in FAQPage schema.

  • !

    Specifics an engine can cite

    The service page (/services/): 359 words, 9 numbers, 1 name (Knoxville) — thin for a page an answer engine should quote. They quote prices, timelines, counts, and named places, products and people.

    What we’d do: Every page is written from the business's own facts: real prices or ranges, timelines, how many and how big, the products and brands used, the towns and neighborhoods worked in, the people by name — 300 words or more that no competitor could publish unchanged.

  • !

    The first paragraph answers

    The service page's first paragraph does not say what its headline is about.

    What we’d do: The first paragraph under the headline answers the question the page is for — what, where, for whom — in two or three sentences, so a searcher sees it without scrolling and an engine can lift it whole.

  • •

    Freshness dates in schema

    No dateModified or datePublished in the schema. Not expected on every home page; a freshness date helps the engines trust the page is current.

  • ✓

    FAQPage schema

    FAQPage schema is present.

  • ✓

    FAQ questions visible on the page

    All 5 questions in the FAQ schema are on the page, with the answers it shows.

  • ✓

    llms.txt

    llms.txt is published (7 KB), headed with the name and linking 60 pages of the site — a plain statement of the business for the AI engines to read.

  • ✓

    Questions answered on the page

    6 questions asked and answered on the pages read (5 on the home page, 1 on the service page) — the shape an AI answer is lifted from.

  • ✓

    Schema on the inner pages

    The inner page read carries its own schema: the business and a BreadcrumbList, with a Service on the service page.

  • ✓

    Readable without JavaScript

    The page's 1,308 words are in the HTML the server sends, so a crawler that runs no JavaScript reads them.

  • ✓

    AI answers may quote the page

    Nothing on the page stops an answer engine from quoting it: no nosnippet, max-snippet limit, noarchive or noai.

  • ✓

    JSON-LD present and valid

    15 schema types: HomeAndConstructionBusiness, ImageObject, Organization, PostalAddress, City, AdministrativeArea, OfferCatalog, Offer, ….

  • ✓

    Extractable structure

    Structure an engine can lift: 6 H2s, 15 H3s, 37 list items.

  • ✓

    AI crawlers allowed

    robots.txt lets every answer engine in: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User and the rest. GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot each get the home page from the edge, as a browser does.

  • ✓

    Speakable specification

    A speakable specification is present.

Local SEO & entity signals 4 of 5 points

  • ✗

    Trust signals

    No insurance, guarantee, license or accreditation language on the home page. Noted, not scored.

    What we’d do: Insurance, a written guarantee and the trade's credentials, stated plainly where the visitor decides.

  • ✗

    Hours shown and in schema

    No hours on the home page or in the schema. “Are they open now?” is the first thing map search and a visitor want to know.

    What we’d do: The hours on every page, in the footer or beside the number, and the same hours in openingHoursSpecification, as the Business Profile shows them.

  • !

    Linked to its profiles

    sameAs names only Nextdoor. The Google Business Profile is the one the map pack and Google's AI read first.

    What we’d do: The business node's sameAs lists every real profile — the Google Business Profile first, then Facebook, Yelp, BBB and the trade's own directories — and the footer links to them.

  • !

    Reviews on the page

    Reviews are quoted but there is no rating or count beside them, and nothing says how many there are.

    What we’d do: The Google rating and count, three or more reviews quoted word for word with the reviewer's first name, and a link to the profile they live on — in the HTML, so the engines read them too.

  • ✓

    Business entity schema

    HomeAndConstructionBusiness schema names the business.

  • ✓

    Service area stated by town

    The service area is stated by town: Brentwood, TN, Franklin, TN and Nashville, TN, in the schema too.

  • ✓

    Business schema completeness

    The business node carries name, url, telephone, address, logo or image, areaServed.

  • ✓

    Address and phone on the page

    The phone ((615) 484-6854) and where the business is (Brentwood, TN) are on the page as text, and the phone matches the schema's.

  • ✓

    Site name for Google

    WebSite schema names the site “Wilhelm Landscapes & Hardscapes” — the name Google shows above each result.

  • ✓

    The trade's own schema type

    HomeAndConstructionBusiness: schema.org's own type for what the business does.

  • ✓

    A named person

    A named person in the schema: Hunter Wilhelm.

Speed, scripts & mobile 19 of 20 points

  • ✗

    Page weight

    3.6 MB downloaded to show the home page on a phone. On a cellular connection that is many seconds before the page settles.

    What we’d do: Our pages weigh 300–700 KB in all: 20–50 KB of HTML, two fonts, pictures sized to the box they fill in WebP or AVIF, and almost no JavaScript.

  • •

    Interaction to Next Paint (INP)

    No real-user INP yet — Google reports it once a page has enough visitors on Chrome. It measures how quickly the page reacts to a tap.

  • ✓

    Mobile viewport

    The viewport meta tag is set for phones.

  • ✓

    No popup on arrival

    Nothing covers the page on arrival: no popup, no email gate.

  • ✓

    Readable and tappable on a phone

    Every piece of text Google's test measured on a phone clears WCAG AA contrast, and the buttons and links are big enough, and far enough apart, to tap.

  • ✓

    Mobile PageSpeed score

    Lighthouse mobile performance 94/100. Google's own bands: 90 and up is good, 50–89 needs improvement.

  • ✓

    Lighthouse accessibility score

    Lighthouse accessibility 98/100.

  • ✓

    Scripts and third parties

    2 scripts, 19 KB of JavaScript, from 1 third party (static.cloudflareinsights.com).

  • ✓

    Nothing blocks the first paint

    1 file loads before anything is drawn — styles and scripts in the head — and PageSpeed puts 0.4 s of the first paint on waiting for it.

  • ✓

    Image hygiene

    7 images: 7 with dimensions, 7 in a modern format or through an image service, 5 lazy-loaded.

  • ✓

    No hero slider or autoplay video

    One hero: no slider and no autoplaying video in the first screen.

  • ✓

    Cumulative Layout Shift (CLS)

    Cumulative Layout Shift 0.00 (lab). Google's thresholds: 0.1 good, 0.25 poor.

  • ✓

    Fonts

    2 font files (45 KB) from Google Fonts.

  • ✓

    The hero image loads first

    The hero image is asked for early and not lazy-loaded (<img srcset="/assets/img/mood/paver-pool-deck-dusk-640.2e496181.webp 6).

  • ✓

    Pinch-to-zoom allowed

    Pinch-to-zoom is allowed.

  • ✓

    No fixed-width overflow

    No inline widths of 400px or more that would push past a phone screen.

  • ✓

    Time to first byte

    First byte in 283 ms from our server.

  • ✓

    HTML weight

    About 9 KB compressed (34 KB of HTML).

  • ✓

    Compression

    Compressed, as Google's PageSpeed test read the page from outside; this scan runs inside Cloudflare's network, where Cloudflare's compression never shows.

  • ✓

    HTTP/2 or HTTP/3

    HTTP/2 — Google's PageSpeed test loaded the page over it (this scan cannot read the protocol itself).

  • ✓

    One chat widget at most

    No chat widget scripts on the page.

  • ✓

    Largest Contentful Paint (LCP)

    Largest Contentful Paint 2.6 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).

  • ✓

    Static files cached

    1 file served with a short or missing cache lifetime, 0 of them the site's own.

  • ✓

    What would speed it up most

    Nothing large left to fix. PageSpeed's remaining suggestions: Render-blocking requests (about 0.4 s); Improve image delivery (about 0.1 s).

Conversion & lead generation 5 of 5 points

  • •

    Chat or text option

    No chat or text option. Not a fault, but a share of visitors will not call; an assistant that answers in seconds, day and night, is the cheapest lead a site can add.

  • ✓

    Contact form

    1 form on the home page.

  • ✓

    Call to action in the first screen

    A phone link, a form or a quote button appears in the top of the page.

  • ✓

    Lead form wiring

    The form posts to /api/lead, guarded by a honeypot.

  • ✓

    Analytics installed

    Measured by Google Analytics.

  • ✓

    Tappable phone number

    6 tel: links — the number dials from a phone.

  • ✓

    A lead form that fits a phone

    The lead form asks 6 fields, labeled, and fits a phone screen.

  • ✓

    No CAPTCHA puzzle

    No CAPTCHA puzzle on the page.

Read with the home page: service page wilhelmlandscapeandhardscape.com/services/

Want these fixed?

Every fix above is part of the work Zorva Labs does. Tell us the business and what you want from the site, and a written, priced proposal comes back in one business day.

Want this fixed?

We can fix every issue on wilhelmlandscapeandhardscape.com.

Zorva Labs builds, hosts and grows websites for businesses across the United States — including the fixes flagged above. Every engagement is priced to the project, with a written proposal in one business day.

ReplyOne business day
ProposalWritten · scoped · priced
ContractMonth to month
Proposal request

Tell us what you need

No spam · One business day reply · Month to month