Detailed Report:

Discoverability

❌ Homepage couldn’t be reached

What we saw

During the check, the domain didn’t resolve and the homepage couldn’t be loaded (ERR_NAME_NOT_RESOLVED). That meant we couldn’t confirm what the homepage returns in a normal crawl.

Why this matters for AI SEO

If the site can’t be reached, generative engines can’t reliably find, read, or reference your content. It also prevents other basic site signals from being discovered.

Next step

Confirm the domain is resolving correctly and that the homepage is consistently accessible.

❌ Indexability couldn’t be verified

What we saw

Because the homepage HTML wasn’t available, we couldn’t verify whether any “do not index” directive is present. This was treated as a failure to confirm indexability.

Why this matters for AI SEO

AI-driven discovery depends on being able to access and include your pages in their understanding of the web. When indexability can’t be confirmed, visibility and retrieval become less reliable.

Next step

Make sure the homepage can be retrieved so indexability signals can be clearly confirmed.

❌ Core page metadata wasn’t found

What we saw

We couldn’t find basic page metadata like a title or description because the homepage didn’t load. As a result, there wasn’t clear page-level context available to review.

Why this matters for AI SEO

Generative engines lean on clear page context to understand what a brand is and what a page is about. When that context isn’t accessible, summarization and matching can be weaker.

Next step

Ensure the homepage renders consistently so its primary page context can be read.

❌ Homepage title couldn’t be evaluated

What we saw

No homepage title tag was detected, because the page content wasn’t available. That also meant we couldn’t confirm whether the title is specific versus generic.

Why this matters for AI SEO

Titles are one of the clearest “labels” for what a page represents. If they’re missing or unreadable, it’s harder for AI systems to confidently categorize and reference the page.

Next step

Make the homepage HTML accessible so the title can be detected and evaluated.

❌ XML sitemap wasn’t found

What we saw

A standard XML sitemap wasn’t found at expected locations. From the check results, there wasn’t a clear “map” of pages available.

Why this matters for AI SEO

Sitemaps help automated systems discover important URLs efficiently and understand site coverage. Without one, discovery can be slower and less complete.

Next step

Publish a standard XML sitemap in a location crawlers can reliably find.

❌ Image or video sitemap wasn’t found

What we saw

Neither an image sitemap nor a video sitemap was detected. Any media-focused content wouldn’t have an obvious discovery path via a dedicated media roadmap.

Why this matters for AI SEO

Generative experiences often pull in images and video summaries when they can understand and source them confidently. Missing media discovery signals can reduce how often that content is surfaced.

Next step

Add a media sitemap if images or videos are an important part of how your content is discovered.

Structured Data

❌ Structured data couldn’t be detected on the homepage

What we saw

The homepage HTML couldn’t be retrieved due to a network error, so we weren’t able to confirm whether any structured data is present. This left the homepage without verifiable machine-readable context in the review.

Why this matters for AI SEO

Structured data helps AI systems interpret key facts more consistently (like what the business is). When it can’t be found or confirmed, understanding and confidence can drop.

Next step

Make the homepage accessible so any structured data present can be detected and validated.

❌ Organization-level structured data couldn’t be verified

What we saw

Because the homepage content was unavailable, we couldn’t verify organization-type structured data on the homepage. That means brand identity details weren’t confirmable through this signal.

Why this matters for AI SEO

AI systems look for consistent identity anchors to reduce ambiguity about who a brand is. If those anchors can’t be verified, identity and trust can be harder to establish.

Next step

Ensure the homepage can be loaded so organization-level identity signals can be confirmed.

❌ Structured data couldn’t be detected on a resource/blog page

What we saw

The resource/blog page HTML couldn’t be retrieved due to a network error, so we couldn’t confirm whether any structured data is present there. This limited what could be verified about content context.

Why this matters for AI SEO

For content pages, structured data can reinforce what the page is, who wrote it, and how it should be interpreted. If it’s missing or unreadable, AI summaries may be less accurate.

Next step

Make the resource/blog page accessible so its content signals can be detected.

❌ Major structured data errors couldn’t be evaluated

What we saw

No structured data was detected to evaluate for errors. Without detectable markup, there wasn’t anything to validate.

