prodigyseweranddrain.com scored 17/100 on the website scan.
Major issues
prodigyseweranddrain.com · Scanned 2026-11-13
30 passed13 warnings33 failed
- Technical SEO & indexability4/10 of 10 points
- On-page SEO & content0/25 of 25 points
- AI search / AEO / GEO readiness2/35 of 35 points
- Local SEO & entity signals0/5 of 5 points
- Speed, scripts & mobile11/20 of 20 points
- Conversion & lead generation0/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.
-
✗
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.
-
✗
Mobile viewport +3 points
No mobile viewport meta tag — a phone shows the desktop layout zoomed out.
What we’d do: Mobile first: the viewport tag and a layout built at 375px.
-
!
llms.txt +2 points
llms.txt exists but is thin (65 characters) — a heading, the services, the places and links to the pages give the engines something to cite.
What we’d do: Every site ships an llms.txt written from its facts: who, what, where, the proof, the pages.
Every check, by category (103 checks)
Technical SEO & indexability 4 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.
-
✗
Missing pages return 404
A made-up URL returns 200 with a page. These soft 404s get crawled and indexed as real pages and waste the crawl on nothing.
What we’d do: Missing routes return a real 404 with a helpful page.
-
✗
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.
-
✗
Language declared
No lang attribute on <html>. Screen readers and translation tools have to guess the language.
What we’d do: <html lang="en"> on every page.
-
!
Canonical URL
No canonical link. With www, trailing-slash and tracking variants of the URL, Google has to guess which one to index.
What we’d do: Every page names itself as its own canonical URL.
-
!
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 73/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.
-
•
Internal links resolve
No links to the site's own pages on the home page to follow.
-
•
www and apex agree
www.prodigyseweranddrain.com answered 525.
-
•
Sitemap dates
The sitemap carries no lastmod dates. Search engines then decide for themselves when to recrawl.
-
✓
Indexable by search engines
No noindex on the page or in the headers, and robots.txt lets Googlebot in.
-
✓
Mixed content
Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.
-
✓
Sitemap
Sitemap at https://prodigyseweranddrain.com/sitemap.xml — 1 URL.
-
✓
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: /sitemap.xml.
-
✓
Sitemap lists the live URLs
The sitemap's 1 URL is on https://prodigyseweranddrain.com, and the pages read from it answer directly and are open to indexing.
-
✓
Lighthouse best practices
Lighthouse best practices 96/100.
On-page SEO & content 0 of 25 points
-
✗
Page title
The home page has no <title>.
What we’d do: Every page gets a title of 30–60 characters with the service, the place and the name.
-
✗
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.
-
✗
Titles across the site
the service page has no title.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
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.
-
✗
Readable content in the HTML
The HTML carries only 0 words of readable text. If the page is drawn by JavaScript, search engines and AI crawlers may be seeing an empty page.
What we’d do: Every page's words are in the HTML the server sends, not assembled in the browser.
-
✗
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.
-
✗
Canonical and share card on every page
The service page (/lander) has no canonical, no share image, no Twitter card and no H1.
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.
-
✗
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.
-
!
A page for each service
Only 1 service page in the sitemap (/lander). A service with no page of its own has nothing to rank for it.
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.
-
!
A menu a thumb can use
The service page read (/lander) is not linked from the home page.
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.
-
•
No stock or AI-marked pictures
No pictures on the pages read.
-
•
Image alt text
No <img> tags in the HTML.
-
•
Share image loads
Skipped — no og:image to fetch.
-
•
Pages that repeat each other
Not enough copy on the pages read to compare.
-
•
Pictures named and described for what they show
No pictures on the pages read.
-
•
Title and H1 differ
Skipped — no title or no H1 to compare.
-
•
Titles lead with the subject
No business name in the schema to compare the titles against.
-
•
Service pages link each other
Skipped — fewer than three service pages to link between.
-
•
Pages read
Read with the home page: service page https://prodigyseweranddrain.com/lander.
-
•
Article schema on the post
No post found in the sitemap to check.
-
✓
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.
-
✓
Not a stock template
No builder or stock theme shows in the page: no template credit, demo pictures or sample text.
-
✓
Favicon
No favicon link, but /favicon.ico is served — browsers and Google find it there.
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.
-
✗
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 (/lander) 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 (/lander) 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
No H2 headings: 0 H2s, 0 H3s, 0 list items. The page reads as one block, which neither search nor AI can quote from.
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 home page has no H1 to answer under; the service 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.
-
!
llms.txt
llms.txt exists but is thin (65 characters) — a heading, the services, the places and links to the pages give the engines something to cite.
What we’d do: Every site ships an llms.txt written from its facts: who, what, where, the proof, the pages.
-
!
Readable without JavaScript
The page needs no JavaScript to read, but its HTML carries only 0 words — little for an engine to read or quote.
What we’d do: Home pages we write carry the services, the places, the proof and the questions people ask, in the HTML itself.
-
•
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.
-
✓
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.
-
✗
Address and phone on the page
Neither a phone number nor a town or street address is on the home page as text. Map search and the answer engines match a business to a place by what its pages say.
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.
-
✗
Trust signals
No insurance, guarantee, license or accreditation language on the home page. Noted, not scored.
What we’d do: Insurance, a written guarantee and the trade's credentials, stated plainly where the visitor decides.
-
✗
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.
-
!
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.
-
•
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 11 of 20 points
-
✗
Mobile viewport
No mobile viewport meta tag — a phone shows the desktop layout zoomed out.
What we’d do: Mobile first: the viewport tag and a layout built at 375px.
-
✗
Cumulative Layout Shift (CLS)
Cumulative Layout Shift 0.30 (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.
-
✗
Compression
The HTML is sent uncompressed — three to five times more bytes than it needs.
What we’d do: Brotli or gzip on every text response; every host we use does it by default.
-
!
Lighthouse accessibility score
Lighthouse accessibility 81/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.
-
!
Fonts
2 font files (65 KB) from widget.trustpilot.com. 2 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.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Avoid multiple page redirects (about 0.8 s); Render-blocking requests (about 0.8 s).
What we’d do: These are the first three things we would fix.
-
•
Image hygiene
No raster images on the page.
-
•
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.
-
•
Pinch-to-zoom allowed
Skipped — no viewport tag to read.
-
✓
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 84/100. Google's own bands: 90 and up is good, 50–89 needs improvement.
-
✓
Scripts and third parties
4 scripts, 243 KB of JavaScript, from 2 third parties (GoDaddy and widget.trustpilot.com).
-
✓
Nothing blocks the first paint
1 file loads before anything is drawn — styles and scripts in the head — and PageSpeed puts 0.8 s of the first paint on waiting for it.
-
✓
No hero slider or autoplay video
One hero: no slider and no autoplaying video in the first screen.
-
✓
The hero image loads first
The largest thing on the first screen is text or a styled block (<p class="footer_parkwebDisclaimerText__cYMIc">), which paints as soon as the HTML arrives.
-
✓
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 323 ms from our server.
-
✓
HTML weight
About 1 KB compressed (1 KB of HTML).
-
✓
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.5 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).
-
✓
Page weight
343 KB downloaded to show the home page on a phone.
-
✓
Static files cached
6 files served with a short or missing cache lifetime, 0 of them the site's own.
Conversion & lead generation 0 of 5 points
-
✗
Contact form
No form and no contact link on the home page.
What we’d do: A short quote form on every page, stored first and emailed second.
-
✗
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.
-
!
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.
-
•
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.
-
✓
No CAPTCHA puzzle
No CAPTCHA puzzle on the page.
Read with the home page: service page prodigyseweranddrain.com/lander
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 prodigyseweranddrain.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.