Detailed Report:

GEO Assessment — maya-constructioninc.com

(Score: 55%) — 09/27/26


Overview:

On 09/27/26 maya-constructioninc.com scored 55% — **Fair** – Overall, the site has a solid base for being found, but a few credibility and content clarity gaps are holding back stronger AI visibility.

Website Screenshot

Executive summary

Most of the issues showed up around trust/identity signals and how content is framed for quick reuse, with some missing verification cues and inconsistent brand details across sources. Beyond that, the gaps are spread across performance, structured data on resource content, and a couple of discoverability and entity signals, so the overall picture is mixed rather than isolated to one area.

Score Breakdown (High Level)

  • Discoverability: 83% - The site’s foundation is in great shape with clear metadata and an XML sitemap, though it's missing a dedicated sitemap for images or video.
  • Structured Data: 58% - The homepage features well-structured organization and local business schema, though we weren't able to confirm author or article markup due to missing resource page data.
  • AI Readiness: 67% - The site's technical foundation is in great shape with open crawler access and a healthy sitemap, but it lacks a Wikidata profile to help AI engines fully anchor the brand's identity.
  • Performance: 50% - Mobile performance is generally solid with great responsiveness and layout stability, though the initial visual load time on the homepage landed in the poor range.
  • Reputation: 50% - While the brand is recognized by multiple models and shows strong third-party review signals, inconsistent offsite identity data and a lack of social links on the homepage are holding back its reputation score.
  • LLM-Ready Content: 40% - The page is well-organized and recently updated, though it misses some technical markers like descriptive subheadings and external citations that help AI systems process content more effectively.

What stands out most overall

The big picture is that the site is generally easy to find and navigate, but it’s not sending as many clear trust and content-source signals as it could. The gaps here are less about “errors” and more about making it easier for AI systems to confidently verify who you are and quickly extract the right takeaways from your content. The next sections walk through the specific areas where signals were missing or inconsistent across discoverability, structured data, AI readiness, performance, reputation, and on-page content structure. None of this is unusual—these are common, fixable blind spots when a site hasn’t been tuned for AI-driven discovery yet.

Detailed Report

Discoverability

❌ Image/video sitemap not found

What we saw

We didn’t find an image sitemap or video sitemap in the available sitemap set. That means visual content isn’t being explicitly surfaced in a way that’s easy to pick up and organize.

Why this matters for AI SEO

Generative engines rely on clear discovery paths to understand what content exists and how it relates to the business. When visual assets aren’t clearly exposed, it can limit how often they’re found and reused in AI-driven answers.

Next step

Publish dedicated image and/or video sitemaps and make sure they’re referenced alongside your main sitemap.

Structured Data

❌ Resource/blog page markup couldn’t be verified

What we saw

We weren’t able to access the specific resource/blog page content needed for this check, so we couldn’t confirm whether that page includes structured data. In practice, this leaves a blind spot in how consistently your content is described beyond the homepage.

Why this matters for AI SEO

AI systems pull a lot of context from consistent, page-level signals—especially on content pages where detailed explanations live. When that information can’t be confirmed or isn’t present, it can reduce how confidently the page is understood and referenced.

Next step

Ensure your resource/blog templates include structured data that clearly describes each article/page.

❌ Blog post author identity wasn’t confirmable

What we saw

We couldn’t confirm a clear, non-generic author for the resource/blog content because the required page data wasn’t available. As a result, the author identity signal for content pages couldn’t be evaluated.

Why this matters for AI SEO

When AI engines can’t clearly connect content to a real author identity, they have fewer trust cues to lean on. That can make it harder for your content to be treated as a reliable source in generated responses.

Next step

Add clear author attribution on resource/blog posts and make sure it’s consistently represented in the page’s structured data.

❌ Author “sameAs” links weren’t present

What we saw

No author-related “sameAs” links could be evaluated because the resource/blog author data wasn’t available. This means there wasn’t a way to confirm connected identity profiles for an author within structured data.

Why this matters for AI SEO

Generative engines tend to trust content more when people and brands are easy to verify across the web. Without connected identity references, it’s harder for systems to confidently disambiguate and validate who created the content.

Next step

Include “sameAs” links for content authors where applicable so their identity is easier to corroborate.

AI Readiness

❌ No Wikidata entity found for the brand

What we saw

We didn’t see a verified Wikidata entity associated with the brand. In other words, there wasn’t a clear, standardized entity reference we could tie back to the business.

Why this matters for AI SEO

AI systems often lean on entity databases to confirm “this is a real, distinct business” and reduce confusion with similarly named companies. When that entity reference is missing, the brand can be harder to validate and consistently represent.

Next step

Establish a verified Wikidata entity for the brand that clearly matches the business identity.

Performance

❌ Homepage main content loads a bit slowly at first

What we saw

The homepage’s initial “main content” load timing came in slower than expected, making the first meaningful view feel delayed. This was the primary performance issue flagged in the evaluation.

Why this matters for AI SEO

When pages feel slow to load, crawlers and users may engage less deeply, which can reduce how reliably content is discovered and interpreted over time. A faster first impression also makes it easier for systems to extract content consistently.

Next step

Reduce whatever is delaying the homepage’s initial main-content render so the page becomes usable sooner.

Reputation

❌ Negative client assertions were surfaced