Why this matters for AI SEO

If AI systems can’t reliably parse structured information, they fall back to guesswork from page text and third-party sources. That can reduce consistency in how your brand is described.

Next step

Ensure structured data is detectable on key pages so it can be evaluated for quality.

❌ Clear author details couldn’t be verified on content

What we saw

We couldn’t confirm a clear, non-generic author on the resource/blog page because the page HTML wasn’t retrievable. Author information wasn’t available to review.

Why this matters for AI SEO

Author clarity can influence how trustworthy and reusable a piece of content feels in generative results. If authorship isn’t visible or verifiable, content credibility can be harder to establish.

Next step

Ensure the content page is accessible so authorship details can be found and confirmed.

❌ Author identity links couldn’t be verified

What we saw

We couldn’t verify whether the author includes “sameAs” identity links because the resource/blog page HTML was missing. That left the author identity less confirmable.

Why this matters for AI SEO

When author identity isn’t clearly anchored, AI systems may have a harder time connecting content to a real, consistent entity. That can reduce trust and proper attribution.

Next step

Make the content page retrievable so author identity signals can be evaluated.

AI Readiness

❌ XML sitemap wasn’t detected for AI discovery

What we saw

An XML sitemap wasn’t found in the check. That left no confirmed crawl “starting point” for automated systems trying to enumerate site pages.

Why this matters for AI SEO

Generative engines depend on predictable discovery paths to find content efficiently. Without a reliable sitemap, important pages can be missed or de-prioritized.

Next step

Provide a discoverable XML sitemap so automated systems can find your key URLs more consistently.

❌ Page update signals weren’t available

What we saw

Because a sitemap wasn’t detected, last-updated (lastmod) information couldn’t be confirmed. There wasn’t a clear signal showing when pages were refreshed.

Why this matters for AI SEO

Freshness cues help AI systems prioritize what to read and what to trust as current. When update signals aren’t present, content may be treated as less timely.

Next step

Make sure update timing information is available in the signals AI systems use to assess recency.

❌ Brand context page couldn’t be confirmed

What we saw

We couldn’t verify whether the site links to an About or brand context page because the homepage HTML was unavailable. That left “who you are” context harder to confirm.

Why this matters for AI SEO

Generative systems look for clear, consistent brand context to reduce ambiguity. When that context can’t be found, brand descriptions may be incomplete or inconsistent.

Next step

Ensure brand context information is accessible and easy to confirm from the main site experience.

❌ No Wikidata entity was found for the brand

What we saw

The check didn’t find a Wikidata entity associated with the brand. As a result, there wasn’t a confirmed public knowledge anchor available.

Why this matters for AI SEO

Knowledge bases can act as stable reference points for AI models trying to confirm identity details. When that’s missing, models may rely more heavily on inconsistent third-party mentions.

Next step

Establish a verifiable public identity footprint that AI systems can consistently reference.

Performance

❌ Homepage responsiveness data wasn’t available

What we saw

We weren’t able to collect homepage responsiveness data during the run. The field was missing or unavailable.

Why this matters for AI SEO

When a site can’t be reliably measured for basic usability and loading behavior, it’s harder to confirm whether real users (and automated systems) can access content smoothly. That uncertainty can hold back consistent discovery and engagement.

Next step

Confirm the homepage is reachable in a way that allows performance data to be collected.

❌ Homepage load experience couldn’t be evaluated

What we saw

Key homepage load and stability measurements weren’t returned, so we couldn’t evaluate basic loading behavior. The results were unavailable for review.

Why this matters for AI SEO

If automated systems can’t reliably access and evaluate page experience, they may treat the page as less dependable to retrieve and use. That can reduce how confidently content is pulled into generative answers.

Next step

Make sure the homepage can be measured consistently so page experience can be evaluated.

❌ Overall homepage performance result wasn’t available

What we saw

The performance analysis didn’t complete for the provided homepage URL, leaving the overall performance result missing. This created a full bottleneck for the performance section.

Why this matters for AI SEO

When evaluation systems can’t complete a basic read of the page, it often lines up with broader accessibility and reliability problems. Those issues can limit how consistently AI systems can retrieve your content.

