feat(seo): add structured data schema on plugin pages#4656
Draft
feat(seo): add structured data schema on plugin pages#4656
Conversation
- SoftwareApplication schema on plugin root and subgroup pages with softwareVersion, softwareRequirements, image, applicationSubCategory, and conditional offers (free vs EE) - TechArticle schema on task/trigger definition pages, linked to parent plugin via `about` - CollectionPage + hasPart schema on /plugins index (capped at 50 entries) - All schemas injected server-side via Fragment slot="head" Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
17 tasks
Contributor
☁️ Cloudflare Worker Preview Deployed!🔗 https://ks-feat-seo-plugin-structured-dat-docs.kestra-io.workers.dev ## 🔦 Lighthouse Benchmark
Scores (0–100, higher is better)
Core Web Vitals (lower is better)
Legend🟢 improved · 🔻 regressed · (blank) no significant change |
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
1 participant
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.
Contexte
Ajout de JSON-LD structured data (
TechArticle/SoftwareApplication) sur les pages plugins pour améliorer la compréhension du contenu par Google et augmenter l'éligibilité aux rich results.Changements
Pages de tâches individuelles →
TechArticle{ "@type": "TechArticle", "headline": "Upload", "description": "...", "about": { "@type": "SoftwareApplication", "@id": "https://kestra.io/plugins/plugin-aws#plugin-aws" }, "author": { "@id": "https://kestra.io/#organization" } }Pages plugin / sous-catégorie →
SoftwareApplication{ "@type": "SoftwareApplication", "name": "AWS", "applicationCategory": "DeveloperApplication", "applicationSubCategory": "Cloud, Data", "operatingSystem": "Linux, macOS, Windows, Docker, Kubernetes", "softwareVersion": "0.22.0", "offers": { "@type": "Offer", "price": "0" } }Fichiers modifiés
src/pages/plugins/[...slug].astroChecklist de test en dev
Setup
npm run devStructured data — pages de tâches (
TechArticle)/plugins/plugin-aws/s3/io.kestra.plugin.aws.s3.upload<script type="application/ld+json">dans le<head>"@type": "TechArticle"présent"headline"= nom de la tâche (ex:"Upload")"about"pointe vers le plugin parentStructured data — pages plugin principal (
SoftwareApplication)/plugins/plugin-aws"@type": "SoftwareApplication""applicationCategory": "DeveloperApplication""softwareVersion"présent (si GitHub releases disponible)"offers.price": "0"pour les plugins open sourceStructured data — plugin Enterprise Edition
/plugins/core/log-ee/io.kestra.plugin.ee.core.log.logshipper)"offers"contient"priceType": "https://schema.org/InvoicePrice"(pas"price": "0")Non-régression
<head>, invisible)/plugins(index général) n'a pas de script ld+json inattendu