www.tennesseecustomcabinets.com scored 41/100 on the website scan.
Needs work
tennesseecustomcabinets.com · Scanned 2026-10-30
50 passed10 warnings15 failed
- Technical SEO & indexability6/10 of 10 points
- On-page SEO & content10/25 of 25 points
- AI search / AEO / GEO readiness5/35 of 35 points
- Local SEO & entity signals0/5 of 5 points
- Speed, scripts & mobile18/20 of 20 points
- Conversion & lead generation2/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 +6 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.
-
✗
llms.txt +6 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.
-
✗
Questions answered on the page +6 points
No question is asked and answered on the 1 page 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.
-
✗
Meta description +4 points
197 characters — the last third is cut in results.
What we’d do: We write descriptions of 120–160 characters, the point first.
-
!
Page title +3 points
“Tennessee Custom Cabinets | Handcrafted Cabinetry in Middle Tennessee” is 69 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.
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.
-
✗
Sitemap
No sitemap found or at /sitemap.xml, /sitemap_index.xml or /wp-sitemap.xml. Crawlers have to discover every page by following links.
What we’d do: A sitemap generated from the site's pages on every build, named in robots.txt and submitted to Google and Bing on every deploy.
-
!
Canonical URL
No canonical link. With www, trailing-slash and tracking variants of the URL, Google has to guess which one to index.
What we’d do: Every page names itself as its own canonical URL.
-
!
robots.txt
No robots.txt. Crawlers assume everything is allowed, and nothing points them at the sitemap.
What we’d do: A robots.txt that names the sitemap and keeps only the private paths out.
-
•
HTTPS certificate
The certificate could not be read from this platform, but the page was fetched over HTTPS.
-
•
Structured data Google accepts
Skipped — no structured data on the pages read.
-
•
Internal links resolve
Too few of the site's links answered this scan to judge (1 tried).
-
•
Sitemap named in robots.txt
Skipped — no robots.txt.
-
•
Sitemap lists the live URLs
Skipped — no sitemap.
-
•
Sitemap dates
Skipped — no sitemap.
-
✓
Indexable by search engines
No noindex on the page or in the headers, and robots.txt lets Googlebot in.
-
✓
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.
-
✓
Missing pages return 404
A made-up URL returns 404, so Google never indexes ghost pages.
-
✓
HTTP redirects to HTTPS
http:// redirects (308) to https://www.tennesseecustomcabinets.com/.
-
✓
Language declared
<html lang="en">.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
www and apex agree
tennesseecustomcabinets.com redirects (308) to www.tennesseecustomcabinets.com.
-
✓
Lighthouse SEO score
Lighthouse SEO 100/100.
-
✓
Lighthouse best practices
Lighthouse best practices 100/100.
On-page SEO & content 10 of 25 points
-
✗
Meta description
197 characters — the last third is cut in results.
What we’d do: We write descriptions of 120–160 characters, the point first.
-
✗
A page for each service
No service pages linked from the home page (no sitemap to read): the site is one page, or its services share one. Each search is for one service, and a page that covers them all ranks for none.
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
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.
-
!
Page title
“Tennessee Custom Cabinets | Handcrafted Cabinetry in Middle Tennessee” is 69 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.
-
!
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.
-
•
Titles across the site
Skipped — no inner page read.
-
•
Share image loads
Skipped — no og:image to fetch.
-
•
Descriptions across the site
Skipped — no inner page read.
-
•
Pages that repeat each other
Skipped — no inner page read.
-
•
Canonical and share card on every page
Skipped — no inner page read.
-
•
Titles lead with the subject
Skipped — no inner page read.
-
•
Service pages link each other
Skipped — no service page read.
-
•
Pages read
No sitemap to pick inner pages from, so the home page stands for the site.
-
•
Article schema on the post
Skipped — no post found in the sitemap.
-
✓
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 1 page read.
-
✓
No placeholder or template text
No template or placeholder text on the 1 page 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: “Built by hand. Made for your Home.”.
-
✓
Image alt text
All 12 images have an alt attribute.
-
✓
Readable content in the HTML
422 words of readable text in the HTML.
-
✓
Pictures named and described for what they show
8 of the 8 pictures on the pages read are named and described for what they show.
-
✓
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.
-
✓
A menu a thumb can use
1 link in the header and menu.
AI search / AEO / GEO readiness 5 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.
-
✗
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.
-
✗
Questions answered on the page
No question is asked and answered on the 1 page 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.
-
✗
JSON-LD present and valid
No JSON-LD on the page. Google and the answer engines get no structured statement of what this is.
What we’d do: Every page carries Organization or LocalBusiness, WebSite, BreadcrumbList and the page's own type.
-
✗
The first paragraph answers
The home page's first paragraph does not say what its headline is about. 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.
-
•
FAQ questions visible on the page
Skipped — no FAQ schema to compare.
-
•
FAQs on the inner pages
Skipped — no inner page read.
-
•
Specifics an engine can cite
Skipped — no service page or post read to hold to the competitor test.
-
•
Schema on the inner pages
Skipped — no inner page read.
-
•
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 422 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.
-
✓
Extractable structure
Structure an engine can lift: 4 H2s, 4 H3s, 8 list items, 1 question heading.
-
✓
AI crawlers allowed
No robots.txt, so every AI crawler is allowed by default. GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot each get the home page from the edge, as a browser does.
Local SEO & entity signals 0 of 5 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.
-
✗
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.
-
!
Service area stated by town
The page says it serves an area (“service area 100% All-Wood Construction How It Works Simple ”) but names no town.
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.
-
!
Linked to its profiles
The page links Facebook and Instagram, 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.
-
!
Address and phone on the page
The phone is on the page, but not the town or the street address. Map search and the answer engines place a business by what its pages say.
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.
-
!
Site name for Google
Only og:site_name (“Tennessee Custom Cabinets”) names the site. Google asks for WebSite schema on the home page to choose the name it shows above each result.
What we’d do: WebSite schema on the home page with the business's name, and alternateName for any other name people use, as on the Business Profile.
-
!
Trust signals
Only years of experience, 40+ 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.
-
•
Business schema completeness
Skipped — no business node to read.
-
•
The trade's own schema type
Skipped — no business node to read.
-
•
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.
Speed, scripts & mobile 18 of 20 points
-
✗
Readable and tappable on a phone
6 pieces of text are too faint to read against their background (“THE CRAFT” 2.73:1, “Amish craftsmanship.” 2.73:1, “BEGIN YOUR CUSTOM PROJECT” 2.73:1); WCAG asks 4.5:1 for text that size. 2 buttons or links are too small or too close to others to tap reliably (“Go to slide 2”, “Go to slide 3”). Google's test read the page as a phone shows it.
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.
-
•
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.
-
✓
Mobile PageSpeed score
Lighthouse mobile performance 95/100. Google's own bands: 90 and up is good, 50–89 needs improvement.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 90/100.
-
✓
Scripts and third parties
10 scripts, 202 KB of JavaScript, from no third party.
-
✓
Nothing blocks the first paint
1 file loads before anything is drawn — styles and scripts in the head — and PageSpeed puts 0.2 s of the first paint on waiting for it.
-
✓
Image hygiene
12 images: 12 with dimensions, 12 in a modern format or through an image service, 10 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
0 font files.
-
✓
The hero image loads first
The largest thing on the first screen is text or a styled block (<h1 style="font-family: var(--font-serif); font-weight: 300;">), which paints as soon as the HTML arrives.
-
✓
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 359 ms from our server.
-
✓
HTML weight
About 9 KB compressed (67 KB of HTML).
-
✓
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.
-
✓
Largest Contentful Paint (LCP)
Largest Contentful Paint 2.2 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).
-
✓
Page weight
324 KB downloaded to show the home page on a phone.
-
✓
Static files cached
Every static file is served with a long cache lifetime.
-
✓
What would speed it up most
Nothing large left to fix. PageSpeed's remaining suggestions: Reduce unused JavaScript (about 0.2 s); Render-blocking requests (about 0.1 s); Legacy JavaScript (about 0.1 s).
Conversion & lead generation 2 of 5 points
-
✗
Contact form
No form and no contact link on the home page.
What we’d do: A short quote form on every page, stored first and emailed second.
-
!
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.
-
•
Lead form wiring
No form in the home page's HTML to read — a form a script draws in the browser can't be read from outside.
-
•
A lead form that fits a phone
No form on the home page to read; the contact form check says whether one is linked.
-
•
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.
-
✓
Call to action in the first screen
A phone link, a form or a quote button appears in the top of the page.
-
✓
Tappable phone number
2 tel: links — the number dials from a phone.
-
✓
No CAPTCHA puzzle
No CAPTCHA puzzle on the page.
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.tennesseecustomcabinets.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.