Full GEO Report for https://jrdlhq.com/test

Detailed Report:

GEO Assessment — jrdlhq.com/test

(Score: 11%) — 06/21/26


Overview:

On 06/21/26 jrdlhq.com/test scored 11% — **Poor** – Overall, the site comes across as difficult for AI systems to find and confidently understand right now, with key signals missing or not visible.

Executive summary

Most of the issues showed up in basic discovery and content visibility, where the site and pages couldn’t be accessed and core page information wasn’t available to review. On top of that, gaps in structured data, performance verification, and offsite trust signals show the limitations are spread across multiple areas rather than isolated to one section.

Score Breakdown (High Level)

  • Discoverability: 25% - The site is currently unreachable due to a DNS error, which prevents search engines from accessing the homepage or finding any sitemaps.
  • Structured Data: 0% - We weren't able to find any schema markup or author data because the site's pages were inaccessible during the evaluation.
  • AI Readiness: 17% - We didn't see an XML sitemap or a Wikidata entry, though AI crawlers aren't being explicitly blocked from the site.
  • Performance: 0% - We weren't able to find any mobile performance data for the homepage, which makes it impossible to verify if the site meets basic speed and stability standards.
  • Reputation: 23% - We weren't able to find any significant offsite signals like social profiles, reviews, or press coverage to establish brand authority.
  • LLM-Ready Content: 0% - We couldn't access the content for this resource, so we weren't able to confirm the structural and trust signals needed for AI optimization.

Where things stand overall right now

The big picture is that many of the signals AI systems rely on to discover and understand a site weren’t available to review because key pages couldn’t be reached. In a couple of places, that turns into a visibility problem—there’s simply not enough clear, readable information for systems to confidently interpret what the brand is and what the content covers. Below, we’ll walk through the specific areas where that lack of access and supporting signals showed up across discovery, content, and reputation. None of this is unusual for an early or recently changed web presence, and the detail will make it clear what’s getting in the way.

Detailed Report

Discoverability

❌ Homepage isn’t reachable

What we saw

The site couldn’t be reached due to a DNS resolution error, so the homepage didn’t load during the evaluation. That prevented us from confirming what search and AI crawlers would normally be able to read on the page.

Why this matters for AI SEO

If the site can’t be accessed reliably, AI systems and search engines can’t discover, interpret, or cite it. It also blocks other visibility signals that depend on the homepage being readable.

Next step

Restore normal site access so the domain reliably loads and returns a valid homepage.

❌ Noindex status couldn’t be confirmed

What we saw

Because the homepage HTML wasn’t available, we couldn’t verify whether the page includes any “do not index” directive. In practice, this means a key indexing signal is unknown.

Why this matters for AI SEO

When indexing signals can’t be confirmed, it becomes harder to trust that the homepage is eligible to appear in search and AI-driven results. That uncertainty can limit discovery and reuse.

Next step

Once the homepage is accessible, confirm it’s clearly eligible to be indexed.

❌ Core page metadata wasn’t detected

What we saw

The homepage HTML was missing, so we didn’t detect a page title or description. As a result, the page’s basic summary information wasn’t available.

Why this matters for AI SEO

AI systems lean on clear page summaries to understand what a brand and page are about. When that information isn’t visible, the site is easier to overlook or misinterpret.

Next step

Make sure the homepage includes a clear title and description that describe the page accurately.

❌ Homepage title is missing

What we saw

We didn’t find a title for the homepage, because the HTML wasn’t available to read. That leaves the primary “label” for the page undefined.

Why this matters for AI SEO

A strong homepage title helps AI and search engines quickly categorize the site and match it to relevant prompts and queries. Without it, the page has less context and weaker recall.

Next step

Add a specific, descriptive homepage title that reflects the brand and what it offers.

❌ XML sitemap wasn’t found

What we saw

A standard XML sitemap wasn’t detected. That means we didn’t see a clear, centralized list of pages for crawlers to follow.

Why this matters for AI SEO

AI and search crawlers use site structure signals to find and prioritize pages. Without a clear map of what exists, key pages are more likely to be missed or discovered late.

Next step

Publish an XML sitemap that lists the key pages you want discoverable.

❌ Image/video sitemap wasn’t found

What we saw

We didn’t detect an image or video sitemap. If the site relies on media to communicate value, those assets may not be as easy to enumerate.

Why this matters for AI SEO

Generative systems increasingly pull from mixed media sources, but they still need reliable discovery paths. When media isn’t well surfaced, it’s less likely to be understood and reused.

Next step

If media is important to the site, add a media sitemap that helps crawlers find those assets.

Structured Data

