www.haventaxadvisory.com scored 35/100 on the website scan.
Major issues
haventaxadvisory.com · Scanned 2026-11-13
51 passed14 warnings22 failed
- Technical SEO & indexability9/10 of 10 points
- On-page SEO & content3/25 of 25 points
- AI search / AEO / GEO readiness8/35 of 35 points
- Local SEO & entity signals1/5 of 5 points
- Speed, scripts & mobile11/20 of 20 points
- Conversion & lead generation3/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 +5 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 +5 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 +5 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.
-
✗
Specifics an engine can cite +3 points
The service page (/blank-2) 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 +3 points
The service page (/blank-2) 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.
Every check, by category (103 checks)
Technical SEO & indexability 9 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.
-
•
HTTPS certificate
The certificate could not be read from this platform, but the page was fetched over HTTPS.
-
•
Internal links resolve
Too few of the site's links answered this scan to judge (1 tried).
-
✓
Indexable by search engines
No noindex on the page or in the headers, and robots.txt lets Googlebot in.
-
✓
Structured data Google accepts
1 schema type 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://www.haventaxadvisory.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.
-
✓
Sitemap
Sitemap at https://www.haventaxadvisory.com/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://haventaxadvisory.com/.
-
✓
Language declared
<html lang="en">.
-
✓
Redirect chain
One redirect (301) to https://www.haventaxadvisory.com/.
-
✓
robots.txt
robots.txt is served (5 groups, 1 sitemap line).
-
✓
Sitemap named in robots.txt
robots.txt names the sitemap: https://www.haventaxadvisory.com/sitemap.xml.
-
✓
www and apex agree
haventaxadvisory.com redirects (301) to www.haventaxadvisory.com.
-
✓
Sitemap lists the live URLs
The sitemap's 2 URLs are all on https://www.haventaxadvisory.com, and the pages read from it answer directly and are open to indexing.
-
✓
Lighthouse SEO score
Lighthouse SEO 92/100.
-
✓
Lighthouse best practices
Lighthouse best practices 100/100.
-
✓
Sitemap dates
2 pages with lastmod dates, from 2026-08-20 to 2026-08-20.
On-page SEO & content 3 of 25 points
-
✗
Page title
“HOME | Haven” is only 12 characters — it says almost nothing to a searcher.
What we’d do: We write titles 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.
-
✗
Titles across the site
the service page's title is 15 characters.
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.
-
✗
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.
-
✗
No stock phrases
The home page: “tailored to your”, “your unique needs” and 3 brochure phrases (“peace of mind”, “comprehensive”, “additionally”). 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.
-
!
Social share cards
Only part of the share markup: Twitter card is there, Open Graph is not.
What we’d do: Every page carries og:title, og:image, twitter:card and twitter:image.
-
!
Canonical and share card on every page
The service page (/blank-2) has no share image 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.
-
!
Pictures named and described for what they show
Of the 6 pictures on the pages read, 4 with alt text that describes nothing (“Moss.png”, the file's own name; “chris.jpg”, the file's own name). Google's image guidelines ask for file names and alt text that say what the picture shows.
What we’d do: Every picture is named for what it shows, in the business's own words (franklin-standing-seam-metal-roof.webp, never IMG_4411.jpg), and its alt text says what is in it — the job, the place, the material — rather than a keyword.
-
!
A page for each service
Only 1 service page in the sitemap (/blank-2). 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.
-
!
About and privacy pages
The home page links an About page (/) 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.
-
!
A menu a thumb can use
The service page read (/blank-2) 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.
-
!
Not a stock template
Built with Wix, from templates thousands of businesses share. Nothing is left over from the template, but the layout says “Wix” before it says anything about the business.
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.
-
•
Title and H1 differ
Skipped — no title or no H1 to compare.
-
•
Service pages link each other
Skipped — fewer than three service pages to link between.
-
•
Pages read
Read with the home page: service page https://www.haventaxadvisory.com/blank-2.
-
•
Article schema on the post
No post found in the sitemap to check.
-
✓
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 6 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.
-
✓
Image alt text
All 7 images have an alt attribute.
-
✓
Readable content in the HTML
377 words of readable text in the HTML.
-
✓
Favicon
A favicon is linked — it shows in the tab and beside the site in Google's results.
-
✓
Titles lead with the subject
The inner pages' titles lead with their subject, not the business name.
AI search / AEO / GEO readiness 8 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 (/blank-2) 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 (/blank-2) 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.
-
✗
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.
-
•
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.
-
✓
llms.txt
llms.txt is published (3 KB), headed with the name and linking 2 pages of the site — a plain statement of the business for the AI engines to read.
-
✓
Readable without JavaScript
The page's 377 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
1 schema type: WebSite.
-
✓
Extractable structure
Structure an engine can lift: 8 H2s, 5 H3s, 6 list items.
-
✓
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 1 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.
-
!
Trust signals
Only cpa. 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.
-
✓
Address and phone on the page
The phone ((615) 804-1140) and where the business is (256 Seaboard Lane) are on the page as text.
-
✓
Site name for Google
WebSite schema names the site “Haven” — the name Google shows above each result.
Speed, scripts & mobile 11 of 20 points
-
✗
Scripts and third parties
89 scripts, 950 KB of JavaScript, from 2 third parties (Wix and browser.sentry-cdn.com). Wix 0.4 s held the phone's main thread while the page loaded. A phone downloads, parses and runs all of it before the page settles.
What we’d do: Our pages load one analytics tag and the form's bot check — two third parties and under 100 KB of JavaScript — and nothing runs before the page is drawn.
-
✗
Image hygiene
7 images: 0 with dimensions, 0 in a modern format or through an image service, 5 lazy-loaded. 7 of 7 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.
-
✗
HTML weight
About 160 KB compressed (997 KB of HTML) — every visit downloads this before anything is drawn.
What we’d do: Our pages are 20–50 KB compressed: the words and the markup, nothing bundled in.
-
✗
Largest Contentful Paint (LCP)
Largest Contentful Paint 10.8 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.
-
!
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.
-
!
Readable and tappable on a phone
One piece of text is too faint to read against its background (“LEARN MORE” 3.85: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.
-
!
Page weight
1.8 MB downloaded to show the home page on a phone. On a cellular connection that is seconds of waiting, and data the visitor pays for.
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.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Avoid multiple page redirects (about 0.8 s); Reduce unused JavaScript (about 0.6 s); Improve image delivery (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.
-
✓
Mobile PageSpeed score
Lighthouse mobile performance 70/100. Google's own bands: 90 and up is good, 50–89 needs improvement.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 93/100.
-
✓
Nothing blocks the first paint
Nothing blocks the first paint: the page is drawn as soon as the HTML arrives.
-
✓
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 (94 KB) from Wix.
-
✓
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 123 ms from our server.
-
✓
Compression
Responses are compressed (br).
-
✓
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.
-
✓
Static files cached
Every static file is served with a long cache lifetime.
Conversion & lead generation 3 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.
-
!
Tappable phone number
A phone number is shown but is not a tel: link — on a phone it has to be copied, not tapped.
What we’d do: Every number on our sites is a tel: link, and every tap is counted as a lead.
-
•
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 back to the page, where a script sends it (no spam guard shows in the page; a filter on the server can't be seen from outside).
-
✓
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.
Read with the home page: service page www.haventaxadvisory.com/blank-2
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 www.haventaxadvisory.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.