nashvilleslandscapelighting.com scored 96/100 on the website scan.
Strong
nashvilleslandscapelighting.com · Scanned 2026-11-07
Up from 92 on 2026-10-09
89 passed4 warnings4 failed
- Technical SEO & indexability10/10 of 10 points
- On-page SEO & content24/25 of 25 points
- AI search / AEO / GEO readiness35/35 of 35 points
- Local SEO & entity signals4/5 of 5 points
- Speed, scripts & mobile20/20 of 20 points
- Conversion & lead generation3/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
-
✗
Tappable phone number +1 point
No phone number on the home page. For a service business the call is the conversion.
What we’d do: A tappable number in the header, the hero and the footer of every page.
-
✗
Service pages link each other +1 point
The service page read links none of the other 5 service pages in its copy. Each stands alone, so nothing moves between them but the menu.
What we’d do: Every service page names the related services in its own copy — the repair page links the replacement page, the inspection page the repair — so a visitor and a crawler move between them without the menu.
-
!
A lead form that fits a phone +1 point
The lead form asks 11 fields. Every field costs a share of the people who start it.
What we’d do: Name, phone, what they need: three to five fields, each labeled, the phone field a tel input so the keypad comes up, and one tap to send.
-
✗
Linked to its profiles +1 point
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.
-
!
Address and phone on the page +1 point
The page says where the business is (Free Quote Nashville, TN) but shows no phone number.
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.
Every check, by category (103 checks)
Technical SEO & indexability 10 of 10 points
-
•
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
17 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://nashvilleslandscapelighting.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://nashvilleslandscapelighting.com/sitemap.xml — 12 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://nashvilleslandscapelighting.com/.
-
✓
Internal links resolve
All 12 internal links read on the home page 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://nashvilleslandscapelighting.com/sitemap.xml.
-
✓
www and apex agree
www.nashvilleslandscapelighting.com redirects (301) to nashvilleslandscapelighting.com.
-
✓
Sitemap lists the live URLs
The sitemap's 12 URLs are all on https://nashvilleslandscapelighting.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.
-
✓
Sitemap dates
12 pages with lastmod dates, from 2026-10-11 to 2026-11-05.
On-page SEO & content 24 of 25 points
-
✗
Service pages link each other
The service page read links none of the other 5 service pages in its copy. Each stands alone, so nothing moves between them but the menu.
What we’d do: Every service page names the related services in its own copy — the repair page links the replacement page, the inspection page the repair — so a visitor and a crawler move between them without the menu.
-
•
Pages read
Read with the home page: service page https://nashvilleslandscapelighting.com/landscape-lighting/.
-
•
Article schema on the post
No post found in the sitemap to check.
-
✓
Page title
“Landscape Lighting & Christmas Lights in Nashville, TN” — 54 characters, inside the 30–60 Google shows in full.
-
✓
Meta description
154 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 9 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 6 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: “Landscape & Holiday Lighting in Nashville”.
-
✓
Image alt text
All 10 images have an alt attribute.
-
✓
Readable content in the HTML
839 words of readable text in the HTML.
-
✓
Share image loads
The share image loads (image/jpeg, 30 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 1 of 21 (5%) between the home and service 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
7 of the 7 pictures on the pages read are named and described for what they show.
-
✓
A page for each service
6 service pages in the sitemap (/landscape-lighting/, /repairs/, /architectural-lighting/, …).
-
✓
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.
-
✓
A menu a thumb can use
4 links in the header and menu, and the service page read is one tap from the home page.
AI search / AEO / GEO readiness 35 of 35 points
-
•
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 4 questions in the FAQ schema are on the page, with the answers it shows.
-
✓
llms.txt
llms.txt is published (8 KB), headed with the name and linking 12 pages of the site — a plain statement of the business for the AI engines to read.
-
✓
Questions answered on the page
8 questions asked and answered on the pages read (4 on the home page, 4 on the service page) — the shape an AI answer is lifted from.
-
✓
FAQs on the inner pages
The inner page read carries its own FAQ with schema (4 questions on the service page), none repeated from another page.
-
✓
Specifics an engine can cite
The service page (/landscape-lighting/): 578 words, 4 numbers, 18 names (LED, Davidson, County, Franklin, …) — specifics only this business could publish, the kind an answer engine quotes.
-
✓
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 839 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: LocalBusiness, ImageObject, Organization, PostalAddress, OpeningHoursSpecification, City, AdministrativeArea, OfferCatalog, ….
-
✓
Extractable structure
Structure an engine can lift: 5 H2s, 12 H3s, 30 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.
-
✓
The first paragraph answers
The first paragraph under the H1 answers in 22 words on the home page and 32 words on the service page.
-
✓
Speakable specification
A speakable specification is present.
Local SEO & entity signals 4 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.
-
✗
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.
-
!
Address and phone on the page
The page says where the business is (Free Quote Nashville, TN) but shows no phone number.
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.
-
!
The trade's own schema type
LocalBusiness — a generic type. schema.org has one for nearly every trade, and the engines file a business by it.
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.
-
!
Reviews on the page
The home page mentions “Nextdoor review” but shows none. For a new business that is the right start; the first three go on the page as they come in.
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
LocalBusiness schema names the business.
-
✓
Service area stated by town
The service area is stated by town: Nashville, TN, Franklin, TN, Brentwood, TN and Nolensville, TN and 8 more, in the schema too.
-
✓
Business schema completeness
The business node carries name, url, address, logo or image, areaServed, openingHours.
-
✓
Site name for Google
WebSite schema names the site “Nashville’s Landscape Lighting” — the name Google shows above each result.
-
✓
A named person
The business node names its founder or people.
-
✓
Hours shown and in schema
The hours are on the page and in the business schema.
Speed, scripts & mobile 20 of 20 points
-
•
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 93/100. Google's own bands: 90 and up is good, 50–89 needs improvement.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 96/100.
-
✓
Scripts and third parties
3 scripts, 18 KB of JavaScript, from 2 third parties (static.cloudflareinsights.com and Google Tag Manager).
-
✓
Nothing blocks the first paint
1 file loads before anything is drawn — styles and scripts in the head — and PageSpeed puts 0.3 s of the first paint on waiting for it.
-
✓
Image hygiene
10 images: 10 with dimensions, 10 in a modern format or through an image service, 8 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 (86 KB) from Google Fonts.
-
✓
The hero image loads first
The hero image is asked for early and not lazy-loaded (<img srcset="/assets/img/scenes/craftsman-home-dusk-lighting-640.0c782).
-
✓
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 117 ms from our server.
-
✓
HTML weight
About 7 KB compressed (31 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 3.0 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).
-
✓
Page weight
416 KB downloaded to show the home page on a phone.
-
✓
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.3 s); Improve image delivery (about 0.1 s).
Conversion & lead generation 3 of 5 points
-
✗
Tappable phone number
No phone number on the home page. For a service business the call is the conversion.
What we’d do: A tappable number in the header, the hero and the footer of every page.
-
!
A lead form that fits a phone
The lead form asks 11 fields. Every field costs a share of the people who start it.
What we’d do: Name, phone, what they need: three to five fields, each labeled, the phone field a tel input so the keypad comes up, and one tap to send.
-
•
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 Turnstile and a honeypot.
-
✓
Analytics installed
Measured by Google Analytics.
-
✓
No CAPTCHA puzzle
Cloudflare Turnstile: a bot check nobody has to solve.
Read with the home page: service page nashvilleslandscapelighting.com/landscape-lighting/
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 nashvilleslandscapelighting.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.