Platform-Specific Guides, Full i18n for Dimension Pages & FAQ Accuracy Fix
Three improvements shipped today: tailored improvement guides per platform, complete Korean/English language switching on dimension detail pages, and corrected FAQ copy that accurately reflects what ClariCard actually measures.
Platform-Specific Improvement Guides
When you open a signal card inside any AI Score dimension page, you'll now see a platform guide section tailored to your site's tech stack. If your site runs on Next.js, WordPress, Webflow, Framer, Oopy, or imweb, ClariCard shows you exactly how to apply the fix on your specific platform — not generic instructions you have to translate yourself.
For example, the Organization Schema signal now shows:
- **Next.js** — insert JSON-LD via `app/layout.tsx` metadata or `next-seo`'s JsonLd component
- **WordPress** — configure the Organization type directly in Yoast SEO or Rank Math's Schema settings
- **Webflow** — paste the script block in Site Settings → Custom Code → Head Code
- **Framer** — use Site Settings → Custom Code → `<head>` section
- **Oopy / imweb** — step-by-step paths through each platform's settings UI
Guides are available for the highest-impact signals: Organization Schema, Brand Name Consistency, Meta Description, FAQ Schema, Structured Q&A Content, Robots.txt, and Sitemap. The platform is detected automatically from your registered site.
Full Korean/English Language Switching on Dimension Pages
The AI Score dimension detail pages (Entity Clarity, Answer Readiness, Semantic Density, Crawl Signals, Trust & Authority) now fully respect the language setting throughout:
- All UI labels — section headers, state indicators, table columns, filter buttons — switch between Korean and English
- All signal content — descriptions, "why it matters" explanations, how-to instructions, checklists, and step-by-step action items — are fully bilingual
- Dimension-level taglines, scoring rationale, and expected impact statements switch with the language toggle as well
Previously the UI chrome was partly hardcoded in Korean, making the pages inaccessible to English-speaking users.
Share Page Gauge Tooltips
Hovering over any segment of the score gauge bar on a public share link (the Poor / Fair / Good / Excellent bands) now shows a tooltip explaining what that score range means in terms of actual AI search visibility — so recipients can immediately understand their score without needing any context.
FAQ Copy Corrected
The homepage FAQ answers previously stated that ClariCard optimizes for "ChatGPT, Claude, Perplexity, Google Bard, and emerging AI platforms." This was inaccurate.
ClariCard currently measures AI visibility using **ChatGPT (GPT-4o)** and **Google Gemini** — the two most widely used AI search engines. Optimization is based on JSON-LD structured data standards, which any AI system can read, so improvements also benefit Perplexity and others indirectly. The FAQ answers now reflect this accurately.