sanctuarylandservices.com scored 41/100 on the website scan.
Needs work
sanctuarylandservices.com · Scanned 2026-10-24
52 passed24 warnings18 failed
- Technical SEO & indexability7/10 of 10 points
- On-page SEO & content9/25 of 25 points
- AI search / AEO / GEO readiness14/35 of 35 points
- Local SEO & entity signals4/5 of 5 points
- Speed, scripts & mobile4/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
-
!
FAQPage schema +4 points
The page asks and answers 6 questions but carries no FAQPage schema, so the engines have to find them on their own.
What we’d do: The FAQ's questions and answers go into FAQPage schema, built from the same text so the two always match.
-
!
llms.txt +4 points
llms.txt is published (1 KB) but links only 2 pages of the site. The format is a heading with the name, a summary, then the pages worth reading, each linked, so an engine knows where to look.
What we’d do: Every site ships an llms.txt written from its facts — who, what, where, the proof — with a link to every service, area and post page, rewritten when the pages change.
-
!
FAQs on the inner pages +4 points
The service page answers questions without FAQPage schema.
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 +4 points
The service page (/land-grading-clearing-development-services-in-arrington-tn/) gives no number — no price, timeline, size or count — and names only Arrington 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.
-
✗
Page title +2 points
“Home - Sanctuary Land Services Excavation Clearing Demolition Nashville TN” is 74 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.
Every check, by category (103 checks)
Technical SEO & indexability 7 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.
-
•
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
13 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://sanctuarylandservices.com/.
-
✓
Mixed content
Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.
-
✓
Sitemap
Sitemap at https://sanctuarylandservices.com/sitemap_index.xml — an index of 1 sitemap.
-
✓
HTTP redirects to HTTPS
http:// redirects (301) to https://sanctuarylandservices.com/.
-
✓
Internal links resolve
All 13 internal links read (12 on the home page, 1 in llms.txt) answer.
-
✓
Language declared
<html lang="en-US">.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
robots.txt
robots.txt is served (22 groups, 1 sitemap line).
-
✓
Sitemap named in robots.txt
robots.txt names the sitemap: https://sanctuarylandservices.com/sitemap_index.xml.
-
✓
www and apex agree
www.sanctuarylandservices.com redirects (301) to sanctuarylandservices.com.
-
✓
Sitemap lists the live URLs
The sitemap's 21 URLs are all on https://sanctuarylandservices.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
21 pages with lastmod dates, from 2026-10-16 to 2026-10-17.
On-page SEO & content 9 of 25 points
-
✗
Page title
“Home - Sanctuary Land Services Excavation Clearing Demolition Nashville TN” is 74 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 130 characters.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
About and privacy pages
Neither an About page nor a privacy policy is linked from the home page: nothing tells a visitor, or Google's quality raters, who runs the business or what happens to what they send.
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.
-
✗
Service pages link each other
The service page read links none of the other 19 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.
-
!
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.
-
!
Pages that repeat each other
19 of the 50 sentences on the home page also appear on the service page (38%).
What we’d do: Every page is written once, for its own subject.
-
!
Canonical and share card on every page
The service page (/land-grading-clearing-development-services-in-arrington-tn/) has no share image.
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.
-
!
Pictures named and described for what they show
Of the 6 pictures on the pages read, 5 with a camera's, a template's or an upload's name (1.png, 2.png, 3.png, …). Google's image guidelines ask for file names and alt text that say what the picture shows.
What we’d do: Every picture is named for what it shows, in the business's own words (franklin-standing-seam-metal-roof.webp, never IMG_4411.jpg), and its alt text says what is in it — the job, the place, the material — rather than a keyword.
-
!
No stock or AI-marked pictures
1 picture marked as AI-made on the pages read: land-clearing-nashville.png (Google's AI mark inside the file). 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 Divi theme and the Divi builder: Divi 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.
-
!
A menu a thumb can use
20 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.
-
•
Share image loads
Skipped — no og:image to fetch.
-
•
Pages read
Read with the home page: service page https://sanctuarylandservices.com/land-grading-clearing-development-services-in-arrington-tn/.
-
•
Article schema on the post
No post found in the sitemap to check.
-
✓
Meta description
140 characters — fills the space Google shows without being cut.
-
✓
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.
-
✓
Single H1
One H1: “Sanctuary Land Services”.
-
✓
Image alt text
All 8 images have an alt attribute.
-
✓
Readable content in the HTML
1,120 words of readable text in the HTML.
-
✓
Descriptions across the site
Each page read has its own description of 120–160 characters.
-
✓
A page for each service
20 service pages in the sitemap (/land-grading-clearing-development-services-in-arrington-tn/, /land-grading-clearing-development-services-in-bellevue-tn/, /land-grading-clearing-development-services-in-brentwood-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.
-
✓
Titles lead with the subject
The inner pages' titles lead with their subject, not the business name.
AI search / AEO / GEO readiness 14 of 35 points
-
✗
Specifics an engine can cite
The service page (/land-grading-clearing-development-services-in-arrington-tn/) gives no number — no price, timeline, size or count — and names only Arrington 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.
-
✗
The first paragraph answers
The home page's first paragraph runs 79 words; the service page's first paragraph runs 77 words. 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.
-
!
FAQPage schema
The page asks and answers 6 questions but carries no FAQPage schema, so the engines have to find them on their own.
What we’d do: The FAQ's questions and answers go into FAQPage schema, built from the same text so the two always match.
-
!
llms.txt
llms.txt is published (1 KB) but links only 2 pages of the site. The format is a heading with the name, a summary, then the pages worth reading, each linked, so an engine knows where to look.
What we’d do: Every site ships an llms.txt written from its facts — who, what, where, the proof — with a link to every service, area and post page, rewritten when the pages change.
-
!
FAQs on the inner pages
The service page answers questions without FAQPage schema.
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.
-
!
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.
-
✓
Questions answered on the page
12 questions asked and answered on the pages read (6 on the home page, 6 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,120 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
12 schema types: WebPage, ReadAction, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, ….
-
✓
Freshness dates in schema
Newest date in the schema: 2026-10-16.
-
✓
Extractable structure
Structure an engine can lift: 4 H2s, 0 H3s, 25 list items.
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.
-
✗
Reviews on the page
No reviews, rating or testimonials on the home page, and no link to a profile that has them — the proof visitors look for first.
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.
-
✗
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, telephone, logo or image, areaServed but not address, openingHours.
What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.
-
•
A named person
No named person in the schema. Not required: a home-service company is known by its brand, and the business node carries what the engines tie the reviews and the pages to. A Person belongs on the About page only when the owner wants to be named.
-
✓
Business entity schema
LocalBusiness / HomeAndConstructionBusiness schema names the business.
-
✓
Service area stated by town
The service area is stated by town: Antioch, Arrington, Bellevue and Brentwood and 16 more, in the schema too.
-
✓
Address and phone on the page
The phone ((615) 209-7643) and where the business is (Nashville, TN) are on the page as text, and the phone matches the schema's.
-
✓
Site name for Google
WebSite schema names the site “Sanctuary Land Services Excavation Clearing Demolition Nashv” — the name Google shows above each result.
-
✓
The trade's own schema type
HomeAndConstructionBusiness: schema.org's own type for what the business does.
Speed, scripts & mobile 4 of 20 points
-
✗
Nothing blocks the first paint
6 files load before anything is drawn — styles and scripts in the head — and PageSpeed puts 3.2 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.
-
✗
Pinch-to-zoom allowed
The viewport tag blocks pinch-to-zoom (user-scalable=no or maximum-scale=1). People with low vision cannot enlarge the page, and Lighthouse's accessibility audit fails it.
What we’d do: Pinch-to-zoom stays on; the layout is built so nothing needs it.
-
✗
Time to first byte
First byte took 2.2 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 14.7 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
5.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.
-
✗
Static files cached
20 files served with a short or missing cache lifetime, 19 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 53/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.
-
!
Lighthouse accessibility score
Lighthouse accessibility 85/100 — the report names what to fix.
What we’d do: Contrast, labels, landmarks and focus order are checked on every page before it ships.
-
!
Scripts and third parties
5 scripts, 468 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
8 images: 8 with dimensions, 0 in a modern format or through an image service, 1 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.
-
!
Cumulative Layout Shift (CLS)
Cumulative Layout Shift 0.17 (lab). Google's thresholds: 0.1 good, 0.25 poor.
What we’d do: Every image and embed has its size in the HTML and fonts load with size-adjust, so nothing moves as the page loads.
-
!
Fonts
8 font files (151 KB) from Google Fonts and sanctuarylandservices.com. 1 face 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.
-
!
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.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Use efficient cache lifetimes (about 11.8 s); Improve image delivery (about 9.9 s); Render-blocking requests (about 2.2 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.
-
✓
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.
-
✓
No hero slider or autoplay video
One hero: no slider and no autoplaying video in the first screen.
-
✓
The hero image loads first
The largest thing on the first screen is text or a styled block (<p class="mb-4 break-words text-base font-normal leading-7 last:mb-0 [), which paints as soon as the HTML arrives.
-
✓
No fixed-width overflow
No inline widths of 400px or more that would push past a phone screen.
-
✓
HTML weight
About 28 KB compressed (171 KB of HTML).
-
✓
One chat widget at most
No chat widget scripts on the page.
Conversion & lead generation 3 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.
-
!
A lead form that fits a phone
The lead form asks 5 fields; the phone field does not bring up the number keypad (type=tel). 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 / (no spam guard shows in the page; a filter on the server can't be seen from outside).
-
✓
Tappable phone number
1 tel: link — the number dials from a phone.
-
✓
No CAPTCHA puzzle
No CAPTCHA puzzle on the page.
Read with the home page: service page sanctuarylandservices.com/land-grading-clearing-development-services-in-arrington-tn/
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 sanctuarylandservices.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.