clickedstudios.com scored 72/100 on the website scan.
Decent
clickedstudios.com · Scanned 2026-09-27
42 passed14 warnings8 failed
- Technical SEO & indexability18/20 of 20 points
- On-page SEO & content16/20 of 20 points
- AI search / AEO / GEO readiness19/30 of 30 points
- Local SEO & entity signals6/10 of 10 points
- Performance & mobile8/10 of 10 points
- Trust / E-E-A-T / reputation2/5 of 5 points
- Conversion & lead generation3/5 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.
What to fix first
-
✗
llms.txt +5 points
/llms.txt returns a web page, not a text file — the site answers unknown paths with its home page, so there is no llms.txt and no real 404 either.
What we’d do: Every site ships an llms.txt written from its facts, and unknown paths return 404.
-
!
FAQPage schema +3 points
The page asks and answers 2 questions but carries no FAQPage schema, so the engines have to find them on their own.
What we’d do: The FAQ's questions and answers go into FAQPage schema, built from the same text so the two always match.
-
✗
Address and phone on the page +2 points
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.
-
✗
Titles across the site +2 points
the post page's title is 70 characters.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
Tappable phone number +2 points
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.
Every check, by category (70 checks)
Technical SEO & indexability 18 of 20 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 redirects (301) instead of returning 404. Better than a soft 404, but a redirect to the home page still teaches Google the site has no missing pages.
What we’d do: Missing routes return a real 404 with a helpful page.
-
!
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 best practices
Lighthouse best practices 73/100 — the report names what to fix.
What we’d do: No console errors, no deprecated APIs, images at their real aspect ratio, HTTPS everywhere.
-
✓
Indexable by search engines
No noindex on the page or in the headers, and robots.txt lets Googlebot in.
-
✓
HTTPS certificate
Valid until 2026-10-28, issued by Google Trust Services, on clickedstudios.com and www.clickedstudios.com.
-
✓
Canonical URL
Canonical is https://clickedstudios.com/.
-
✓
Mixed content
Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.
-
✓
Sitemap
Sitemap at http://clickedstudios.com/sitemap_index.xml — an index of 6 sitemaps.
-
✓
HTTP redirects to HTTPS
http:// redirects (301) to https://clickedstudios.com/.
-
✓
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: http://clickedstudios.com/sitemap_index.xml.
-
✓
Sitemap dates
46 pages with lastmod dates, from 2008-11-12 to 2024-09-26.
-
✓
www and apex agree
www.clickedstudios.com redirects (301) to clickedstudios.com.
-
✓
Lighthouse SEO score
Lighthouse SEO 100/100.
On-page SEO & content 16 of 20 points
-
✗
Titles across the site
the post page's title is 70 characters.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
Descriptions across the site
the post page has no description.
What we’d do: Every page gets its own 120–160 character description, checked in the build.
-
!
Social share cards
Only part of the share markup: Open Graph is there, the Twitter card is not.
What we’d do: Every page carries og:title, og:image, twitter:card and twitter:image.
-
•
Pages read
Read with the home page: post page https://clickedstudios.com/state-online-marketing-2014-presentation/.
-
✓
Page title
“St. Louis Web Design | Clicked Studios” — 38 characters, inside the 30–60 Google shows in full.
-
✓
Meta description
140 characters — fills the space Google shows without being cut.
-
✓
Single H1
One H1: “Harness the Power of Digital Brand Marketing.”.
-
✓
Readable content in the HTML
324 words of readable text in the HTML.
-
✓
Pages that repeat each other
The pages read share no sentences beyond the header, footer and calls to action.
-
✓
Image alt text
All 29 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/webp, 8 KB).
AI search / AEO / GEO readiness 19 of 30 points
-
✗
llms.txt
/llms.txt returns a web page, not a text file — the site answers unknown paths with its home page, so there is no llms.txt and no real 404 either.
What we’d do: Every site ships an llms.txt written from its facts, and unknown paths return 404.
-
!
FAQPage schema
The page asks and answers 2 questions but carries no FAQPage schema, so the engines have to find them on their own.
What we’d do: The FAQ's questions and answers go into FAQPage schema, built from the same text so the two always match.
-
!
FAQs on the inner pages
the post page answers questions without FAQPage schema.
What we’d do: Every service, area and post page carries its own researched questions — the ones people ask about that subject — visible and in FAQPage schema.
-
!
Freshness dates in schema
The newest date in the schema is 2024-09-12, 2 years ago. The engines read that as a page nobody has touched.
What we’d do: dateModified is written from the page's real last change on every build.
-
•
FAQ questions visible on the page
Skipped — no FAQ schema to compare.
-
•
Speakable specification
No speakable specification. Google's speakable is a news-only beta, so this is noted, not scored.
-
✓
Questions answered on the page
6 questions asked and answered on the pages read (2 on the home page, 4 on the post page) — the shape an AI answer is lifted from.
-
✓
Readable without JavaScript
The page's 324 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: WebPage, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, ….
-
✓
Extractable structure
Structure an engine can lift: 5 H2s, 0 H3s, 8 list items, 2 question headings.
-
✓
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 6 of 10 points
-
✗
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.
-
!
Business schema completeness
The business node has name, url, logo or image but not telephone, address.
What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.
-
!
Linked to its profiles
sameAs names only Facebook. The Google Business Profile is the one the map pack and Google's AI read first.
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.
-
!
Service area stated
The home page does not say which towns the business serves — visitors and engines both need it.
What we’d do: A service-area line in the hero and footer, a page per town, and areaServed in the schema.
-
✓
Business entity schema
Organization schema names the business.
Performance & mobile 8 of 10 points
-
✗
Largest Contentful Paint (LCP)
Largest Contentful Paint 9.9 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 57/100 (measured 2026-09-27). 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.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Render-blocking requests (about 1.7 s); Font display (about 1.1 s); Improve image delivery (about 0.1 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.
-
✓
Cumulative Layout Shift (CLS)
Cumulative Layout Shift 0.00 (lab). Google's thresholds: 0.1 good, 0.25 poor.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 93/100.
-
✓
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 791 ms from our server.
-
✓
HTML weight
About 22 KB compressed (129 KB of HTML).
-
✓
Compression
Responses are compressed (br).
-
✓
Image hygiene
14 images: 9 with dimensions, 8 in a modern format or through an image service, 7 lazy-loaded.
-
✓
HTTP/2 or HTTP/3
HTTP/2 negotiated, HTTP/3 advertised.
Trust / E-E-A-T / reputation 2 of 5 points
-
✗
Reviews on the page
No reviews, rating or testimonials on the home page — the proof visitors look for first.
What we’d do: The live Google rating, count and newest reviews on every page.
-
!
Trust signals
Only years of experience, <n> years — 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.
-
•
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.
-
✓
Article schema on the post
Article schema with an author on the post.
Conversion & lead generation 3 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.
-
!
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.
-
•
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.
Read with the home page: post page clickedstudios.com/state-online-marketing-2014-presentation/
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 clickedstudios.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.