wilhelmlandscapesandhardscapes.com scored 35/100 on the website scan.
Major issues
wilhelmlandscapesandhardscapes.com · Scanned 2026-11-06
47 passed23 warnings24 failed
- Technical SEO & indexability6/10 of 10 points
- On-page SEO & content7/25 of 25 points
- AI search / AEO / GEO readiness9/35 of 35 points
- Local SEO & entity signals3/5 of 5 points
- Speed, scripts & mobile6/20 of 20 points
- Conversion & lead generation4/5 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
-
✗
FAQPage schema +5 points
No FAQ — not in the schema and not on the page. Question-and-answer blocks are what the answer engines lift most readily.
What we’d do: Every substantive page carries a visible FAQ with FAQPage schema built from the same text.
-
✗
Questions answered on the page +5 points
No question is asked and answered on the 2 pages read. When someone asks ChatGPT or Google's AI about a service, the engines quote pages that ask that question and answer it in a sentence or two.
What we’d do: Every service page answers the questions people ask about that service — four or more, each asked as a heading and answered in its first sentence — with FAQPage schema from the same text.
-
✗
FAQs on the inner pages +5 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 +2 points
The service page (/): 784 words, 2 numbers, 2 names (Middle, French) — 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.
-
!
Schema on the inner pages +2 points
The service page (/) has no BreadcrumbList and no Service for what it offers.
What we’d do: Every page carries the business node, a BreadcrumbList and its own type — a Service on each service page, BlogPosting on each post — so an engine knows what each page is and whose it is.
Every check, by category (103 checks)
Technical SEO & indexability 6 of 10 points
-
✗
Security headers
Missing 4 of the four baseline security headers: Content-Security-Policy, X-Content-Type-Options, frame protection (X-Frame-Options or CSP frame-ancestors), Referrer-Policy.
What we’d do: Content-Security-Policy, X-Content-Type-Options, frame protection and Referrer-Policy on every response.
-
!
HSTS header
No Strict-Transport-Security header. Browsers still use HTTPS, but a first visit typed without it can be intercepted.
What we’d do: HSTS with a one-year max-age on every response.
-
!
Missing pages return 404
A made-up URL redirects (301) instead of returning 404. Better than a soft 404, but a redirect to the home page still teaches Google the site has no missing pages.
What we’d do: Missing routes return a real 404 with a helpful page.
-
!
robots.txt
robots.txt is served, but OAI-SearchBot, ChatGPT-User, GPTBot and PerplexityBot and others have groups of their own that don't repeat the * group's Disallow: /wp-admin/. A crawler named in its own group follows only that group, so they may read what the site keeps from every other crawler.
What we’d do: Every group in robots.txt repeats the private paths, so a crawler named on its own is kept out of them too.
-
!
Lighthouse SEO score
Lighthouse SEO 85/100 — the report names what to fix.
What we’d do: Our sites score 100 on Lighthouse SEO: every page crawlable, titled, described, with valid links and alt text.
-
!
Sitemap lists the live URLs
The service page it lists (/elementor-hf/footer/) redirects to /.
What we’d do: The sitemap is written from the pages themselves on every build: only final, indexable https URLs, on the one host the site answers on.
-
•
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
5 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://wilhelmlandscapesandhardscapes.com/.
-
✓
Mixed content
Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.
-
✓
Sitemap
Sitemap at https://wilhelmlandscapesandhardscapes.com/sitemap_index.xml — an index of 5 sitemaps.
-
✓
HTTP redirects to HTTPS
http:// redirects (301) to https://wilhelmlandscapesandhardscapes.com/.
-
✓
Internal links resolve
All 10 internal links read on the home page answer (the rest were not reached in the time a scan allows).
-
✓
Language declared
<html lang="en-US">.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
Sitemap named in robots.txt
robots.txt names the sitemap: https://wilhelmlandscapesandhardscapes.com/sitemap_index.xml.
-
✓
www and apex agree
www.wilhelmlandscapesandhardscapes.com redirects (301) to wilhelmlandscapesandhardscapes.com.
-
✓
Lighthouse best practices
Lighthouse best practices 100/100.
-
✓
Sitemap dates
1 page with lastmod dates.
On-page SEO & content 7 of 25 points
-
✗
Page title
“Home - Wilhelm Landscapes & Hardscapes Brentwood TN Custom Outdoor Living” is 73 characters — a third of it is cut in search results.
What we’d do: We write titles of 30–60 characters, the topic first and the brand last.
-
✗
Titles across the site
the service page's title is 73 characters.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
Single H1
No H1 heading on the page — the one line that says what the page is about.
What we’d do: Every page gets one H1 that names the service and the place.
-
✗
Descriptions across the site
the service page's description repeats the home page's.
What we’d do: Every page gets its own 120–160 character description, checked in the build.
-
✗
Pages that repeat each other
40 of the 40 sentences on the home page also appear on the service page (100%). Pages that repeat each other with a word swapped are what Google's scaled-content rules are written against.
What we’d do: Every page is written once, for its own subject, from the business's own facts — no page is another with the city swapped.
-
✗
No stock phrases
The home page: “we take pride in” and 4 brochure phrases (“comprehensive”, “transform your”, “attention to detail”, …); the service page: “we take pride in” and 4 brochure phrases (“comprehensive”, “transform your”, “attention to detail”, …). This is what copy written without facts sounds like: nothing in it only this business could say.
What we’d do: Every sentence is written from the business's own facts — what the crew found, what it cost, what the owner says — so none of it is a line any competitor could use.
-
✗
A menu a thumb can use
11 links in the header and menu; the service page read (/elementor-hf/footer/) is not linked from the home page. A phone shows about seven menu items before the visitor has to scroll the menu itself.
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.
-
!
Canonical and share card on every page
The service page (/) has no H1.
What we’d do: Every page names itself as its canonical, carries its own og:image and twitter:image, and opens with one H1 — checked on every page before the site ships.
-
!
A page for each service
Only 1 service page in the sitemap (/elementor-hf/footer/). A service with no page of its own has nothing to rank for it.
What we’d do: A page for every service the business sells, each with its own title, its own words, its own FAQ and Service schema, so a search for that service lands on the page about it and an engine can quote it.
-
!
About and privacy pages
The home page links an About page (/about/) but no privacy policy — a site whose form takes names, phone numbers and emails says what it does with them.
What we’d do: An About page with the owner and the crew by name, their photos and roles, and a privacy policy, both linked from every page's footer.
-
!
No stock or AI-marked pictures
2 pictures marked as bought stock on the pages read: istockphoto-508072701-612x612-1.jpg (an iStock download's name); istockphoto-184154120-612x612-1.jpg (an iStock download's name). Visitors comparing businesses, and Google's quality raters, look for photos of the business's own work.
What we’d do: The owner's own photos of real jobs are the proof of work, in every section that shows the work; a stock or generated picture only ever sets the mood, and it is named and described for what it shows.
-
!
Not a stock template
Built with WordPress, the Astra theme and Elementor: Astra is a stock theme thousands of sites run, most of them from the same starter layouts.
What we’d do: A site designed for this business — its own layout, type and colors, written from its own facts — with nothing left of whatever it was built from.
-
•
Title and H1 differ
Skipped — no title or no H1 to compare.
-
•
Service pages link each other
Skipped — fewer than three service pages to link between.
-
•
Pages read
Read with the home page: service page https://wilhelmlandscapesandhardscapes.com/elementor-hf/footer/.
-
•
Article schema on the post
No post found in the sitemap to check.
-
✓
Meta description
157 characters — fills the space Google shows without being cut.
-
✓
Social share cards
Open Graph title and image and a Twitter card. A share on any platform unfurls with a picture.
-
✓
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.
-
✓
Image alt text
All 20 images have an alt attribute.
-
✓
Readable content in the HTML
948 words of readable text in the HTML.
-
✓
Share image loads
The share image loads (image/jpeg, 306 KB).
-
✓
Pictures named and described for what they show
15 of the 18 pictures on the pages read are named and described for what they show (not: 3 with alt text that describes nothing (“vector” on 3 pictures)).
-
✓
Favicon
A favicon is linked — it shows in the tab and beside the site in Google's results.
-
✓
Titles lead with the subject
The inner pages' titles lead with their subject, not the business name.
AI search / AEO / GEO readiness 9 of 35 points
-
✗
FAQPage schema
No FAQ — not in the schema and not on the page. Question-and-answer blocks are what the answer engines lift most readily.
What we’d do: Every substantive page carries a visible FAQ with FAQPage schema built from the same text.
-
✗
Questions answered on the page
No question is asked and answered on the 2 pages read. When someone asks ChatGPT or Google's AI about a service, the engines quote pages that ask that question and answer it in a sentence or two.
What we’d do: Every service page answers the questions people ask about that service — four or more, each asked as a heading and answered in its first sentence — with FAQPage schema from the same text.
-
✗
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.
-
✗
The first paragraph answers
The home page has no H1 to answer under; the service page has no H1 to answer under. An answer engine quotes the sentence right under the heading.
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.
-
!
Specifics an engine can cite
The service page (/): 784 words, 2 numbers, 2 names (Middle, French) — 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.
-
!
Schema on the inner pages
The service page (/) has no BreadcrumbList and no Service for what it offers.
What we’d do: Every page carries the business node, a BreadcrumbList and its own type — a Service on each service page, BlogPosting on each post — so an engine knows what each page is and whose it is.
-
!
AI crawlers allowed
robots.txt blocks CCBot (Common Crawl (training data for many models)). A defensible choice for training data, but every answer engine is allowed. GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot each get the home page from the edge, as a browser does.
What we’d do: We block nothing an answer engine reads.
-
•
FAQ questions visible on the page
Skipped — no FAQ schema to compare.
-
•
Speakable specification
No speakable specification. Google's speakable is a news-only beta, so this is noted, not scored.
-
✓
llms.txt
llms.txt is published (1 KB), headed with the name and linking 2 pages of the site — a plain statement of the business for the AI engines to read.
-
✓
Readable without JavaScript
The page's 948 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
5 schema types: WebSite, WebPage, Organization, Person, SearchAction.
-
✓
Freshness dates in schema
Newest date in the schema: 2026-06-11.
-
✓
Extractable structure
Structure an engine can lift: 7 H2s, 4 H3s, 36 list items.
Local SEO & entity signals 3 of 5 points
-
✗
Linked to its profiles
Nothing ties this site to the business's profiles elsewhere: no sameAs in the schema, and no link to a Google Business Profile, Facebook or Yelp page. Those links are how the engines tell this business from others with a similar name.
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.
-
✗
The trade's own schema type
Organization only: it says a company exists, not what it does or where.
What we’d do: The business node uses schema.org's own type for the trade — RoofingContractor, Plumber, HVACBusiness, Electrician, HousePainter, GeneralContractor, MovingCompany, Locksmith and the rest under HomeAndConstructionBusiness and LocalBusiness — so the engines file it under what it does, not only that it exists.
-
✗
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.
-
!
Business schema completeness
The business node has name, url, logo or image but not telephone, address.
What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.
-
!
Address and phone on the page
The phone is on the page, but not the town or the street address. Map search and the answer engines place a business by what its pages say.
What we’d do: The business name, phone and town — or street address — in the footer of every page, exactly as the Google Business Profile has them, and the same in the schema.
-
!
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
Organization schema names the business.
-
✓
Service area stated by town
The service area is stated by town: Serving Brentwood, Franklin and Nashville.
-
✓
Site name for Google
WebSite schema names the site “Wilhelm Landscapes & Hardscapes Brentwood TN Custom Outd” — the name Google shows above each result.
-
✓
A named person
A named person in the schema: ar6fhDSFw2yb5a.
Speed, scripts & mobile 6 of 20 points
-
✗
Nothing blocks the first paint
54 files load before anything is drawn — styles and scripts in the head — and PageSpeed puts 6.8 s of the first paint on waiting for them.
What we’d do: The styles the first screen needs are inlined and the rest load after it, every script is deferred, and the hero image is preloaded: nothing stands between the HTML and the first paint.
-
✗
Fonts
9 font files (341 KB) from Google Fonts and wilhelmlandscapesandhardscapes.com. 3 faces without font-display, so the words wait for the file.
What we’d do: Two font families in the weights the page uses, from one host, with font-display set so the words show at once in a fallback face.
-
✗
Readable and tappable on a phone
5 pieces of text are too faint to read against their background (“(615) 484-6854” 3.5:1, “huntertwilhelm@gmail.com” 3.5:1, “Get A Free Quote” 3.5:1); WCAG asks 4.5:1 for text that size. 4 buttons or links are too small or too close to others to tap reliably (“Go to slide 1”, “Go to slide 2”, “Go to slide 3”). Google's test read the page as a phone shows it.
What we’d do: Every word clears WCAG AA contrast — 4.5:1, or 3:1 for large text — measured as rendered at phone and desktop widths, and every button and link is at least 44 pixels square with room around it.
-
✗
Time to first byte
First byte took 2.3 s from our server — the page cannot be fast if the server is slow to start.
What we’d do: Static pages served from an edge network answer in well under half a second.
-
✗
Compression
The HTML is sent uncompressed — three to five times more bytes than it needs.
What we’d do: Brotli or gzip on every text response; every host we use does it by default.
-
✗
Largest Contentful Paint (LCP)
Largest Contentful Paint 10.5 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).
What we’d do: The hero image sized and preloaded, no render-blocking scripts, a fast first byte: our pages paint in about a second.
-
✗
Page weight
3.2 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.
-
✗
Static files cached
90 files served with a short or missing cache lifetime, 90 of them the site's own. Every visit downloads the site again.
What we’d do: Every static file — styles, scripts, fonts, pictures — is served with a year-long cache header and a fingerprinted name, so a return visit downloads only the HTML.
-
!
Mobile PageSpeed score
Lighthouse mobile performance 56/100. Google calls 50–89 “needs improvement”; lab runs vary, so we grade 70 and up as a pass.
What we’d do: Our sites score 90 and up on mobile: static HTML from an edge network, images sized and in modern formats, almost no JavaScript.
-
!
Scripts and third parties
29 scripts, 652 KB of JavaScript, from no third party. Every script is a download, a parse and a run on a phone before the visitor can tap anything.
What we’d do: Our pages load one analytics tag and the form's bot check — two third parties and under 100 KB of JavaScript — and nothing runs before the page is drawn.
-
!
Image hygiene
20 images: 12 with dimensions, 0 in a modern format or through an image service, 8 lazy-loaded. none are WebP or AVIF, which are half the size of JPEG and PNG.
What we’d do: Every image has width and height, is served as WebP or AVIF at the size it is shown, and loads lazily below the fold.
-
!
HTTP/2 or HTTP/3
Google's PageSpeed test loaded the page over http/1.1 — HTTP/1.1 loads one resource at a time per connection.
What we’d do: Every host we use speaks HTTP/2 and HTTP/3.
-
!
No hero slider or autoplay video
A video plays itself in the first screen. On a phone that is megabytes before the headline is readable, and the words on top of it move.
What we’d do: One hero: one picture, one headline, one call to action. A slider shows the visitor's answer for a few seconds and then takes it away, and it is the heaviest thing on most templated pages.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Use efficient cache lifetimes (about 6.9 s); Render-blocking requests (about 6.8 s); Reduce unused CSS (about 3.0 s).
What we’d do: These are the first three things we would fix.
-
•
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.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 92/100.
-
✓
Cumulative Layout Shift (CLS)
Cumulative Layout Shift 0.02 (lab). Google's thresholds: 0.1 good, 0.25 poor.
-
✓
The hero image loads first
The largest thing on the first screen is text or a styled block (<p class="elementor-heading-title elementor-size-default">), which paints as soon as the HTML arrives.
-
✓
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.
-
✓
HTML weight
About 30 KB compressed (191 KB of HTML).
-
✓
One chat widget at most
No chat widget scripts on the page.
Conversion & lead generation 4 of 5 points
-
!
Analytics installed
No analytics tag found — nothing counts the visits, the calls or the forms, so nothing can be improved on evidence.
What we’d do: First-party traffic logging on every site, and GA4 as the second source.
-
•
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 back to the page, where a script sends it (no spam guard shows in the page; a filter on the server can't be seen from outside).
-
✓
Tappable phone number
2 tel: links — the number dials from a phone.
-
✓
A lead form that fits a phone
The lead form asks 5 fields, labeled, and fits a phone screen.
-
✓
No CAPTCHA puzzle
No CAPTCHA puzzle on the page.
Read with the home page: service page wilhelmlandscapesandhardscapes.com/elementor-hf/footer/
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.
We can fix every issue on wilhelmlandscapesandhardscapes.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.