contextcontinuitylayer.org
https://contextcontinuitylayer.org/STACCR
Scanned on August 4, 2026
Quick Wins — Top 5 Issues to Fix
- ✗Title-H1 alignment: 14% word overlap — title and H1 should share key termscontent
- ✗No external links — consider linking to authoritative sourcescontent
- ✗URL contains uppercase characters — use lowercase for consistency and to avoid duplicate contenttechnical
- ✗No hreflang tags — add if targeting multiple languagestechnical
- ✗No About page link detected — add for credibilitytrust
SEO — 85/100 (16 issues)
Failed Checks (16)
- ✗Title-H1 alignment: 14% word overlap — title and H1 should share key termscontent
- ✗No external links — consider linking to authoritative sourcescontent
- ✗URL contains uppercase characters — use lowercase for consistency and to avoid duplicate contenttechnical
- ✗No hreflang tags — add if targeting multiple languagestechnical
- ✗No About page link detected — add for credibilitytrust
- ✗No Contact page link detected — add for trust signalstrust
- ✗No Privacy Policy link — required by GDPR and improves trusttrust
- ✗No Terms of Service link — add for legal compliance and trusttrust
- ✗Schema may be excessive: 2 JSON-LD blocks, 11.1 KB total — consider consolidatingschema
- ✗1 JSON-LD block(s) with syntax errors — fix invalid JSONschema
- ✗URL lacks title keywords — use a descriptive URL slugtechnical
- ✗No Web App Manifest — add for installability and modern web signalstechnical
- ✗No max-image-preview:large — add to robots meta for Google Discovermeta
- ✗Event content found but no Event schema — add for event rich resultsschema
- ✗Missing ARIA landmarks — add <main>, <nav>, and skip-to-content link for accessibilityaccessibility
- ✗No RSS/Atom feed in <head> — add for content discovery by aggregators and AItechnical
Passed Checks (84)
- ✓Title tag found: "STACCR™ — Continuity without custody | Context Layer Systems"meta
- ✓Title length: 60 characters (optimal)meta
- ✓Meta description found (139 chars)meta
- ✓Description length: 139 chars (optimal)meta
- ✓Viewport meta tag found (mobile-friendly)meta
- ✓UTF-8 charset declaredmeta
- ✓Language attribute set on HTML tagmeta
- ✓No meta refresh redirect (good)meta
- ✓Robots: "index, follow"meta
- ✓meta keywords tag found — deprecated since 2009, Google ignores it. Remove to keep HTML cleanmeta
- ✓Single H1 tag foundcontent
- ✓12 H2 tags foundcontent
- ✓Heading hierarchy is correctcontent
- ✓2596 words on page (good content depth)content
- ✓Readability: 31 (moderate — aim for 60+)content
- ✓27% long sentences (>20 words) — good readabilitycontent
- ✓No images found on pagecontent
- ✓No images to check for dimensionscontent
- ✓No below-fold images to lazy loadcontent
- ✓6 internal links foundcontent
- ✓No empty href attributes foundcontent
- ✓All link texts are descriptive (no "click here" or "read more")content
- ✓Open Graph title foundsocial
- ✓Open Graph description foundsocial
- ✓Open Graph image foundsocial
- ✓Open Graph URL foundsocial
- ✓og:type set to "website"social
- ✓og:site_name: "Context Layer Systems"social
- ✓Twitter Card: "summary_large_image"social
- ✓Twitter title foundsocial
- ✓Twitter description foundsocial
- ✓Twitter image foundsocial
- ✓HTTPS enabledtechnical
- ✓Canonical tag foundtechnical
- ✓Canonical tag is self-referencing (correct)technical
- ✓Favicon foundtechnical
- ✓Compression: brtechnical
- ✓URL length: 41 chars (good)technical
- ✓URL uses hyphens or no separators (good)technical
- ✓No deprecated HTML tags foundtechnical
- ✓Text-to-HTML ratio: 14.8% (good)technical
- ✓Inline CSS: 0.0 KB (acceptable)performance
- ✓Inline JS: 12.5 KB (acceptable)performance
- ✓All 1 external scripts use defer/asyncperformance
- ✓Font preload/preconnect found — faster font loadingperformance
- ✓Cache-Control: private, max-age=14400performance
- ✓HSTS header present — enforces HTTPSsecurity
- ✓X-Content-Type-Options: nosniffsecurity
- ✓Content-Security-Policy header presentsecurity
- ✓Author byline foundtrust
- ✓2 JSON-LD schema block(s) foundschema
- ✓Schema types: WebPage, Serviceschema
- ✓<!DOCTYPE html> declaredtechnical
- ✓No mixed content — all resources use HTTPStechnical
- ✓font-display: swap detected — prevents invisible textperformance
- ✓Viewport includes width=device-width (responsive)meta
- ✓robots.txt found and allows crawlingtechnical
- ✓robots.txt includes Sitemap referencetechnical
- ✓No AI crawlers blocked in robots.txt — AI search and training can access contenttechnical
- ✓sitemap.xml found with valid formattechnical
- ✓Sitemap contains 17 URL(s)technical
- ✓All 5 checked internal links are workingcontent
- ✓0% nofollow links (0/6) — good link equity flowcontent
- ✓OG image uses absolute URL (correct)social
- ✓2 resource hint(s) (dns-prefetch/preconnect) — faster loadingperformance
- ✓All schema types have required propertiesschema
- ✓9 first-person pronouns — some experience showncontent
- ✓Title uses "|" separator — Google may rewrite it; consider using "—" insteadmeta
- ✓Referrer-Policy: strict-origin-when-cross-originsecurity
- ✓Permissions-Policy header presentsecurity
- ✓H1 length: 45 characters (optimal)content
- ✓Title and meta description are different (good)meta
- ✓OG URL matches canonical URL (consistent)social
- ✓Viewport allows zoom (good for accessibility)accessibility
- ✓11 links on page (within limit)content
- ✓DOM size: ~945 elements (good)performance
- ✓No snippet blocking detected (good — content is fully accessible)technical
- ✓Trailing slash consistent between URL and canonicaltechnical
- ✓No render-blocking scripts in head (good)performance
- ✓0 third-party script domain(s) (acceptable)performance
- ✓All 1 form input(s) have labels or aria-labelsaccessibility
- ✓No duplicate IDs found (31 unique IDs)accessibility
- ✓No iframes on pagesecurity
- ✓All 12 H2 sections have sufficient depth (avg 186 words)content
AEO — 65/100 (17 issues)
Failed Checks (17)
- ✗No definition lists (<dl>) — great for term/value pairsdiscoverability
- ✗No FAQ/Q&A section found — Q&A content helps AI extraction (FAQ schema markup is optional since Google retired FAQ rich results in May 2026)structure
- ✗No concise answer paragraphs detected — add short summaries after headingsstructure
- ✗Few key-value patterns — use "**Label:** value" format for AIstructure
- ✗No date information — AI prefers fresh, dated contentcitation
- ✗Only 2/5 E-E-A-T signals — add about, contact, author infocitation
- ✗No source citations — reference studies and data for authoritycitation
- ✗Few external links — cite authoritative sources for AI trustcitation
- ✗Only 0 concise answer paragraph(s) after headings — add 2+ short summaries (40-200 chars) right after H2/H3 tagscitation
- ✗No summary section — add Key Takeaways for AI extractionvoice
- ✗Few Q&A blocks — add question headings followed by answer paragraphsvoice
- ✗No Last-Modified header or dateModified — AI prefers content with freshness signalscitation
- ✗Content not updated in 90+ days — stale content loses AI visibilitycitation
- ✗No video content — multimedia increases AI engagement and citation ratediscoverability
- ✗Statistics lack source references — attribute data to boost AI trustcitation
- ✗No <details>/<summary> elements — use for expandable Q&A contentstructure
- ✗Brand name used inconsistently (30 partial vs 4 full) — standardizecitation
Passed Checks (29)
- ✓Structured data found — AI can understand your contentdiscoverability
- ✓2596 words in HTML — good content for AI parsingdiscoverability
- ✓Clean URL structurediscoverability
- ✓4 semantic HTML5 elements founddiscoverability
- ✓19 content sections — well-structured for AIdiscoverability
- ✓Description + OG description both present — clear topic signalsdiscoverability
- ✓68 named entities found — helps AI understand contextdiscoverability
- ✓6 internal links — good topic cluster signaldiscoverability
- ✓Question-style headings found — ideal for AI snippetsstructure
- ✓2 lists found — structured content for AIstructure
- ✓2 data table(s) foundstructure
- ✓Step-by-step content detected — AI loves procedural answersstructure
- ✓73% short sentences — easy for AI to extractstructure
- ✓100% concise paragraphs — scannable for AIstructure
- ✓Avg 186 words/section — sufficient depthstructure
- ✓Author information found — builds E-E-A-Tcitation
- ✓Statistics and data found in content — highly citablecitation
- ✓Organization schema found — AI can identify your brandcitation
- ✓Content references 2026/2025 — fresh contentcitation
- ✓Topic focus: 100% — title keywords found in contentcitation
- ✓38 conversational words — good for AI summariesvoice
- ✓First paragraph is snippet-ready (20-60 words)voice
- ✓Avg 17 words/sentence — easy reading levelvoice
- ✓Active voice dominant (12% passive) — AI-friendlyvoice
- ✓Pronoun density: 1% — engaging, user-focusedvoice
- ✓20 H2/H3 headings — good content structure for AIvoice
- ✓No AI-blocking robots directives — AI crawlers can access contentdiscoverability
- ✓AI search crawlers not blocked in robots.txt (8/8 allowed)discoverability
- ✓Table of Contents detected — helps AI navigate long contentstructure
GEO — 65/100 (22 issues)
Failed Checks (22)
- ✗Few question headings — add Q&A headings for AI Overviewoverview
- ✗Title and H1 don't align — confusing for AI topic matchingoverview
- ✗No step-by-step content — add numbered guides for AIoverview
- ✗24% optimal paragraphs — aim for 20-80 words per paragraphoverview
- ✗No author schema — add for AI trust signalsauthority
- ✗No source citations — reference studies and data for authorityauthority
- ✗No examples or case studies — add real-world examplesauthority
- ✗No links to authoritative sources — cite Google, Schema.org, etc.authority
- ✗Few external source domains — diversify your referencesauthority
- ✗No comparison content — add vs. sections for AI recommendationsformat
- ✗No summary section — add Key Takeaways or TL;DR for AIformat
- ✗No images — add visuals with descriptive ALT textformat
- ✗Only one list type — use both <ul> and <ol> for content varietyformat
- ✗Single-perspective content — add "on the other hand..." for balanceformat
- ✗No conclusion — add recommendations or a verdict sectionformat
- ✗4/14 semantic elements — add <article>, <figure>, <time>, etc.semantic
- ✗No <time> elements — wrap dates in <time datetime="...">semantic
- ✗Only 2 Schema type(s) — add more for AI contexttechnical
- ✗Only 0 data points — adding statistics measurably boosts generative-engine visibility (GEO study, arXiv:2311.09735)authority
- ✗Author lacks credentials — anonymous content is a GEO penaltyauthority
- ✗No authoritative sameAs links — add Wikipedia/Wikidata/LinkedIn URIs to schema for entity disambiguationauthority
- ✗Possible keyword stuffing: "quot" at 6.5% density (116×) — diversify vocabularyauthority
Passed Checks (35)
- ✓Definition-style content found — featured snippet candidateoverview
- ✓Content freshness signals detectedoverview
- ✓Comprehensive content (2596 words, 12 sections)overview
- ✓2-level heading hierarchy — deep content structureoverview
- ✓3/5 trust signals foundauthority
- ✓Brand identity consistent (OG + Schema)authority
- ✓Original research/data signals foundauthority
- ✓Expert quotes or testimonials found — authority signalauthority
- ✓4 industry terms used — domain expertise signalauthority
- ✓BreadcrumbList schema found — helps AI understand site structureformat
- ✓Data visualization elements found (tables/charts)format
- ✓5/6 formatting types used — rich contentformat
- ✓Actionable advice found — AI prefers practical contentformat
- ✓3 entity types in Schema — AI can classify contentsemantic
- ✓100% title keywords in first 200 words — good prominencesemantic
- ✓9 contextual links — good cross-referencingsemantic
- ✓Content categorization found — clear topic classificationsemantic
- ✓2 sections have subtopics (H3) — deep coveragesemantic
- ✓Mobile-friendly (viewport set)technical
- ✓HTTPS secure — trusted by AI systemstechnical
- ✓Page size: 122 KB — reasonabletechnical
- ✓Open Graph fully configured (title, description, image)technical
- ✓Canonical URL set — prevents AI from citing duplicatestechnical
- ✓Page allows AI indexing (no noindex/nosnippet)technical
- ✓Language + OG locale set — clear language signaltechnical
- ✓2 ARIA landmarks found — good accessibility for AItechnical
- ✓2596 words — sufficient depth for AI analysisoverview
- ✓First 200 words contain topic keywords — AI extracts primarily from the startoverview
- ✓Definition + list combo — strong featured snippet candidateoverview
- ✓No snippet restrictions — AI can freely extract content (good)technical
- ✓3/6 question types (5W1H) in headings — comprehensiveoverview
- ✓Link anchor texts are descriptive — good AI context signalsemantic
- ✓No hidden-text cloaking patterns detectedtrust
- ✓Healthy content-to-chrome ratio (~1% boilerplate)overview
- ✓All tested AI crawlers can access the page (GPTBot, ClaudeBot, PerplexityBot)authority
Fix These Issues Automatically
Using WordPress? Install SEO Autopilot for one-click auto-fixes on 65+ issues — with full undo support.
Get SEO Autopilot Plugin