Overview:
On 06/03/26 drewidlife.com scored 53% — **Fair** – Overall, the site is in a workable place for AI visibility, but some key context and credibility signals aren’t coming through as clearly as they could.
Executive summary
Score Breakdown (High Level)
- Discoverability: 100% - The site's discovery foundation is mostly solid with clear crawler access and unique metadata, though it's currently missing a dedicated image or video sitemap.
- Structured Data: 0% - We weren't able to find any schema markup on the site, which is a key component for helping search engines identify your brand and content.
- AI Readiness: 67% - Overall, the site’s technical foundation for AI readiness is quite strong, though it lacks a formal Wikidata presence to anchor its brand identity.
- Performance: 50% - The site shows excellent responsiveness and layout stability, but the main visual content takes far too long to load on mobile devices.
- Reputation: 58% - The site has a solid start with social media links and AI recognition, but it lacks the formal identity anchors and independent reviews needed to fully establish brand authority.
- LLM-Ready Content: 44% - The site establishes strong trust through clear authorship and frequent updates, but its technical structure lacks the header-driven organization required for optimal AI readability.
The main takeaway at a glance
The big picture is that the site is visible and recognizable, but it’s not consistently easy for AI systems to “lock in” who the brand is and how to reuse the content confidently. Most of what’s missing shows up as clarity gaps—structured context, stronger third-party trust signals, and content formatting that reads cleanly in sections. Below, you’ll see a breakdown of the specific areas where the signals didn’t come through as clearly as expected. None of this is unusual, and it’s all the kind of stuff that tends to improve quickly once it’s clearly identified.
Detailed Report
Discoverability
❌ No image or video sitemap found
What we saw
We didn’t see any sign of a dedicated image sitemap or video sitemap. That means visual assets don’t have an extra layer of guidance helping them get discovered and cataloged.
Why this matters for AI SEO
Generative engines can use visual content as supporting context, but they need consistent ways to find and understand those assets at scale. When visuals are harder to index, they’re less likely to be surfaced or referenced.
Next step
Add a dedicated image and/or video sitemap so your key visual assets are easier for crawlers to consistently discover.
Structured Data
❌ No schema markup detected on the homepage
What we saw
We didn’t find any valid structured data markup on the homepage. As a result, the page isn’t providing explicit, machine-readable context about what it represents.
Why this matters for AI SEO
Structured data helps generative engines reduce ambiguity when summarizing who you are and what you do. Without it, systems have to infer more from page text alone, which can lead to weaker or less consistent understanding.
Next step
Add valid homepage schema markup so the site’s core identity and context are clearer to generative engines.
❌ No organization-type schema found on the homepage
What we saw
Because no schema was detected, we also didn’t see any organization-related structured data on the homepage. That leaves “who is behind this site” less explicit than it could be.
Why this matters for AI SEO
Generative engines lean on clear entity context to build trust and confidently connect a site to a real-world brand. When that context is missing, your brand footprint can be harder to anchor.
Next step
Include organization-related schema on the homepage so the brand/entity behind the site is clearly defined.
❌ Resource/blog structured data couldn’t be verified
What we saw
A dedicated resource/blog page file wasn’t available in the provided data, so we couldn’t confirm whether schema exists on that content. This leaves a blind spot around how well article-level content is described to search and AI systems.
Why this matters for AI SEO
Generative engines often pull summaries and citations from informational content, and structured context can help them interpret it correctly. When that structured layer can’t be confirmed, it’s harder to rely on consistent AI understanding.
Next step
Make sure your resource/blog content is included for evaluation so structured data on articles can be validated.
❌ Schema quality couldn’t be evaluated
What we saw
Since no schema markup was found, there was nothing available to check for major structured data issues. In practice, this means schema quality is currently “unknown” because the baseline isn’t present.
Why this matters for AI SEO
When structured context is missing entirely, generative engines lose a reliable signal they can use to interpret and classify your site. That can reduce confidence when generating answers, summaries, or attributions.
Next step
Add structured data first, then validate that it’s clean and consistent so it can be confidently used by crawlers.
❌ Author clarity on resource/blog content couldn’t be verified
What we saw
Because the resource/blog page data wasn’t available, we couldn’t verify whether the content has a clear, non-generic author signal in structured form. That limits confidence in author attribution for content used by AI.
Why this matters for AI SEO
Generative engines care about who is behind a piece of content when deciding what to quote or trust. Unclear author signals can make attribution weaker and reduce perceived credibility.
Next step
Ensure your resource/blog pages include clear author information that can be verified in the page data.
❌ No author “sameAs” links detected in structured data
What we saw
We didn’t detect any author-related structured data, including author identity links that connect the author to known profiles. This makes it harder to tie the author to a consistent identity footprint.
Why this matters for AI SEO
Identity connections help generative engines disambiguate people and strengthen trust signals. Without those links, it’s easier for systems to treat the author as “just text on a page,” rather than a well-defined entity.
Next step
Add author structured data that includes clear identity links so AI systems can better confirm and connect the author’s footprint.
AI Readiness
❌ No Wikidata entity found for the brand
What we saw
We didn’t find an associated Wikidata entity for the brand. In other words, there isn’t a clear structured “entity record” that AI systems can reference for official brand grounding.
Why this matters for AI SEO
Entity grounding helps generative engines connect your site to a stable, recognized identity across the web. When that anchor is missing, it can be harder for AI to confidently attribute information and keep details consistent.
Next step
Create and/or connect a Wikidata entity for the brand so AI systems have a stronger identity anchor to reference.
Performance
❌ Main content loads very slowly on the homepage (LCP)
What we saw
The homepage’s Largest Contentful Paint came in at 13.98 seconds, which indicates the main on-page content is taking a long time to fully appear. This is a noticeable delay, especially on mobile.
Why this matters for AI SEO
When pages feel slow to load, users are less likely to engage deeply, and that can indirectly limit how often your content gets discovered, referenced, or shared. It also makes it harder for AI-driven experiences to reliably pull and present your content quickly.
Next step
Identify what’s delaying the homepage’s main content render and reduce that load time so the primary content appears sooner.
Reputation
❌ Physical address/identity consistency wasn’t confirmed
What we saw
We weren’t able to identify or confirm a physical address that matches consistently across sources. That makes the brand’s “official identity” less anchored.
Why this matters for AI SEO
Generative engines look for consistent, corroborated identity details when deciding what to trust. When core identity signals are hard to confirm, it can reduce confidence in the entity behind the site.
Next step
Standardize and surface consistent business identity details across the web so they’re easy to verify.
❌ No matching Wikidata entity was found
What we saw
We didn’t see a matching Wikidata listing for the brand. This overlaps with AI readiness, but it also impacts offsite trust and identity confirmation.
Why this matters for AI SEO
Wikidata is one of the clearer “public reference points” AI systems may use to resolve entity questions. If it’s missing, AI has fewer reliable anchors to connect brand details across sources.
Next step
Create or claim a Wikidata entry that matches the brand so offsite entity signals are easier to confirm.
❌ No verified identity anchors on Wikidata
What we saw
We didn’t find official identifiers like a confirmed website reference on Wikidata because there wasn’t a Wikidata entity present to validate against. That leaves a gap in “official source” anchoring.
Why this matters for AI SEO
Identity anchors help AI systems confirm they’ve connected the right site to the right entity. Without those anchors, it’s easier for systems to stay cautious or inconsistent.
Next step
Add official brand identifiers to a verified entity profile so AI systems can connect the dots with more confidence.
❌ No third-party customer reviews were found
What we saw
We didn’t see third-party customer reviews reflected in the available data. That means there’s limited external proof of how others experience or validate the brand.
Why this matters for AI SEO
Independent reviews are a common trust signal that AI systems can use to gauge legitimacy and reputation beyond owned channels. When reviews are absent, authority signals tend to look thinner.
Next step
Build a review footprint on reputable third-party platforms so trust signals exist outside your owned properties.
❌ No concrete review sources could be verified
What we saw
Because no third-party reviews were found, there were also no specific review sources we could validate. That makes it difficult to point to any single “trusted place” where feedback is consistently documented.
Why this matters for AI SEO
Generative engines prefer citing or summarizing information that comes from recognizable, verifiable sources. When there are no review sources to reference, reputation context stays limited.
Next step
Establish reviews on recognizable third-party sources so there’s verifiable reputation data available.
❌ No independent press coverage was identified
What we saw
We didn’t identify independent, third-party press mentions in the data reviewed. That suggests the brand’s visibility may be mostly contained to owned channels.
Why this matters for AI SEO
Independent coverage helps AI systems corroborate notability and authority from sources outside your site and social profiles. Without it, AI has fewer external references to lean on.
Next step
Earn and document independent mentions so there are credible third-party references available for AI systems to draw from.
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 isn’t chunked into readable sections
What we saw
We detected only two sections based on the main section headers, and the sections themselves were extremely short. This makes the piece feel more like fragments than clearly separated blocks of information.
Why this matters for AI SEO
Generative engines work best when they can quickly segment content into coherent parts and map each part to a specific idea. When content isn’t chunked well, it’s harder for AI to extract, summarize, and reuse accurately.
Next step
Restructure the article into multiple clearly defined sections so each segment supports a distinct idea.
❌ No HTML table present (bonus)
What we saw
We didn’t detect a table element in the content. That means there isn’t a compact, structured summary area for key details.
Why this matters for AI SEO
Tables can make it easier for AI systems to identify “definitional” facts and compare attributes without misreading context. Without that structure, important details can be harder to pull cleanly.
Next step
Add a simple table where it makes sense to summarize key attributes or quick-reference information.
❌ Subheadings are not descriptive
What we saw
The subheadings we saw were generic one-word labels (like “name” or “age”) rather than descriptive phrases. That makes it difficult to understand what each section is actually meant to cover.
Why this matters for AI SEO
Generative engines use headings to understand content hierarchy and intent. When headings don’t describe the topic, AI has less guidance on what belongs where, which can lead to weaker summaries.
Next step
Rewrite section headings so they describe the idea of the section in plain language.
❌ Key answers don’t appear early in sections
What we saw
None of the sections began with a substantive opening paragraph; one started with a single-word identifier. This makes the “point” of each section hard to grasp at a glance.
Why this matters for AI SEO
AI systems often prioritize early lines when deciding what a section is about. If the first part doesn’t clearly state the takeaway, the system may miss or misclassify the section’s intent.
Next step
Start each section with a short, clear paragraph that states the main point up front.
❌ Readability and cohesion couldn’t be established
What we saw
The content structure was too fragmentary to judge cohesion well, since one section was a short list and another was effectively empty. There isn’t enough connected narrative in the section structure to evaluate flow.
Why this matters for AI SEO
When content doesn’t read as a cohesive explanation, AI has a harder time generating accurate summaries without dropping nuance or context. Cohesion is one of the signals that supports safe, reliable reuse.
Next step
Expand and connect sections so the content reads like complete, self-contained explanations instead of fragments.
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.
