ksdk.com scored 71/100 on the website scan.
Decent
ksdk.com · Scanned 2026-09-17
19 passed6 warnings6 failed
- Technical SEO & indexability74
- On-page SEO & content47
- AI search / AEO / GEO readiness13
- Local SEO & entity signals0
- Performance & mobile88
What to fix first
-
✗
Meta description (150–160 chars)
Description is only 79 chars. Way under the 150-char sweet spot — Google often rewrites short descriptions, losing your messaging.
What we’d do: We write 150–160 char descriptions so Google uses what you wrote.
-
✗
Social share cards (OG + Twitter)
No OpenGraph or Twitter Card metadata. Shares on Slack, X, LinkedIn, iMessage will look broken.
What we’d do: Every Zorva page gets OG + Twitter cards with a custom image.
-
✗
JSON-LD schema markup
No JSON-LD schema found. Google and AI search engines lose the structured signal.
What we’d do: Every Zorva-built site ships 8+ JSON-LD schema types — Organization, LocalBusiness, FAQPage, Review, Breadcrumb, Service, Product, HowTo.
-
✗
Business entity schema
No Organization or LocalBusiness schema. Google can't build a knowledge-graph entry without it.
What we’d do: Standard on every Zorva site, with NAP + service area + hours.
-
✗
llms.txt (AI summary file)
No llms.txt at the domain root. ChatGPT, Perplexity, and Claude have to guess your business facts.
What we’d do: Every Zorva site ships a tuned llms.txt — see /blog/llms-txt-small-business-setup-guide for the playbook.
Every check, by category (35 checks)
AI search / AEO / GEO readiness 13
-
✗
llms.txt (AI summary file)
No llms.txt at the domain root. ChatGPT, Perplexity, and Claude have to guess your business facts.
What we’d do: Every Zorva site ships a tuned llms.txt — see /blog/llms-txt-small-business-setup-guide for the playbook.
-
!
Speakable spec (voice/AEO)
No SpeakableSpecification. Voice engines (Siri, Alexa, Google Assistant) have nothing tuned to read aloud.
What we’d do: We add Speakable + data-speakable hooks to TLDR + key paragraphs on every page.
-
✓
AI crawler permissions
robots.txt does not block major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.).
Performance & mobile 88
-
•
Mobile PageSpeed score
Couldn't fetch Google PageSpeed Insights for this URL. PageSpeed Insights timed out after 28s.
-
•
HTTP/2 or HTTP/3
Couldn't detect HTTP/2 or HTTP/3 from response headers. Server may still support it, but isn't advertising via Alt-Svc.
-
✓
Page load time
Fetched in 293ms — fast.
-
✓
HTML payload size
37KB on the wire (gzipped) · 37KB uncompressed. Lean and fast.
-
✓
Compression
Server is using gzip compression — saves 60–80% of bytes.
Trust / E-E-A-T / reputation
-
!
Author / Person schema
No Person schema. Google + AI engines prefer content with a named human author entity.
What we’d do: We add a Person/Founder schema graph on the home + about + team pages.
SEO basics
-
✗
Meta description (150–160 chars)
Description is only 79 chars. Way under the 150-char sweet spot — Google often rewrites short descriptions, losing your messaging.
What we’d do: We write 150–160 char descriptions so Google uses what you wrote.
-
✗
Social share cards (OG + Twitter)
No OpenGraph or Twitter Card metadata. Shares on Slack, X, LinkedIn, iMessage will look broken.
What we’d do: Every Zorva page gets OG + Twitter cards with a custom image.
-
!
Image alt text
10 of 96 images missing alt text.
What we’d do: We write descriptive alt text on every image for accessibility + Image SEO.
-
✓
Page title (50–60 chars)
"St. Louis Breaking News, Weather, Traffic, Sports | ksdk.com" — 60 chars, dead-on Google's sweet spot.
-
✓
Single H1
Exactly one H1 on the page.
-
✓
Canonical URL
Canonical points to https://www.ksdk.com/
-
✓
Sitemap.xml
Sitemap published with 33 URLs.
-
✓
Favicon
Favicon link tag present — branded SERP appearance + browser tab icon.
-
✓
HTML lang attribute
<html lang="en-US"> — accessibility + AI search signal.
-
✓
robots.txt
robots.txt present (280 bytes).
-
✓
Sitemap directive in robots.txt
robots.txt points crawlers at the sitemap explicitly.
-
✓
Title vs H1 differentiation
Title and H1 are distinct — Google reads them as complementary signals.
-
✓
404 page handling
Random URLs return a proper 404 — Google won't index ghost pages.
Mobile, accessibility + security
-
✗
Mixed content
Found 1 insecure http:// reference on an https:// page. Browsers warn / block these.
What we’d do: Zorva sites are 100% HTTPS — we replace any http:// asset URLs at build time.
-
!
Possible fixed-width overflow
Found 1 inline width(s) at 728px — these may overflow a 360px phone viewport.
What we’d do: Zorva sites use fluid widths and CSS Grid/Flex so every layout scales to phone, tablet, and desktop.
-
!
Security headers
Missing 2/4 baseline security headers: Content-Security-Policy, Referrer-Policy.
What we’d do: Zorva-hosted sites ship all four (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy) by default.
-
✓
Mobile viewport
Viewport meta tag set for responsive design.
-
✓
Mobile zoom not blocked
Pinch-to-zoom is allowed. Accessibility-compliant.
-
✓
HTTPS (SSL)
Site loads over HTTPS.
-
✓
HSTS header
Strict-Transport-Security is set — browsers force HTTPS forever.
-
✓
HTTP → HTTPS redirect
Plain HTTP requests redirect (301) to HTTPS.
Structured data
-
✗
JSON-LD schema markup
No JSON-LD schema found. Google and AI search engines lose the structured signal.
What we’d do: Every Zorva-built site ships 8+ JSON-LD schema types — Organization, LocalBusiness, FAQPage, Review, Breadcrumb, Service, Product, HowTo.
-
✗
Business entity schema
No Organization or LocalBusiness schema. Google can't build a knowledge-graph entry without it.
What we’d do: Standard on every Zorva site, with NAP + service area + hours.
-
!
FAQPage schema
No FAQPage schema. AI Overview + voice engines lean heavily on this format.
What we’d do: We add FAQPage schema to every site, auto-extracted from the visible Q&A blocks.
-
•
Article / BlogPosting schema
Not a blog/article URL — skipped.
-
•
HowTo schema
No HowTo schema. Optional — only valuable on pages that describe a step-by-step process.
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 ksdk.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.