Search the site · Ask Zorva

Results appear as you type. Press Enter and Zorva answers from this site’s own pages.

Public scan result · scored by the Zorva Labs website scan

sbcnashville.com scored 95/100 on the website scan.

Strong

sbcnashville.com · Scanned 2026-11-08

Unchanged from 2026-10-10

95 passed3 warnings1 failed

  • Technical SEO & indexability10 of 10 points
  • On-page SEO & content23 of 25 points
  • AI search / AEO / GEO readiness35 of 35 points
  • Local SEO & entity signals5 of 5 points
  • Speed, scripts & mobile18 of 20 points
  • Conversion & lead generation4 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

  • !

    Scripts and third parties +2 points

    5 scripts, 526 KB of JavaScript, from 2 third parties (Google Tag Manager and Google Ads). Google Tag Manager 0.6 s held the phone's main thread while the page loaded. 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.

  • ✗

    Service pages link each other +1 point

    The service page read links none of the other 46 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.

  • !

    A menu a thumb can use +1 point

    17 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.

  • !

    A lead form that fits a phone +1 point

    The lead form asks 9 fields. 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.

Every check, by category (103 checks)

Technical SEO & indexability 10 of 10 points

  • •

    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

    26 schema types on the 3 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://sbcnashville.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.

  • ✓

    Security headers

    All four baseline security headers are set.

  • ✓

    Sitemap

    Sitemap at https://sbcnashville.com/sitemap.xml — 56 URLs.

  • ✓

    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://sbcnashville.com/.

  • ✓

    Internal links resolve

    All 40 internal links read (30 on the home page, 10 in llms.txt) answer.

  • ✓

    Language declared

    <html lang="en">.

  • ✓

    Redirect chain

    The URL answers directly, with no redirect.

  • ✓

    robots.txt

    robots.txt is served (11 groups, 1 sitemap line, the private paths repeated in each crawler's own group).

  • ✓

    Sitemap named in robots.txt

    robots.txt names the sitemap: https://sbcnashville.com/sitemap.xml.

  • ✓

    www and apex agree

    www.sbcnashville.com redirects (301) to sbcnashville.com.

  • ✓

    Sitemap lists the live URLs

    The sitemap's 56 URLs are all on https://sbcnashville.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

    56 pages with lastmod dates, from 2026-10-09 to 2026-11-05.

On-page SEO & content 23 of 25 points

  • ✗

    Service pages link each other

    The service page read links none of the other 46 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.

  • !

    A menu a thumb can use

    17 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.

  • •

    Pages read

    Read with the home page: service page https://sbcnashville.com/kitchen-remodeling/; post page https://sbcnashville.com/blueprints/kitchen-remodel-cost-nashville/.

  • ✓

    Page title

    “Nashville General Contractor, Custom Homes | Southern Belle” — 59 characters, inside the 30–60 Google shows in full.

  • ✓

    Meta description

    160 characters — fills the space Google shows without being cut.

  • ✓

    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.

  • ✓

    Titles across the site

    Each page read has its own title of 30–60 characters.

  • ✓

    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 3 pages read.

  • ✓

    No placeholder or template text

    No template or placeholder text on the 3 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 35 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: “Custom homes and remodels, built like they’re ours.”.

  • ✓

    Image alt text

    All 28 images have an alt attribute.

  • ✓

    Readable content in the HTML

    2,314 words of readable text in the HTML.

  • ✓

    Share image loads

    The share image loads (image/jpeg, 128 KB).

  • ✓

    Descriptions across the site

    Each page read has its own description of 120–160 characters.

  • ✓

    Pages that repeat each other

    The pages read share few sentences: at most 1 of 34 (3%) between the service and home pages.

  • ✓

    Canonical and share card on every page

    Each inner page read names itself as its canonical, carries a share image and a Twitter card, and has one H1.

  • ✓

    Pictures named and described for what they show

    34 of the 35 pictures on the pages read are named and described for what they show (not: 1 with alt text that describes nothing (“Spacious white bedroom with light oak plank floors…”, a string of keywords)).

  • ✓

    A page for each service

    47 service pages in the sitemap (/blueprints/kitchen-remodel-cost-nashville/, /blueprints/bathroom-remodel-cost-and-planning-nashville/, /kitchen-remodeling/, …).

  • ✓

    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/).

  • ✓

    Titles lead with the subject

    The inner pages' titles lead with their subject, not the business name.

  • ✓

    Article schema on the post

    BlogPosting schema with an author on the post.

