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

kmlremodeling.com scored 58/100 on the website scan.

Needs work

kmlremodeling.com · Scanned 2026-10-02

48 passed13 warnings6 failed

  • Technical SEO & indexability13 of 15 points
  • On-page SEO & content12 of 20 points
  • AI search / AEO / GEO readiness15 of 30 points
  • Local SEO & entity signals10 of 10 points
  • Performance & mobile3 of 10 points
  • Trust / E-E-A-T / reputation1 of 10 points
  • Conversion & lead generation4 of 5 points

Why AI search is 30 of the 100 points

Google is sending fewer people to websites. When it answers with an AI Overview, the top-ranked page gets 58% fewer clicks (Ahrefs, 300,000 keywords, 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 +8 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.

  • !

    Questions answered on the page +6 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.

  • ✗

    About and privacy pages +3 points

    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.

  • ✗

    No stock phrases +2 points

    The home page: “say goodbye to” and 4 brochure phrases (“cutting-edge”, “you can trust”, “not just a”, …). This is what copy written without facts sounds like: nothing in it only this business could say.

    What we’d do: Every sentence is written from the business's own facts — what the crew found, what it cost, what the owner says — so none of it is a line any competitor could use.

  • !

    Meta description +2 points

    162 characters. Google shows about 160 and cuts the rest with an ellipsis.

    What we’d do: We write descriptions of 120–160 characters, the point first.

Every check, by category (85 checks)

Technical SEO & indexability 13 of 15 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.

  • •

    HTTPS certificate

    The certificate could not be read from this platform, but the page was fetched over HTTPS.

  • •

    Sitemap dates

    The sitemap carries no lastmod dates. Search engines then decide for themselves when to recrawl.

  • •

    Sitemap lists the live URLs

    The sitemap lists no page URLs to check.

  • ✓

    Indexable by search engines

    No noindex on the page or in the headers, and robots.txt lets Googlebot in.

  • ✓

    Canonical URL

    Canonical is https://kmlremodeling.com/.

  • ✓

    Mixed content

    Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.

  • ✓

    Sitemap

    Sitemap at https://kmlremodeling.com/sitemap.xml — an index of 0 sitemaps.

  • ✓

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

  • ✓

    Internal links resolve

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

  • ✓

    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.

  • ✓

    Language declared

    <html lang="en-US">.

  • ✓

    Redirect chain

    The URL answers directly, with no redirect.

  • ✓

    robots.txt

    robots.txt is served (1 group, 2 sitemap lines).

  • ✓

    Sitemap named in robots.txt

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

  • ✓

    www and apex agree

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

  • ✓

    Lighthouse SEO score

    Lighthouse SEO 92/100.

  • ✓

    Lighthouse best practices

    Lighthouse best practices 100/100.

On-page SEO & content 12 of 20 points

  • ✗

    No stock phrases

    The home page: “say goodbye to” and 4 brochure phrases (“cutting-edge”, “you can trust”, “not just a”, …). This is what copy written without facts sounds like: nothing in it only this business could say.

    What we’d do: Every sentence is written from the business's own facts — what the crew found, what it cost, what the owner says — so none of it is a line any competitor could use.

  • !

    Meta description

    162 characters. Google shows about 160 and cuts the rest with an ellipsis.

    What we’d do: We write descriptions of 120–160 characters, the point first.

  • !

    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.

  • •

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

  • •

    Descriptions across the site

    Skipped — no inner page read.

  • •

    Pages read

    No sitemap to pick inner pages from, so the home page stands for the site.

  • ✓

    Page title

    “Home Remodeling Services in Millstadt, IL - KML Remodeling” — 58 characters, inside the 30–60 Google shows in full.

  • ✓

    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.

  • ✓

    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.

  • ✓

    Readable content in the HTML

    1,431 words of readable text in the HTML.

  • ✓

    Image alt text

    All 32 images have an alt attribute.

  • ✓

    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.

  • ✓

    Share image loads

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

  • ✓

    Pictures named and described for what they show

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

AI search / AEO / GEO readiness 15 of 30 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.

  • !

    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.

  • •

    Specifics an engine can cite

    Skipped — no service page or post read to hold to the competitor test.

  • •

    FAQ questions visible on the page

    Skipped — no FAQ schema to compare.

  • •

    FAQs on the inner pages

    Skipped — no inner page read.

  • •

    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.

  • ✓

    llms.txt

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

  • ✓

    Readable without JavaScript

    The page's 1,431 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: BreadcrumbList, ListItem, Organization, ImageObject, WebPage, WebSite, LocalBusiness, GeoCoordinates, ….

  • ✓

    Freshness dates in schema

    Newest date in the schema: 2026-04-14.

  • ✓

    Extractable structure

    Structure an engine can lift: 6 H2s, 9 H3s, 41 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 10 of 10 points

  • ✓

    Business entity schema

    LocalBusiness schema names the business.

  • ✓

    Business schema completeness

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

  • ✓

    Linked to its profiles

    The business node's sameAs names Facebook, Instagram, YouTube 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 ((618) 606-7608) and where the business is (83 Rhineland Pl) are on the page as text, and the phone matches the schema's.

  • ✓

    Service area stated

    The page says where the business works.

  • ✓

    Site name for Google

    WebSite schema names the site “KML Remodeling” — the name Google shows above each result.

Performance & mobile 3 of 10 points

  • ✗

    Largest Contentful Paint (LCP)

    Largest Contentful Paint 9.5 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.

  • ✗

    Readable and tappable on a phone

    6 pieces of text are too faint to read against their background (“REQUEST A QUOTE” 2.41:1, “remodeling company” 1.76:1, “Millstadt, IL” 1.87: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.

  • !

    Mobile PageSpeed score

    Lighthouse mobile performance 51/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.

  • !

    Cumulative Layout Shift (CLS)

    Cumulative Layout Shift 0.13 (lab). Google's thresholds: 0.1 good, 0.25 poor.

    What we’d do: Every image and embed has its size in the HTML and fonts load with size-adjust, so nothing moves as the page loads.

  • !

    Lighthouse accessibility score

    Lighthouse accessibility 83/100 — the report names what to fix.

    What we’d do: Contrast, labels, landmarks and focus order are checked on every page before it ships.

  • !

    Time to first byte

    First byte took 1707 ms from our server. Google's guidance is under 800 ms; everything on the page waits for this.

    What we’d do: Static pages served from an edge network answer in well under half a second.

  • !

    Image hygiene

    32 images: 20 with dimensions, 0 in a modern format or through an image service, 17 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.

  • !

    What would speed it up most

    PageSpeed's biggest savings on this page: Use efficient cache lifetimes (about 6.8 s); Render-blocking requests (about 5.8 s); Reduce unused CSS (about 3.0 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.

  • ✓

    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.

  • ✓

    HTML weight

    About 40 KB compressed (228 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).

Trust / E-E-A-T / reputation 1 of 10 points

  • ✗

    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.

  • !

    Trust signals

    Only warranty, family-owned — a visitor comparing three sites wants license, insurance, guarantee and years stated plainly.

    What we’d do: License number, insurance, warranty and founding year on every page, and in the schema.

  • !

    Reviews on the page

    The home page mentions “what clients say” but shows no rating, review count or live reviews.

    What we’d do: The live Google rating and count, and the newest reviews, on the home page.

  • •

    Article schema on the post

    Skipped — no post found in the sitemap.

  • •

    A named person

    No named person on the home page. Not expected here — the About or team page is where a Person node belongs, with the name Google can tie to reviews and articles.

  • ✓

    No stock or AI-marked pictures

    None of the 26 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

    WordPress, with a theme of its own (dwell) and Elementor; nothing of a stock template shows — no theme credit, demo pictures or sample text.

Conversion & lead generation 4 of 5 points

  • !

    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.

  • •

    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.

  • •

    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.

  • ✓

    Tappable phone number

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

  • ✓

    Call to action in the first screen

    A phone link, a form or a quote button appears in the top of the page.

  • ✓

    Analytics installed

    Measured by Google Analytics.

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