Overview:
On 05/12/26 philnoni.com.ph scored 47% — **Below Average** – Overall, the site feels solid in a few core areas, but some missing clarity signals are holding back how confidently AI can understand and reference it.
Executive summary
Score Breakdown (High Level)
- Discoverability: 100% - The site's technical foundation for discovery is solid and crawl-friendly, though adding media-specific sitemaps would help your visual content get better visibility.
- Structured Data: 58% - The homepage features solid organization and product schema, but we weren't able to find any structured data or author identification for the blog content.
- AI Readiness: 50% - The site is accessible to AI crawlers and offers clear brand context, though it lacks sitemap update timestamps and a Wikidata entity.
- Performance: 50% - The site shows decent loading speed and responsiveness, but it's held back by a very high layout shift score that makes the mobile experience feel unstable.
- Reputation: 12% - We weren't able to find most reputation signals in the provided data, though the site does successfully link to its social profiles.
- LLM-Ready Content: 48% - The site establishes strong expert authority through its founders, but the extremely brief content sections and generic subheadings limit its effectiveness for generative engine optimization.
The main takeaway at a glance
The big picture is that your foundation is visible, but a few missing trust and clarity signals are making it harder for AI to form a confident, consistent understanding of the brand and its content. Most of the gaps aren’t “errors” so much as places where the information isn’t expressed in a way that’s easy for generative systems to interpret and reuse. Below, we’ll walk through the specific areas that didn’t come through clearly—covering content structure, update/identity signals, page experience, and reputation validation. Once those are clearer, it’s much easier for AI tools to summarize you accurately and consistently.
Detailed Report
Discoverability
❌ Image or video sitemap not found
What we saw
We didn’t detect an image sitemap or a video sitemap. This is a common gap for sites that publish a lot of visual content.
Why this matters for AI SEO
When visual assets aren’t clearly surfaced, generative systems may have a harder time discovering and confidently referencing your images or videos in summaries and recommendations.
Next step
Add an image sitemap and/or video sitemap (as applicable) so visual content is easier to discover.
Structured Data
❌ Blog/resource structured data couldn’t be validated
What we saw
The resource/blog page file wasn’t available for review, so we couldn’t confirm whether that page includes structured data. As a result, this part of the site didn’t have enough information for a proper read.
Why this matters for AI SEO
If AI systems can’t reliably interpret your blog content and its context, they’re less likely to reuse it accurately when answering questions or comparing options.
Next step
Make sure the blog/resource page is available for evaluation so its structured data can be confirmed.
❌ Blog post author wasn’t confirmed
What we saw
Because the resource/blog page wasn’t provided, we weren’t able to verify that the post has a clear, non-generic author. This leaves authorship unclear from the data we had.
Why this matters for AI SEO
Clear authorship helps AI systems judge credibility and attribute information correctly, especially for health-related topics where trust matters.
Next step
Ensure each blog/resource post includes a clearly identified author that can be validated.
❌ Author profile links weren’t confirmed
What we saw
We couldn’t confirm whether the author information includes profile/identity links, since the resource/blog page wasn’t available for review. That leaves the author’s broader identity unverified in this snapshot.
Why this matters for AI SEO
When author identity isn’t easy to corroborate, AI systems tend to be more cautious about citing or summarizing the content as authoritative.
Next step
Provide consistent author identity links where appropriate so attribution can be verified.
AI Readiness
❌ Update timestamps missing from the sitemap
What we saw
The sitemap was found, but it didn’t include page update timestamps. That makes it less clear when content has changed.
Why this matters for AI SEO
AI crawlers use update signals to understand freshness, prioritize recrawls, and decide which version of a page to trust and reference.
Next step
Add update timestamps to sitemap URLs so page freshness is clearly communicated.
❌ Brand Wikidata entity not found
What we saw
No Wikidata item ID was identified for the brand. From this dataset, there wasn’t a clear entity to anchor the brand to.
Why this matters for AI SEO
Entity anchors help generative systems connect your brand to a consistent identity, which can reduce confusion and improve how often you’re referenced accurately.
Next step
Confirm whether a Wikidata entity exists for the brand and connect it consistently where appropriate.
Performance
❌ Homepage layout appears visually unstable
What we saw
The homepage showed significant visual shifting as the page loads, which can make the experience feel jumpy. This stood out as the main performance issue in the snapshot.
Why this matters for AI SEO
A shaky on-page experience can reduce user trust and engagement, which indirectly affects how confidently your content gets consumed and referenced.
Next step
Stabilize the homepage layout during load so key content stays in place as the page renders.
Reputation
❌ Client sentiment couldn’t be confirmed
What we saw
The report packet didn’t include enough information to confirm whether there are affirmed negative client assertions. As a result, client sentiment wasn’t verifiable in this run.
Why this matters for AI SEO
When sentiment signals are unclear, AI systems have less confidence summarizing how customers feel about the brand.
Next step
Collect and provide verifiable client-sentiment signals so this can be confirmed.
❌ Employee sentiment couldn’t be confirmed
What we saw
We didn’t have enough information in the packet to confirm whether there are affirmed negative employee assertions. This leaves employee sentiment unclear in the current output.
Why this matters for AI SEO
Employee-related narratives can influence how AI systems describe a company’s credibility and culture, especially in brand overviews.
Next step
Provide verifiable employee-sentiment context so this can be assessed reliably.
❌ Brand recognition signals weren’t confirmed
What we saw
The packet didn’t include enough data to confirm whether the brand is recognized consistently across multiple AI models. That makes the recognition picture incomplete here.
Why this matters for AI SEO
Recognition consistency influences whether AI systems confidently “know who you are” and describe you accurately without hedging.
Next step
Ensure brand recognition signals can be validated across the sources used for reputation checks.
❌ Brand identity consistency wasn’t confirmed
What we saw
We couldn’t verify whether the brand identity is consistent, because the packet didn’t include the necessary consensus/contrast details. This leaves potential identity conflicts unverified.
Why this matters for AI SEO
If identity signals aren’t consistent, AI summaries can drift—mixing details, mislabeling the brand, or presenting an unclear description.
Next step
Provide consistent, verifiable brand identity signals so agreement can be confirmed.
❌ Wikidata presence wasn’t confirmed (reputation context)
What we saw
In the reputation dataset, Wikidata matching details weren’t available, so this check couldn’t be confirmed from that angle. This overlaps with the broader brand-entity visibility story.
Why this matters for AI SEO
A clear entity footprint helps AI systems connect the dots between your site and trusted third-party identity references.
Next step
Confirm and document the brand’s entity references so this portion of reputation can be validated.
❌ Official identity anchors on Wikidata weren’t confirmed
What we saw
The packet didn’t include enough information to verify whether Wikidata includes official identity anchors (like an official website reference). That leaves entity verification incomplete.
Why this matters for AI SEO
Official anchors help AI systems trust they’re connecting your brand to the right entity, especially when similar names exist.
Next step
Ensure any entity profile includes clear official identity anchors that can be validated.
❌ Third-party reviews weren’t confirmed
What we saw
We didn’t have enough information to confirm whether independent third-party reviews exist. This makes the external feedback layer unclear.
Why this matters for AI SEO
AI systems often lean on third-party validation when summarizing products and brands, especially for “is it legit?” style queries.
Next step
Provide verifiable third-party review signals so they can be confidently recognized.
❌ Review sources weren’t confirmed
What we saw
The dataset didn’t include enough detail to confirm that review sources are concrete and countable. That means we can’t clearly point to where reviews live.
Why this matters for AI SEO
When review sources are vague, AI systems may avoid referencing them or may summarize sentiment with extra caution.
Next step
Document concrete review sources so AI systems (and people) can trace the claims back to a real place.
❌ Consensus on major social profiles wasn’t confirmed
What we saw
The packet didn’t include enough information to confirm whether there’s consensus on the brand’s major social profiles. This leaves some ambiguity about “official” accounts.
Why this matters for AI SEO
Clear official profiles help AI systems attribute content to the right brand and reduce the chances of mix-ups with lookalike accounts.
Next step
Ensure official social profiles are consistently referenced so consensus can be confirmed.
❌ Independent press/coverage wasn’t confirmed
What we saw
We didn’t have enough information to confirm independent press mentions or coverage. That external validation layer wasn’t clearly present in this run.
Why this matters for AI SEO
Independent coverage is a common trust signal AI systems use when summarizing a brand’s legitimacy and prominence.
Next step
Provide verifiable independent coverage references so they can be recognized.
❌ Owned press/press releases weren’t confirmed
What we saw
The packet didn’t include enough information to confirm owned press mentions or press releases. So we couldn’t validate whether there’s a consistent place for official announcements.
Why this matters for AI SEO
Owned announcements can help AI systems understand what the brand considers “official,” especially around launches, claims, and milestones.
Next step
Make owned press/announcement sources easy to verify so they can be incorporated into brand understanding.
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 are too thin for AI-friendly parsing
What we saw
The main content is split into very short sections, with each block feeling more like a quick snippet than a complete thought. That makes the page harder to interpret as a set of fully developed points.
Why this matters for AI SEO
Generative systems summarize best when each section has enough substance to extract a clear claim, supporting context, and a takeaway.
Next step
Rewrite core sections so each one carries a complete idea with enough context to stand on its own.
❌ No table-based summary was found
What we saw
We didn’t see a visible table on the page. That removes one of the easiest “at-a-glance” formats for comparing claims, ingredients, or differences.
Why this matters for AI SEO
Tables give AI systems a structured way to extract comparisons and key facts without guessing what belongs together.
Next step
Add a simple comparison or key-points table where it naturally supports the topic.
❌ Subheadings are mostly generic
What we saw
Many subheadings read like general labels instead of describing what the section actually covers. That makes the content feel fragmented and harder to scan.
Why this matters for AI SEO
Descriptive subheadings help AI systems map the page into meaningful concepts, which improves summarization and accurate quoting.
Next step
Update headings so they clearly state the question or point each section answers.
❌ Key answers don’t show up early in most sections
What we saw
Most sections don’t lead with a clear, fully formed opening explanation. Instead, the “so what?” often arrives late or stays implied.
Why this matters for AI SEO
AI systems tend to rely heavily on early, direct statements to understand what a section is claiming and how to summarize it.
Next step
Restructure sections so the first paragraph clearly states the main takeaway in plain language.
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.
