allsummerlandscapingtn.com scored 38/100, provisionally, on the website scan.
PageSpeed Insights could not be measured (PageSpeed Insights did not answer within 60 seconds.), so the performance checks are not in the score.
Major issues · provisional
allsummerlandscapingtn.com · Scanned 2026-09-29
Unchanged from 2026-09-29
37 passed17 warnings12 failed
- Technical SEO & indexability9/15 of 15 points
- On-page SEO & content6/20 of 20 points
- AI search / AEO / GEO readiness5/30 of 30 points
- Local SEO & entity signals3/10 of 10 points
- Performance & mobile7/10 of 10 points
- Trust / E-E-A-T / reputation3/10 of 10 points
- Conversion & lead generation5/5 of 5 points
Why AI search is 30 of the 100 points
Google is sending fewer people to websites. When it answers with an AI Overview, the top-ranked page gets 58% fewer clicks (Ahrefs, 300,000 keywords, 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 +4 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 +4 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.
-
✗
Specifics an engine can cite +4 points
The post page (/landscaping-mistakes/) gives no number — no price, timeline, size or count — and names only Antarctica beyond the business and its town. A competitor could publish it unchanged, and the answer engines quote pages with specifics they can check.
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.
-
✗
Business entity schema +4 points
No Organization or LocalBusiness schema. The engines have no entity to attach the reviews, the phone and the service area to.
What we’d do: LocalBusiness (or the trade's own type) with name, phone, address, hours, service area and sameAs on every page.
-
✗
llms.txt +3 points
No llms.txt at the site root. ChatGPT, Claude and Perplexity have to piece the business together from the pages.
What we’d do: Every site ships an llms.txt written from its facts: who, what, where, the proof, the pages.
Every check, by category (85 checks)
Technical SEO & indexability 9 of 15 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.
-
✗
Sitemap lists the live URLs
All 999 of its URLs are on http://allsummerlandscapingtn.com while the site answers on https://allsummerlandscapingtn.com, so each one redirects — Search Console files them under “Page with redirect” rather than indexing them; the post page it lists (/landscaping-mistakes/) redirects to /landscaping-mistakes/.
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.
-
!
Internal links resolve
/testimonials/ (404) and /blog/ (500) answer with an error, of the 23 internal links read on the home page.
What we’d do: Every internal link points at a page that exists: the build checks each one before it ships, and a page that moves gets a 301 from its old address.
-
!
Structured data Google accepts
An article's author or publisher written as a bare {"@id"} with no type beside it (the post page).
What we’d do: Structured data generated from the page's own content and checked against Google's rules before every deploy: a rating only on the business and only where the page shows it, every reference typed, no empty values.
-
!
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.
-
!
robots.txt
robots.txt is served, but Googlebot has a group of its own that doesn't repeat the * group's Disallow: /wp-admin/. A crawler named in its own group follows only that group, so it 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.
-
!
Sitemap named in robots.txt
robots.txt has no Sitemap: line — Google and Bing have to find the sitemap some other way.
What we’d do: Every robots.txt names the sitemap.
-
•
HTTPS certificate
The certificate could not be read from this platform, but the page was fetched over HTTPS.
-
•
www and apex agree
www.allsummerlandscapingtn.com answered 530.
-
•
Lighthouse SEO score
Not measured — PageSpeed Insights did not answer.
-
•
Lighthouse best practices
Not measured — PageSpeed Insights did not answer.
-
✓
Indexable by search engines
No noindex on the page or in the headers, and robots.txt lets Googlebot in.
-
✓
Canonical URL
Canonical is https://allsummerlandscapingtn.com/.
-
✓
Mixed content
Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.
-
✓
Sitemap
Sitemap at https://allsummerlandscapingtn.com/sitemap_index.xml — an index of 65 sitemaps.
-
✓
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://allsummerlandscapingtn.com/.
-
✓
Language declared
<html lang="en-US">.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
Sitemap dates
999 pages with lastmod dates, from 2015-12-22 to 2026-07-07.
On-page SEO & content 6 of 20 points
-
✗
Titles across the site
the post page's title is 20 characters.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
Image alt text
21 of 22 images have no alt attribute — screen readers and image search get nothing.
What we’d do: Every image gets an alt that says what is in it; decorative ones get alt="".
-
✗
No stock phrases
The home page: “look no further” and 3 brochure phrases (“peace of mind”, “world-class”, “top-notch”). 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.
-
!
Page title
“Landscaping Murfreesboro & Franklin TN | All Summer Landscape Group” is 67 characters. Google shows about 60 and cuts the rest, so the end of it is lost in results.
What we’d do: We write titles of 30–60 characters, the topic first and the brand last, so nothing is cut.
-
!
Meta description
166 characters. Google shows about 160 and cuts the rest with an ellipsis.
What we’d do: We write descriptions of 120–160 characters, the point first.
-
!
Single H1
2 H1 headings. One is the convention search engines and screen readers expect.
What we’d do: One H1 per page; the rest become H2s.
-
!
Social share cards
Only part of the share markup: Twitter card is there, Open Graph is not.
What we’d do: Every page carries og:title, og:image, twitter:card and twitter:image.
-
!
Canonical and share card on every page
The post page (/landscaping-mistakes/) 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.
-
•
Share image loads
Skipped — no og:image to fetch.
-
•
Pages read
Read with the home page: post page http://Allsummerlandscapingtn.com/landscaping-mistakes/.
-
✓
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.
-
✓
Readable content in the HTML
476 words of readable text in the HTML.
-
✓
Pages that repeat each other
The pages read share no sentences beyond the header, footer and calls to action.
-
✓
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.
-
✓
Descriptions across the site
Each page read has its own description of 120–160 characters.
-
✓
Pictures named and described for what they show
11 of the 11 pictures on the pages read are named and described for what they show.
AI search / AEO / GEO readiness 5 of 30 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.
-
✗
Specifics an engine can cite
The post page (/landscaping-mistakes/) gives no number — no price, timeline, size or count — and names only Antarctica beyond the business and its town. A competitor could publish it unchanged, and the answer engines quote pages with specifics they can check.
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.
-
✗
llms.txt
No llms.txt at the site root. ChatGPT, Claude and Perplexity have to piece the business together from the pages.
What we’d do: Every site ships an llms.txt written from its facts: who, what, where, the proof, the pages.
-
✗
FAQs on the inner pages
The post 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.
-
!
Schema on the inner pages
The post page (/landscaping-mistakes/) has nothing naming the business.
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.
-
•
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.
-
✓
Readable without JavaScript
The page's 476 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
8 schema types: WebPage, ReadAction, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification.
-
✓
Freshness dates in schema
Newest date in the schema: 2026-07-14.
-
✓
Extractable structure
Structure an engine can lift: 7 H2s, 0 H3s, 40 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.
Local SEO & entity signals 3 of 10 points
-
✗
Business entity schema
No Organization or LocalBusiness schema. The engines have no entity to attach the reviews, the phone and the service area to.
What we’d do: LocalBusiness (or the trade's own type) with name, phone, address, hours, service area and sameAs on every page.
-
!
Linked to its profiles
The page links Facebook and YouTube, but there is no business node to carry a sameAs naming them, so the engines have to guess that they are the same business.
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.
-
!
Service area stated
The home page does not say which towns the business serves — visitors and engines both need it.
What we’d do: A service-area line in the hero and footer, a page per town, and areaServed in the schema.
-
•
Business schema completeness
Skipped — no business node to read.
-
✓
Address and phone on the page
The phone ((615) 604-8942) and where the business is (Murfreesboro, Tennessee) are on the page as text.
-
✓
Site name for Google
WebSite schema names the site “All Summer Landscaping” — the name Google shows above each result.
Performance & mobile 7 of 10 points
-
✗
Image hygiene
20 images: 1 with dimensions, 0 in a modern format or through an image service, 0 lazy-loaded. 19 of 20 images have no width and height, so the page jumps as they load; 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.
-
!
HTML weight
About 120 KB compressed (341 KB of HTML) — heavy for one page; the usual cause is inlined scripts and styles.
What we’d do: Our pages are 20–50 KB compressed: the words and the markup, nothing bundled in.
-
•
Mobile PageSpeed score
Not measured this time: PageSpeed Insights did not answer within 60 seconds. The score below is provisional until it is.
-
•
Largest Contentful Paint (LCP)
Not measured — PageSpeed Insights did not answer.
-
•
Cumulative Layout Shift (CLS)
Not measured — PageSpeed Insights did not answer.
-
•
Interaction to Next Paint (INP)
Not measured — PageSpeed Insights did not answer.
-
•
Lighthouse accessibility score
Not measured — PageSpeed Insights did not answer.
-
•
Readable and tappable on a phone
Not measured — PageSpeed Insights did not answer.
-
•
HTTP/2 or HTTP/3
Could not tell which HTTP version the server speaks.
-
•
What would speed it up most
Not measured — PageSpeed Insights did not answer.
-
✓
Mobile viewport
The viewport meta tag is set for phones.
-
✓
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 787 ms from our server.
-
✓
Compression
Responses are compressed (gzip).
Trust / E-E-A-T / reputation 3 of 10 points
-
!
Trust signals
Only <n> years — a visitor comparing three sites wants license, insurance, guarantee and years stated plainly.
What we’d do: License number, insurance, warranty and founding year on every page, and in the schema.
-
!
Reviews on the page
The home page mentions “Testimonials” but shows no rating, review count or live reviews.
What we’d do: The live Google rating and count, and the newest reviews, on the home page.
-
!
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.
-
•
A named person
No named person on the home page. Not expected here — the About or team page is where a Person node belongs, with the name Google can tie to reviews and articles.
-
✓
No stock or AI-marked pictures
None of the 15 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.
-
✓
Article schema on the post
Article schema with an author on the post.
-
✓
Not a stock template
WordPress, with a theme of its own (titan); nothing of a stock template shows — no theme credit, demo pictures or sample text.
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.
-
✓
Tappable phone number
3 tel: links — the number dials from a phone.
-
✓
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 /, guarded by a honeypot.
-
✓
Analytics installed
Measured by Google Analytics, Meta pixel.
Read with the home page: post page Allsummerlandscapingtn.com/landscaping-mistakes/
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 allsummerlandscapingtn.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.