StoneCast Studio
Sample Report — Studio Demonstration

SEO + AI-Visibility Audit

Search finds you. Do AI assistants?

Subject site
www.stonecladmedia.com
Audit date
2026-07-11
Pages crawled
7 key pages + robots + sitemap
Overall grade
B+  (strong, fixable gaps)

Honesty label: this is a demonstration report produced by Stonecast Studio's real audit pipeline, run against a website our studio owns (Stoneclad Media — our parent company). Every data point below was measured, not invented. Client reports follow this exact template — with your branding on this page instead of ours (white-label delivery).

01 — Executive Scorecard

Where the site stands

B+
Overall

The technical foundation is genuinely strong — clean indexing setup, perfect Lighthouse SEO and Best-Practices scores, hardened security headers. The gaps cluster in one theme: the site is optimized for search engines but under-equipped for AI assistants. Entity signals are thin, canonicals are missing, and there is no AI-crawler guidance. All of it is fixable in weeks, not months.

Technical foundation
A−
On-page content
B+
Structured data & AI-readiness
C+
Social & sharing
B
Performance & security
A

Grades are the studio's assessment rubric applied to measured signals (methodology in §6). They rank priorities; they are not a Google metric.

02 — What's already working

Keep doing this

Measured strengths

  • Lighthouse (mobile, live run): SEO 100 · Best Practices 100 · Accessibility 92
  • Valid robots.txt with sitemap declared; clean 20-URL XML sitemap
  • Unique, descriptive <title> + meta description on all 7 audited pages
  • Exactly one <h1> per page with a logical H2 outline
  • FAQPage structured data with 10 Q&A pairs — a genuine AI-answer asset
  • 404 page correctly returns noindex, nofollow

Infrastructure strengths

  • HTTPS with HSTS (includeSubDomains; preload)
  • Content-Security-Policy + X-Frame-Options headers present
  • Fast edge delivery (Vercel CDN, cache HITs; homepage HTML fetched in ~0.5s)
  • Host consolidation exists: apex redirects to www
  • Mobile viewport + lang="en" set sitewide
  • twitter:card summary_large_image on all pages

03 — Prioritized Findings

Nine findings, ranked by impact ÷ effort

#SeverityFindingEffort
F-01HighNo canonical URL tags on any audited page — 0 of 7 pages declare rel=canonicalLow
F-02HighOrganization schema too thin for entity recognition — no logo, sameAs, address, or founderLow
F-03MedHost redirect uses 307 (temporary) instead of 308/301 — signals don't consolidate cleanlyLow
F-04MedHomepage missing og:image — the most-shared page falls back to blank link previewsLow
F-05MedMeta descriptions over display limit on 3 pages (202–229 chars vs ~155 shown)Low
F-06MedNo AI-crawler policy or llms.txt/llms.txt 404s; robots.txt silent on AI agentsLow
F-07LowService pages carry no Service/Breadcrumb schema — missed rich-result + extraction surfaceMed
F-08LowAccessibility: contrast + color-only links — the two failed Lighthouse auditsMed
F-09LowHub pages thin on extractable copy (/assets 435 words, /growth 394) + zero outbound citations sitewideMed

04 — Findings in Detail

Evidence and exact fixes

F-01 · HIGH · TECHNICAL

No canonical tags, anywhere

None of the 7 audited pages declares rel=canonical. The apex→www redirect currently does the de-duplication work, but any tracking parameter, mirror, or scraper republication creates a duplicate Google must guess about. Canonicals are the cheap insurance policy — and AI crawlers use them to pick the authoritative copy of a page too.

$ audit crawl — canonical extraction, 7 pages / canonical: null /the-model canonical: null /assets canonical: null /growth canonical: null /about canonical: null /faq canonical: null /contact canonical: null
Add self-referencing canonicals sitewide. In Next.js: set metadataBase + alternates.canonical in the root layout — one change covers every route. Add og:url at the same time.
F-02 · HIGH · AI-VISIBILITY (AEO)

The Organization entity is a ghost

AI assistants decide who you are from structured entity signals. The site's Organization schema has a name, URL, and description — and nothing else. No logo, no sameAs links to social profiles, no address, no founder. When an assistant tries to disambiguate "Stoneclad Media" from every other similarly-named business, you've given it almost nothing to anchor on.

// Live JSON-LD on homepage (complete object, as served) { "@type": "Organization", "name": "Stoneclad Media", "url": "https://stonecladmedia.com", "description": "..." } // Missing: logo, sameAs[], address, founder, contactPoint, areaServed
Expand to a full Organization entity: logo, sameAs (YouTube, LinkedIn, X…), founder (Person), address (Tulsa, OK), contactPoint. This single block is the highest-leverage AEO edit on the site.
F-03 · MED · TECHNICAL

Temporary redirect doing a permanent job

The apex host answers with 307 Temporary Redirect to www. A 307 tells crawlers "this move might reverse — keep checking the old URL." Ranking signals consolidate slower and less completely than with a permanent 308/301.

$ curl -sI https://stonecladmedia.com/ HTTP/1.1 307 Temporary Redirect Location: https://www.stonecladmedia.com/
Switch host-level redirects to 308 Permanent (Vercel: "permanent": true in redirect config, or set the canonical domain in project settings).
F-04 · MED · SOCIAL

Homepage link previews have no image

Interior pages declare og:image (1200×630) — the homepage doesn't. Shares of the root URL in Slack, LinkedIn, iMessage, and X render text-only. That's the single most-shared URL losing its richest preview format.

