Overview:
On 01/26/26 sitetuners.com scored 71% — **Good** – Overall, the site looks solid for AI visibility, with a few clarity and credibility gaps that keep it from showing up as strongly as it could.
Executive summary
Score Breakdown (High Level)
- Discoverability: 67% - Most of the key discovery basics are in place, but we didn't find an XML sitemap or any media sitemaps for this site.
- Structured Data: 92% - Schema markup is in solid shape across both the homepage and resource pages, with clear organization and author details, but the author schema is missing sameAs links.
- AI Readiness: 50% - The site didn’t have an XML sitemap or a Wikidata entity, but everything else—from AI crawler access to About page coverage—looked solid.
- Performance: 72% - The only real gap here is the homepage LCP, which just tips into the 'poor' zone, but everything else on the homepage and resource page looks solid for mobile speed and stability.
- Reputation: 88% - All major reputation and offsite signals checked out, but we did see a flagged negative employee assertion from one LLM model.
- LLM-Ready Content: 60% - Author, publish/update dates, and outbound links are present and up-to-date, but the article’s sectioning and early-answer visibility are weak (one or more sections are overly long and many sections don’t put a 25+ word summary up front).
Where things stand overall
The big picture is that the site is in a pretty healthy place for AI visibility, but a few missing signals make it harder for systems to confidently discover, identify, and reuse your information. Most of what came up isn’t “wrong” so much as incomplete or unevenly presented, especially around site-wide discovery, brand/entity clarity, and how the blog article is packaged for quick extraction. The sections below walk through each of the specific areas that didn’t meet the mark, in plain English. None of this is unusual—these are common gaps, and they’re generally very manageable once they’re clearly identified.
Detailed Report
Discoverability
❌ No standard sitemap found
What we saw
We weren’t able to find a standard sitemap for the site. That means there isn’t a clear, centralized list of pages for systems to reference.
Why this matters for AI SEO
When page discovery is less straightforward, it’s easier for important pages to get missed or treated as lower confidence. This can reduce how consistently the site is understood and pulled into AI-generated answers.
Next step
Create and publish a standard sitemap that reflects the site’s key URLs.
❌ No image or video sitemap found
What we saw
We didn’t see a dedicated sitemap for images or videos. As a result, media assets don’t have a clear discovery path.
Why this matters for AI SEO
Generative results increasingly blend in visuals, and missing media discovery signals can limit how easily those assets get recognized and reused. It can also weaken overall page understanding when key media is harder to connect.
Next step
Publish an image sitemap and/or video sitemap if images or videos are an important part of the site.
Structured Data
❌ Author profile isn’t connected to external references
What we saw
The author is clearly identified, but the author profile data doesn’t include external reference links (like public profiles) that help confirm identity.
Why this matters for AI SEO
When author identity is harder to corroborate across the web, it can reduce confidence in attribution and expertise signals. That can make it tougher for AI systems to consistently “trust” and reuse author-led content.
Next step
Add a small set of relevant external profile links for the author where appropriate.
AI Readiness
❌ Sitemap missing
What we saw
A standard sitemap wasn’t found for the site. This leaves AI-focused crawlers and indexers without a reliable “map” of your key pages.
Why this matters for AI SEO
If discovery is inconsistent, it’s harder for generative engines to build a complete picture of what the brand offers. That can lead to thinner or less accurate AI visibility over time.
Next step
Publish a standard sitemap that includes the site’s primary pages.
❌ Sitemap freshness signals not available
What we saw
Because a sitemap wasn’t available, we also couldn’t confirm any page update/freshness information within it.
Why this matters for AI SEO
When update timing isn’t clearly communicated, it can be harder for systems to tell what’s current versus outdated. That can affect confidence in pulling the site into answers that depend on timely information.
Next step
Include page update information in the sitemap so update timing can be interpreted more reliably.
❌ Brand entity not confirmed
What we saw
We weren’t able to confirm a matched brand entity in a common public knowledge source used for entity recognition.
Why this matters for AI SEO
If the brand isn’t easy to anchor to a recognized entity, AI systems can be less consistent in how they identify and describe it. That can show up as weaker brand recognition or more ambiguity in generative results.
Next step
Confirm whether an official brand entity exists and is clearly associated with the brand’s identity.
Performance
❌ Homepage main content loads slowly
What we saw
The homepage’s primary content took longer than expected to fully appear for users, indicating a meaningful slowdown on the main entry point.
Why this matters for AI SEO
When the core content is slower to load, it can reduce how reliably the page is processed and understood, especially at scale. Over time, that can impact how confidently the homepage is treated as a strong source for brand and offering context.
Next step
Prioritize improving how quickly the homepage’s main content becomes visible.
Reputation & Offsite Signals
| Model | ChatGPT | Claude | Perplexity | Grok | Gemini |
|---|---|---|---|---|---|
| Assessment | ✅ Verified, trustworthy brand | ⚠️ Limited footprint | ✅ Verified, trustworthy brand | ⚠️ Mixed signals | ✅ Verified, trustworthy brand |
❌ Negative employee-related claim surfaced in AI results
What we saw
At least one AI model response included an affirmed negative claim related to employees. This is the kind of thing that can stick around in generative summaries even when it’s not representative.
Why this matters for AI SEO
Employee sentiment and workplace claims can influence brand trust in AI-generated answers, especially for people doing vendor research. Even a single strong negative assertion can skew how a brand is framed.
Next step
Review the specific employee-related claim showing up in AI results and validate it against real, public-facing sources.
❌ Brand entity not found in Wikidata
What we saw
We didn’t find a matched Wikidata entry for the brand. That leaves one less consistent reference point for entity-based understanding.
Why this matters for AI SEO
Entity alignment helps generative systems connect brand mentions, identity details, and reputation signals more reliably. Without that anchor, brand recognition can be less stable across different AI experiences.
Next step
Confirm whether the brand has a Wikidata entry and whether it clearly matches the brand identity.
❌ No official identity anchors confirmed in Wikidata
What we saw
Because there wasn’t a matched entity, we also couldn’t confirm official identity anchors there (like an official website and identifiers).
Why this matters for AI SEO
Official anchors act like “ground truth” for systems that synthesize brand information. When they’re missing, there’s more room for inconsistency in how the brand gets represented.
Next step
Ensure the brand’s official identity anchors are present and correctly associated wherever the brand entity is maintained.
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
❌ Content sections aren’t consistently “chunked” for reuse
What we saw
The article is broken into sections, but at least one section runs long enough that it’s harder to scan and reuse cleanly. Overall section length also wasn’t consistently in a “sweet spot” for easy extraction.
Why this matters for AI SEO
Generative engines tend to pull smaller, self-contained pieces of content when assembling answers. Overlong sections can make it tougher for them to isolate clear, quotable blocks.
Next step
Refactor long sections into smaller, more self-contained blocks that keep one clear idea per segment.
❌ No table detected in the article
What we saw
We didn’t find a table element in the article content.
Why this matters for AI SEO
Tables can make key comparisons and definitions easier to interpret and reuse in AI-generated responses. When they’re absent, important details may be harder to extract cleanly.
Next step
Add a simple table where it naturally helps summarize options, steps, or comparisons in the article.
❌ Key answers don’t consistently show up early in sections
What we saw
In many sections, the opening paragraph is brief, so the “main point” doesn’t reliably appear right away. This makes sections feel more like a build-up than a quick answer.
Why this matters for AI SEO
AI systems often rely on early, explicit statements to understand what a section is about and what it’s answering. When the answer is buried deeper, the content can be underused in generative summaries.
Next step
Rework section openings so the main takeaway is clearly stated up front before supporting detail.
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.
