buildwithinspiration.com scored 71/100 on the website scan.
Decent
buildwithinspiration.com · Scanned 2026-10-01
60 passed15 warnings4 failed
- Technical SEO & indexability12/15 of 15 points
- On-page SEO & content16/20 of 20 points
- AI search / AEO / GEO readiness22/30 of 30 points
- Local SEO & entity signals8/10 of 10 points
- Performance & mobile5/10 of 10 points
- Trust / E-E-A-T / reputation4/10 of 10 points
- Conversion & lead generation4/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
-
!
Questions answered on the page +4 points
Only 2 questions asked and answered on the pages read (1 on the home page, 1 on the post 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.
-
✗
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.
-
✗
No stock phrases +2 points
The home page: “tailored to your” and 4 brochure phrases (“highest quality”, “you can trust”, “we strive”, …); the post page: “when it comes to”, “ultimate guide”. 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.
-
!
Business schema completeness +2 points
The business node has name, url, telephone, address, areaServed but not logo or image, openingHours.
What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.
-
!
Trust signals +2 points
Only guarantee — 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.
Every check, by category (85 checks)
Technical SEO & indexability 12 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.
-
!
Structured data Google accepts
An article's author or publisher written as a bare {"@id"} with no type beside it (the home page and 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.
-
!
Lighthouse best practices
Lighthouse best practices 73/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://buildwithinspiration.com/.
-
✓
Mixed content
Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.
-
✓
Sitemap
Sitemap at https://buildwithinspiration.com/sitemap_index.xml — an index of 5 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://buildwithinspiration.com/.
-
✓
Internal links resolve
All 34 internal links read (24 on the home page, 10 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 (1 group, 1 sitemap line).
-
✓
Sitemap named in robots.txt
robots.txt names the sitemap: https://buildwithinspiration.com/sitemap_index.xml.
-
✓
Sitemap dates
60 pages with lastmod dates, from 2026-06-03 to 2026-09-25.
-
✓
www and apex agree
www.buildwithinspiration.com redirects (301) to buildwithinspiration.com.
-
✓
Sitemap lists the live URLs
The sitemap's 60 URLs are all on https://buildwithinspiration.com, and the pages read from it answer directly and are open to indexing.
-
✓
Lighthouse SEO score
Lighthouse SEO 100/100.
On-page SEO & content 16 of 20 points
-
✗
No stock phrases
The home page: “tailored to your” and 4 brochure phrases (“highest quality”, “you can trust”, “we strive”, …); the post page: “when it comes to”, “ultimate guide”. 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.
-
!
Image alt text
1 of 26 images have no alt attribute.
What we’d do: Every image gets an alt that says what is in it; decorative ones get alt="".
-
!
Pictures named and described for what they show
Of the 7 pictures on the pages read, 1 with a camera's, a template's or an upload's name (placeholder.png) and 1 with alt text that describes nothing (“Luxury bathroom with terracotta tile walls, wooden…”, a string of keywords). 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.
-
•
Pages read
Read with the home page: post page https://buildwithinspiration.com/blog/the-timeless-appeal-of-stone-incorporating-natural-elements-into-modern-homes/.
-
✓
Page title
“Custom Home Builder - Spring Hill TN - Inspiration Homes” — 56 characters, inside the 30–60 Google shows in full.
-
✓
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.
-
✓
Meta description
141 characters — fills the space Google shows without being cut.
-
✓
Single H1
One H1: “Home Builder & Remodeler Company in Williamson County, TN”.
-
✓
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.
-
✓
Readable content in the HTML
1,292 words of readable text in the HTML.
-
✓
Titles across the site
Each page read has its own title of 30–60 characters.
-
✓
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.
-
✓
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.
-
✓
Share image loads
The share image loads (image/webp, 148 KB).
-
✓
Descriptions across the site
Each page read has its own description of 120–160 characters.
AI search / AEO / GEO readiness 22 of 30 points
-
✗
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.
-
!
Questions answered on the page
Only 2 questions asked and answered on the pages read (1 on the home page, 1 on the post 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.
-
•
Speakable specification
No speakable specification. Google's speakable is a news-only beta, so this is noted, not scored.
-
✓
FAQPage schema
FAQPage schema is present.
-
✓
Specifics an engine can cite
The post page (/blog/the-timeless-appeal-of-stone-incorporating-natural-elements-into-modern-homes/): 709 words, 6 numbers, 11 names (Knudsen, Founder, CEO, Previous, …) — specifics only this business could publish, the kind an answer engine quotes.
-
✓
FAQ questions visible on the page
All 5 questions in the FAQ schema are on the page, with the answers it shows.
-
✓
llms.txt
llms.txt is published (80 KB), headed with the name and linking 170 pages of the site — a plain statement of the business for the AI engines to read.
-
✓
Schema on the inner pages
The inner page read carries its own schema: the business and a BreadcrumbList.
-
✓
Readable without JavaScript
The page's 1,292 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
18 schema types: Organization, ImageObject, WebSite, SearchAction, WebPage, Person, Article, HomeAndConstructionBusiness, ….
-
✓
Freshness dates in schema
Newest date in the schema: 2026-06-07.
-
✓
Extractable structure
Structure an engine can lift: 6 H2s, 4 H3s, 53 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 8 of 10 points
-
!
Business schema completeness
The business node has name, url, telephone, address, areaServed but not logo or image, openingHours.
What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.
-
✓
Business entity schema
HomeAndConstructionBusiness / LocalBusiness schema names the business.
-
✓
Linked to its profiles
The business node's sameAs names Facebook, Instagram, YouTube and Yelp — the links the engines use to know this site and those profiles are one business.
-
✓
Address and phone on the page
The phone ((615) 241-0174) and where the business is (3370 Mahlon Moore Rd.) are on the page as text, and the phone matches the schema's.
-
✓
Service area stated
The page says where the business works.
-
✓
Site name for Google
WebSite schema names the site “Inspiration Homes”, also known as “Inspiration Homes, LLC” — the name Google shows above each result.
Performance & mobile 5 of 10 points
-
✗
Readable and tappable on a phone
7 pieces of text are too faint to read against their background (“From kitchens and baths to full renovations, additions, and outdoor spaces.” 3.29:1, “Browse Services” 3.29:1, “Explore a wide range of thoughtfully designed custom homes to suit every lifest…” 3.29:1); WCAG asks 4.5:1 for text that size. 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.
-
!
Mobile PageSpeed score
Lighthouse mobile performance 56/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.
-
!
Largest Contentful Paint (LCP)
Largest Contentful Paint 5.8 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.
-
!
HTML weight
About 98 KB compressed (737 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.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Minimize main-thread work (about 0.5 s); Reduce JavaScript execution time (about 0.5 s); Legacy JavaScript (about 0.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.
-
✓
Cumulative Layout Shift (CLS)
Cumulative Layout Shift 0.00 (lab). Google's thresholds: 0.1 good, 0.25 poor.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 97/100.
-
✓
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 172 ms from our server.
-
✓
Compression
Compressed, as Google's PageSpeed test read the page from outside; this scan runs inside Cloudflare's network, where Cloudflare's compression never shows.
-
✓
Image hygiene
12 images: 11 with dimensions, 1 in a modern format or through an image service, 1 lazy-loaded.
-
✓
HTTP/2 or HTTP/3
HTTP/2 — Google's PageSpeed test loaded the page over it (this scan cannot read the protocol itself).
Trust / E-E-A-T / reputation 4 of 10 points
-
!
Trust signals
Only guarantee — 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.
-
!
Not a stock template
Built with WordPress, the Hello Elementor theme and Elementor: Hello Elementor 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.
-
✓
No stock or AI-marked pictures
None of the 11 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
BlogPosting schema with an author on the post.
-
✓
About and privacy pages
The home page links an About page (/about-us/) and a privacy policy (/privacy-policy/).
-
✓
A named person
A named person in the schema: Dev Team.
Conversion & lead generation 4 of 5 points
-
!
Contact form
No form on the home page; a contact or quote page is linked. Every extra tap loses a share of visitors.
What we’d do: Our home pages carry the quote form itself — name, phone, what they need — stored before it is emailed, so nothing is lost.
-
•
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.
-
•
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
5 tel: links — the number dials from a phone.
-
✓
Call to action in the first screen
A phone link, a form or a quote button appears in the top of the page.
-
✓
Analytics installed
Measured by Google Tag Manager.
Read with the home page: post page buildwithinspiration.com/blog/the-timeless-appeal-of-stone-incorporating-natural-elements-into-modern-homes/
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 buildwithinspiration.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.