docs(seo): add FAQPage JSON-LD to 2 FAQ pages#1249
Open
ekline[bot] wants to merge 1 commit into
Open
Conversation
Add FAQPage structured data (JSON-LD) to the main FAQ page and the billing FAQ section. This helps AI assistants, Knowledge Panels, and site search parse and surface FAQ content accurately. ekline[bot] <202747777+ekline[bot]@users.noreply.github.com> Signed-off-by: ekline[bot] <202747777+ekline[bot]@users.noreply.github.com>
✅ Deploy Preview for okteto-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds FAQPage JSON-LD structured data on 2 of 2 FAQ pages. Helps AI assistants (ChatGPT, Perplexity, Gemini, Claude), Knowledge Panels, and site search understand your FAQs.
Eligibility
DOES NOT QUALIFY for Google FAQ rich snippets. Since August 2023, Google restricts FAQ rich results to well-known government and health sites. However, the structured data still provides real value:
Coverage
No files deferred — full coverage achieved in this run.
Pages changed
src/content/reference/faqs.mdx.mdxsrc/content/admin/billing.mdx.mdxFramework and strategy
docusaurus.config.js)<script type="application/ld+json">inside<Head>from@docusaurus/Head(Docusaurus.mdxmatrix row).mdx— no rename neededReviewer checklist
yarn build) and view each affected page<script type="application/ld+json">is in the rendered HTMLhttps://search.google.com/test/rich-results)https://validator.schema.org/Rollback
To revert, remove the
<Head>import and the<Head><script type="application/ld+json">...</script></Head>block from each file and re-deploy.ekline[bot] <202747777+ekline[bot]@users.noreply.github.com>