Detailed Report:

GEO Assessment — rocketcityhomes.com

(Score: 51%) — 07/12/26


Overview:

On 07/12/26 rocketcityhomes.com scored 51% — **Fair** – Overall, the site has a solid base, but a few visibility and clarity gaps are holding it back in key areas.

Website Screenshot

Executive summary

Across the results, most of the issues showed up around AI access/verification signals, page experience, and how the resource content is structured for reuse, with a few discoverability gaps as well. The misses are spread across multiple areas rather than being isolated to one category, so the overall picture is mixed.

Score Breakdown (High Level)

  • Discoverability: 92% - The site is mostly in great shape for discovery, though adding image and video sitemaps would help engines better index and display your visual content.
  • Structured Data: 58% - The site has a good foundation with valid organization schema on the homepage, but we weren't able to find or verify any author details on the blog post side.
  • AI Readiness: 50% - The site has a solid technical foundation with a valid sitemap and clear brand info, but the explicit block on GPTBot is a significant roadblock for AI engine discovery.
  • Performance: 0% - Mobile performance metrics for the homepage landed in the poor range across the board, with significant issues in load speed and visual stability.
  • Reputation: 69% - Overall, this section looks to be in good shape with strong review and social signals, though we did see some conflicting address data and a lack of Wikidata presence that needs attention.
  • LLM-Ready Content: 48% - This page is rich in trust signals like specific authors and recent dates, but the content structure and subheading depth make it harder for AI to extract key information efficiently.

The big picture at a glance

What stands out most is that the site has a good baseline of visibility signals, but a few core pieces are either missing, unverified, or hard for AI systems to confidently use. These gaps aren’t so much “errors” as they are clarity and access issues that can limit how consistently your brand and content get understood. Next, we’ll walk through the specific areas that didn’t meet the bar, organized by section so you can see exactly where the friction is coming from. None of this is unusual, and it’s all the kind of stuff that’s very fixable once it’s clearly surfaced.

Detailed Report

Discoverability

❌ Image or video sitemap not found

What we saw

An image sitemap and a video sitemap weren’t detected in the site data we reviewed. That means your visual content may not be as clearly surfaced for engines that rely on these files.

Why this matters for AI SEO

Generative engines can be more likely to miss or underuse visual assets when they’re harder to discover and enumerate. That can limit how often your images or videos show up in richer, AI-driven experiences.

Next step

Publish an image and/or video sitemap (as relevant) and make sure it’s discoverable alongside your existing sitemap setup.

Structured Data

❌ Resource/blog structured data couldn’t be verified

What we saw

The resource/blog page file wasn’t provided for evaluation, so we weren’t able to confirm whether that area includes structured data. As a result, this part of the site couldn’t be validated.

Why this matters for AI SEO

When content pages don’t have clear, verifiable page-level signals, AI systems have a harder time confidently understanding what the content is and how it should be attributed. That can reduce how reliably the resource content gets recognized and reused.

Next step

Include the resource/blog page in the review set and ensure it has clear, page-level structured data.

❌ Author clarity on the resource/blog post couldn’t be confirmed

What we saw

Because the resource/blog page file wasn’t provided, we couldn’t verify whether the post shows a clear, non-generic author. This prevented us from confirming who is responsible for the content.

Why this matters for AI SEO

Clear authorship helps AI systems attach the content to a real person or entity, which supports trust and accurate attribution. When that’s missing or unconfirmed, the content can be treated as less reliable.

Next step

Make sure each resource/blog post clearly names a specific author and that the page is available for validation.

❌ Author sameAs links couldn’t be validated

What we saw

The resource/blog page file wasn’t provided, so we couldn’t verify whether author structured data includes sameAs links to official profiles. That means author verification signals couldn’t be confirmed.

Why this matters for AI SEO

Author identity signals help generative engines connect content to the right person across the web. Without those verification cues, it’s easier for systems to stay uncertain about who the author is.

Next step

Add and validate author identity connections (sameAs links) within author-related structured data on resource/blog content.

AI Readiness

❌ Major AI crawler is explicitly blocked

What we saw

Your robots.txt explicitly disallows GPTBot. This effectively tells that crawler not to access your site.

Why this matters for AI SEO

If a major AI crawler is blocked, it can limit how well your content is discovered, understood, and reflected in generative experiences. Even strong onsite signals won’t help much if the content can’t be accessed.

Next step

Update robots.txt rules so GPTBot is not disallowed if you want that ecosystem to be able to access your content.

❌ No Wikidata entity found for the brand

What we saw

A Wikidata item ID for the brand wasn’t found in the evaluation. That suggests there isn’t a matching entity available for AI systems to reference there.

Why this matters for AI SEO

Knowledge-base entities can act like a “source of truth” for identity, helping AI systems verify who you are and connect brand details consistently. Without that, engines may have less confidence when reconciling brand information.

Next step

Create and/or claim a Wikidata entity for the brand and ensure it clearly matches your official identity.

Performance

❌ Homepage interactivity is heavily delayed

What we saw

The homepage showed unusually high blocking time during loading. This points to a page that can feel sluggish or unresponsive as it loads.

Why this matters for AI SEO

When the page experience is rough, users bounce faster—and that can indirectly reduce the odds of your content being engaged with and referenced. It also makes it harder for systems that simulate user experience to treat the page as high-quality.