❌ Structured data wasn’t detected on the homepage

What we saw

We couldn’t find structured data on the homepage because the page content was missing or couldn’t be reached. That prevented any validation of what’s present.

Why this matters for AI SEO

Structured data helps AI systems interpret the site’s identity and key page meaning quickly and consistently. When it isn’t present or readable, that clarity is reduced.

Next step

Once the homepage is accessible, add structured data that clearly describes the site and brand.

❌ Organization-type structured data wasn’t found

What we saw

No organization-related structured data type was found on the homepage. This leaves the brand’s official identity less explicit.

Why this matters for AI SEO

AI engines rely on consistent identity signals to avoid confusion between similarly named brands. If the brand isn’t clearly defined, attribution and trust are harder to establish.

Next step

Add organization-focused structured data that reflects the official brand identity.

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

What we saw

The resource page (resource.html.html) was missing or empty, so we couldn’t detect any page-level structured data there. That includes details that would typically support article understanding.

Why this matters for AI SEO

Content pages need clear context for AI systems to summarize and cite them responsibly. Without readable structure signals, the content is less likely to be confidently used.

Next step

Ensure the resource/blog page loads and includes structured data appropriate to the content.

❌ Structured data quality couldn’t be evaluated

What we saw

Because no structured data was found, we couldn’t evaluate whether it contains errors or inconsistencies. The evaluation hit a dead end at detection.

Why this matters for AI SEO

AI systems do better with clean, consistent signals they can trust at scale. If structured data isn’t present, you lose a major clarity layer that supports reliable interpretation.

Next step

Add structured data first, then validate it to ensure it’s consistent and usable.

❌ Resource/blog author identity wasn’t detected

What we saw

We couldn’t verify a clear, non-generic author on the resource/blog page because the page was missing or empty. That means author attribution wasn’t available.

Why this matters for AI SEO

Clear authorship is a trust signal for AI-generated summaries and citations. When author identity isn’t visible, content can feel less credible and harder to reference.

Next step

Make sure the resource/blog content includes a clear author name that’s easy to identify.

❌ Author identity links weren’t detected

What we saw

We couldn’t confirm author identity links (like “sameAs” references) because the resource/blog page HTML wasn’t available. As a result, author verification signals weren’t present.

Why this matters for AI SEO

When an author can be tied to consistent public profiles, AI systems have an easier time trusting and attributing content. Without those anchors, author confidence can be lower.

Next step

Add clear author identity references that connect the author to consistent public profiles.

AI Readiness

❌ XML sitemap wasn’t detected

What we saw

No standard XML sitemap was detected at expected locations. This limits how clearly the site’s page set can be understood.

Why this matters for AI SEO

AI discovery improves when systems can quickly map what exists and what’s most important. Without a clear map, coverage is less reliable.

Next step

Publish an XML sitemap that represents the site’s key pages.

❌ Sitemap freshness signals weren’t found

What we saw

Because a sitemap wasn’t found, we didn’t see any “last modified” timestamps in it. That means update signals weren’t available in this pathway.

Why this matters for AI SEO

Freshness and recency cues help AI systems prioritize what to read and what to surface. If update timing isn’t visible, newer or maintained pages can be harder to recognize.

Next step

Include update timestamps in the sitemap so recency is easier to interpret.

❌ About/brand context page couldn’t be detected

What we saw

We couldn’t detect a link to an about or brand context page because the homepage HTML was unavailable or empty. That made it impossible to confirm where your brand story is clearly explained.

Why this matters for AI SEO

AI systems look for clear “who we are” and “what we do” context to avoid misrepresenting a brand. If that context isn’t easy to find, the brand is harder to summarize accurately.

Next step

Ensure there’s a clearly accessible page that explains the brand and is easy to discover from the main site.

❌ No Wikidata entity was found for the brand

What we saw

We didn’t find a Wikidata item ID associated with the brand. That means there isn’t a central entity record we could confirm.

Why this matters for AI SEO

Generative systems often lean on knowledge graphs to verify identity and relationships. Without a recognized entity record, it’s harder for AI to confidently “place” the brand.

Next step

Establish a clear brand entity record in places AI systems commonly reference.

Performance

❌ Homepage responsiveness data wasn’t available

What we saw

We couldn’t retrieve homepage responsiveness data because the metric was missing or null. In short, we weren’t able to validate how the page behaves in this area.

Why this matters for AI SEO

If performance can’t be verified, it creates uncertainty about whether users (and crawlers) can reliably access and consume the content. That uncertainty can limit how confidently content is surfaced.

Next step

Make the homepage reliably accessible and then re-check that it behaves smoothly for users.

