docs(seo): add FAQPage JSON-LD to MCP troubleshooting FAQ

[ekline]

Outcome

Adds FAQPage JSON-LD to 1 of 1 detected FAQ page. Helps AI assistants (ChatGPT, Perplexity, Gemini, Claude), Knowledge Panels, and site search understand your FAQs.

Eligibility

DOES NOT QUALIFY for Google FAQ rich snippets. Google restricts FAQ rich results to authoritative government- and health-focused domains, and is removing the FAQ rich result appearance from Search (deprecation effective May 7, 2026). The schema still delivers value: it helps AI assistants (ChatGPT, Perplexity, Gemini, Claude) cite the page, feeds Knowledge Panels, and improves site search understanding of the FAQs.

Coverage

• FAQ pages found: 1
• Changed in this PR: 1
• Deferred past cap: 0
• Already-valid: 0
• Unsupported: 0

Pages changed

Path	Ext	Action	Q&A count
src/content/docs/authenticate/mcp/troubleshooting.mdx	.mdx	add	2

The two Q&A pairs are the only headings on the page phrased as questions (ending in ?): "What is the difference between DCR and CIMD?" and "How do I view authentication logs to debug a failed connection?". The remaining troubleshooting headings are symptom statements, not questions, so they are intentionally excluded from FAQPage.mainEntity. Question and answer text is copied verbatim from the page; Markdown was mechanically converted to Google's allowed HTML tags for acceptedAnswer.text.

Framework + strategy

Astro/Starlight, .mdx file. Strategy: add a script (type application/ld+json) entry to the frontmatter head: array. No page content was moved.

Reviewer checklist

• Build the docs locally and view the affected page.
• Confirm <script type="application/ld+json"> is in the rendered HTML.
• After deploy, run the live URL through Google's Rich Results Test (https://search.google.com/test/rich-results).
• Validate the JSON-LD payload at https://validator.schema.org/.
• AI-citation spot check: ask ChatGPT or Perplexity one of the FAQ questions and confirm the model reaches the page.
• Submit the page for re-indexing in Google Search Console if rich results are urgent.

Rollback

To revert, remove the head: entry (the application/ld+json script) from the page frontmatter and re-deploy.

Notes

Local render check was skipped (the production build fetches remote SDK content and needs a GITHUB_TOKEN); the reviewer runs the build via the checklist above. Frontmatter YAML and the embedded JSON-LD were validated locally (parses; @type FAQPage; 2 valid Question entities).

Preview link (after CI assigns a PR number): https://deploy-preview-{PR_NUMBER}--scalekit-starlight.netlify.app/authenticate/mcp/troubleshooting/

---

📝 Created with EkLine · View session

[netlify]

✅ Deploy Preview for scalekit-starlight ready!

Name	Link
🔨 Latest commit	ddd7679
🔍 Latest deploy log	https://app.netlify.com/projects/scalekit-starlight/deploys/6a463868be23010008a3846f
😎 Deploy Preview	https://deploy-preview-825--scalekit-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 45 (🟢 up 7 from production) Accessibility: 98 (no change from production) Best Practices: 92 (no change from production) SEO: 92 (no change from production) PWA: - View the detailed breakdown and full score reports
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.