fix(seo): remove @type from JSON-LD stub references on plugin pages#4763
Draft
fix(seo): remove @type from JSON-LD stub references on plugin pages#4763
Conversation
Google Rich Results validates every node with @type as an independent entity, even when it's a cross-page reference via @id. On plugin task pages, this caused the SoftwareApplication stub in TechArticle.about to fail validation (missing name, applicationCategory, etc.) despite the canonical entity being correctly defined on the parent plugin page. Drop @type from pure @id references so they're treated as pointers, not new declarations. The canonical SoftwareApplication on /plugins/<name> remains the source of truth. Same pattern fixed on plugins index page (about: SoftwareApplication stub) and the SoftwareApplication.isPartOf reference to #software. Test: https://search.google.com/test/rich-results?url=https%3A%2F%2Fkestra.io%2Fplugins%2Fplugin-jdbc-vectorwise%2Fio.kestra.plugin.jdbc.vectorwise.batch Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Contributor
☁️ Cloudflare Worker Preview Deployed!🔗 https://ks-fix-schema-stub-references-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
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
Google Rich Results test flagged the `SoftwareApplication` schema as invalid on plugin task pages (e.g. `/plugins/plugin-jdbc-vectorwise/io.kestra.plugin.jdbc.vectorwise.batch`) with two critical errors:
Root cause
In `TechArticle.about` on task pages, the `SoftwareApplication` was referenced as a stub:
```json
"about": {
"@type": "SoftwareApplication",
"@id": "https://kestra.io/plugins/plugin-jdbc-vectorwise#plugin-jdbc-vectorwise"
}
```
Google's validator treats every node with `@type` as an independent entity to validate, even when it's a cross-page reference. It doesn't follow the `@id` to find the canonical definition on the parent plugin page.
Fix
Drop `@type` from pure `@id` references — treat them as pointers, not new declarations. The full `SoftwareApplication` definition on `/plugins/` (with all required fields) remains untouched and serves as the source of truth.
Same pattern applied to:
Test plan
🤖 Generated with Claude Code