Next step

Resolve the access issues preventing a complete homepage performance read.

Reputation

❌ Negative client feedback surfaced

What we saw

The research indicated affirmed negative client feedback was present. This showed up as a clear negative signal in the reputation review.

Why this matters for AI SEO

Generative engines weigh trust heavily when deciding what brands to reference. Negative reputation signals can reduce confidence and make the brand less likely to be recommended or cited.

Next step

Document and review the specific negative claims showing up in brand-facing search and AI summaries.

❌ Limited brand recognition across models

What we saw

The brand was recognized by only one model, without broader consensus. That suggests the brand isn’t consistently “known” in the places AI systems commonly pull from.

Why this matters for AI SEO

When recognition is limited, AI answers can be sparse, inconsistent, or overly dependent on a small set of sources. That makes brand visibility less predictable.

Next step

Validate where and how the brand is currently being referenced across the broader web.

❌ Inconsistent brand identity details

What we saw

There was no consensus on the brand’s official name, domain, and physical address. This indicates identity information isn’t being presented consistently across sources.

Why this matters for AI SEO

Identity inconsistency makes it harder for AI systems to confidently connect mentions back to the right entity. That can lead to confusion, mixed descriptions, or missing citations.

Next step

Audit the brand’s public identity details to see where they differ across sources.

❌ No Wikidata entity was found

What we saw

No Wikidata entry was identified for the brand. As a result, there wasn’t a centralized identity record available through that channel.

Why this matters for AI SEO

Wikidata can act as a reliable identity anchor for AI systems. Without it, models often rely more on scattered mentions that may be incomplete or inconsistent.

Next step

Assess whether a Wikidata presence is appropriate for the brand and how identity information is represented elsewhere.

❌ No identity anchors in Wikidata

What we saw

Because there was no Wikidata entity, there were also no Wikidata identity anchors like an official website or identifiers. Those standard reference points weren’t available.

Why this matters for AI SEO

Identity anchors help AI systems connect the dots between a brand and its verified properties. Without them, it’s harder to build consistent trust and attribution.

Next step

Make sure there are consistent, verifiable identity anchors available across trusted public sources.

❌ Third-party reviews couldn’t be confirmed

What we saw

A majority of model responses couldn’t confirm that third-party reviews exist for the brand. Review presence wasn’t clearly established.

Why this matters for AI SEO

Third-party validation is a common trust shortcut in generative answers. If reviews aren’t visible or confirmable, AI systems may be more cautious about describing the brand positively.

Next step

Identify whether credible third-party review coverage exists and where it’s published.

❌ Review sources weren’t concrete

What we saw

There was no consensus on concrete, verifiable review sources. Even when reviews were discussed, sources weren’t consistently identifiable.

Why this matters for AI SEO

AI systems tend to trust claims more when they can tie them to a specific, reputable source. Without clear sources, review-based trust signals don’t land as strongly.

Next step

Compile a short list of the most credible review sources associated with the brand.

❌ No consensus on official social profiles

What we saw

The review didn’t find consensus on major social media profiles for the brand. Social identity signals weren’t consistent.

Why this matters for AI SEO

Consistent social profiles can reinforce that a brand is real and active, and they often serve as entity confirmation points. If profiles aren’t clear, AI systems may have less confidence in the brand footprint.

Next step

Verify which social profiles are officially owned and consistently referenced across the web.

❌ Homepage couldn’t confirm links to social profiles

What we saw

Because the homepage was unreachable, we couldn’t confirm whether it links out to official social profiles. The supporting on-site confirmation wasn’t available.

Why this matters for AI SEO

When on-site sources reinforce official profiles, it’s easier for AI systems to connect brand mentions to the right accounts. Without that confirmation, identity confidence can be weaker.

Next step

Ensure the homepage is accessible so on-site identity references can be verified.

❌ Independent press coverage wasn’t found

What we saw

No independent press mentions were identified. The brand didn’t appear to have a visible footprint in third-party publications.

Why this matters for AI SEO

Independent coverage can serve as strong third-party validation and context for AI answers. Without it, AI systems may have less to work with when assessing authority and legitimacy.

