Japanese SEO Agent Skill: Audits, Core Web Vitals, AI Search

Where this fits

You are the developer who gets called after a Japanese e-commerce site loses rankings in a Google core update. You need to inspect robots.txt, canonical tags, structured data, Core Web Vitals, and AI crawler settings, but the knowledge is scattered across docs. This skill turns that fragmented process into a checklist-driven workflow your agent can load and execute.

Why agents benefit

• Maps vague client requests like 'SEO改善して' to the correct reference file: technical-seo.md, content-seo.md, structured-data.md, or core-web-vitals.md.
• Generates current schema.org JSON-LD for Product, Article, FAQPage, and more, reducing manual validation time.
• Runs a six-phase audit covering crawlability, indexation, performance, and AI search visibility with prioritized fixes.
• Suggests concrete Core Web Vitals code changes for LCP, INP, and CLS in Next.js/Nuxt.js.
• Handles Japanese-specific factors: hreflang for ja/ja-jp, E-E-A-T structure, llms.txt, and control of GPTBot, ClaudeBot, and Google-Extended.

Practical scenarios

Post-core-update traffic recovery for a Japanese blog

The agent combines PageSpeed data with crawl checks, finds that INP is failing and E-E-A-T signals are weak, then rewrites headings and adds Person/Organization structured data.

Product rich results in an e-commerce catalog

Ask for schema on a product page; the agent loads structured-data.md, generates JSON-LD with offers and reviews, and validates it before you commit.

AI search readiness for a SaaS documentation site

The agent adds llms.txt, adjusts AI crawler rules, and recommends FAQPage structured data so content can surface in AI Overviews and AI mode.

Add it to your agent workflow

Install the skill with:

npx skills add kpab/seo-mastery-agent-skills --skill seo-mastery-jp

Then ask your agent: 'Audit https://example.com using seo-mastery-jp. Prioritize technical SEO and Core Web Vitals issues, then generate JSON-LD for the main product page.' The agent loads relevant reference files and returns a structured audit with code snippets.

Compare before adopting

Compare this against a generic SEO prompt or manual checklist. Check recent commits and issue responses, because SEO guidance changes often. Alternatives like Lighthouse CI cover only performance; a dedicated crawler covers indexation but not content strategy. Confirm the Japanese-language focus fits your sites, since that is the skill's main workflow.

Why it is worth tracking

This skill is a focused package, not a framework. Its value is in the complete audit workflow and AI-search controls, which older SEO skills lack. Watch for version bumps around Google guideline or AI crawler policy changes, and use star growth and issue resolution as quality signals. If you maintain Japanese-facing sites, evaluate it now and track it on OpenAgentSkill at https://www.openagentskill.com/skills/kpab-seo-mastery-jp.