/ og:image: null /the-model og:image: https://stonecladmedia.com/og-image.png ✓ /about og:image: https://stonecladmedia.com/og-image.png ✓
Add the same og:image to the homepage metadata (and reference it via the www host so it resolves without a redirect hop).
F-05 · MED · ON-PAGE

Three meta descriptions get truncated in results

Google displays roughly 155–160 characters. Three pages run long, so the call-to-action tail — usually the most persuasive part — is cut mid-sentence in the search snippet.

/ 202 chars ▸ truncates ~45 chars early /about 228 chars ▸ truncates ~70 chars early /faq 229 chars ▸ truncates ~70 chars early (other 4 pages: 147–179 chars — acceptable)
Rewrite the three to ≤155 characters with the value proposition front-loaded. Keep the two-beat positioning; trim the qualifier clauses.
F-06 · MED · AI-VISIBILITY (AEO)

No instructions for AI crawlers at all

The site has no llms.txt (returns 404) and robots.txt takes no position on AI agents (GPTBot, ClaudeBot, PerplexityBot). Silence means default behavior — you're neither guiding AI systems to your best content nor deliberately opting out. For a business that sells expertise, being well-represented in AI answers is the win; that takes explicit signals.

$ curl https://www.stonecladmedia.com/llms.txt → 404 $ robots.txt (complete): User-Agent: * Allow: / Disallow: /studio/ Sitemap: https://stonecladmedia.com/sitemap.xml ← no AI-agent directives
Publish /llms.txt summarizing what the business does, key pages, and the FAQ. Make an explicit robots.txt decision per AI crawler. Point the sitemap URL at the www host while you're in the file.
F-07 · LOW · STRUCTURED DATA

Service pages describe offers Google can't parse

The eight service pages (/assets/*, /growth/*) carry zero structured data. Each is a well-defined service — a natural fit for Service + BreadcrumbList markup that feeds both rich results and AI extraction.

Add a Service JSON-LD block per offer page (provider → the Organization entity from F-02) and BreadcrumbList sitewide.
F-08 · LOW · ACCESSIBILITY

The two failed Lighthouse audits

Accessibility scored 92/100. The two failures: some text sits below WCAG contrast ratio on the dark theme, and in-text links are distinguishable by color alone. Both matter for users — and accessibility quality correlates with how cleanly machines parse the page.

lighthouse (mobile) — failed audits: 2 of 50 color-contrast score 0 "Background and foreground colors do not have a sufficient contrast ratio" link-in-text-block score 0 "Links rely on color to be distinguishable"
Raise muted-text opacity steps on dark backgrounds to clear 4.5:1; add underline (or underline-on-idle) to in-paragraph links.
F-09 · LOW · CONTENT / E-E-A-T

Hub pages are lean where AI wants sentences

/assets (435 words) and /growth (394 words) are elegant menu pages — good UX, but AI systems quote sentences, not layouts. Neither page contains an extractable plain-language definition of the service category. Related: the audited pages contain zero outbound links, a missed authority/citation signal.

Add a 2–3 sentence extractable summary block ("What is a digital-asset build?") near the top of each hub page, and cite 2–3 authoritative external sources where natural (e.g., platform documentation).

05 — 90-Day Action Plan

The order to fix it in

Week 1–2
Quick wins
  • Self-referencing canonicals + og:url sitewide (F-01) — one layout change
  • Homepage og:image (F-04) · trim 3 meta descriptions (F-05)
  • Flip apex redirect 307 → 308 permanent (F-03)
Week 3–4
Entity build
  • Full Organization schema: logo, sameAs, founder, address, contactPoint (F-02)
  • Publish llms.txt; set explicit AI-crawler policy in robots.txt (F-06)
  • Verify all sitemap + schema URLs reference the www host consistently
Month 2
Extraction surface
  • Service + BreadcrumbList schema on all 8 offer pages (F-07)
  • Extractable summary blocks on /assets and /growth (F-09)
  • Contrast + link-styling accessibility pass (F-08)
Month 3
Measure
  • Re-crawl and re-grade against this baseline (expect Structured Data pillar C+ → A−)
  • Run live AI-assistant visibility testing (the full AEO module) against the upgraded entity
  • Review Search Console: impressions/CTR deltas on pages with rewritten snippets

06 — Methodology & Disclosure

How this report was produced

Measured, not templated. Every finding above comes from live data collected on 2026-07-11: a crawl of 7 key pages plus robots.txt and sitemap.xml; header inspection (redirects, security headers, caching); HTML extraction of titles, meta tags, canonicals, Open Graph tags, JSON-LD blocks, heading outlines, link graphs, and word counts; and a live Google Lighthouse run (mobile emulation) for the SEO / Best-Practices / Accessibility scores quoted.

AI-assisted, human-reviewed. Stonecast Studio's pipeline does the measurement and drafts the analysis; a human reviews every report before delivery. That combination is why turnaround is 24 hours instead of a week.

What the paid audit adds beyond this sample: competitor benchmarking (3–5 competitors), Core Web Vitals field data, local/GBP signals where relevant, and — on AI-visibility tiers — live buyer-style query testing across ChatGPT, Perplexity, and Google AI results with a consistency-scored visibility scorecard.

Sample-report disclosure: the subject site is owned by our parent company, chosen so we could publish a full, unredacted report without exposing any client's data. No client information appears in this document.