❌ Homepage loading experience couldn’t be validated (LCP)

What we saw

We couldn’t pull the homepage loading metric because it was missing or null. That left a gap in confirming the page’s loading experience.

Why this matters for AI SEO

When loading behavior isn’t measurable, it’s harder to confirm the site delivers a stable experience that supports engagement. AI systems tend to prefer sources that appear reliable and usable.

Next step

Restore full homepage access and re-check that loading behavior can be measured.

❌ Homepage layout stability couldn’t be validated (CLS)

What we saw

We couldn’t retrieve the homepage layout stability metric because it was missing or null. That means we couldn’t confirm whether the layout stays steady while loading.

Why this matters for AI SEO

A stable experience helps users actually consume and trust the page content. If stability can’t be validated, it weakens confidence in the page as a dependable destination.

Next step

Make sure the homepage loads consistently so layout stability can be evaluated.

❌ Overall homepage performance score couldn’t be retrieved

What we saw

The overall performance score for the homepage was missing or null. We weren’t able to confirm a baseline view of the page’s performance profile.

Why this matters for AI SEO

When a site’s usability signals aren’t available, it can reduce confidence that the page is a strong reference to send users to. That can indirectly limit visibility in AI-driven results.

Next step

Restore normal site access so performance can be measured consistently.

Reputation

❌ Brand wasn’t recognized by major LLMs

What we saw

The brand was not recognized by any of the LLMs referenced in the report details (GPT-4, Gemini, Grok, Claude). In practice, that suggests very limited baseline awareness.

Why this matters for AI SEO

If AI systems don’t recognize a brand, they’re less likely to surface it as a confident recommendation. Recognition also affects how easily AI can connect brand mentions across the web.

Next step

Strengthen consistent, public brand references so AI systems have more to corroborate.

❌ Brand identity wasn’t consistent across sources

What we saw

The report notes missing consensus on the official brand name and physical address, with only the domain identified. That makes the brand’s “official” identity harder to pin down.

Why this matters for AI SEO

Generative engines work best when they can match a brand to a consistent identity record. Inconsistency (or missing details) increases the chance of confusion or omission.

Next step

Make sure the brand’s official name and core identity details are consistent wherever they appear publicly.

❌ No matching Wikidata entity was found

What we saw

No matching entity was found in Wikidata for the brand. That means there wasn’t an entity hub we could confirm.

Why this matters for AI SEO

Knowledge graph sources help AI verify “this is a real, distinct entity.” Without that, AI may have less confidence connecting the brand to accurate facts.

Next step

Create and align an entity record that clearly represents the brand.

❌ No official identity anchors were found in Wikidata

What we saw

Because no Wikidata record exists, there were no official anchors available there to corroborate identity. This removes a common verification pathway.

Why this matters for AI SEO

AI systems prefer brands that can be verified through consistent, third-party identity references. Missing anchors can reduce authority signals and increase ambiguity.

Next step

Ensure the brand has clear, verifiable identity anchors in recognized public sources.

❌ No third-party reviews or customer feedback were identified

What we saw

No customer reviews or third-party feedback were identified in the offsite signals reviewed. That leaves the brand with minimal external validation.

Why this matters for AI SEO

Independent feedback helps AI systems gauge legitimacy and satisfaction signals. Without it, the brand can look less established or harder to trust.

Next step

Build a track record of third-party feedback on credible platforms.

❌ No concrete review sources were detected

What we saw

The report indicates zero concrete review sources were detected. This reinforces that reviews weren’t just sparse—they weren’t found at all.

Why this matters for AI SEO

When sources can’t be named or corroborated, AI has less to cite or rely on when summarizing reputation. That can reduce visibility in recommendation-style results.

Next step

Establish reviews on recognizable platforms that are easy to verify.

❌ No consensus on official social profiles

What we saw

No major social media profiles were identified or agreed upon in the report’s offsite findings. That suggests official profiles aren’t clearly discoverable.

Why this matters for AI SEO

Official social profiles act as identity proof points and help AI connect the dots between a brand and its public presence. Without them, entity confidence is weaker.

Next step

Make sure official social profiles are clearly established and consistently attributed to the brand.

❌ Social profile links couldn’t be confirmed on the homepage

What we saw

The homepage HTML couldn’t be resolved or was empty, so we couldn’t detect links to major social profiles. That removed an easy on-site confirmation signal.

Why this matters for AI SEO

When the site directly points to official profiles, it helps AI systems verify which accounts are real and relevant. If those links aren’t visible, verification is harder.

Next step

Once the homepage loads properly, make sure it clearly links to the brand’s official social profiles.

