welcomehomekzoo.com scored 31/100 on the website scan.
Major issues
welcomehomekzoo.com · Scanned 2026-10-30
45 passed22 warnings19 failed
- Technical SEO & indexability7/10 of 10 points
- On-page SEO & content8/25 of 25 points
- AI search / AEO / GEO readiness2/35 of 35 points
- Local SEO & entity signals0/5 of 5 points
- Speed, scripts & mobile13/20 of 20 points
- Conversion & lead generation1/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 +3 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 +3 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 +3 points
No question is asked and answered on the 2 pages read. When someone asks ChatGPT or Google's AI about a service, the engines quote pages that ask that 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 +3 points
The service 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.
-
✗
Meta description +2 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.
Every check, by category (103 checks)
Technical SEO & indexability 7 of 10 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.
-
!
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 SEO score
Lighthouse SEO 85/100 — the report names what to fix.
What we’d do: Our sites score 100 on Lighthouse SEO: every page crawlable, titled, described, with valid links and alt text.
-
•
HTTPS certificate
The certificate could not be read from this platform, but the page was fetched over HTTPS.
-
•
Structured data Google accepts
Skipped — no structured data on the pages read.
-
✓
Indexable by search engines
No noindex on the page or in the headers, and robots.txt lets Googlebot in.
-
✓
Canonical URL
Canonical is https://welcomehomekzoo.com/.
-
✓
Mixed content
Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.
-
✓
Sitemap
Sitemap at https://welcomehomekzoo.com/wp-sitemap.xml — an index of 1 sitemap.
-
✓
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://welcomehomekzoo.com/.
-
✓
Internal links resolve
All 6 internal links read on the home page answer.
-
✓
Language declared
<html lang="en-US">.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
robots.txt
robots.txt is served (2 groups, 1 sitemap line).
-
✓
Sitemap named in robots.txt
robots.txt names the sitemap: https://welcomehomekzoo.com/wp-sitemap.xml.
-
✓
www and apex agree
www.welcomehomekzoo.com redirects (301) to welcomehomekzoo.com.
-
✓
Sitemap lists the live URLs
The sitemap's 6 URLs are all on https://welcomehomekzoo.com, and the pages read from it answer directly and are open to indexing.
-
✓
Lighthouse best practices
Lighthouse best practices 96/100.
-
✓
Sitemap dates
6 pages with lastmod dates, from 2026-10-13 to 2026-10-27.
On-page SEO & content 8 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.
-
✗
Social share cards
No Open Graph or Twitter card tags. A share in Messages, LinkedIn, Facebook or Slack shows a bare link.
What we’d do: Every page carries og:title, og:image, twitter:card and twitter:image, with a real picture.
-
✗
Descriptions across the site
the service page has no description.
What we’d do: Every page gets its own 120–160 character description, checked in the build.
-
✗
About and privacy pages
Neither an About page nor a privacy policy is linked from the home page: nothing tells a visitor, or Google's quality raters, who runs the business or what happens to what they send.
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.
-
✗
Service pages link each other
The service page read links none of the other 3 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.
-
!
Single H1
3 H1 headings. One is the convention search engines and screen readers expect.
What we’d do: One H1 per page; the rest become H2s.
-
!
Image alt text
2 of 9 images have no alt attribute.
What we’d do: Every image gets an alt that says what is in it; decorative ones get alt="".
-
!
Readable content in the HTML
223 words of readable text on the home page — thin for a page that has to explain a business.
What we’d do: Home pages we write carry the services, the places, the proof and the questions people ask.
-
!
Canonical and share card on every page
The service page (/archived-issues/) has no share image, no Twitter card and 2 H1s.
What we’d do: Every page names itself as its canonical, carries its own og:image and twitter:image, and opens with one H1 — checked on every page before the site ships.
-
!
Not a stock template
Built with WordPress, the Twenty Twenty-Five theme: Twenty Twenty-Five 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.
-
•
Share image loads
Skipped — no og:image to fetch.
-
•
Pages that repeat each other
Not enough copy on the pages read to compare.
-
•
Titles lead with the subject
No business name in the schema to compare the titles against.
-
•
Pages read
Read with the home page: service page https://welcomehomekzoo.com/archived-issues/.
-
•
Article schema on the post
No post found in the sitemap to check.
-
✓
Page title
“Welcome Home Kalamazoo – "Great Things Local"” — 45 characters, inside the 30–60 Google shows in full.
-
✓
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 25 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.
-
✓
Pictures named and described for what they show
24 of the 24 pictures on the pages read are named and described for what they show.
-
✓
A page for each service
4 service pages in the sitemap (/archived-issues/, /distribution/, /advertise/, …).
-
✓
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.
-
✓
A menu a thumb can use
A header with no menu links to read, and the service page read is one tap from the home page.
AI search / AEO / GEO readiness 2 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.
-
✗
Questions answered on the page
No question is asked and answered on the 2 pages read. When someone asks ChatGPT or Google's AI about a service, the engines quote pages that ask that 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
The service 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.
-
✗
Specifics an engine can cite
The service page (/archived-issues/) gives no number — no price, timeline, size or count — and names nothing beyond the business and its town. A competitor could publish it unchanged, and the answer engines quote pages with specifics they can check.
What we’d do: Every page is written from the business's own facts: real prices or ranges, timelines, how many and how big, the products and brands used, the towns and neighborhoods worked in, the people by name — 300 words or more that no competitor could publish unchanged.
-
✗
Schema on the inner pages
The service page (/archived-issues/) has no structured data. Past the home page the engines get no structured statement of what a page is or whose it is.
What we’d do: Every page carries the business node, a BreadcrumbList and its own type — a Service on each service page, BlogPosting on each post — so an engine knows what each page is and whose it is.
-
✗
JSON-LD present and valid
No JSON-LD on the page. Google and the answer engines get no structured statement of what this is.
What we’d do: Every page carries Organization or LocalBusiness, WebSite, BreadcrumbList and the page's own type.
-
!
Extractable structure
Little for an engine to lift: 2 H2s, 1 H3s, 6 list items. Answer engines quote headed sections, lists and question-and-answer blocks.
What we’d do: Every page is written in headed sections with lists and question headings, so an answer can be lifted whole.
-
!
The first paragraph answers
The service page's headline is followed by buttons and pictures, not a sentence.
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.
-
•
FAQ questions visible on the page
Skipped — no FAQ schema to compare.
-
•
Freshness dates in schema
No dateModified or datePublished in the schema. Not expected on every home page; a freshness date helps the engines trust the page is current.
-
•
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 223 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.
-
✓
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 0 of 5 points
-
✗
Business entity schema
No Organization or LocalBusiness schema. The engines have no entity to attach the reviews, the phone and the service area to.
What we’d do: LocalBusiness (or the trade's own type) with name, phone, address, hours, service area and sameAs on every page.
-
✗
Service area stated by town
The home page does not say which towns the business serves — visitors and engines both need it.
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.
-
✗
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.
-
!
Address and phone on the page
The page says where the business is (3111 Lake St) but shows no phone number.
What we’d do: The business name, phone and town — or street address — in the footer of every page, exactly as the Google Business Profile has them, and the same in the schema.
-
!
Site name for Google
Nothing names the site: no WebSite schema and no og:site_name, so Google picks the name shown above each result from the title and headings.
What we’d do: WebSite schema on the home page with the business's name, and alternateName for any other name people use, as on the Business Profile.
-
!
Trust signals
Only 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 schema completeness
Skipped — no business node to read.
-
•
The trade's own schema type
Skipped — no business node to read.
-
•
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.
Speed, scripts & mobile 13 of 20 points
-
!
Nothing blocks the first paint
3 files load before anything is drawn — styles and scripts in the head — and PageSpeed puts 0.5 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.
-
!
Readable and tappable on a phone
3 pieces of text are too faint to read against their background (“Most Recent Issue” 3.3:1, “Home” 4.05:1, “Archived Issues” 4.05:1); WCAG asks 4.5:1 for text that size.
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.
-
!
Image hygiene
9 images: 7 with dimensions, 0 in a modern format or through an image service, 4 lazy-loaded. 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.
-
!
Fonts
3 font files (293 KB) from welcomehomekzoo.com. 3 faces without font-display, so the words wait for the file.
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.
-
!
Static files cached
10 files served with a short or missing cache lifetime, 10 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.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Font display (about 3.0 s); Document request latency (about 0.6 s); Reduce initial server response time (about 0.6 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.
-
✓
Mobile PageSpeed score
Lighthouse mobile performance 90/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, 22 KB of JavaScript, from no third party.
-
✓
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.
-
✓
The hero image loads first
The hero image is asked for early and not lazy-loaded (<img fetchpriority="high" decoding="async" width="762" height="161" sr).
-
✓
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 19 KB compressed (110 KB of HTML).
-
✓
Compression
Responses are compressed (gzip).
-
✓
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.7 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).
-
✓
Page weight
457 KB downloaded to show the home page on a phone.
Conversion & lead generation 1 of 5 points
-
✗
Tappable phone number
No phone number on the home page. For a service business the call is the conversion.
What we’d do: A tappable number in the header, the hero and the footer of every page.
-
!
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.
-
!
Call to action in the first screen
Nothing in the top of the page asks for the call — no number, form or quote button before the visitor scrolls.
What we’d do: Our heroes carry the number and the quote button; most visitors decide there.
-
!
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.
-
!
No CAPTCHA puzzle
hCaptcha on the page: no puzzle most of the time, but several hundred KB of script on every page load and a share of real visitors challenged.
What we’d do: Turnstile, or a honeypot and a time trap, on the form: nothing the visitor has to solve, under 20 KB, and the lead stored before it is emailed.
-
•
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.
-
•
A lead form that fits a phone
No form on the home page to read; the contact form check says whether one is linked.
-
•
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.
Read with the home page: service page welcomehomekzoo.com/archived-issues/
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 welcomehomekzoo.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.