AI Search Readiness for gaeilgeoir

Strong: 80/100

3 checks need attention. Top fixes are listed below.

Last run May 8, 2026.

80/ 100

Strong

AI engines are likely to cite and recommend you for the right queries.

Passing
14
Warnings
2
Failing
3
Skipped
9

Low awareness mode

ChatGPT doesn't know you yet — here are 5 pages to publish.

This path skips competitor evidence and focuses on giving AI engines enough source material to recognize the brand.

  1. 1. Canonical product definition page with a 25-50 word description.
  2. 2. Best your category for your target buyer page.
  3. 3. top competitor alternatives page
  4. 4. Pricing or plan comparison page with a real table.
  5. 5. Third-party directory/list placements that cite your category.

Top fixes

Highest-impact issues first, ranked by severity.

  • FAQ content presentFailcontent.faq_present

    FAQs cover the long-tail questions AI engines answer for buyers.

    Evidence: No FAQ content detected.

    Fix: Add a 5–10 question FAQ block on the homepage or pricing page covering: what it is, who it's for, pricing, integrations, alternatives, and onboarding. Wrap it in FAQPage JSON-LD.

  • sameAs profile links presentFailentity.same_as_profiles_present

    Schema links your brand to authoritative external profiles AI engines trust.

    Evidence: No sameAs links on the entity node.

    Fix: In your Organization schema, add a sameAs array linking to LinkedIn, X/Twitter, Crunchbase, Wikipedia/Wikidata, GitHub, and major product directories.

  • Terms of service link presentFailauthority.terms_link

    A terms of service link is reachable from the homepage.

    Evidence: No terms / TOS / legal link on the homepage.

    Fix: Add a footer link to Terms of Service.

  • Clean heading hierarchyWarnstructure.heading_hierarchy_clean

    Headings follow H1 → H2 → H3 without skipping levels.

    Evidence: Heading hierarchy skips levels (e.g., H1 directly to H3).

    Fix: Don't skip heading levels. Use H1 → H2 → H3 in order so AI engines parse the document outline correctly.

  • Semantic HTML landmarks presentWarnstructure.semantic_html_present

    Page uses semantic HTML (<main>, <article>, <header>, <footer>) for clean parsing.

    Evidence: Only 1/4 semantic landmarks (looking for main/header/footer/nav).

    Fix: Wrap page regions in semantic tags: <main> for primary content, <header>/<footer> for site chrome, <nav> for navigation. Helps AI parse layout.

Full check breakdown

All 19 evaluated checks across 6 dimensions.

AI visibility

Whether AI engines actually mention you for buyer-intent queries.

  • Brand recognized in AI enginesSkipped

    Skipped — could not derive category/audience from site copy.

  • Brand description accurateSkipped

    Skipped — could not derive category/audience from site copy.

  • Cited in category buying queriesSkipped

    Skipped — could not derive category/audience from site copy.

  • Recommended for primary use caseSkipped

    Skipped — could not derive category/audience from site copy.

  • Surfaces in competitor comparisonsSkipped

    Skipped — could not derive category/audience from site copy.

Answer accuracy

Whether AI engines describe your product without contradicting your site.

  • AI describes pricing accuratelySkipped

    Skipped — could not derive category/audience from site copy.

  • AI describes core features accuratelySkipped

    Skipped — could not derive category/audience from site copy.

  • AI describes target audience accuratelySkipped

    Skipped — could not derive category/audience from site copy.

  • No contradictory claims about the productSkipped

    Skipped — could not derive category/audience from site copy.

Entity signals

Whether AI engines can identify your brand as a distinct entity.

78/100
  • Organization schema presentPass

    Found WebPage with name, url, and description.

  • sameAs profile links presentFail

    No sameAs links on the entity node.

  • Brand name consistent across signalsPass

    Brand name consistent across 4 signals.

  • Canonical URL setPass

    Canonical: https://gaeilgeoir.ai/

  • Logo or hero image declaredPass

    og:image set

Content & citability

Whether your homepage gives AI engines quotable answers.

77/100
  • Meta description in citation rangePass

    Meta description is 134 characters.

  • Quotable product definition near topPass

    Brand + definition pattern detected in first 300 words.

  • FAQ content presentFail

    No FAQ content detected.

  • Pricing visible or linkedPass

    1 pricing rows extracted.

  • Use case or audience statedPass

    Detected 2 audience/use-case signals.

Machine-readability

Whether your markup is machine-readable enough to parse cleanly.

79/100
  • Valid JSON-LD on homepagePass

    15 typed JSON-LD blocks present.

  • Clean heading hierarchyWarn

    Heading hierarchy skips levels (e.g., H1 directly to H3).

  • Semantic HTML landmarks presentWarn

    Only 1/4 semantic landmarks (looking for main/header/footer/nav).

  • Tables or lists for parallel dataPass

    1 table(s) and 12 list(s) on the page.

Trust signals

Whether trust and recency signals are present.

88/100
  • HTTPS enforcedPass

    Site served over HTTPS.

  • Privacy policy link presentPass

    Privacy link: https://gaeilgeoir.ai/privacy-policy/

  • Terms of service link presentFail

    No terms / TOS / legal link on the homepage.

  • Contact channel visiblePass

    Email link: mailto:hello@gaeilgeoir.ai

  • Recency signal presentPass

    Found 2026 or 2025 on the page.

Want the full prioritized fix list?

Sign up free to get a one-shot fix brief tailored to gaeilgeoir. Paid plans add ongoing monitoring, competitor benchmarks, and prioritized fix lists.

gaeilgeoir in AI search: 80/100 visibility score | FactSentry