leadgendigitalmarketing.com scored 95/100 on the website scan.
Strong
leadgendigitalmarketing.com · Scanned 2026-11-07
Down from 96 on 2026-10-09
89 passed7 warnings3 failed
- Technical SEO & indexability10/10 of 10 points
- On-page SEO & content24/25 of 25 points
- AI search / AEO / GEO readiness35/35 of 35 points
- Local SEO & entity signals3/5 of 5 points
- Speed, scripts & mobile19/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
-
!
Service area stated by town +1 point
Two towns are named (United States and Canada). A service business is found town by town; three or more, on the page and in areaServed, is the floor.
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.
-
!
A menu a thumb can use +1 point
15 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.
-
!
Static files cached +1 point
3 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
Nothing ties this site to the business's profiles elsewhere: no sameAs in the schema, and no link to a Google Business Profile, Facebook or Yelp page. Those links are how the engines tell this business from others with a similar name.
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.
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-05) — 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
19 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://leadgendigitalmarketing.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://leadgendigitalmarketing.com/sitemap.xml — 18 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://leadgendigitalmarketing.com/.
-
✓
Internal links resolve
All 19 internal links read (18 on the home page, 1 in llms.txt) answer.
-
✓
Language declared
<html lang="en">.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
robots.txt
robots.txt is served (5 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://leadgendigitalmarketing.com/sitemap.xml.
-
✓
www and apex agree
www.leadgendigitalmarketing.com redirects (301) to leadgendigitalmarketing.com.
-
✓
Sitemap lists the live URLs
The sitemap's 18 URLs are all on https://leadgendigitalmarketing.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 24 of 25 points
-
!
A menu a thumb can use
15 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://leadgendigitalmarketing.com/seo/; post page https://leadgendigitalmarketing.com/blog/contractor-website-design-three-stone-roofing/.
-
✓
Page title
“Lead Gen Digital Marketing | SEO, AI Visibility and Leads” — 57 characters, inside the 30–60 Google shows in full.
-
✓
Meta description
151 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 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.
-
✓
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: “Lead generation for owner-run businesses: calls from your own website, Google an…”.
-
✓
Image alt text
All 12 images have an alt attribute.
-
✓
Readable content in the HTML
3,231 words of readable text in the HTML.
-
✓
Share image loads
The share image loads (image/jpeg, 56 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 6 of 52 (12%) 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
10 of the 10 pictures on the pages read are named and described for what they show.
-
✓
A page for each service
11 service pages in the sitemap (/seo/, /web-design/, /angi-leads/, …).
-
✓
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.
-
✓
Service pages link each other
The service page read links 5 other service pages in its copy (/lead-generation/, /web-design/, /ai-visibility/).
-
✓
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 8 questions in the FAQ schema are on the page, with the answers it shows.
-
✓
llms.txt
llms.txt is published (7 KB), headed with the name and linking 18 pages of the site — a plain statement of the business for the AI engines to read.
-
✓
Questions answered on the page
33 questions asked and answered on the pages read (12 on the home page, 7 on the service page, 14 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 (6 questions on the service page, 6 questions on the post page), none repeated from another page.
-
✓
Specifics an engine can cite
The service page (/seo/): 1,110 words, 16 numbers, 17 names (Google, Bing, IndexNow, Michael, …); the post page (/blog/contractor-website-design-three-stone-roofing/): 2,044 words, 117 numbers, 31 names (Stone, Google, Michael, Blair, …) — 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 3,231 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
15 schema types: ProfessionalService, Organization, ImageObject, PostalAddress, Country, OfferCatalog, Offer, Service, ….
-
✓
Freshness dates in schema
Newest date in the schema: 2026-11-05.
-
✓
Extractable structure
Structure an engine can lift: 17 H2s, 11 H3s, 72 list items, 1 table, 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.
-
✓
The first paragraph answers
The first paragraph under the H1 answers in 42 words on the home page and 42 words on the service page.
-
✓
Speakable specification
A speakable specification is present.
Local SEO & entity signals 3 of 5 points
-
✗
Linked to its profiles
Nothing ties this site to the business's profiles elsewhere: no sameAs in the schema, and no link to a Google Business Profile, Facebook or Yelp page. Those links are how the engines tell this business from others with a similar name.
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.
-
✗
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
Two towns are named (United States and Canada). A service business is found town by town; three or more, on the page and in areaServed, is the floor.
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.
-
!
The trade's own schema type
ProfessionalService / Organization — 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.
-
!
Trust signals
Only cpa, since <year>. 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 entity schema
ProfessionalService / Organization schema names the business.
-
✓
Business schema completeness
The business node carries name, url, telephone, address, logo or image, areaServed.
-
✓
Address and phone on the page
The phone ((615) 488-7399) and where the business is (Nashville, Tennessee) are on the page as text, and the phone matches the schema's.
-
✓
Site name for Google
WebSite schema names the site “Lead Gen Digital Marketing” — the name Google shows above each result.
-
✓
A named person
A named person in the schema: Terry McCarthy.
Speed, scripts & mobile 19 of 20 points
-
!
Static files cached
3 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 100/100. Google's own bands: 90 and up is good, 50–89 needs improvement.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 96/100.
-
✓
Scripts and third parties
5 scripts, 191 KB of JavaScript, from 1 third party (Google Tag Manager).
-
✓
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, 9 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
2 font files (45 KB) from Google Fonts.
-
✓
The hero image loads first
The largest thing on the first screen is text or a styled block (<p class="hero__p lead">), 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 108 ms from our server.
-
✓
HTML weight
About 21 KB compressed (107 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 0.9 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).
-
✓
Page weight
309 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.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
3 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 /api/lead, guarded by Turnstile and a honeypot.
-
✓
Analytics installed
Measured by Google Analytics.
-
✓
Tappable phone number
6 tel: links — the number dials from a phone.
-
✓
No CAPTCHA puzzle
Cloudflare Turnstile: a bot check nobody has to solve.
Read with the home page: service page leadgendigitalmarketing.com/seo/ · post page leadgendigitalmarketing.com/blog/contractor-website-design-three-stone-roofing/
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 leadgendigitalmarketing.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.