Search Health

Indexing, crawlability, answer-engine readiness and AI-search access for the public site.

Technical SEO
80 /100
Content SEO
2 /100
AEO
50 /100
AI Search Readiness
50 /100
Indexable public pages
8
Noindex pages
0
Published articles in sitemap
183
Crawl & AI access
  • robots.txt reachable
  • Googlebot allowed
  • Bingbot allowed
  • OAI-SearchBot allowed (ChatGPT Search)
  • Sitemap declared in robots.txt
  • Admin areas disallowed
  • Sitemap index reachable
  • Media & Press sitemap has URLs
  • Media & Press sitemap carries hreflang
  • Public pages sitemap reachable
  • No admin URLs in sitemaps
  • No legacy duplicate routes in sitemaps
Sitemap & indexing match
  • Every published article is in the sitemap
  • Every indexable public page is in the sitemap
  • No noindex page appears inside a sitemap
  • No redirect chains in sitemaps (all URLs are canonical)
Answer engine (AEO) coverage
  • Home answers published (6 questions)
  • About answers published (2 questions)
  • Every answer has an independent Thai version
  • Answers exposed as FAQPage structured data linked to the Person entity
  • Identity, AI, EOS / Emotional Scale AI, Better Half AI and Zoul all answered
  • Meditation, human development and portfolio answered
Platform limitations — not fixable in app code
  • Platform limitationServer-side rendered metadata (SSR)

    This Base44 app injects title, meta, canonical, hreflang and JSON-LD client-side after React mounts. Google renders JavaScript, but crawlers that do not execute JS see an empty head. This cannot be marked PASS.

  • Platform limitationTrue HTTP 301 redirects

    Redirects are client-side route replacements, not 301 responses. Link equity transfer is weaker than a server 301. Cleanest available fallback is implemented: canonical URL normalisation + client redirect + canonical tag on the destination.

  • Platform limitationLCP image preload and cache headers

    Hero images come from the CMS at runtime, and the platform controls response caching headers, so a build-time <link rel="preload"> for the largest image and custom Cache-Control values are not available. Implemented instead: AVIF/WebP responsive delivery, eager + high fetch priority on hero images, lazy loading everywhere below the fold, and deferred third-party tags.

  • Platform limitationHTTP 410 Gone for deleted content

    No server status code control, so removed articles cannot return 410. They are removed from the sitemap and return the 404 page instead.

Actionable issues (2141)
2081 more issues of the same kinds — fix the ones above first, then re-run the audit.