What we saw

At least one model identified negative client assertions connected to the brand. That introduces a visible “trust drag” in the broader brand narrative.

Why this matters for AI SEO

Generative engines weigh reputation cues when deciding what to recommend or cite. Even a small amount of surfaced negativity can make the brand less likely to be presented confidently.

Next step

Identify the specific source(s) behind the negative client assertions and address them directly with clear, public-facing resolution context where appropriate.

❌ Brand identity details appear inconsistent across sources

What we saw

We saw significant conflicts in the business address across different sources (including Florida and California), which didn’t align cleanly with Maryland-based onsite information. This creates confusion about which listing details are definitive.

Why this matters for AI SEO

When identity signals don’t line up, AI systems may hesitate to confidently describe the business or may mix details from different entities. Consistency is a big part of being treated as a clear, trustworthy brand.

Next step

Standardize the official business name/address details across the web so the same identity shows up everywhere.

❌ No matching Wikidata entity for the brand

What we saw

We didn’t find a Wikidata entry that matches the brand. This leaves an entity-level “anchor” missing from your offsite identity signals.

Why this matters for AI SEO

Entity references help generative engines disambiguate brands and keep details consistent in answers. Without that anchor, it’s easier for systems to second-guess or confuse the business with similar names.

Next step

Create or claim a Wikidata entity that clearly maps to the brand and its official details.

❌ Official identity anchors in Wikidata are missing

What we saw

Because no Wikidata entity was found, the expected “official identity anchors” tied to that entity weren’t present either. That means there’s no standardized, third-party reference point connecting the brand to its core identifiers.

Why this matters for AI SEO

When AI systems can’t confirm official identifiers through a stable entity record, they rely more heavily on mixed web mentions—which is where inconsistencies tend to creep in. That can lead to less reliable brand representation.

Next step

Once a Wikidata entity exists, ensure it includes the brand’s key official identifiers and references.

❌ Homepage doesn’t link out to major social profiles

What we saw

We didn’t find homepage links pointing to major social platforms (like Facebook or LinkedIn). That removes a common, easy-to-verify set of brand reference points.

Why this matters for AI SEO

Consistent, official profiles help AI systems confirm the brand’s legitimacy and connect related mentions back to the same entity. Without clear links, systems have less confidence they’ve found the “right” profiles.

Next step

Add clear homepage links to the brand’s official social profiles so they’re unambiguous.

❌ No independent third-party coverage was found

What we saw

We didn’t see independent press or third-party coverage identified for the brand in this evaluation. This limits the amount of external validation visible in the brand’s footprint.

Why this matters for AI SEO

Generative engines often look for corroboration from sources outside a brand’s own website. When that independent layer is thin or missing, it can reduce how confidently the brand is summarized or recommended.

Next step

Build a clearer footprint of independent mentions so there are more third-party references supporting the brand story.

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

Persona Targeting: This content appears to be aimed at homeowners in the Silver Spring and Montgomery County area who are comparing professional remodeling options and looking for a credible local team.

❌ No clear individual author

What we saw

We didn’t see an explicit author name tied to an individual (either on-page or via article markup), beyond the organization itself. That makes the source of the information feel more anonymous than it needs to.

Why this matters for AI SEO

Generative engines tend to trust content more when they can attribute it to a real person with a consistent identity. Missing authorship can limit how confidently the page is summarized, cited, or reused.

Next step

Add a clear, non-generic author name to the article and keep it consistent wherever the article appears.

❌ No non-social outbound citations

What we saw

The only outbound links we saw were platform-style links (like Google Business), and we didn’t find external citations to third-party resources. That limits the contextual “trail” that supports the claims on the page.

Why this matters for AI SEO

AI systems look for signals that content is grounded in a broader, verifiable context. When there are no external references, it can be harder for models to treat the content as well-supported.

Next step

Include a small number of relevant third-party citations that support key points on the page.

❌ No table-based structure for key info

What we saw

We didn’t find any HTML tables on the page. That means there’s no “at-a-glance” structured layout for comparisons, specs, or quick summaries.

Why this matters for AI SEO

Tables can make it easier for generative engines to extract precise facts and relationships without guessing. Without that structure, key details may be harder to pull cleanly.

Next step

Add a simple table where it naturally fits (like services, project types, timelines, or comparison points).

❌ Subheadings weren’t descriptive enough

What we saw

Some subheadings were very short or generic, and others didn’t clearly align with the wording used in the section content. This makes the page feel organized for humans, but less “self-labeling” for AI extraction.

Why this matters for AI SEO

Generative engines often use headings to understand what each section is actually about. If headings are vague, models can miss or misclassify what the section contains.

Next step

Rewrite section subheadings so they clearly state what the section answers or covers.

❌ Key answers don’t show up early enough

What we saw

A couple of sections (like “Recent Projects” and “Reviews”) didn’t lead with a substantial intro that explains the point of the section upfront. That can make the page feel scan-friendly, but context-light at the top of sections.

Why this matters for AI SEO

AI systems often grab early text to decide what a section is about and whether it contains a usable answer. If the first lines are thin, important context may not get picked up.

Next step

Add a short, specific lead-in at the start of each section that states the main takeaway right away.

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.

Share This Report With Your Team

Enter email addresses to send this assessment report to colleagues