Next step

Review whether any independent coverage exists and how discoverable it is.

❌ Owned press coverage wasn’t found

What we saw

No owned press releases or owned press mentions were identified. There wasn’t a clear self-published press trail to reference.

Why this matters for AI SEO

Owned announcements can help AI systems understand milestones, positioning, and official messaging. When that trail is missing, brand context can be thinner and less current.

Next step

Confirm whether the brand has an official announcements or press area that can be consistently found.

LLM-Ready Content

❌ Content page couldn’t be retrieved for review

What we saw

The content/resource page HTML was missing and returned ERR_NAME_NOT_RESOLVED during the check. That prevented any page-level content assessment.

Why this matters for AI SEO

If AI systems can’t fetch the content, they can’t extract key points, understand intent, or reuse the page in answers. It’s a hard stop for visibility.

Next step

Make sure the resource/blog URL is accessible and returns full HTML reliably.

❌ Author information wasn’t available

What we saw

We couldn’t confirm a non-generic author because the page HTML wasn’t retrievable. Authorship details weren’t visible to evaluate.

Why this matters for AI SEO

Clear authorship helps content feel grounded and attributable, which supports trust in generative summaries. Missing authorship makes it harder for AI to gauge credibility.

Next step

Ensure the content page exposes clear author information that can be read by crawlers.

❌ Publish/update date wasn’t available

What we saw

We couldn’t find a publish or update date because the page HTML couldn’t be retrieved. Date context wasn’t available.

Why this matters for AI SEO

Dates help AI systems judge timeliness and decide whether to surface or cite content. Without them, content can be treated as less trustworthy or harder to place in context.

Next step

Make sure publish/update date information is present and accessible on the content page.

❌ Recency couldn’t be confirmed

What we saw

“Updated within the last 12 months” couldn’t be confirmed because the page HTML wasn’t available. Recency signals couldn’t be checked.

Why this matters for AI SEO

AI systems often prefer current, maintained sources for answers. If recency can’t be established, the content may be less likely to be used.

Next step

Expose clear update timing signals on the page so recency can be verified.

❌ External supporting links couldn’t be verified

What we saw

We couldn’t confirm the presence of any non-social outbound link because the page HTML wasn’t retrievable. Supporting references weren’t visible.

Why this matters for AI SEO

Outbound references can strengthen credibility by showing where claims come from. Without verifiable references, AI systems may treat content as less supported.

Next step

Ensure the page includes accessible external references where they support key claims.

❌ Readable structure couldn’t be evaluated

What we saw

We couldn’t evaluate whether the content is broken into readable sections because the page HTML was missing. Content organization signals weren’t available.

Why this matters for AI SEO

Well-structured content is easier for AI to scan, extract, and summarize accurately. When structure can’t be seen, content reuse becomes less reliable.

Next step

Make sure the page content is accessible and clearly organized into scannable sections.

❌ Descriptive subheadings couldn’t be verified

What we saw

Descriptive subheadings couldn’t be checked because the page HTML wasn’t retrievable. We couldn’t confirm whether headings provide clear context.

Why this matters for AI SEO

Subheadings help AI understand topic shifts and pull the right snippet for the right question. Without them, summarization can be less precise.

Next step

Ensure headings and subheadings are present and readable on the page.

❌ Key answers appearing early couldn’t be evaluated

What we saw

We couldn’t verify whether key answers appear early in the content because the page HTML wasn’t available. The content layout and lead-in weren’t assessable.

Why this matters for AI SEO

AI systems often prioritize content that gets to the point and makes the main takeaway easy to extract. If that pattern can’t be confirmed, content is less likely to be reused cleanly.

Next step

Make the full content accessible so it can be evaluated for answer-first clarity.

❌ Readability and cohesion couldn’t be assessed

What we saw

Readability and cohesion couldn’t be reviewed because the content page HTML wasn’t retrievable. There wasn’t enough accessible text to evaluate.

Why this matters for AI SEO

Clear writing helps AI produce accurate summaries and reduces the risk of misinterpretation. When content can’t be read, it can’t be confidently used.

Next step

Ensure the page is reachable and renders the full written content for crawlers and users.

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.