lightspeed-schema-and-ai-discoverability-planner

name

lightspeed-schema-and-ai-discoverability-planner

description

plan schema markup, faq schema, internal linking, ai-search discoverability and answer-engine optimisation for lightspeed wordpress website launches using approved website content, page briefs, claim registers, faq maps and source-of-truth notes. use when the user asks for page-level schema recommendations, organization/service/faqpage/article/breadcrumblist notes, ai visibility baseline checklists, answer-engine optimisation checklists, internal linking plans or claim-safe ai/search wording.

LightSpeed Schema and AI Discoverability Planner

Purpose

Turn approved or near-final website content into practical schema, internal-linking and AI-search discoverability guidance for WordPress website launches.

Use this skill after content collection, content generation or readiness assessment has produced page drafts, page briefs, FAQs, claim registers, source-of-truth notes or launch plans.

Core rules

• Do not guarantee rankings, rich results, featured snippets, AI citations, voice-search visibility, traffic or ROI.
• Treat schema as eligibility and clarity support, not a guarantee.
• Use only approved or review-ready content for schema recommendations.
• Do not add FAQ schema for hidden, collapsed-only-without-visible-content, unpublished or unapproved FAQ answers.
• Flag unsupported claims as Evidence Required.
• Separate public-facing wording from internal implementation notes.
• Use UK English and a practical, non-hype tone.

Inputs to accept

Accept any combination of:

• website page list or sitemap
• approved website copy
• page briefs
• service and solution page drafts
• FAQ source libraries
• company FAQ page drafts
• claim registers
• source-of-truth registers
• AI readiness assessment outputs
• content collection outputs
• Search Console notes
• GA4 notes
• crawl exports
• schema validation results
• internal linking plans

If input evidence is missing, create a safe schema/discoverability plan and list the missing evidence rather than pretending validation has been completed.

Output types

Generate:

• page-level schema recommendation tables
• FAQ schema maps
• Organization schema notes
• WebSite schema notes
• Service schema notes
• FAQPage schema notes
• Article schema notes
• BreadcrumbList schema notes
• internal linking recommendations
• AI visibility baseline checklists
• answer-engine optimisation checklists
• claim-safe AI/search wording
• schema validation QA checklists
• post-launch monitoring notes
• complete Markdown packs for launch teams

Workflow

1. Confirm the website/project context and page set.
2. Identify source status: Approved, Needs Review, Evidence Required, Legal Review or Not for Chatbot.
3. Classify each page by page type: homepage, service, solution, article, case study, FAQ, policy, contact or landing page.
4. Recommend schema types per page.
5. Map FAQs to visible pages and mark which are eligible for FAQPage schema.
6. Recommend internal links based on user intent, service hierarchy and entity clarity.
7. Rewrite AI/search claims safely where needed.
8. Create an AI visibility baseline checklist.
9. Create validation and post-launch monitoring tasks.
10. End with internal notes, missing evidence and next actions.

Required output sections

For schema/discoverability plans, include:

• Executive summary
• Page-level schema recommendations
• FAQ schema map
• Organization/WebSite schema notes
• Service/Solution schema notes
• Article/Case study schema notes
• BreadcrumbList notes
• Internal linking recommendations
• Claim-safe AI/search wording
• AI visibility baseline checklist
• Answer-engine optimisation checklist
• Validation checklist
• Post-launch monitoring notes
• Evidence required
• Internal LightSpeed notes

Reference loading

Use these references as needed:

• references/schema-workflow.md for the full workflow.
• references/schema-types.md for page type to schema type guidance.
• references/faq-schema-map.md for FAQ schema rules and templates.
• references/ai-visibility-baseline.md for monthly AI/search checks.
• references/answer-engine-optimisation.md for content and entity recommendations.
• references/internal-linking-rules.md for link planning.
• references/claim-safe-wording.md before using AI/search, AEO, SEO or performance claims.
• references/validation-and-monitoring.md for launch and post-launch QA.

Quality standard

Outputs should be implementation-ready for a WordPress launch team, but must remain honest about evidence, validation status and search/AI uncertainty.

---

Maintained by the 🤖 LightSpeedWP Automation Team

📋 AI Governance · 🧠 Agents · 📞 Contact