www.kingdompoolstn.com scored 38/100 on the website scan.
Major issues
kingdompoolstn.com · Scanned 2026-10-26
55 passed27 warnings11 failed
- Technical SEO & indexability9/10 of 10 points
- On-page SEO & content8/25 of 25 points
- AI search / AEO / GEO readiness6/35 of 35 points
- Local SEO & entity signals2/5 of 5 points
- Speed, scripts & mobile9/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.
-
✗
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.
-
!
llms.txt +3 points
llms.txt is published (3 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.
-
!
Questions answered on the page +3 points
Only 1 question asked and answered on the pages read (1 on the home page). Answer engines quote pages that ask the customer's 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.
-
✗
Schema on the inner pages +3 points
The service page (/custom-pools) has no structured data. Past the home page the engines get no structured statement of what a page is or whose it is.
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 9 of 10 points
-
✗
Security headers
Missing 3 of the four baseline security headers: Content-Security-Policy, 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.
-
•
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
3 schema types on the 1 page 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://www.kingdompoolstn.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.
-
✓
Sitemap
Sitemap at https://www.kingdompoolstn.com/sitemap.xml — an index of 1 sitemap.
-
✓
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://www.kingdompoolstn.com/.
-
✓
Internal links resolve
All 3 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).
-
✓
Sitemap named in robots.txt
robots.txt names the sitemap: https://www.kingdompoolstn.com/sitemap.xml.
-
✓
www and apex agree
kingdompoolstn.com redirects (301) to www.kingdompoolstn.com.
-
✓
Sitemap lists the live URLs
The sitemap's 4 URLs are all on https://www.kingdompoolstn.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
4 pages with lastmod dates, from 2025-10-30 to 2025-10-30.
On-page SEO & content 8 of 25 points
-
✗
Meta description
Only 70 characters. Google will almost certainly replace it with text of its own choosing.
What we’d do: We write descriptions of 120–160 characters, the point first.
-
✗
Titles across the site
the service page's title is 28 characters.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
Descriptions across the site
the service page has no description.
What we’d do: Every page gets its own 120–160 character description, checked in the build.
-
✗
No stock phrases
The home page: “whether you’re looking”, “elevate your”, “we pride ourselves” and 3 brochure phrases (“peace of mind”, “transform your”, “attention to detail”); the service page: “tailored to your” and 3 brochure phrases (“comprehensive”, “transform your”, “you can trust”). 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
“Kingdom Pools | Custom Pools Tennessee | College Grove, TN, USA” is 63 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.
-
!
Single H1
5 H1 headings. One is the convention search engines and screen readers expect.
What we’d do: One H1 per page; the rest become H2s.
-
!
Canonical and share card on every page
The service page (/custom-pools) has 2 H1s.
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 7 pictures on the pages read, 7 with a camera's, a template's or an upload's name (image.png, 00be85_fa8678d1be8f4b1dad85b6fa6570ea0ef000.jpg, 9d89dc_5a584d4d2f93441695518b860d86e394~mv2.png, …) and 3 with alt text that describes nothing (“image.png”, the file's own name; “a frame cabana 2.png”, the file's own name). 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.
-
!
A page for each service
Only 2 service pages in the sitemap (/custom-pools, /project-gallery). 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.
-
!
Not a stock template
Built with Wix, from templates thousands of businesses share. Nothing is left over from the template, but the layout says “Wix” before it says anything about the business.
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.
-
•
Service pages link each other
Skipped — fewer than three service pages to link between.
-
•
Pages read
Read with the home page: service page https://www.kingdompoolstn.com/custom-pools.
-
•
Article schema on the post
No post found in the sitemap to check.
-
✓
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.
-
✓
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 7 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.
-
✓
Image alt text
All 5 images have an alt attribute.
-
✓
Readable content in the HTML
579 words of readable text in the HTML.
-
✓
Share image loads
The share image loads (image/png, 360 KB).
-
✓
Pages that repeat each other
The pages read share few sentences: at most 1 of 19 (5%) between the service and home pages.
-
✓
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.
-
✓
A menu a thumb can use
3 links in the header and menu, and the service page read is one tap from the home page.
AI search / AEO / GEO readiness 6 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.
-
✗
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.
-
✗
Schema on the inner pages
The service page (/custom-pools) has no structured data. Past the home page the engines get no structured statement of what a page is or whose it is.
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.
-
!
llms.txt
llms.txt is published (3 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.
-
!
Questions answered on the page
Only 1 question asked and answered on the pages read (1 on the home page). Answer engines quote pages that ask the customer's 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 service page (/custom-pools): 425 words, 1 number, 0 names — 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 home page's headline is followed by buttons and pictures, not a sentence.
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.
-
•
FAQ questions visible on the page
Skipped — no FAQ schema to compare.
-
•
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.
-
•
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 579 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
3 schema types: LocalBusiness, PostalAddress, WebSite.
-
✓
Extractable structure
Structure an engine can lift: 5 H2s, 3 H3s, 4 list items, 1 question heading.
-
✓
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 2 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.
-
!
Service area stated by town
One town is named (Williamson County). A service business is found town by town; three or more, on the page and in areaServed, is the floor.
What we’d do: The towns the business works in, named — a service-area line in the footer of every page and areaServed in the schema with each town — so a search from any of them finds it.
-
!
Business schema completeness
The business node has name, url, telephone, address, logo or image but not areaServed, openingHours.
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 schema gives (123) 456-7890, but the page shows (615) 979-7369. The engines trust a business whose phone is the same everywhere.
What we’d do: One number — the one on the Google Business Profile — in the header, the footer and 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.
-
!
Trust signals
Only years of experience. Noted, not scored: a visitor comparing three sites reads whether the work is insured and guaranteed.
What we’d do: Insurance, a written guarantee and the trade's credentials, stated plainly where the visitor decides.
-
!
Reviews on the page
The home page mentions “Leave a 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.
-
!
Hours shown and in schema
The hours are on the page but not in the business schema, so the engines read them out of the prose.
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.
-
•
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 schema names the business.
-
✓
Site name for Google
WebSite schema names the site “Kingdom Pools” — the name Google shows above each result.
Speed, scripts & mobile 9 of 20 points
-
✗
Scripts and third parties
99 scripts, 1448 KB of JavaScript, from 4 third parties (Wix, browser.sentry-cdn.com, app.commentsplugin.com and static.cloudflareinsights.com). Wix 0.7 s held the phone's main thread while the page loaded. A phone downloads, parses and runs all of it before the page settles.
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.
-
✗
HTML weight
About 181 KB compressed (1038 KB of HTML) — every visit downloads this before anything is drawn.
What we’d do: Our pages are 20–50 KB compressed: the words and the markup, nothing bundled in.
-
!
Mobile PageSpeed score
Lighthouse mobile performance 52/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.
-
!
Image hygiene
5 images: 5 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.
-
!
Fonts
7 font files (104 KB) from Wix. 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.
-
!
The hero image loads first
The hero image is not preloaded or marked high priority, so the browser finds it late.
What we’d do: The hero picture is the first thing the HTML asks for: sized, in a modern format, preloaded with fetchpriority=high and never lazy-loaded, so the first screen paints in about a second.
-
!
Readable and tappable on a phone
One piece of text is too faint to read against its background (“SEND” 3.94:1); WCAG asks 4.5:1 for text that size.
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.
-
!
Largest Contentful Paint (LCP)
Largest Contentful Paint 5.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
2.4 MB downloaded to show the home page on a phone. On a cellular connection that is seconds of waiting, and data the visitor pays for.
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.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Minimize main-thread work (about 1.0 s); Reduce JavaScript execution time (about 0.7 s); Improve image delivery (about 0.1 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 95/100.
-
✓
Nothing blocks the first paint
Nothing blocks the first paint: the page is drawn as soon as the HTML arrives.
-
✓
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.
-
✓
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 337 ms from our server.
-
✓
Compression
Responses are compressed (br).
-
✓
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.
-
✓
Static files cached
8 files served with a short or missing cache lifetime, 0 of them the site's own.
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 4 fields, labeled, and fits a phone screen.
-
✓
No CAPTCHA puzzle
No CAPTCHA puzzle on the page.
Read with the home page: service page www.kingdompoolstn.com/custom-pools
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 www.kingdompoolstn.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.