AI Search Readiness for OC Maker
Weak: 57/100
3 checks need attention. Top fixes are listed below.
Last run May 6, 2026.
Weak
AI engines struggle to identify, describe, or recommend you reliably.
- Passing
- 9
- Warnings
- 6
- Failing
- 3
- Skipped
- 10
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. Canonical product definition page with a 25-50 word description.
- 2. Best your category for your target buyer page.
- 3. top competitor alternatives page
- 4. Pricing or plan comparison page with a real table.
- 5. Third-party directory/list placements that cite your category.
Top fixes
Highest-impact issues first, ranked by severity.
- Organization schema presentFailentity.organization_schema_present
Your site exposes an Organization or product entity AI engines can read.
Evidence: No Organization, Product, or SoftwareApplication JSON-LD on the homepage.
Fix: Add JSON-LD with @type Organization (or Product / SoftwareApplication for SaaS) to the homepage. Include name, url, description, and logo.
- Quotable product definition near topFailcontent.product_definition_likely
A clear definition of what your product is appears in the first 300 words AI engines extract.
Evidence: No clear definition pattern in the first 300 words.
Fix: Add a 25–50 word definition above the fold matching the template: "<Brand> is <category> that <primary function>, <key differentiator>." AI engines often cite this verbatim.
- Valid JSON-LD on homepageFailstructure.json_ld_valid
Homepage exposes parseable JSON-LD blocks AI engines can read.
Evidence: No JSON-LD <script> blocks on the homepage.
Fix: Add JSON-LD with @type Organization (or SoftwareApplication / Product). Without structured data, AI engines fall back to heuristics and miss your brand definition.
- FAQ content presentWarncontent.faq_present
FAQs cover the long-tail questions AI engines answer for buyers.
Evidence: 16 FAQ entries but no FAQPage JSON-LD schema.
Fix: Wrap your FAQ section in FAQPage JSON-LD so AI engines parse Q/A pairs cleanly.
- Pricing visible or linkedWarncontent.pricing_visible
Pricing is visible or one click away — AI engines extract this constantly.
Evidence: Pricing link found (/pricing) but no pricing table on the homepage.
Fix: Surface a pricing summary (3 tiers, headline price each) on the homepage or above-the-fold of /pricing. AI engines pull from tables far more reliably than from prose.
Full check breakdown
All 18 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.
- Organization schema presentFail
No Organization, Product, or SoftwareApplication JSON-LD on the homepage.
- sameAs profile links presentSkipped
Skipped — no entity node to attach sameAs to.
- Brand name consistent across signalsPass
Brand name consistent across 3 signals.
- Canonical URL setPass
Canonical: https://www.ocmaker.net
- Logo or hero image declaredPass
og:image set
Content & citability
Whether your homepage gives AI engines quotable answers.
- Meta description in citation rangeWarn
Meta description is 165 characters (target 50–160).
- Quotable product definition near topFail
No clear definition pattern in the first 300 words.
- FAQ content presentWarn
16 FAQ entries but no FAQPage JSON-LD schema.
- Pricing visible or linkedWarn
Pricing link found (/pricing) but no pricing table on the homepage.
- Use case or audience statedPass
Detected 3 audience/use-case signals.
Machine-readability
Whether your markup is machine-readable enough to parse cleanly.
- Valid JSON-LD on homepageFail
No JSON-LD <script> blocks on the homepage.
- Clean heading hierarchyWarn
Heading hierarchy skips levels (e.g., H1 directly to H3).
- Semantic HTML landmarks presentPass
3/4 semantic landmarks present.
- Tables or lists for parallel dataWarn
Only 2 list(s) and no tables.
Trust signals
Whether trust and recency signals are present.
- HTTPS enforcedPass
Site served over HTTPS.
- Privacy policy link presentPass
Privacy link: https://docs.google.com/document/d/1BkO0QWTmBB9XdKlvvVmU7w3byTpUvHZQsEJ09XdgRtI/edit?usp=sharing
- Terms of service link presentPass
Terms link: https://docs.google.com/document/d/1s_R-i9iXCtSaYyMOUFGd5Y7_0J0D70M6OPKbblBOlsw/edit?usp=sharing
- Contact channel visiblePass
Contact page: /contact
- Recency signal presentWarn
Most recent year on page: 2020.
Want the full prioritized fix list?
Sign up free to get a one-shot fix brief tailored to OC Maker. Paid plans add ongoing monitoring, competitor benchmarks, and prioritized fix lists.