venashcorporation.com scored 43/100 on the website scan.
Needs work
venashcorporation.com · Scanned 2026-11-21
55 passed14 warnings15 failed
- Technical SEO & indexability7/10 of 10 points
- On-page SEO & content12/25 of 25 points
- AI search / AEO / GEO readiness10/35 of 35 points
- Local SEO & entity signals2/5 of 5 points
- Speed, scripts & mobile8/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
-
✗
FAQPage schema +7 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 +7 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 +5 points
Only 1 question asked and answered on the pages read (1 on the home 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.
-
✗
Meta description +3 points
The home page has no meta description, so Google writes its own from the page.
What we’d do: Every page gets a 120–160 character description written to earn the click.
-
✗
No stock or AI-marked pictures +2 points
4 pictures marked as AI-made on the pages read: media-generation-venash-cocina-backsplash-piedr-0-2878c880-19e7-49e1-b3df-90be8a02cebb.jpg (the IPTC mark for an AI-generated picture inside the file); media-generation-venash-patio-concreto-0-1da656bf-a286-48c8-bb06-3e803bed1dd8.jpg (the IPTC mark for an AI-generated picture inside the file); media-generation-venash-escalones-terminados-0-b29e5ce2-c664-4157-902f-b07843d1faec.jpg (the IPTC mark for an AI-generated picture inside the file); …. Visitors comparing businesses, and Google's quality raters, look for photos of the business's own work.
What we’d do: The owner's own photos of real jobs are the proof of work, in every section that shows the work; a stock or generated picture only ever sets the mood, and it is named and described for what it shows.
Every check, by category (103 checks)
Technical SEO & indexability 7 of 10 points
-
✗
Security headers
Missing 3 of the four baseline security headers: Content-Security-Policy, 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.
-
✗
HTTP redirects to HTTPS
The site serves pages over plain http:// (200). A visitor who types the address without https gets the insecure copy.
What we’d do: Every http:// URL goes straight to its https:// twin with a 301.
-
!
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.
-
•
HTTPS certificate
The certificate could not be read from this platform, but the page was fetched over HTTPS.
-
•
Internal links resolve
No links to the site's own pages on the home page to follow.
-
✓
Indexable by search engines
No noindex on the page or in the headers, and robots.txt lets Googlebot in.
-
✓
Structured data Google accepts
10 schema types on the 1 page 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://venashcorporation.com/.
-
✓
Mixed content
Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.
-
✓
Sitemap
Sitemap at https://venashcorporation.com/sitemap_index.xml — an index of 2 sitemaps.
-
✓
Missing pages return 404
A made-up URL returns 404, so Google never indexes ghost pages.
-
✓
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://venashcorporation.com/sitemap_index.xml.
-
✓
www and apex agree
www.venashcorporation.com redirects (301) to venashcorporation.com.
-
✓
Sitemap lists the live URLs
The sitemap's 1 URL is on https://venashcorporation.com.
-
✓
Lighthouse SEO score
Lighthouse SEO 92/100.
-
✓
Lighthouse best practices
Lighthouse best practices 100/100.
-
✓
Sitemap dates
1 page with lastmod dates.
On-page SEO & content 12 of 25 points
-
✗
Meta description
The home page has no meta description, so Google writes its own from the page.
What we’d do: Every page gets a 120–160 character description written to earn the click.
-
✗
No stock or AI-marked pictures
4 pictures marked as AI-made on the pages read: media-generation-venash-cocina-backsplash-piedr-0-2878c880-19e7-49e1-b3df-90be8a02cebb.jpg (the IPTC mark for an AI-generated picture inside the file); media-generation-venash-patio-concreto-0-1da656bf-a286-48c8-bb06-3e803bed1dd8.jpg (the IPTC mark for an AI-generated picture inside the file); media-generation-venash-escalones-terminados-0-b29e5ce2-c664-4157-902f-b07843d1faec.jpg (the IPTC mark for an AI-generated picture inside the file); …. Visitors comparing businesses, and Google's quality raters, look for photos of the business's own work.
What we’d do: The owner's own photos of real jobs are the proof of work, in every section that shows the work; a stock or generated picture only ever sets the mood, and it is named and described for what it shows.
-
✗
Single H1
No H1 heading on the page — the one line that says what the page is about.
What we’d do: Every page gets one H1 that names the service and the place.
-
✗
A page for each service
No service pages in the sitemap: 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
The home page links an About page (/#AboutUs) but no privacy policy — a site whose form takes names, phone numbers and emails says what it does with them.
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.
-
•
Titles across the site
Skipped — no inner page read.
-
•
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.
-
•
Title and H1 differ
Skipped — no title or no H1 to compare.
-
•
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.
-
✓
Page title
“Venash Corporation - Venash Corporation” — 39 characters, inside the 30–60 Google shows in full.
-
✓
Social share cards
Open Graph title and image and a Twitter card. A share on any platform unfurls with a picture.
-
✓
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.
-
✓
Not a stock template
WordPress, with a theme of its own (hello-biz) and Elementor; nothing of a stock template shows — no theme credit, demo pictures or sample text.
-
✓
Image alt text
All 241 images have an alt attribute.
-
✓
Readable content in the HTML
1,334 words of readable text in the HTML.
-
✓
Share image loads
The share image loads (image/png, 20 KB).
-
✓
Pictures named and described for what they show
16 of the 16 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.
-
✓
A menu a thumb can use
A header with no menu links to read.
AI search / AEO / GEO readiness 10 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.
-
✗
The first paragraph answers
The home page has no H1 to answer under. 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.
-
!
Questions answered on the page
Only 1 question asked and answered on the pages read (1 on the home 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.
-
•
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.
-
•
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 1,334 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
10 schema types: WebPage, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, ….
-
✓
Freshness dates in schema
Newest date in the schema: 2026-11-12.
-
✓
Extractable structure
Structure an engine can lift: 13 H2s, 16 H3s, 12 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 2 of 5 points
-
✗
The trade's own schema type
Organization only: it says a company exists, not what it does or where.
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.
-
!
Service area stated by town
One town is named (Middle Tennessee). 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.
-
!
Business schema completeness
The business node has name, url, logo or image but not telephone, address.
What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.
-
!
Reviews on the page
Reviews are quoted but there is no rating or count beside them, and nothing says how many there are.
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
The hours are on the page but not in the business schema, so the engines read them out of the prose.
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.
-
•
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.
-
✓
Business entity schema
Organization schema names the business.
-
✓
Linked to its profiles
The business node's sameAs names Facebook and Instagram — the links the engines use to know this site and those profiles are one business.
-
✓
Address and phone on the page
The phone ((629) 251-4699) and where the business is (Murfreesboro, Tennessee) are on the page as text.
-
✓
Site name for Google
WebSite schema names the site “Venash Corporation” — the name Google shows above each result.
-
✓
Trust signals
Trust language present: licensed, insured, years of experience, since <year>, founded <year>.
Speed, scripts & mobile 8 of 20 points
-
✗
Image hygiene
19 images: 3 with dimensions, 0 in a modern format or through an image service, 2 lazy-loaded. 16 of 19 images have no width and height, so the page jumps as they load; none are WebP or AVIF, which are half the size of JPEG and PNG.
What we’d do: Every image has width and height, is served as WebP or AVIF at the size it is shown, and loads lazily below the fold.
-
✗
Readable and tappable on a phone
6 pieces of text are too faint to read against their background (“19. August, 2026.” 3.81:1, “Ver Google reviews” 3.67:1, “Escribir una reseña” 3.67: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.
-
✗
No hero slider or autoplay video
A Swiper slider in the first screen. A slider is the heaviest element on most templated pages, and the headline a visitor was reading slides away before they finish it.
What we’d do: One hero: one picture, one headline, one call to action. A slider shows the visitor's answer for a few seconds and then takes it away, and it is the heaviest thing on most templated pages.
-
✗
Largest Contentful Paint (LCP)
Largest Contentful Paint 30.7 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.
-
✗
Page weight
7.4 MB downloaded to show the home page on a phone. On a cellular connection that is many seconds before the page settles.
What we’d do: Our pages weigh 300–700 KB in all: 20–50 KB of HTML, two fonts, pictures sized to the box they fill in WebP or AVIF, and almost no JavaScript.
-
!
Mobile PageSpeed score
Lighthouse mobile performance 67/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.
-
!
Nothing blocks the first paint
22 files load before anything is drawn — styles and scripts in the head — and PageSpeed puts 0.9 s of the first paint on waiting for them.
What we’d do: The styles the first screen needs are inlined and the rest load after it, every script is deferred, and the hero image is preloaded: nothing stands between the HTML and the first paint.
-
!
Fonts
7 font files (144 KB) from Trustindex and Google Fonts.
What we’d do: Two font families in the weights the page uses, from one host, with font-display set so the words show at once in a fallback face.
-
!
The hero image loads first
The hero image is not preloaded or marked high priority, so the browser finds it late.
What we’d do: The hero picture is the first thing the HTML asks for: sized, in a modern format, preloaded with fetchpriority=high and never lazy-loaded, so the first screen paints in about a second.
-
!
HTTP/2 or HTTP/3
Google's PageSpeed test loaded the page over http/1.1 — HTTP/1.1 loads one resource at a time per connection.
What we’d do: Every host we use speaks HTTP/2 and HTTP/3.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Improve image delivery (about 10.1 s); Render-blocking requests (about 0.8 s); Use efficient cache lifetimes (about 0.3 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.
-
✓
No popup on arrival
Nothing covers the page on arrival: no popup, no email gate.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 91/100.
-
✓
Scripts and third parties
21 scripts, 188 KB of JavaScript, from 1 third party (Trustindex).
-
✓
Cumulative Layout Shift (CLS)
Cumulative Layout Shift 0.00 (lab). Google's thresholds: 0.1 good, 0.25 poor.
-
✓
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 253 ms from our server.
-
✓
HTML weight
About 29 KB compressed (206 KB of HTML).
-
✓
Compression
Responses are compressed (br).
-
✓
One chat widget at most
No chat widget scripts on the page.
-
✓
Static files cached
1 file served with a short or missing cache lifetime, 0 of them the site's own.
Conversion & lead generation 4 of 5 points
-
!
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.
-
•
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 / (no spam guard shows in the page; a filter on the server can't be seen from outside).
-
✓
Tappable phone number
2 tel: links — the number dials from a phone.
-
✓
A lead form that fits a phone
The lead form asks 4 fields, labeled, and fits a phone screen.
-
✓
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 venashcorporation.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.