Overview:
On 06/21/26 brownhazejewelry.com scored 40% — **Weak** – Overall, the site has a solid baseline for being found, but a few big visibility gaps keep it from coming across as clearly established to AI systems.
Executive summary
Score Breakdown (High Level)
- Discoverability: 92% - The site's discoverability is strong with clean metadata and valid standard sitemaps, though adding a dedicated image sitemap would further boost visibility for your product photography.
- Structured Data: 58% - The site has a solid foundation with valid business schema on the homepage, but we weren't able to confirm author or article markup since a resource page wasn't provided.
- AI Readiness: 67% - The site has a strong technical foundation for AI discovery with clear sitemaps and open crawling, although it lacks a Wikidata entity to anchor its brand identity.
- Performance: 50% - Mobile performance generally landed outside the poor range, though the homepage is noticeably slow to fully load its main visual elements.
- Reputation: 12% - The site has a good foundation with direct social media links, but it’s missing the bigger authority signals like Wikidata and independent press coverage in the data we reviewed.
- LLM-Ready Content: 8% - The page functions primarily as a visual storefront and lacks the structural markers like named authors, dates, and descriptive headings that help AI systems fully contextulize and trust the content.
Where things stand overall
The big picture is that the site is generally easy for systems to access and understand at a baseline, but it’s missing several signals that help AI feel confident about authority and context. Most of the gaps aren’t “errors” so much as missing clarity—especially around content attribution, freshness, and external validation. The next section breaks down the specific areas where those signals didn’t show up so you can see exactly what’s being held back. None of this is unusual, and it’s the kind of cleanup that tends to be very doable once it’s clearly mapped.
Detailed Report
Discoverability
❌ Image or video sitemap not found
What we saw
We didn’t find an image sitemap or video sitemap available for the site. That means visual content may not be getting the clearest possible path to being discovered and cataloged.
Why this matters for AI SEO
Generative engines and search systems rely on clear, consistent signals to understand and surface a brand’s content. When visual assets aren’t as easy to discover, they’re less likely to show up reliably in AI-driven results.
Next step
Add a dedicated image and/or video sitemap so your visual assets are easier to consistently discover.
Structured Data
❌ Resource/blog structured data couldn’t be evaluated
What we saw
The resource/blog page file that was expected for review was missing or empty, so we couldn’t confirm whether content pages include the same structured signals as the homepage.
Why this matters for AI SEO
AI systems tend to understand brands better when content pages are consistently described and attributed. When that content layer can’t be verified, it limits how confidently systems can interpret and reuse your material.
Next step
Make sure the resource/blog page is accessible and includes structured data that matches the level of detail found on key site pages.
❌ No clear, non-generic author on the resource/blog content
What we saw
An author couldn’t be identified for the resource/blog content because the page wasn’t available to review. As a result, authorship couldn’t be confirmed.
Why this matters for AI SEO
Generative engines look for clear attribution to gauge credibility and context. Missing author identity makes it harder for AI to treat content as trustworthy and reusable.
Next step
Add a clearly named author to resource/blog posts so attribution is consistent and easy to verify.
❌ Author “sameAs” identity links couldn’t be verified
What we saw
Because the resource/blog page wasn’t provided, we couldn’t verify whether author identity links (like matching profile references) were present.
Why this matters for AI SEO
When AI can connect a writer to consistent identity references, it improves confidence in who created the content. Without that, the author’s credibility is harder to establish.
Next step
Include consistent identity references for authors so they’re easier for AI systems to recognize and connect.
AI Readiness
❌ No Wikidata entity found for the brand
What we saw
We didn’t find a Wikidata item ID for the brand in the provided results. That leaves a gap in widely recognized “source of truth” style references.
Why this matters for AI SEO
Generative engines often lean on well-known entity references to confirm brand identity. Without one, AI may have less confidence when matching your brand to external information.
Next step
Create or confirm a Wikidata entity for the brand so identity signals are easier to corroborate.
Performance
❌ Main content took too long to appear on the homepage
What we saw
The homepage’s main content took over six seconds to fully display in the evaluation results. This points to a slower initial load experience.
Why this matters for AI SEO
When primary content takes longer to appear, it can reduce how effectively the page is understood and used—both by people and by systems that try to process pages quickly and reliably.
Next step
Reduce the time it takes for the homepage’s primary content to display so the page is easier to consume quickly.
Reputation
❌ Negative client sentiment couldn’t be confirmed
What we saw
The reputation field needed to confirm the absence of negative client assertions was missing from the provided packet. That means this point couldn’t be verified either way.
Why this matters for AI SEO
AI systems weigh external trust cues when deciding how confidently to present a brand. If sentiment signals aren’t verifiable, the overall trust picture can look incomplete.
Next step
Ensure client sentiment signals are documented in a verifiable way so reputation can be assessed more confidently.
❌ Negative employee sentiment couldn’t be confirmed
What we saw
The field needed to confirm the absence of negative employee assertions was missing from the provided packet. This prevented a clear read on that aspect of reputation.
Why this matters for AI SEO
Generative engines try to avoid amplifying brands with unclear or risky reputation signals. Missing verification points can reduce confidence in brand safety and reliability.
Next step
Make employee sentiment signals easier to validate through consistent, accessible third-party references.
❌ Brand recognition across LLMs couldn’t be verified
What we saw
The summary field required to confirm multi-model recognition wasn’t present in the structured results. As a result, broad AI recognition couldn’t be validated.
Why this matters for AI SEO
When multiple systems consistently recognize a brand, it tends to show up more reliably in generative answers. If recognition can’t be confirmed, visibility may be less predictable.
Next step
Establish and document clearer off-site brand references that make recognition easier to confirm.
❌ Brand identity consistency couldn’t be verified
What we saw
The required consensus fields used to confirm consistent brand identity were missing from the packet. That blocked validation of name/identity consistency in the structured results.
Why this matters for AI SEO
AI systems do better when they can confidently tie all mentions back to the same entity. If identity consistency can’t be verified, AI may treat brand references as ambiguous.
Next step
Make sure your brand identity is consistently represented across major third-party sources that AI commonly references.
❌ Wikidata entity status couldn’t be verified
What we saw
The field used to confirm a Wikidata match status was missing from the packet. That prevented verification of whether a Wikidata entry exists.
Why this matters for AI SEO
Wikidata is one of the common reference points for entity validation. If that status isn’t verifiable, it weakens the external “identity anchor” layer AI often looks for.
Next step
Confirm whether a Wikidata entry exists and ensure it clearly maps back to the official brand.
❌ Wikidata identity anchors couldn’t be verified
What we saw
The fields needed to validate official identity anchors (like website identifiers) were missing. That means official entity-to-brand linking couldn’t be confirmed.
Why this matters for AI SEO
Identity anchors help AI connect the dots between your site and external references. Without verifiable anchors, AI has fewer dependable signals to confirm it’s talking about the right brand.
Next step
Ensure there are clear, verifiable identity anchors that connect third-party entity references back to your official site.
❌ Third-party reviews couldn’t be confirmed
What we saw
The structured field used to confirm whether third-party reviews exist was missing from the packet. So review presence couldn’t be validated.
Why this matters for AI SEO
Independent reviews are a common trust cue that helps AI evaluate credibility. If they can’t be confirmed, the brand’s external validation looks thin.
Next step
Make third-party review presence easier to verify by ensuring reviews live on well-known platforms and are referenced consistently.
❌ Review sources couldn’t be verified
What we saw
The structured field needed to confirm concrete review sources was missing. That prevented validation of where reviews are coming from.
Why this matters for AI SEO
AI tends to trust reviews more when they’re tied to recognizable, consistent sources. If sources aren’t verifiable, review signals carry less weight in practice.
Next step
Standardize and clearly reference the main review sources so they’re easy to confirm.
❌ Social profile consensus couldn’t be verified
What we saw
The field used to confirm social profiles via consensus data was missing from the packet. Even though social links were present on-site, consensus verification wasn’t available.
Why this matters for AI SEO
When AI can confirm “official” profiles across sources, it reduces identity confusion and improves trust. Missing consensus signals can make those connections less reliable.
Next step
Ensure your official social profiles are consistently referenced across trusted sources so they can be validated more easily.
❌ Independent press coverage couldn’t be confirmed
What we saw
The structured field used to confirm independent press mentions was missing from the packet. That means off-site coverage couldn’t be validated.
Why this matters for AI SEO
Independent coverage is a strong credibility signal that can help AI systems feel confident summarizing and recommending a brand. Without it, your broader authority is harder to establish.
Next step
Compile and make independent coverage easy to verify so AI systems can connect your brand to credible third-party mentions.
❌ Owned press coverage couldn’t be confirmed
What we saw
The structured field used to confirm owned press (like brand-published announcements) was missing from the packet. That prevented validation of any owned coverage footprint.
Why this matters for AI SEO
Owned coverage helps AI understand what the brand considers important, recent, and official. If it can’t be confirmed, AI has fewer reliable reference points to pull from.
Next step
Ensure owned announcements and updates are consistently published in a way that’s easy to find and verify.
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 specific author listed
What we saw
We didn’t see a specific individual author identified in the visible content or associated markup. Authorship came across as missing or generic.
Why this matters for AI SEO
AI systems look for clear attribution to judge whether content is credible and quotable. Without an author, the content can feel less trustworthy and harder to reference.
Next step
Add a clearly named author to the page so attribution is unambiguous.
❌ No publish or update date found
What we saw
We didn’t find a publication date or a last-updated date on the content. That removes an important piece of context about freshness.
Why this matters for AI SEO
Generative engines often factor timeliness into what they surface and how they frame answers. Missing dates make it harder to interpret how current the information is.
Next step
Include a clear publish date (and update date when relevant) on the page.
❌ Recency couldn’t be confirmed
What we saw
Because no publish/update date was present, we couldn’t confirm whether the content has been updated within the last year. The recency signal was effectively unavailable.
Why this matters for AI SEO
When AI can’t confirm recency, it may be more cautious about using the page as a reference—especially for topics where freshness affects confidence.
Next step
Add date information so recency can be evaluated and understood.
❌ No non-social outbound reference links
What we saw
All outbound links identified pointed to social platforms, with no non-social external references. That leaves the page without supporting citations or references.
Why this matters for AI SEO
Outbound references can help AI validate claims and understand context. When links are limited to social profiles only, the content can appear less grounded in external sources.
Next step
Add at least one relevant non-social outbound link that supports or contextualizes the content.
❌ Content sections were too thin for extraction
What we saw
While the page had multiple sections, the average section length was very short (around a dozen words). The structure reads more like a quick catalog than a resource with reusable depth.
Why this matters for AI SEO
Generative engines extract meaning best from clear, substantial blocks of information. When sections are extremely short, there’s less material for AI to accurately summarize or cite.
Next step
Expand sections so each one contains enough text to stand on its own as a useful, extractable chunk.
❌ No HTML table found (bonus)
What we saw
No table element was detected on the page. That means there wasn’t a structured, scannable block of data for quick reuse.
Why this matters for AI SEO
Tables can make key details easier for AI to pull accurately, especially for comparisons, specs, or quick reference information. Without one, important details may remain buried or implied.
Next step
Add a simple table where it naturally fits to present key details in a structured way.
❌ Subheadings weren’t consistently descriptive
What we saw
Only a small portion of the subheadings were descriptive enough to clearly communicate what each section is about. Several headings were too short or generic to carry meaning on their own.
Why this matters for AI SEO
AI relies on headings to understand the hierarchy and intent of a page. When headings don’t say much, it’s harder for systems to map and extract the page accurately.
Next step
Rewrite section headings so they clearly describe the takeaway of the section.
❌ Key answers didn’t appear early in sections
What we saw
None of the sections opened with a substantial first paragraph that clearly delivers an answer or takeaway. The early content didn’t give AI much to latch onto quickly.
Why this matters for AI SEO
Generative engines often prioritize pages that make the main point clear right away. When key answers aren’t surfaced early, the page is less likely to be used as a reliable source.
Next step
Adjust section openings so the main takeaway is clear near the top of each section.
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.
