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

nashvilleswebdesign.com scored 97/100 on the website scan.

Strong

nashvilleswebdesign.com · Scanned 2026-11-08

Unchanged from 2026-11-07

92 passed5 warnings2 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 signals4 of 5 points
  • Speed, scripts & mobile20 of 20 points
  • Conversion & lead generation5 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

  • ✗

    A menu a thumb can use +1 point

    28 links in the header and menu; the service page read (/leads/tree-service/) is not linked from the home page. 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.

  • !

    Service pages link each other +1 point

    The service page read links one other service page in its copy (/seo-check/), of 157.

    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.

  • !

    Static files cached +1 point

    4 files served with a short or missing cache lifetime, 3 of them the site's own. A return visitor downloads them 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.

  • !

    Linked to its profiles +1 point

    The page links Google Business Profile, but the business node has no sameAs naming it, 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.

  • !

    The trade's own schema type +1 point

    Organization / ProfessionalService — 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.

Every check, by category (103 checks)

Technical SEO & indexability 10 of 10 points

  • !

    Sitemap dates

    Every page in the sitemap carries the same date (2026-11-07) — a build stamp, not the day each page changed. Google ignores dates it has learned not to trust.

    What we’d do: Each page's lastmod is the day its own content last changed, written from the content's hash, never the build date.

  • •

    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

    27 schema types on the 2 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://nashvilleswebdesign.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://nashvilleswebdesign.com/sitemap.xml — 168 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://nashvilleswebdesign.com/.

  • ✓

    Internal links resolve

    All 40 internal links read (30 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 (20 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://nashvilleswebdesign.com/sitemap.xml.

  • ✓

    www and apex agree

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

  • ✓

    Sitemap lists the live URLs

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

On-page SEO & content 23 of 25 points

  • ✗

    A menu a thumb can use

    28 links in the header and menu; the service page read (/leads/tree-service/) is not linked from the home page. 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.

  • !

    Service pages link each other

    The service page read links one other service page in its copy (/seo-check/), of 157.

    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.

  • •

    Pages read

    Read with the home page: service page https://nashvilleswebdesign.com/leads/tree-service/.

  • •

    Article schema on the post

    No post found in the sitemap to check.

  • ✓

    Page title

    “Nashville’s Web Design | Web Design, SEO & AI Search Agency” — 59 characters, inside the 30–60 Google shows in full.

  • ✓

    Meta description

    155 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 2 pages read.

  • ✓

    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 21 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: “Nashville web design and SEO you can check on your phone before you ever call us…”.

  • ✓

    Image alt text

    All 22 images have an alt attribute.

  • ✓

    Readable content in the HTML

    4,359 words of readable text in the HTML.

  • ✓

    Share image loads

    The share image loads (image/png, 45 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 9 of 45 (20%) between the service and home pages.

  • ✓

    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.

  • ✓

    Pictures named and described for what they show

    19 of the 19 pictures on the pages read are named and described for what they show.

  • ✓

    A page for each service

    158 service pages in the sitemap (/leads/tree-service/, /services/branding/, /services/web-design/, …).

  • ✓

    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.

AI search / AEO / GEO readiness 35 of 35 points

  • ✓

    FAQPage schema

    FAQPage schema is present.

  • ✓

    FAQ questions visible on the page

    All 6 questions in the FAQ schema are on the page, with the answers it shows.

  • ✓

    llms.txt

    llms.txt is published (44 KB), headed with the name and linking 166 pages of the site — a plain statement of the business for the AI engines to read.

  • ✓

    Questions answered on the page

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

  • ✓

    FAQs on the inner pages

    The inner page read carries its own FAQ with schema (4 questions on the service page), none repeated from another page.

  • ✓

    Specifics an engine can cite

    The service page (/leads/tree-service/): 706 words, 13 numbers, 16 names (Middle, NashvillesTreeServicecom, Davidson, County, …) — specifics only this business could publish, the kind an answer engine quotes.

  • ✓

    Schema on the inner pages

    The 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 4,359 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: Organization, ProfessionalService, ImageObject, PostalAddress, City, State, AdministrativeArea, ContactPoint, ….

  • ✓

    Freshness dates in schema

    Newest date in the schema: 2026-11-07.

  • ✓

    Extractable structure

    Structure an engine can lift: 18 H2s, 25 H3s, 79 list items, 2 tables, 3 question headings.

  • ✓

    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 56 words on the home page and 38 words on the service page.

  • ✓

    Speakable specification

    A speakable specification is present.

Local SEO & entity signals 4 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.

  • !

    Linked to its profiles

    The page links Google Business Profile, but the business node has no sameAs naming it, 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.

  • !

    The trade's own schema type

    Organization / ProfessionalService — 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.

  • ✓

    Business entity schema

    Organization / ProfessionalService schema names the business.

  • ✓

    Service area stated by town

    The service area is stated by town: Nashville, Franklin, Brentwood and Murfreesboro and 18 more, in the schema too.

  • ✓

    Business schema completeness

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

  • ✓

    Address and phone on the page

    The phone ((615) 913-4895) 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 “Nashville’s Web Design” — the name Google shows above each result.

  • ✓

    A named person

    A named person in the schema: Michael Blair.

  • ✓

    Trust signals

    Trust language present: guarantee, bbb, cpa, since <year>.

  • ✓

    Reviews on the page

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

Speed, scripts & mobile 20 of 20 points

  • !

    Static files cached

    4 files served with a short or missing cache lifetime, 3 of them the site's own. A return visitor downloads them 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.

  • •

    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 99/100 (measured 2026-11-07). Google's own bands: 90 and up is good, 50–89 needs improvement.

  • ✓

    Lighthouse accessibility score

    Lighthouse accessibility 100/100.

  • ✓

    Scripts and third parties

    5 scripts, 206 KB of JavaScript, from 2 third parties (Google Tag Manager and static.cloudflareinsights.com).

  • ✓

    Nothing blocks the first paint

    1 file loads before anything is drawn — styles and scripts in the head — and PageSpeed puts 0.3 s of the first paint on waiting for it.

  • ✓

    Image hygiene

    22 images: 22 with dimensions, 20 in a modern format or through an image service, 19 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 (107 KB) from nashvilleswebdesign.com.

  • ✓

    The hero image loads first

    The largest thing on the first screen is text or a styled block (<p class="lede">), 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 386 ms from our server.

  • ✓

    HTML weight

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

  • ✓

    Page weight

    421 KB downloaded to show the home page on a phone.

  • ✓

    What would speed it up most

    Nothing large left to fix. PageSpeed's remaining suggestions: Render-blocking requests (about 0.3 s); Reduce unused CSS (about 0.1 s).

Conversion & lead generation 5 of 5 points

  • ✓

    Contact form

    8 forms 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 a honeypot.

  • ✓

    Analytics installed

    Measured by Google Analytics.

  • ✓

    Tappable phone number

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

  • ✓

    A lead form that fits a phone

    The lead form asks 6 fields, labeled, and fits a phone screen.

  • ✓

    No CAPTCHA puzzle

    No CAPTCHA puzzle on the page.

  • ✓

    Chat or text option

    A chat widget, an assistant or a text link is present — a way to ask without calling.

Read with the home page: service page nashvilleswebdesign.com/leads/tree-service/

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