Overview:
On 06/27/26 outlawhorseproducts.com scored 59% — **Fair** – Overall, the site has a solid base for AI visibility, with a few clear gaps around brand clarity and content depth holding it back.
Executive summary
Score Breakdown (High Level)
- Discoverability: 100% - Overall, the site is very easy for search engines to find and index, though adding a dedicated image sitemap would be a smart next step for your product photos.
- Structured Data: 58% - The homepage has a solid foundation with valid organization schema, but the lack of article-level markup and author details is a missed opportunity for building authority.
- AI Readiness: 33% - The site is doing the basics right by not blocking AI bots, but it's missing the deeper structural signals like lastmod data and a clear About page that help models verify brand authority.
- Performance: 50% - Mobile performance generally landed in a good spot, though we did see some visual stability issues on the homepage.
- Reputation: 69% - The brand shows good recognition and social engagement, though some negative customer feedback and missing business identity anchors are visible.
- LLM-Ready Content: 56% - The site features expert-backed content and recent updates, but it relies on brief sections and lacks external citations that would help search engines establish broader context.
The big picture on what’s missing
What stands out most is that the site generally communicates what it is, but a few key signals around brand identity and content packaging aren’t coming through as clearly as they could. The gaps here read more like visibility and confidence issues for AI systems than outright problems. The next section breaks down the specific areas where information was missing, unclear, or couldn’t be verified across discoverability, structured data, AI readiness, performance, reputation, and the blog content snapshot. None of this is unusual—it’s the kind of cleanup that often separates “pretty good” from “consistently show up” in generative results.
Detailed Report
Discoverability
❌ Missing image or video sitemap
What we saw
We weren’t able to find a dedicated image or video sitemap in the site data. A standard XML sitemap was present, but nothing specifically calling out visual content.
Why this matters for AI SEO
AI-driven discovery often leans on clear signals about what visual assets exist and how they relate to your pages. When those signals aren’t present, it can be harder for systems to confidently surface your images or videos in relevant results.
Next step
Create and publish a dedicated image sitemap and/or video sitemap and make sure it’s discoverable alongside your existing sitemap.
Structured Data
❌ Resource/blog page markup couldn’t be verified
What we saw
A resource/blog page wasn’t included in the evaluation data, so we couldn’t confirm whether that page includes the expected structured details. In short, there wasn’t enough provided to validate what’s on the article layer.
Why this matters for AI SEO
Generative engines tend to rely heavily on consistent, page-level details to understand and reuse articles confidently. When the article layer isn’t clearly defined, it can limit how well your content gets interpreted and surfaced.
Next step
Make sure a resource/blog page is available for review and includes clear, article-level structured details.
❌ Author identity on resource content couldn’t be confirmed
What we saw
Because the resource/blog page file wasn’t provided, we couldn’t verify whether the author is clearly identified (and not generic) at the post level. That left author identity unconfirmed in this run.
Why this matters for AI SEO
Clear authorship helps AI systems judge credibility and context—especially when they’re deciding whether to quote or summarize content. When author identity isn’t easy to verify, it can reduce trust signals around the content.
Next step
Ensure each resource/blog post clearly names a specific author in a consistent way.
❌ Author “SameAs” profile links couldn’t be evaluated
What we saw
Author profile linking (the “SameAs” connections) couldn’t be reviewed because the author schema on the resource/blog page wasn’t available in the provided data. As a result, we couldn’t confirm those external identity connections.
Why this matters for AI SEO
When AI engines can connect an author to consistent, public profiles, it makes it easier to disambiguate identity and build trust. Without those connections, authors can look less verifiable.
Next step
Add consistent author identity links that point to the author’s official profiles.
AI Readiness
❌ Sitemap update dates weren’t found
What we saw
The sitemap was present, but it didn’t include update timestamps for content. That means the system couldn’t see clear “last updated” signals from the sitemap.
Why this matters for AI SEO
AI systems benefit from reliable freshness cues when deciding what to crawl, re-check, and cite. If update timing isn’t clear, it can reduce confidence about what’s current.
Next step
Add update timestamps to your sitemap entries so content freshness is clearly communicated.
❌ Brand context page wasn’t surfaced from the homepage
What we saw
We didn’t find internal links from the homepage that clearly point to a brand context page (like an about/company/team-style destination). From the homepage alone, that “who we are” trail wasn’t obvious.
Why this matters for AI SEO
LLMs commonly look for straightforward brand context to confirm legitimacy, ownership, and background. When that context isn’t easy to locate, the brand can be harder to summarize confidently.
Next step
Make sure the homepage clearly links to a page that explains who the company is and what it does.
❌ No Wikidata entity was identified
What we saw
A Wikidata item ID for the brand wasn’t identified in the evaluation. In other words, there wasn’t a matching entity the system could point to.
Why this matters for AI SEO
Entity-based understanding is a big part of how generative systems confirm “this brand is this brand.” Without an identifiable entity, it can be harder to verify and consistently represent your brand in generated answers.
Next step
Create or claim a Wikidata entity for the brand so there’s a consistent public reference point.
Performance
❌ Homepage layout stability issue
What we saw
The homepage showed higher-than-expected layout shifting, meaning elements appear to move around while the page loads. This can make the page feel less steady even when it’s otherwise quick.
Why this matters for AI SEO
A shaky experience can reduce user trust and engagement, which indirectly affects how confidently platforms and assistants interpret the site as a good recommendation. It also makes content consumption feel less polished.
Next step
Reduce homepage layout shifts so the page remains visually stable as it loads.
Reputation
❌ Negative customer service feedback was detected
What we saw
The evaluation surfaced negative client sentiment tied to customer service. This indicates at least some public-facing feedback that’s not fully positive.
Why this matters for AI SEO
Generative engines weigh reputation signals when deciding whether to recommend a brand or frame it positively. Negative themes—especially around service—can influence how the brand gets described.
Next step
Review the surfaced customer service themes across third-party feedback sources and document the recurring issues.
❌ Brand identity wasn’t consistent across sources
What we saw
A consistent physical address wasn’t identified across the majority of model responses. In practice, that means the business’s “official identity” details didn’t come through consistently.
Why this matters for AI SEO
When core business details vary or are missing, AI systems have a harder time confidently pinning down who the brand is. That can lead to weaker trust and more ambiguity in generated summaries.
Next step
Standardize the brand’s official business address information so it’s consistent wherever it appears publicly.
❌ No Wikidata entity found for the brand
What we saw
No matching Wikidata entity was found for the brand during the evaluation. This left the brand without a central entity reference in that ecosystem.
Why this matters for AI SEO
Wikidata is a common “authority anchor” used to connect brand mentions, attributes, and official references. Without it, it’s harder for generative systems to reconcile identity cleanly.
Next step
Create or get a Wikidata item established for the brand so it can serve as a stable identity reference.
❌ Wikidata identity anchors couldn’t be verified
What we saw
Because a Wikidata entity wasn’t found, the evaluation couldn’t verify official identity anchors tied to that entity. This is essentially a knock-on effect of the missing entity.
Why this matters for AI SEO
Identity anchors help AI systems connect “this website” to “this real-world business” with high confidence. When those anchors aren’t available, brand verification tends to be less consistent.
Next step
Once a Wikidata entity exists, ensure it includes clear official references that point back to the brand.
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 non-social outbound references found
What we saw
The resource relied on internal links and social platform links, but didn’t include external citations or references to third-party sources. That makes the article feel more “self-contained” than supported.
Why this matters for AI SEO
External references can help AI systems understand what information is being grounded in broader, verifiable sources. Without them, the content may be seen as less supported when it’s summarized or reused.
Next step
Add a small set of relevant third-party references that support key claims or guidance in the article.
❌ Sections were too short for deeper extraction
What we saw
The content was split into many very short sections, with an average section length that fell well below the typical range for detailed indexing. The structure is readable, but the sections don’t carry much standalone depth.
Why this matters for AI SEO
AI systems pull meaning in chunks, and overly thin sections can limit how much useful context gets extracted from each part of the page. That can make it harder for the article to show up for more specific, long-tail questions.
Next step
Consolidate or expand the shortest sections so each one contains enough context to stand on its own.
❌ No tables were used to structure key info
What we saw
No HTML table was detected, so there wasn’t a structured way to present comparisons, specs, or quick-reference details. Everything was communicated purely through narrative sections.
Why this matters for AI SEO
Tables can make it easier for AI systems to extract and reuse precise comparisons and definitions. When that structure isn’t present, important details can be harder to summarize cleanly.
Next step
Add a simple table where it naturally fits (for example, comparisons, ingredients, use cases, or product differences).
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.
