### Describe the issue

# Context

Kestra Blueprints are one of the strongest assets for organic acquisition: they represent **ready-to-run workflow use cases** that users actively search for.

However, Blueprint pages are currently named using **full workflow descriptions or internal phrasing**, not **clear use-case language aligned with search intent**.

As a result:
- Blueprint Titles are often truncated in search results
- Pages lack a visible H1 and meta description
- Use cases are hard to scan and difficult to discover

Blueprints should act as **SEO entry points for real-world workflow examples**, not as long technical descriptions.

---

## Scope

All URLs under: /blueprints/**

(≈ 275 pages)

---

## Current problems

### 1) Titles are too long and descriptive

Current Titles often:
- Are full sentences
- Describe every workflow step
- Exceed 80–150 characters

This causes:
- SERP truncation
- Poor readability
- Unclear primary use case

---

### 2) Missing H1 on Blueprint pages

- Most Blueprint detail pages have **no `

`**
- The page does not clearly state *what the blueprint is*
- Weak accessibility and on-page structure

---

### 3) Missing meta descriptions

- Search engines generate random snippets
- No consistent “Kestra Blueprint” messaging
- Lower click-through rate

---

### 4) Blueprint identity is unclear

- Titles do not consistently indicate:
- that the page is a **Kestra Blueprint**
- that it is a **ready-to-run workflow example**

---

## Goal

Transform Blueprint pages into **search-aligned use-case pages** by:
- Naming Blueprints after **the problem they solve**
- Making Titles concise and scannable
- Adding clear H1 and meta descriptions
- Explicitly positioning Blueprints as reusable workflow examples

---

## Proposed SEO-first naming model

### 1) Title tag (use-case-driven)

**Format**
[Use Case / Outcome] with [Key Technology] – Kestra Blueprint

**Examples**

| Current Title (Too Long) | Use Case | New SEO Title | New H1 |
| ------------------------ | -------- | ------------- | ------ |
| Trigger multiple Airbyte Cloud syncs in parallel, then run a dbt job | ELT / Analytics | Parallel Airbyte Syncs + dbt Job – Kestra Blueprint | Parallel Airbyte Syncs with dbt |
| Send an email every morning containing a daily digest of weather and train times | Notifications | Daily Weather & Commute Digest Email – Kestra Blueprint | Daily Weather & Commute Digest Email |
| Extract data from a REST API, process it in Python with Polars, then run DuckDB query | Data Pipeline | REST API to Analytics Pipeline – Kestra Blueprint | REST API to Analytics Pipeline |
| Orchestrate AWS Batch jobs with dynamic parameters and retries | Cloud Compute | Orchestrate AWS Batch Jobs – Kestra Blueprint | Orchestrate AWS Batch Jobs |
| Run an AI agent workflow to analyze data and generate insights | AI / GenAI | AI Agent Workflow for Data Analysis – Kestra Blueprint | AI Agent Data Analysis Workflow |

---

### 2) H1 (clear, use-case-oriented)

**Format**
[Use Case / Outcome]

**Examples**
- `Parallel Airbyte Syncs with dbt`
- `Daily Weather and Commute Digest Email`
- `REST API to Analytics Pipeline`

**Rules**
- Exactly **one `

` per page**
- Must be readable without surrounding context
- Should not repeat the full Title suffix (“Kestra Blueprint”)

---

### 3) Meta descriptions (intent reinforcement)

**Format**
Kestra blueprint to [solve X problem] using [technology]. Ready-to-run workflow example.

**Examples**
- “Kestra blueprint to run multiple Airbyte Cloud syncs in parallel and trigger a dbt job.”
- “Kestra blueprint to send a daily email combining weather and commute data.”

---

### 4) Blueprint listing & pagination

- Blueprint listing pages must:
- Use **unique Titles** per page (e.g. “Blueprints – Page 2”)
- or define a canonical URL to page 1
- Avoid duplicate Titles like `Kestra Blueprints Library` across paginated pages

---

## Acceptance criteria

- Every `/blueprints/**` page has:
- A Title under ~65 characters
- Exactly one `

`
- A meta description
- Titles describe a **use case**, not workflow internals
- All Blueprint pages clearly identify themselves as **Kestra Blueprints**
- No duplicate Titles across blueprint pages or pagination

---

## Non-goals

- ❌ Do not list every workflow step in the Title
- ❌ Do not expose YAML, task names, or internal execution details
- ❌ Do not keep sentence-length Titles

---

## Reference

- SEO audit CSV:

[blueprints.csv](https://github.com/user-attachments/files/24524775/blueprints.csv)

Start with the SEO audit CSV and inspect the pages under /blueprints/** to compare current titles, headings, and descriptions with the requested formats. Done means every blueprint page has a concise unique title, exactly one H1, and a meta description, with pagination titles or canonicalization handled as specified.

Written by the indexing model from the issue text.