Overview:
On 03/24/26 a21.org scored 26% — **Quite Weak** – Overall, the site is easy to access, but it’s not giving AI systems enough clear signals to confidently understand, trust, and summarize it.
Executive summary
Score Breakdown (High Level)
- Discoverability: 100% - The site's technical foundation is solid and accessible, but we didn't see any XML sitemaps to help search engines fully map out your content.
- Structured Data: 0% - Overall, this section is a complete miss since we didn't find any structured data on the homepage and didn't have a resource page to check for author details.
- AI Readiness: 33% - The site is properly open to AI crawlers and includes clear brand links, but the absence of an XML sitemap and Wikidata entity limits its overall readiness for generative search.
- Performance: 17% - Mobile load times and responsiveness are currently in the poor range, though the page layout remains very stable.
- Reputation: 0% - We couldn't confirm the brand's reputation or social signals because the data packet was missing structured consensus fields and the homepage uses relative links for social profiles.
- LLM-Ready Content: 32% - The page identifies a credible author and provides outbound links, but the content is too fragmentary and lacks the timestamps needed for optimal AI indexing.
The big picture on AI visibility
What stands out most is that the site is accessible, but it’s missing several of the signals that help AI systems confidently identify the brand and interpret what matters on key pages. The gaps read less like “errors” and more like missing clarity and verification points that AI relies on when it summarizes and recommends sources. Below, we’ll walk through the specific areas where the evaluation couldn’t find what it needed, organized by section so it’s easy to follow. None of this is unusual—once these fundamentals are clearer, the rest of the story tends to come through much more cleanly.
Detailed Report
Discoverability
❌ No XML sitemap found
What we saw
We didn’t find a standard XML sitemap for the site.
Why this matters for AI SEO
Without a clear map of your URLs, AI-powered crawlers and search systems can miss pages or take longer to understand what content exists and how it’s organized.
Next step
Publish a standard XML sitemap that lists your key indexable pages.
❌ No image or video sitemaps found
What we saw
We didn’t find an image sitemap or a video sitemap.
Why this matters for AI SEO
When rich media isn’t clearly surfaced, it’s harder for AI systems to fully interpret and reuse key visual/video context tied to your brand and pages.
Next step
Add an image sitemap and/or video sitemap if images or videos are a meaningful part of your content.
Structured Data
❌ No structured data found on the homepage
What we saw
We didn’t see any valid structured data markup on the homepage.
Why this matters for AI SEO
Structured data helps AI systems interpret key entities and page meaning more reliably, especially when they’re summarizing or validating information.
Next step
Add structured data to the homepage so the page can clearly communicate what it represents.
❌ Organization identity wasn’t defined in structured data
What we saw
Because no structured data was detected, we couldn’t find any organization-type markup that identifies the brand.
Why this matters for AI SEO
When a brand isn’t explicitly defined, generative engines have a harder time connecting your site to a consistent identity across the web.
Next step
Include organization-focused structured data that clearly identifies the brand.
❌ Resource/blog structured data couldn’t be evaluated
What we saw
A resource or blog page wasn’t provided, so we couldn’t confirm whether structured data is used on content pages.
Why this matters for AI SEO
Content pages are where AI systems often look for stronger signals about authorship, topical focus, and how to attribute information.
Next step
Provide (or audit) a representative resource/blog URL to confirm structured data coverage beyond the homepage.
❌ Structured data integrity couldn’t be confirmed
What we saw
Since no structured data exists on the site (in the page we reviewed), there was nothing to validate for quality or errors.
Why this matters for AI SEO
If structured data isn’t present and verifiable, AI systems lose a reliable layer of meaning and identity confirmation.
Next step
Implement structured data and validate it so it can be consistently interpreted.
❌ Author clarity couldn’t be verified on a resource/blog page
What we saw
Because a resource/blog page wasn’t provided, we couldn’t verify whether articles have a clear, non-generic author.
Why this matters for AI SEO
AI summaries tend to be more trustworthy when authorship is clear and attributable, especially for informational content.
Next step
Confirm that key content pages clearly identify the author.
❌ Author identity links couldn’t be verified
What we saw
No author structured data was detected, and the resource/blog page needed to verify identity links wasn’t provided.
Why this matters for AI SEO
When author identity can’t be connected to known profiles, it’s harder for AI systems to build confidence in who created the content.
Next step
Ensure author identity information is consistently present and can be connected to official profiles.
AI Readiness
❌ No XML sitemap available for AI-friendly discovery
What we saw
We didn’t find a standard XML sitemap for the site.
Why this matters for AI SEO
AI crawlers rely on clear site structure signals to find and prioritize content efficiently.
Next step
Make a standard XML sitemap available so automated systems can better understand the site’s structure.
❌ No page update data found in the sitemap
What we saw
We didn’t see update information (like last modified dates) in sitemap data.
Why this matters for AI SEO
Without update signals, AI systems have a harder time judging what’s current versus outdated when deciding what to surface or cite.
Next step
Include last modified information in your sitemap data so freshness is easier to interpret.
❌ No Wikidata entity connected to the brand
What we saw
We didn’t find a Wikidata entity associated with the brand.
Why this matters for AI SEO
A recognized entity makes it easier for generative engines to resolve your brand accurately and consistently across different sources.
Next step
Create or connect a Wikidata entity for the brand so identity is easier to verify.
Performance
❌ Homepage is slow to become responsive
What we saw
The homepage showed significant delays before it was fully responsive for users, especially on mobile.
Why this matters for AI SEO
When pages take a long time to become usable, crawlers and AI systems may capture less page content reliably, which can reduce how well the page is understood.
Next step
Reduce what delays interactivity on the homepage so the core content becomes usable faster.
❌ Main homepage content appears too late
What we saw
The primary content on the homepage took a long time to appear on mobile.
Why this matters for AI SEO
If the main content loads late, AI systems can struggle to quickly extract the page’s key topic and purpose.
Next step
Improve how quickly the main homepage content renders on mobile.
❌ Overall mobile performance is low
What we saw
The homepage scored poorly for mobile performance in the evaluation.
Why this matters for AI SEO
Slower experiences can limit how effectively content is processed and understood, especially when systems prioritize fast, accessible pages.
Next step
Address the factors causing slow mobile performance so the homepage experience is easier to process.
Reputation
❌ Negative client feedback status couldn’t be verified
What we saw
The data needed to confirm whether affirmed negative client assertions exist wasn’t available in the evaluation packet.
Why this matters for AI SEO
When reputation signals can’t be verified, AI systems have less dependable context for summarizing the brand’s standing.
Next step
Collect and provide the missing reputation fields so this can be confirmed.
❌ Negative employee feedback status couldn’t be verified
What we saw
The data needed to confirm whether affirmed negative employee assertions exist wasn’t available in the evaluation packet.
Why this matters for AI SEO
AI overviews often weigh employee sentiment and brand narratives, and missing confirmation data can weaken trust context.
Next step
Collect and provide the missing employee-negative fields so this can be confirmed.
❌ Brand recognition across models couldn’t be confirmed
What we saw
The data required to verify broader brand recognition wasn’t present in the evaluation packet.
Why this matters for AI SEO
If recognition signals aren’t available or consistent, it’s harder for generative engines to treat the brand as a known entity.
Next step
Gather and include the missing brand recognition fields for validation.
❌ Brand identity consistency couldn’t be validated
What we saw
The consensus/conflict identity fields needed to verify consistency (name, domain, address) were missing or unavailable.
Why this matters for AI SEO
When identity consistency can’t be confirmed, AI systems are more likely to hedge, confuse entities, or provide less confident summaries.
Next step
Provide the missing identity consensus fields so brand consistency can be evaluated.
❌ Wikidata match status wasn’t available
What we saw
We couldn’t confirm a matching Wikidata entity status for the brand based on the available data.
Why this matters for AI SEO
Wikidata is a common reference point for entity resolution, and missing match signals reduce deterministic brand identification.
Next step
Verify a matching Wikidata entity and ensure match status can be confirmed.
❌ Official identity anchors in Wikidata couldn’t be confirmed
What we saw
The fields needed to confirm official identity anchors (like official website and identifier counts) were missing from the available Wikidata data.
Why this matters for AI SEO
Official anchors help AI systems connect your brand to the right web properties and reduce confusion with similarly named entities.
Next step
Ensure Wikidata includes official identity anchors that can be validated.
❌ Third-party reviews/customer feedback couldn’t be confirmed
What we saw
The fields needed to confirm whether third-party reviews exist weren’t available in the evaluation packet.
Why this matters for AI SEO
Independent feedback is a common trust signal that helps AI systems summarize credibility and public sentiment.
Next step
Gather and include the missing reviews-related fields so this can be verified.
❌ Review sources couldn’t be validated
What we saw
We didn’t have the required data to confirm that review sources are concrete and countable.
Why this matters for AI SEO
When sources can’t be validated, AI systems are less likely to treat reputation claims as dependable.
Next step
Provide review source data so the quality and specificity of review signals can be confirmed.
❌ Social profile consensus couldn’t be confirmed
What we saw
The evaluation packet didn’t include the data needed to confirm consensus on major social profiles.
Why this matters for AI SEO
When official profiles aren’t clearly agreed upon, AI systems may hesitate to attribute brand content to the right channels.
Next step
Collect and include the missing social-consensus fields for verification.
❌ Homepage doesn’t clearly link to official social profiles
What we saw
We didn’t find homepage links pointing to major social domains; the existing social links appear to be relative paths (for example, “instagram”) instead of full external URLs.
Why this matters for AI SEO
If official profiles aren’t clearly linked, it’s harder for AI systems to treat them as verified offsite signals tied to the brand.
Next step
Update social links so they point directly to the official social profile URLs.
❌ Independent press/coverage couldn’t be confirmed
What we saw
The data needed to confirm independent press mentions wasn’t available in the evaluation packet.
Why this matters for AI SEO
Independent coverage is a strong corroboration signal that helps AI systems build confidence in brand legitimacy and relevance.
Next step
Gather and include the missing independent-press fields for validation.
❌ Onsite press/press releases couldn’t be confirmed
What we saw
The data needed to confirm owned press mentions wasn’t available in the evaluation packet.
Why this matters for AI SEO
When onsite press context isn’t clearly available, AI systems may have less first-party material to reference for brand milestones and announcements.
Next step
Gather and include the missing owned-press fields for validation.
LLM-Ready Content (Blog Analysis)
Heads up: this section looks at one article as a snapshot, so it’s a little more interpretive than the rest of the report and may shift slightly from run to run. Have questions? Just shoot us an email at hello@v9digital.com
❌ No clear publish or update date
What we saw
We didn’t find a specific publish date or update timestamp in the content or metadata for the page reviewed.
Why this matters for AI SEO
Without a clear timestamp, AI systems have a harder time judging whether the information is current, which can reduce confidence in summaries and citations.
Next step
Add a clear publish date (and update date when applicable) that’s visible and consistent.
❌ Freshness couldn’t be confirmed
What we saw
No modification date was detected, so there wasn’t a clear way to confirm recent updates.
Why this matters for AI SEO
When freshness isn’t obvious, AI systems may be less likely to prioritize or rely on the content for up-to-date answers.
Next step
Make update timing explicit so recency can be evaluated.
❌ Content sections are too thin for deep understanding
What we saw
The page content is broken into very short sections, with minimal explanatory text in each.
Why this matters for AI SEO
AI systems do best when each section has enough context to extract meaning, supporting details, and clear intent.
Next step
Expand key sections so each one contains enough descriptive text to stand on its own.
❌ No table-based structured information
What we saw
We didn’t find any table elements on the page.
Why this matters for AI SEO
Tables can provide clean, structured context that AI systems can interpret quickly (for example, comparisons, stats, or definitions).
Next step
Add a simple table where it naturally fits to present key facts in a structured format.
❌ Subheadings don’t clearly map to supporting content
What we saw
Subheadings weren’t followed by enough related explanatory text for the headings to function as useful signposts.
Why this matters for AI SEO
Clear heading-to-content alignment helps AI systems chunk topics correctly and produce more accurate summaries.
Next step
Ensure each subheading is followed by a meaningful block of text that directly supports it.
❌ Key answers aren’t stated early in sections
What we saw
The page doesn’t include substantial opening paragraphs that clearly explain the point of each section upfront.
Why this matters for AI SEO
When the “why this matters” and core explanation show up late (or not at all), AI systems have less to anchor on for concise, accurate summaries.
Next step
Add a short but substantive first paragraph under key sections that states the main takeaway clearly.
Does Anything Seem Off?
Thanks for taking our free GEO Grader for a spin. When we started this journey, the tool had a fairly long processing time to check everything we wanted both onsite and offsite, so we made a few adjustments on the backend to speed things up. As a result, there are times when the grader may not get everything 100% right. If something feels off, we recommend running the tool a second time to confirm the results. From there, you’re always welcome to reach out to us to schedule a GEO consultation, or to have your SEO provider validate the findings with a more detailed crawl and manual review.
