seo: make plugin task page titles/H1 unique and descriptive#4977
Open
vfanucci wants to merge 1 commit into
Open
seo: make plugin task page titles/H1 unique and descriptive#4977vfanucci wants to merge 1 commit into
vfanucci wants to merge 1 commit into
Conversation
Plugin task pages (io.kestra.*) set both <title> and <h1> to the bare class name via formatElementName(pluginType) — "Trigger", "Query", "Create", "Delete". Since most plugins expose those same task names, the crawl found ~1,200 duplicate titles, ~1,200 duplicate H1s and ~1,860 titles under 30 characters, almost all from this one branch. Prefix the task name with the page's plugin/subgroup container title (the same title the group/subgroup pages already use), e.g. "AWS S3 Trigger", "Google Cloud BigQuery Query", "PostgreSQL Query". This resolves the duplicate title, duplicate H1 and short-title issues in one change, and adds integration keywords to every task page. Subgroup/group pages are unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
☁️ Cloudflare Worker Preview Deployed!🔗 https://ks-seo-fix-plugin-task-titles-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 |
Member
|
I'm not sure about this change technically - best to ask a Front End to review or plugin team. |
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.
Context
Technical SEO audit (Screaming Frog, 2026-06-15), highest-volume on-page issue. Single root cause: plugin task pages (
io.kestra.*, 1361 pages) use the bare class name as both<title>and<h1>.Trigger | KestraDelete | KestraQuery | KestraCreate | KestraBecause most plugins expose those same task names, this single branch produces ~1,204 duplicate titles, ~1,204 duplicate H1s and ~1,862 titles under 30 characters. (
/blueprintsis not affected: 19 duplicate titles, 0 duplicate H1s.)This is complementary to #4688 (which added "how to use" markdown + FAQs to plugin parent pages). That work never touched the auto-generated task pages — the 2026-06-15 crawl, taken after #4688 rolled out, still showed these duplicates.
Change
In
buildPluginPageProps.ts, task pages now prefix the task name with their plugin/subgroup container title (the same title group/subgroup pages already use) instead of the bare class name:aws/s3/…Triggergcp/bigquery/…Queryslack/chats/…Createjdbc-postgres/…QueryA single variable (
headingTitle) is changed, resolving duplicate titles, duplicate H1s and short titles at once, and adding integration keywords to every task page. Group/subgroup pages are unchanged;elementTitle(sidebar/breadcrumb) is unchanged.Verified
node_modules) → please rely on CI + preview to validate the rendered<title>/<h1>on a few task pages.Out of scope (intentional)
Task-page meta descriptions: short (~35 chars) but unique and accurate → "Opportunity/Low", low ROI (Google rewrites short metas). Can be revisited later if needed.
🤖 Generated with Claude Code