Transparency
How AI Onboard Easy Applies Its Own Methodology
We rebuilt aionboardeasy.com to visibly follow the same standards the AI Search Readiness Audit recommends. This page is the running record of what changed, why and what is still open.
Methodology version 1.0 · Last reviewed 2026-07-12 · This is internal review, not independent certification.
What was improved
- Semantic heading structureOne H1 per page and hierarchical H2/H3s let assistive tech and AI extract intent.
- Accessible audit formExplicit labels, aria-describedby help text, error summary with focus management and specific submit label.
- Public methodology pageDocuments scoring dimensions and weights so results can be judged.
- Absolute XML sitemapEvery <loc> is a full canonical URL — required by Google Search Console and Bing.
- Robots.txt with sitemap referencePoints crawlers to the sitemap at an absolute URL; sensible disallows only.
- Unique page metadataEvery route has route-specific title, description, canonical and og:* rendered in initial HTML.
- Sitewide structured dataOrganization and WebSite JSON-LD in the root shell; page-specific Article, Service, FAQPage where visible.
- Answer-first summariesEvery major H2 opens with a direct answer paragraph before elaboration.
- Buyer-question coverageFAQ blocks on homepage, GEO guide, GEO vs SEO and pricing use questions buyers actually ask.
- Public sample reportA stable, indexable /sample-report page lets AI systems and prospects preview real output.
- Content update datesMethodology, pillar pages and this page show 'Last reviewed' dates to signal freshness.
- Optional llms.txtA concise, factual llms.txt orients AI crawlers. Not a ranking factor; supplemental only.
- Privacy and termsReal policy pages with clear ownership, not placeholder # links.
Before and after
Real changes made to this site during the rebuild.
| Before | After |
|---|---|
| Relative <loc> paths in sitemap.xml | Absolute canonical URLs at https://aionboardeasy.com/… |
| No <main> landmark; page content nested inside decorative divs | Single <main id="main-content"> landmark in the root shell with skip link |
| Placeholder <label> without htmlFor and placeholder-as-label patterns | Explicit <label htmlFor> on every input, with aria-describedby help text and error summary |
| Generic sitewide title on every route | Unique per-route title, description, canonical and og:url in server-rendered HTML |
| No content architecture for GEO/AEO/AI-search questions | New /generative-engine-optimization, /geo-vs-seo, /ai-search-readiness-checklist and /resources pages |
Public technical artifacts
Known limitations
- Domain-level redirects for http → https and www → apex are DNS-level configurations at the hosting layer; they are documented as owner actions in the SEO setup doc.
- Open Graph share images are generic; per-page branded 1200×630 images are a documented owner follow-up.
- Search Console and Bing Webmaster verification tokens must be supplied by the owner as environment variables (VITE_GOOGLE_SITE_VERIFICATION, VITE_BING_SITE_VERIFICATION).
- GA4 measurement ID is wired but disabled until the owner provides VITE_GA_MEASUREMENT_ID.
- Internal readiness review is not independent certification.