Overview:
On 04/19/26 nike.com scored 40% — **Weak** – Overall, the site is easy to access, but several gaps make it harder for AI systems to confidently understand and trust what they’re seeing.
Executive summary
Score Breakdown (High Level)
- Discoverability: 100% - Overall, this section looks to be in good shape, although we didn't see an image or video sitemap.
- Structured Data: 58% - The homepage is well-equipped with valid Organization and WebSite schema, though we weren't able to find any structured data or author details for the blog content.
- AI Readiness: 67% - This looks mostly solid, but we weren't able to find a Wikidata entity to help anchor the brand's identity.
- Performance: 17% - Mobile performance ran into significant issues with load times and responsiveness, though visual stability on the homepage was excellent.
- Reputation: 0% - Overall, this section looks to be in poor shape because we couldn't find official identity anchors or social links, and the key consensus data we needed for scoring was missing from the packet.
- LLM-Ready Content: 40% - The page functions as a visual navigation hub but lacks the structured text blocks and descriptive headings required for effective AI content synthesis.
Where things stand at a glance
The big picture is that the site is generally accessible, but a few core signals that help AI systems trust and interpret the brand and its content aren’t coming through clearly. What stands out most is that reputation and identity context looks thin in the data we reviewed, and the content snapshot reads more like visual navigation than a page built to be easily summarized. Below, we’ll walk through the specific areas where information was missing or unclear so you can see exactly what’s holding visibility back. None of this is unusual—it’s the kind of gap that shows up when brand and content signals aren’t consistently reinforced across the full site.
Detailed Report
Discoverability
❌ Image or video discovery support not found
What we saw
We didn’t see any dedicated image or video sitemap available for the site. That means visual content may not be getting the clearest path to discovery.
Why this matters for AI SEO
Generative engines often pull from images and video when summarizing brands, products, and topics. If visual assets are harder to surface and understand at scale, it can limit how often they’re used or referenced.
Next step
Add an image and/or video sitemap so visual content is easier for search and AI systems to discover.
Structured Data
❌ Resource/blog page schema wasn’t detected
What we saw
We weren’t able to evaluate structured data for the resource/blog page because the resource page HTML wasn’t available in the provided inputs. As a result, we couldn’t confirm whether that content has the same level of machine-readable detail as the homepage.
Why this matters for AI SEO
AI systems rely on consistent, clear structured context to interpret what a page is and how it relates to the brand. When content pages don’t carry that clarity, they’re more likely to be misunderstood or underused.
Next step
Ensure your resource/blog pages include structured data that clearly describes the content and how it connects to the brand.
❌ Resource/blog author attribution wasn’t confirmable
What we saw
Because the resource/blog page HTML wasn’t available in this run, we couldn’t find a clear, non-generic author on the content page. That leaves authorship unclear at the content level.
Why this matters for AI SEO
When authorship is unclear, AI systems have a harder time assessing credibility and assigning the content to a trusted source. That can reduce how confidently the content is cited or summarized.
Next step
Make sure each resource/blog post clearly names a specific author (not just a generic brand label).
❌ Author identity links weren’t present
What we saw
We didn’t see author schema that includes external identity references (like profile links), because author schema couldn’t be confirmed without the resource/blog page HTML. In practice, this means author identity isn’t strongly supported in machine-readable form.
Why this matters for AI SEO
Generative engines tend to trust entities more when they can connect them to consistent, verifiable profiles across the web. Without those links, author trust and attribution signals are weaker.
Next step
Add author structured data that connects the author to consistent external profiles.
AI Readiness
❌ Wikidata entity for the brand wasn’t found
What we saw
We couldn’t detect a Wikidata item ID for the brand in the data provided. That leaves a missing “public identity anchor” that some AI systems use to confirm who a brand is.
Why this matters for AI SEO
When a brand is tied to a recognized entity record, AI systems can more easily disambiguate it from lookalikes and keep facts consistent. Without that anchor, brand understanding can be more fragmented.
Next step
Create or confirm a Wikidata entity for the brand and ensure it clearly matches the official brand identity.
Performance
❌ Mobile responsiveness lag was detected
What we saw
On mobile, the page showed significant delay between a user trying to interact and the site responding. That generally points to a heavier-than-ideal experience during load.
Why this matters for AI SEO
When a site feels sluggish, users and crawlers may engage less deeply, which can reduce the visibility and usefulness of the content that AI systems can reliably pull from. Performance friction can also limit how well content gets processed at scale.
Next step
Reduce mobile interaction lag so the page responds quickly while it’s loading.
❌ Main content loaded very slowly on mobile
What we saw
The site took a long time before the primary on-page content appeared on mobile. This suggests users are waiting too long to see the “meat” of the page.
Why this matters for AI SEO
If key content is slow to show up, it can reduce engagement and make it harder for systems to consistently capture and reuse the most important information. That can indirectly limit how often the site’s content is surfaced.
Next step
Improve mobile load timing so the main content becomes visible much earlier in the visit.
❌ Overall mobile performance came back low
What we saw
The overall mobile performance result landed in a range that indicates the page is doing too much heavy lifting before it feels usable. This lines up with the slower loading and responsiveness signals.
Why this matters for AI SEO
AI-driven discovery still depends on content being accessible and usable in real-world conditions. When the overall experience is strained, it can reduce how confidently systems surface the content as a good reference.
Next step
Bring overall mobile performance into a healthier range by reducing what slows the page down during initial load.
Reputation
❌ Client sentiment signal wasn’t verifiable
What we saw
We couldn’t confirm whether there are affirmed negative client assertions because the required reconciled data wasn’t available in this run. In other words, we didn’t have enough information to validate this trust signal.
Why this matters for AI SEO
Generative engines tend to weigh credibility and sentiment signals when deciding how to describe a brand. When those signals aren’t verifiable, the brand’s trust picture can be less complete.
Next step
Compile and confirm a clear set of client feedback signals that AI systems can reliably reference.
❌ Employee sentiment signal wasn’t verifiable
What we saw
We couldn’t confirm whether there are affirmed negative employee assertions because the required reconciled data wasn’t available in this run. This leaves another part of the trust picture unconfirmed.
Why this matters for AI SEO
AI systems often summarize brands using a blend of public sentiment and third-party signals. Missing or unverified signals can make brand summaries less consistent or less confident.
Next step
Gather and validate employee reputation signals in a way that’s easy to verify across sources.
❌ Brand recognition across AI systems wasn’t confirmable
What we saw
We weren’t able to confirm broad brand recognition because the recognition count field wasn’t available in the inputs. That means we can’t validate whether multiple systems consistently recognize the brand.
Why this matters for AI SEO
When recognition is consistent across systems, brands tend to show up more reliably in AI answers. If recognition can’t be confirmed, visibility may be more inconsistent.
Next step
Validate how consistently the brand is recognized across major AI surfaces and document the findings.
❌ Brand identity consistency wasn’t confirmed
What we saw
We couldn’t confirm consistent brand identity details (like name, domain, and address) because the consensus/conflict fields weren’t available in the inputs. That left identity consistency unverified.
Why this matters for AI SEO
AI systems are more confident when core brand details are consistent across sources. Unverified identity consistency can lead to confusion or mismatched brand information.
Next step
Audit and confirm that the brand’s key identity details match cleanly across major public references.
❌ Wikidata brand match wasn’t found
What we saw
We didn’t find a matching Wikidata entry for the brand in the provided data. That removes a common entity reference point used for verification.
Why this matters for AI SEO
Wikidata is one of the places AI systems may use to resolve “who is this brand?” questions. Without a match, it can be harder to keep brand facts aligned.
Next step
Create or claim a Wikidata record that correctly represents the brand.
❌ Official identity anchors weren’t confirmed
What we saw
We couldn’t confirm that Wikidata includes official identity anchors because those fields weren’t available in the provided inputs. This leaves official verification signals unclear.
Why this matters for AI SEO
When official identity anchors are present and consistent, AI systems can connect the dots faster and reduce ambiguity. Missing confirmation weakens that verification chain.
Next step
Ensure the brand’s primary identity anchors are clearly represented in trusted entity references.
❌ Third-party reviews weren’t found
What we saw
We couldn’t confirm the presence of third-party reviews or customer feedback because the relevant field wasn’t available in the inputs. As a result, we didn’t see a clear external feedback footprint.
Why this matters for AI SEO
External feedback and reviews help AI systems build a more balanced view of a brand. When those signals aren’t present or verifiable, AI summaries can skew sparse or generic.
Next step
Confirm and surface credible third-party feedback sources associated with the brand.
❌ Review sources weren’t confirmable
What we saw
We couldn’t confirm whether review sources are concrete because the source count field wasn’t available in the provided inputs. That makes it hard to validate where feedback is coming from.
Why this matters for AI SEO
AI systems trust reviews more when they’re clearly tied to recognizable platforms or sources. If sources aren’t concrete, credibility signals are harder to establish.
Next step
Document the specific review platforms and sources that represent real customer feedback.
❌ Consensus on official social profiles wasn’t confirmed
What we saw
We couldn’t confirm consensus on major social profiles because the relevant consensus field wasn’t available in the provided inputs. That leaves uncertainty around which profiles are “official.”
Why this matters for AI SEO
Official social profiles are a common identity signal that AI systems use to validate brands. Without a clear consensus signal, identity confidence can drop.
Next step
Confirm which social profiles are official and ensure they’re consistently referenced across trusted sources.
❌ Homepage social profile links weren’t found
What we saw
We didn’t see links from the homepage pointing to major social platforms. This is a common gap that removes an easy-to-verify identity connection.
Why this matters for AI SEO
When official social profiles are clearly linked, AI systems can more confidently validate brand ownership and reduce confusion with unofficial accounts. Missing links make that verification harder.
Next step
Add clear homepage links to the brand’s official social profiles.
❌ Independent press coverage wasn’t confirmed
What we saw
We couldn’t confirm independent (offsite) press or coverage because the relevant field wasn’t available in the inputs. That left external coverage signals unverified.
Why this matters for AI SEO
Independent coverage helps generative engines establish broader legitimacy and context beyond the brand’s own site. Without those signals, AI summaries can be thinner or less confident.
Next step
Identify and confirm credible independent coverage sources that reference the brand.
❌ Owned press or press releases weren’t confirmed
What we saw
We couldn’t confirm owned/onsite press or press releases because the relevant field wasn’t available in the inputs. That means we couldn’t validate whether the brand has a clear press footprint on its own channels.
Why this matters for AI SEO
A clear owned press footprint can help AI systems understand major announcements, timelines, and brand milestones. When it’s missing or unclear, those details are easier to miss.
Next step
Confirm whether the brand has an owned press/announcements area and ensure it’s easy to recognize.
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
❌ Recent update signal wasn’t clear
What we saw
We didn’t see a clear “last updated” signal that indicates the content has been refreshed recently. The available dating signals didn’t support a recent update.
Why this matters for AI SEO
AI systems tend to prefer content that’s clearly current when summarizing fast-moving topics or brand moments. If freshness isn’t clear, the page may be treated as less reliable for up-to-date answers.
Next step
Add a clear on-page update date (when relevant) so content freshness is easy to understand.
❌ Sections were too thin to build context
What we saw
The content was broken into many small fragments, with sections that are very short on average. That creates a “snackable” layout, but it’s light on explanatory depth.
Why this matters for AI SEO
Generative engines do best when they can extract complete ideas in coherent blocks. When sections are very thin, it’s harder for AI to form confident summaries or reuse the content accurately.
Next step
Rewrite key sections into fuller, self-contained blocks that explain the main idea clearly.
❌ Table-style summary wasn’t present
What we saw
We didn’t see any table element used to summarize key details. That removes one of the easiest formats for quick scanning and structured extraction.
Why this matters for AI SEO
Tables can make key facts and comparisons more straightforward for AI systems to interpret and reuse. Without them, important details can be more scattered and easier to miss.
Next step
Add a simple table where it naturally fits to summarize key information.
❌ Subheadings were too generic
What we saw
The subheadings we saw were very short and didn’t describe what the following sections are actually about. Labels like these don’t carry much meaning on their own.
Why this matters for AI SEO
Subheadings help AI systems map the structure and topics of a page quickly. If headings are vague, the page becomes harder to categorize and summarize accurately.
Next step
Replace generic subheads with descriptive headings that reflect the content in each section.
❌ Key answers didn’t appear early in sections
What we saw
Section openings were very brief and didn’t introduce the main takeaway upfront. The content often made the reader (and AI) hunt for what the section is trying to say.
Why this matters for AI SEO
Generative engines look for quick, clear statements that answer “what is this?” and “why does it matter?” early on. When that context doesn’t show up quickly, extraction quality can drop.
Next step
Adjust section intros so the main point is stated clearly at the start.
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.