❌ No independent press or coverage was found

What we saw

No independent press mentions or external coverage were identified. That suggests the brand hasn’t built much third-party visibility yet.

Why this matters for AI SEO

Independent coverage can act as corroboration that a brand is real, active, and relevant. Without it, AI has fewer trusted references to pull from.

Next step

Develop a base of credible third-party mentions that clearly reference the brand.

❌ No owned press or press releases were identified

What we saw

No owned press releases or onsite news mentions were identified in the report’s offsite/brand footprint review. That limits the brand’s ability to present verified updates in its own voice.

Why this matters for AI SEO

When a brand publishes clear announcements and updates, it gives AI systems more authoritative material to reference. Without it, the narrative footprint is thinner.

Next step

Create a clear, discoverable place where brand updates and announcements are published.

LLM-Ready Content

❌ Author name wasn’t present

What we saw

We couldn’t verify a non-generic author on the content page because the HTML was missing due to net::ERR_NAME_NOT_RESOLVED. As a result, authorship wasn’t visible.

Why this matters for AI SEO

AI systems tend to trust content more when it has clear attribution to a real person or team. Missing authorship makes it harder to evaluate credibility.

Next step

Ensure the page is accessible and includes a clear, non-generic author name.

❌ Publish or update date wasn’t present

What we saw

We couldn’t find a publish or updated date because the page HTML wasn’t accessible. This removed a key recency signal from the content.

Why this matters for AI SEO

Dates help AI systems understand whether information is current and appropriate to cite. Without them, content can be treated as less reliable or harder to place in time.

Next step

Make the page accessible and display a clear publish date or “last updated” date.

❌ Recent update status couldn’t be verified

What we saw

Because no date information was available, we couldn’t verify whether the page was updated within the last 12 months. That means recency couldn’t be confirmed.

Why this matters for AI SEO

When AI systems can’t tell whether content is maintained, they may be less likely to recommend it for time-sensitive topics. Clear update signals reduce that uncertainty.

Next step

Add and maintain visible update information so recency can be verified.

❌ No non-social outbound link was detected

What we saw

We couldn’t verify any outbound link to a non-social source because the page HTML wasn’t accessible. That left the content without confirmable external references.

Why this matters for AI SEO

External citations can help AI systems understand what claims are grounded in real sources. Without visible references, content can look less supported.

Next step

Include at least one relevant, non-social external reference link within the content.

❌ Content section structure couldn’t be verified

What we saw

We couldn’t confirm whether the content was chunked into readable sections because the HTML was missing. That made it impossible to review how scannable the page is.

Why this matters for AI SEO

Clear structure helps AI systems extract, summarize, and quote the right parts of a page. If structure isn’t visible, comprehension and reuse get harder.

Next step

Ensure the page loads and is organized into clearly separated sections.

❌ No HTML table was found

What we saw

We didn’t detect an HTML table, but the bigger issue is that the content HTML wasn’t available to evaluate. So this structural element couldn’t be confirmed.

Why this matters for AI SEO

Tables can make key comparisons and definitions easier for AI to interpret and reuse. When content structure isn’t accessible, those extraction benefits are lost.

Next step

Where it fits the topic, add a simple table that summarizes key information.

❌ Descriptive subheadings weren’t verified

What we saw

We couldn’t confirm the presence of descriptive subheadings because the HTML wasn’t accessible. That left the page’s outline unclear.

Why this matters for AI SEO

Subheadings help AI systems understand what each section covers and pull the right snippet for a given question. Without them, the page is harder to parse.

Next step

Add clear, descriptive subheadings that match the questions the content is answering.

❌ Key answers weren’t found near the top

What we saw

We couldn’t verify whether the page puts key answers early because the HTML was missing. The content’s “time to value” couldn’t be evaluated.

Why this matters for AI SEO

AI systems often prefer content that gets to the point quickly and supports direct answers. If answers are buried—or can’t be confirmed—visibility can suffer.

Next step

Make sure the page opens with a clear, direct answer or summary before going deeper.

❌ Readability and cohesion couldn’t be evaluated

What we saw

Because the page HTML couldn’t be accessed, we weren’t able to assess whether the writing is cohesive and easy to follow. This was effectively blocked by missing content access.

Why this matters for AI SEO

AI summaries tend to be better when the underlying content is clearly written and well organized. If readability can’t be confirmed, it adds uncertainty to how well the page will perform as a source.

Next step

Ensure the content is accessible and written in a clear, scannable, consistently structured way.

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.

Share This Report With Your Team

Enter email addresses to send this assessment report to colleagues