www.claro.studio scored 31/100 on the website scan.
Major issues
claro.studio · Scanned 2026-10-30
48 passed19 warnings23 failed
- Technical SEO & indexability9/10 of 10 points
- On-page SEO & content8/25 of 25 points
- AI search / AEO / GEO readiness4/35 of 35 points
- Local SEO & entity signals1/5 of 5 points
- Speed, scripts & mobile8/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 +4 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 +4 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 +4 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 +4 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.
-
✗
Scripts and third parties +2 points
41 scripts, 931 KB of JavaScript, from 5 third parties (Squarespace, definitions.sqspcdn.com, ajax.googleapis.com and a public CDN). Squarespace 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.
Every check, by category (103 checks)
Technical SEO & indexability 9 of 10 points
-
!
Security headers
Missing: Content-Security-Policy, 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.
-
•
www and apex agree
claro.studio answered 526.
-
✓
Indexable by search engines
No noindex on the page or in the headers, and robots.txt lets Googlebot in.
-
✓
Structured data Google accepts
2 schema types on the 2 pages 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.claro.studio/.
-
✓
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.claro.studio/sitemap.xml — 15 URLs.
-
✓
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://www.claro.studio/.
-
✓
Internal links resolve
All 3 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 (1 group, 1 sitemap line).
-
✓
Sitemap named in robots.txt
robots.txt names the sitemap: https://www.claro.studio/sitemap.xml.
-
✓
Sitemap lists the live URLs
The sitemap's 15 URLs are all on https://www.claro.studio, and the pages read from it answer directly and are open to indexing.
-
✓
Lighthouse SEO score
Lighthouse SEO 100/100.
-
✓
Lighthouse best practices
Lighthouse best practices 96/100.
-
✓
Sitemap dates
15 pages with lastmod dates, from 2025-03-23 to 2025-04-01.
On-page SEO & content 8 of 25 points
-
✗
Titles across the site
the service page's title repeats the home page's.
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's description repeats the home page's.
What we’d do: Every page gets its own 120–160 character description, checked in the build.
-
✗
Pages that repeat each other
5 of the 5 sentences on the home page also appear on the service page (100%). Pages that repeat each other with a word swapped are what Google's scaled-content rules are written against.
What we’d do: Every page is written once, for its own subject, from the business's own facts — no page is another with the city swapped.
-
✗
Canonical and share card on every page
The service page (/home) has a canonical naming the home page, so Google is told to index the home page in its place 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.
-
✗
Titles lead with the subject
Every inner page's title starts with the business name (“CLARO | Custom Millwork & Cabinetry”) — the builder's default — so the service and the place come last, or are cut.
What we’d do: Every title puts the subject first and the brand last — “Roof Repair in Franklin, TN | Hale Roofing” — because Google bolds the words that match the search, and nobody searches the business's name to find a service.
-
✗
Service pages link each other
The service page read links none of the other 11 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.
-
!
Readable content in the HTML
132 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.
-
!
Pictures named and described for what they show
Of the 9 pictures on the pages read, 6 with a camera's, a template's or an upload's name (Nashville+architectural+photographer+-+Ford+Photographs+-+Claro+-+February+07,+2025+-+018.jpg, Nashville+architectural+photographer+-+Ford+Photographs+-+Claro+-+February+15,+2025+-+052.jpg, Resize.Nashville+architectural+photographer+-+Ford+Photographs+-+Claro+-+February+07,+2025+-+021.jpg, …). 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.
-
!
Not a stock template
Built with Squarespace, from templates thousands of businesses share. Nothing is left over from the template, but the layout says “Squarespace” 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.
-
!
About and privacy pages
The home page links an About page (/about) 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 (/home) 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.
-
•
Title and H1 differ
Skipped — no title or no H1 to compare.
-
•
Pages read
Read with the home page: service page https://www.claro.studio/home.
-
•
Article schema on the post
No post found in the sitemap to check.
-
✓
Page title
“CLARO | Custom Millwork & Cabinetry” — 35 characters, inside the 30–60 Google shows in full.
-
✓
Meta description
134 characters — fills the space Google shows without being cut.
-
✓
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.
-
✓
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 9 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 12 images have an alt attribute.
-
✓
Share image loads
The share image loads (image/webp, 98 KB).
-
✓
A page for each service
11 service pages in the sitemap (/sid-mashburn, /sony, /crieve-hall, …).
-
✓
Favicon
A favicon is linked — it shows in the tab and beside the site in Google's results.
AI search / AEO / GEO readiness 4 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.
-
✗
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.
-
!
Specifics an engine can cite
The service page (/home): 102 words, 1 number, 1 name (Nashville) — thin for a page an answer engine should quote. They quote prices, timelines, counts, and named places, products and people.
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 (/home) has no BreadcrumbList and no Service for what it offers.
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.
-
!
Readable without JavaScript
The page needs no JavaScript to read, but its HTML carries only 132 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.
-
✓
JSON-LD present and valid
2 schema types: WebSite, LocalBusiness.
-
✓
Extractable structure
Structure an engine can lift: 7 H2s, 0 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
-
✗
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.
-
✗
Business schema completeness
The business node carries only logo or image — no name, url, telephone, address, areaServed, openingHours.
What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.
-
✗
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.
-
!
Linked to its profiles
The page links Instagram, but the business node has no sameAs naming it, so the engines have to guess that they are the same business.
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.
-
!
The trade's own schema type
LocalBusiness — a generic type. schema.org has one for nearly every trade, and the engines file a business by it.
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.
-
•
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
LocalBusiness schema names the business.
-
✓
Site name for Google
WebSite schema names the site “CLARO” — the name Google shows above each result.
Speed, scripts & mobile 8 of 20 points
-
✗
Scripts and third parties
41 scripts, 931 KB of JavaScript, from 5 third parties (Squarespace, definitions.sqspcdn.com, ajax.googleapis.com and a public CDN). Squarespace 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.
-
✗
Nothing blocks the first paint
9 files load before anything is drawn — styles and scripts in the head — and PageSpeed puts 2.0 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.
-
✗
Image hygiene
10 images: 2 with dimensions, 0 in a modern format or through an image service, 1 lazy-loaded. 8 of 10 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.
-
✗
Largest Contentful Paint (LCP)
Largest Contentful Paint 8.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.
-
!
Mobile PageSpeed score
Lighthouse mobile performance 68/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.
-
!
Fonts
1 font file (62 KB) from Squarespace. 1 face 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.
-
!
Time to first byte
First byte took 873 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.
-
!
Page weight
1.4 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: Render-blocking requests (about 1.9 s); Reduce unused JavaScript (about 1.8 s); Reduce unused CSS (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.
-
✓
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.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 100/100.
-
✓
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 alt="" data-src="https://images.squarespace-cdn.com/content/v1/66).
-
✓
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 37 KB compressed (481 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.
-
✓
Static files cached
Every static file is served with a long cache lifetime.
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.
-
•
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 www.claro.studio/home
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.claro.studio.
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.