kingdom-doors.com scored 42/100 on the website scan.
Needs work
kingdom-doors.com · Scanned 2026-10-24
60 passed20 warnings15 failed
- Technical SEO & indexability6/10 of 10 points
- On-page SEO & content15/25 of 25 points
- AI search / AEO / GEO readiness6/35 of 35 points
- Local SEO & entity signals5/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 +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.
-
✗
FAQs on the inner pages +4 points
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.
-
!
llms.txt +3 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.
-
✗
Titles across the site +3 points
the post page's title is 80 characters.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
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.
-
!
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.
-
!
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.
-
!
Lighthouse best practices
Lighthouse best practices 88/100 — the report names what to fix.
What we’d do: No console errors, no deprecated APIs, images at their real aspect ratio, HTTPS everywhere.
-
•
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.
-
✓
Canonical URL
Canonical is https://kingdom-doors.com/.
-
✓
Mixed content
Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.
-
✓
Sitemap
Sitemap at https://kingdom-doors.com/sitemap_index.xml — an index of 6 sitemaps.
-
✓
HTTP redirects to HTTPS
http:// redirects (301) to https://kingdom-doors.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://kingdom-doors.com/sitemap_index.xml.
-
✓
www and apex agree
www.kingdom-doors.com redirects (301) to kingdom-doors.com.
-
✓
Sitemap lists the live URLs
The sitemap's 4 URLs are all on https://kingdom-doors.com, and the pages read from it answer directly and are open to indexing.
-
✓
Lighthouse SEO score
Lighthouse SEO 100/100.
-
✓
Sitemap dates
4 pages with lastmod dates, from 2024-11-24 to 2024-11-24.
On-page SEO & content 15 of 25 points
-
✗
Titles across the site
the post page's title is 80 characters.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
No stock phrases
The home page: “look no further”, “dedicated to providing”. 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.
-
✗
Descriptions across the site
the post page has no description.
What we’d do: Every page gets its own 120–160 character description, checked in the build.
-
✗
A menu a thumb can use
30 links in the header and menu. 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.
-
!
Pictures named and described for what they show
Of the 7 pictures on the pages read, 6 with a camera's, a template's or an upload's name (1000013340.jpg, IMG_1058.jpg, IMG_0300.jpg, …). 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.
-
•
Service pages link each other
Skipped — no service page read.
-
•
Pages read
Read with the home page: post page https://kingdom-doors.com/disclosing-the-secrets-of-success-in-luxury-hospitality-2-3/.
-
✓
Page title
“Home - Kingdom Doors Nashville Custom Garage Doors” — 50 characters, inside the 30–60 Google shows in full.
-
✓
Meta description
138 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.
-
✓
No stock or AI-marked pictures
None of the 8 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
WordPress, with a theme of its own (hoteller) and Elementor; nothing of a stock template shows — no theme credit, demo pictures or sample text.
-
✓
Single H1
One H1: “Kingdom Doors”.
-
✓
Image alt text
All 8 images have an alt attribute.
-
✓
Readable content in the HTML
1,098 words of readable text in the HTML.
-
✓
Share image loads
The share image loads (image/jpeg, 54 KB).
-
✓
Pages that repeat each other
The pages read share no sentences beyond the header, footer and calls to action.
-
✓
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.
-
✓
A page for each service
4 service pages in the sitemap (/disclosing-the-secrets-of-success-in-luxury-hospitality-2-3/, /disclosing-the-secrets-of-success-in-luxury-hospitality-2-2/, /disclosing-the-secrets-of-success-in-luxury-hospitality-2-2-2/, …).
-
✓
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-policy-2/).
-
✓
Titles lead with the subject
The inner pages' titles lead with their subject, not the business name.
-
✓
Article schema on the post
Article schema with an author on the post.
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.
-
✗
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 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.
-
✗
The first paragraph answers
The home page's headline is followed by buttons and pictures, not a sentence. 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.
-
!
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.
-
!
Specifics an engine can cite
The post page (/disclosing-the-secrets-of-success-in-luxury-hospitality-2-3/): 175 words, 3 numbers, 6 names (FaceTime, Zoom, Repair, Covered, …) — 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 post page (/disclosing-the-secrets-of-success-in-luxury-hospitality-2-3/) 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.
-
!
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.
-
✓
Readable without JavaScript
The page's 1,098 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
14 schema types: WebPage, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, ….
-
✓
Freshness dates in schema
Newest date in the schema: 2026-10-08.
-
✓
Extractable structure
Structure an engine can lift: 6 H2s, 3 H3s, 168 list items.
Local SEO & entity signals 5 of 5 points
-
✗
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.
-
!
Trust signals
Only 2 years. 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
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.
-
•
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: Nashville, Antioch, Arrington and Bellevue and 17 more, in the schema too.
-
✓
Business schema completeness
The business node carries name, url, telephone, address, logo or image, areaServed.
-
✓
Linked to its profiles
The business node's sameAs names Facebook and Instagram — the links the engines use to know this site and those profiles are one business.
-
✓
Address and phone on the page
The phone ((615) 810-6415) and where the business is (Franklin, TN) are on the page as text, and the phone matches the schema's.
-
✓
Site name for Google
WebSite schema names the site “Kingdom Doors Nashville Custom Garage Doors” — 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 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 4.3 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.
-
✗
Time to first byte
First byte took 2.7 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.
-
✗
Largest Contentful Paint (LCP)
Largest Contentful Paint 10.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.7 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
122 files served with a short or missing cache lifetime, 122 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 65/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
55 scripts, 727 KB of JavaScript, from 2 third parties (www.google.com and reCAPTCHA). 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.
-
!
Fonts
5 font files (87 KB) from kingdom-doors.com.
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
2 pieces of text are too faint to read against their background (“SUBMIT REQUEST” 3.5:1, “Home” 2.01: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.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Use efficient cache lifetimes (about 4.3 s); Render-blocking requests (about 4.3 s); Reduce unused JavaScript (about 1.6 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.
-
✓
Image hygiene
8 images: 5 with dimensions, 3 in a modern format or through an image service, 1 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.
-
✓
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 (220 KB of HTML).
-
✓
Compression
Responses are compressed (gzip).
-
✓
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.
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.
-
!
No CAPTCHA puzzle
Invisible reCAPTCHA on the page: no puzzle most of the time, but several hundred KB of script on every page load and a share of real visitors challenged.
What we’d do: Turnstile, or a honeypot and a time trap, on the form: nothing the visitor has to solve, under 20 KB, and the lead stored before it is emailed.
-
•
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, guarded by reCAPTCHA.
-
✓
Tappable phone number
3 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.
Read with the home page: post page kingdom-doors.com/disclosing-the-secrets-of-success-in-luxury-hospitality-2-3/
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 kingdom-doors.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.