docs(blog): enable FAQPage schema on 14 blog posts with qualifying Q&A headers#20522
Open
workprentice[bot] wants to merge 1 commit into
Open
docs(blog): enable FAQPage schema on 14 blog posts with qualifying Q&A headers#20522workprentice[bot] wants to merge 1 commit into
workprentice[bot] wants to merge 1 commit into
Conversation
…A headers These posts already contain genuine question-form H2/H3 sections (5-25 each) but were missing the faq_schema: true front-matter flag required by layouts/partials/schema/collectors/faq-entity.html to emit FAQPage JSON-LD. Enabling FAQPage schema on these pages supports both traditional rich-result eligibility and AI answer-engine citation (GEO), consistent with the pattern already shipped on prior comparison/guide pages this week.
github-actions
Bot
added
review:triaging
Contributor
Author
|
@claude #new-review |
Collaborator
Contributor
Author
|
@claude #new-review |
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
2 participants
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
Enables
FAQPagestructured data (JSON-LD) on 14 blog posts that already contain genuine question-form H2/H3 sections but were missing thefaq_schema: truefront-matter flag required bylayouts/partials/schema/collectors/faq-entity.html.Why
Per Pulumi's SEO/AEO strategy, FAQPage schema is the highest-leverage lever for both traditional rich-result eligibility and AI answer-engine citation (GEO) — content that isn't structured for extraction gets skipped by LLM chunking. These 14 posts already have qualifying Q&A content (5–25 question-form headers each) and simply weren't opted into schema emission. This follows the same pattern shipped on prior comparison/guide pages (PR #20499).
Files changed (14, +1 line each, front matter only)
content/blog/announcing-per-user-pricing-and-unlimited-stacks-for-teams/index.md(6 question headers)content/blog/aws-lambda-container-support/index.md(7)content/blog/azure-container-solutions/index.md(6)content/blog/backstage-vs-pulumi-idp-why-infrastructure-first-platform-engineering-matters/index.md(5)content/blog/developer-experience-business-critical/index.md(9)content/blog/embrace-kubernetes-part1/index.md(6)content/blog/fast-docker-image-builds-with-pulumi/index.md(7)content/blog/generative-ai-apps-devops-talks-pulumi-user-group/index.md(6)content/blog/helm-release-resource-for-kubernetes-generally-available/index.md(5)content/blog/kubernetes-best-practices-i-wish-i-had-known-before/index.md(25)content/blog/run-deepseek-on-aws-ec2-using-pulumi/index.md(7)content/blog/serverless-api/index.md(7)content/blog/the-guide-platform-engineering-idp-steps-best-practices/index.md(8)content/blog/why-switch-to-pulumi/index.md(6)Verification
layouts/partials/schema/collectors/faq-entity.htmldirectly (front-matter field isfaq_schema: true; the unrelatedschema_typefield is not read by this collector).##/###headers before adding the flag — every file has at least 5 qualifying headers.faq_schema: trueset and no other content altered.git diff --statconfirms exactly 14 files changed, +1 line each — no unintended content changes.#new-review
@claude please review
🧠 This PR was created by workprentice via automated technical-SEO agent on behalf of the Pulumi marketing/growth workspace.