Next step

Reduce what’s causing long main-thread blocking so the homepage becomes responsive sooner.

❌ Main content appears very late on mobile

What we saw

The homepage’s primary content took a long time to fully appear in the mobile test results. This creates a noticeably slow “time to value” for visitors.

Why this matters for AI SEO

If users have to wait too long to see the core message, they’re less likely to trust the site or stick around—especially from AI-driven discovery paths where attention is limited. That can suppress visibility signals over time.

Next step

Prioritize getting the main homepage content to render earlier on mobile.

❌ Layout shifts create a “jumpy” experience

What we saw

The page showed significant layout shifting while loading, meaning elements move around after they first appear. This often feels unstable on mobile.

Why this matters for AI SEO

A visually unstable page reduces perceived quality and trust, especially for first-time visitors coming from AI answers. It also makes it harder for automated systems to consistently interpret what users see during load.

Next step

Stabilize the homepage layout during load so content doesn’t shift around as assets arrive.

❌ Overall homepage performance is in a poor range

What we saw

The combined performance results for the homepage landed well below commonly accepted quality ranges. In practice, this aligns with a slow and unstable loading experience.

Why this matters for AI SEO

When overall experience is weak, it can limit how confidently platforms surface your pages as recommended sources. Better-performing competitors are simply easier to send traffic to.

Next step

Treat homepage performance as a priority item and bring it up to a consistently smooth baseline.

Reputation

❌ Affirmed negative client feedback was identified

What we saw

The research data included affirmed negative client feedback related to communication and service experience. This stands out as a reputational friction point.

Why this matters for AI SEO

Generative engines often weigh sentiment and recurring themes when deciding how confidently to recommend a brand. Negative assertions can introduce hesitation or soften the language AI uses when describing your services.

Next step

Review the surfaced feedback theme and address it in your public-facing reputation and customer experience narrative.

❌ Conflicting business addresses were found

What we saw

Multiple different addresses were associated with the brand across sources (including 200 Clinton Avenue, 1300 Meridian St, and 3508 South Memorial Parkway). This creates an identity mismatch.

Why this matters for AI SEO

When core identity details conflict, AI systems have a harder time confidently tying mentions, reviews, and listings back to one verified entity. That uncertainty can dilute trust and reduce consistent visibility.

Next step

Standardize the official address across your key profiles and citations so the brand’s identity resolves cleanly.

❌ No matching Wikidata entity was found

What we saw

A matching Wikidata entity wasn’t found for the brand during the evaluation. This leaves a gap in third-party identity verification.

Why this matters for AI SEO

Wikidata is a common reference point for entity resolution, especially when a brand name or details overlap with other sources. Without an entity there, systems may have fewer “anchors” to confirm the right brand.

Next step

Create a Wikidata entry that matches the brand and connects to your official web presence.

❌ Official identity anchors in Wikidata couldn’t be verified

What we saw

Because no Wikidata entity was found, the evaluation couldn’t verify official identity anchors (like a confirmed website/identifiers) in that database. This is a downstream effect of the missing entity.

Why this matters for AI SEO

Official anchors help AI systems distinguish your brand from similarly named entities and reduce confusion in knowledge-graph style lookups. Missing anchors can contribute to inconsistent brand understanding.

Next step

Once a Wikidata entity exists, ensure it includes official brand anchors that match your real-world identity.

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

Persona Targeting: It appears to be aimed at home buyers and sellers in the Huntsville, Alabama area who want personalized local real estate guidance from a professional husband-wife team.

❌ Sections are too thin to stand on their own

What we saw

The content is split into multiple sections, but the sections are very short on average. That makes each chunk feel more like a teaser than a complete idea.

Why this matters for AI SEO

Generative engines tend to reuse content in chunks, and short sections often lack enough context to be quoted or summarized accurately. This can reduce how much of the article is “liftable” into AI answers.

Next step

Expand key sections so each one contains enough substance to fully explain one topic without needing surrounding text.

❌ No table-based structure detected

What we saw

No HTML table was detected on the page. The information is presented primarily in narrative blocks.

Why this matters for AI SEO

Structured formats make it easier for AI systems to extract comparisons, definitions, and step-by-step details cleanly. Without that, useful details can be harder to isolate and reuse.

Next step

Add at least one simple table where it naturally fits (for example, summarizing options, timelines, or side-by-side comparisons).

❌ Subheadings are too generic

What we saw

The subheadings read as generic labels (e.g., “About Us,” “Reviews”) rather than describing the specific question or takeaway of each section. This makes the structure harder to interpret at a glance.

Why this matters for AI SEO

Descriptive subheadings act like signposts for AI systems, helping them understand what each section is about without guessing. Generic headings reduce clarity and can make content harder to map to user questions.

Next step

Rewrite subheadings so they clearly state the specific topic or answer each section delivers.

❌ Key answers don’t show up early enough

What we saw

Only a minority of sections start with a substantial first paragraph, which means the page often takes too long to “get to the point.” The early lines don’t consistently deliver a clear answer or takeaway.

Why this matters for AI SEO

AI systems frequently prioritize content that answers quickly and clearly, especially for snippet-like reuse. When the answer is buried, the content is less likely to be pulled into concise generative responses.

Next step

Adjust section openings so the first paragraph delivers a clear, concrete takeaway before any additional context.

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