AI search / AEO / GEO readiness 35 of 35 points

  • ✓

    FAQPage schema

    FAQPage schema is present.

  • ✓

    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 (11 KB), headed with the name and linking 54 pages of the site — a plain statement of the business for the AI engines to read.

  • ✓

    Questions answered on the page

    20 questions asked and answered on the pages read (5 on the home page, 9 on the service page, 6 on the post page) — the shape an AI answer is lifted from.

  • ✓

    FAQs on the inner pages

    Both inner pages read carry their own FAQ with schema (5 questions on the service page, 4 questions on the post page), none repeated from another page.

  • ✓

    Specifics an engine can cite

    The service page (/kitchen-remodeling/): 921 words, 7 numbers, 11 names (Middle, Brentwood, Google, Metro, …); the post page (/blueprints/kitchen-remodel-cost-nashville/): 1,238 words, 51 numbers, 20 names (Middle, Hogue, Google, Metro, …) — specifics only this business could publish, the kind an answer engine quotes.

  • ✓

    Schema on the inner pages

    Each 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 2,314 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

    22 schema types: GeneralContractor, HomeAndConstructionBusiness, ImageObject, Organization, PostalAddress, GeoCoordinates, OpeningHoursSpecification, ContactPoint, ….

  • ✓

    Freshness dates in schema

    Newest date in the schema: 2026-10-09.

  • ✓

    Extractable structure

    Structure an engine can lift: 11 H2s, 28 H3s, 49 list items.

  • ✓

    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.

  • ✓

    The first paragraph answers

    The first paragraph under the H1 answers in 26 words on the home page and 25 words on the service page.

  • ✓

    Speakable specification

    A speakable specification is present.

Local SEO & entity signals 5 of 5 points

  • ✓

    Business entity schema

    GeneralContractor / HomeAndConstructionBusiness schema names the business.

  • ✓

    Service area stated by town

    The service area is stated by town: Nashville, TN, White House, TN, Hendersonville, TN and Gallatin, TN and 26 more, in the schema too.

  • ✓

    Business schema completeness

    The business node carries name, url, telephone, address, logo or image, areaServed, openingHours.

  • ✓

    Linked to its profiles

    The business node's sameAs names Facebook, Instagram, TikTok, LinkedIn, BBB and Google Business Profile — the links the engines use to know this site and those profiles are one business.

  • ✓

    Address and phone on the page

    The phone ((615) 815-7698) and where the business is (600 N Sage Rd) are on the page as text, and the phone matches the schema's.

  • ✓

    Site name for Google

    WebSite schema names the site “Southern Belle Construction”, also known as “SBC Nashville” — the name Google shows above each result.

  • ✓

    The trade's own schema type

    GeneralContractor / HomeAndConstructionBusiness: schema.org's own type for what the business does.

  • ✓

    A named person

    A named person in the schema: Mary Wood.

  • ✓

    Trust signals

    Trust language present: licensed, insured, warranty, bbb, accredited.

  • ✓

    Reviews on the page

    Reviews on the home page: a rating and count in the schema, reviews quoted, and a link to where they live.

  • ✓

    Hours shown and in schema

    The hours are on the page and in the business schema.

Speed, scripts & mobile 18 of 20 points

  • !

    Scripts and third parties

    5 scripts, 526 KB of JavaScript, from 2 third parties (Google Tag Manager and Google Ads). Google Tag Manager 0.6 s held the phone's main thread while the page loaded. 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.

  • •

    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.

  • ✓

    Mobile PageSpeed score

    Lighthouse mobile performance 87/100. Google's own bands: 90 and up is good, 50–89 needs improvement.

  • ✓

    Lighthouse accessibility score

    Lighthouse accessibility 97/100.

  • ✓

    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

    25 images: 25 with dimensions, 25 in a modern format or through an image service, 24 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

    4 font files (124 KB) from sbcnashville.com.

  • ✓

    The hero image loads first

    The hero image is asked for early and not lazy-loaded (<img srcset="/assets/img/work/pergola-pavilion-640.6a2f8261.webp 640w,).

  • ✓

    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 353 ms from our server.

  • ✓

    HTML weight

    About 20 KB compressed (89 KB of HTML).

  • ✓

    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.

  • ✓

    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 1.9 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).

  • ✓

    Page weight

    881 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: Render-blocking requests (about 0.1 s).

Conversion & lead generation 4 of 5 points

  • !

    A lead form that fits a phone

    The lead form asks 9 fields. 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 /api/lead, guarded by a honeypot.

  • ✓

    Analytics installed

    Measured by Google Analytics.

  • ✓

    Tappable phone number

    8 tel: links — the number dials from a phone.

  • ✓

    No CAPTCHA puzzle

    No CAPTCHA puzzle on the page.

Read with the home page: service page sbcnashville.com/kitchen-remodeling/ · post page sbcnashville.com/blueprints/kitchen-remodel-cost-nashville/

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.

Want this fixed?

We can fix every issue on sbcnashville.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.

ReplyOne business day
ProposalWritten · scoped · priced
ContractMonth to month
Proposal request

Tell us what you need

No spam · One business day reply · Month to month