Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

seo-sections

Sterne12

Forks2

Aktualisiert1. Juli 2026 um 19:21

Use when a site's SEO metadata (title, og:tags, LD+JSON) is missing, incomplete, or handled by a weak custom component. Covers configuring the apps SEO sections for general pages, PDPs, and PLPs via the deco admin.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

decocms

decocms/storefront-skills

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

WebentwicklerInformatik- und Mathematikberufe·SOC 15-1254

SKILL.md

readonly

name	seo-sections
description	Use when a site's SEO metadata (title, og:tags, LD+JSON) is missing, incomplete, or handled by a weak custom component. Covers configuring the apps SEO sections for general pages, PDPs, and PLPs via the deco admin.

deco's apps ships ready-made SEO sections for every major page type, configurable directly via the admin panel. When a site has no SEO section or a custom one that lacks structured data, replace it with the appropriate apps component.

Three page types, three SEO sections

All three are configurable via the deco admin under SEO Type:

Admin label	Page type	Data source to connect
General pages	Home, institutional, etc.	Manual title/description
Product details	PDP	Same loader as the product section
Product listing	PLP/category pages	Same loader as the listing section

Select the correct type in the admin and connect the same data loader already used by the page — the section generates <title>, og:tags, and LD+JSON automatically from that data.

Render mode: async (deferred)

SEO sections should be async/deferred, not SSR. For regular users, metadata is injected into <head> via HTMX head-support after load. For bots, shouldForceRender forces SSR automatically — no extra config needed. See [[deco-bot-rendering]].

HTMX head-support is required

Without this extension, <title> and og:tags never reach <head> for regular users:

{
  "htmx": {
    "version": "1.9.12",
    "extensions": ["head-support"]
  }
}

Common mistakes

Mistake	Symptom	Fix
Wrong loader connected	LD+JSON has missing/wrong data	Use the same loader as the product/listing section
HTMX missing `head-support`	Users don't get `<title>` or og:tags	Add `"head-support"` to HTMX extensions in site.json
Custom component without LD+JSON	`<title>` works but 0 rich snippets	Replace with the apps SEO section for that page type
PLP SEO not noindexing empty results	Empty category pages get indexed	This is handled automatically — ensure the data source is correctly connected
Auditing without `?__decoFBT=0`	Metadata appears absent in curl	Use `?__decoFBT=0` to see what bots actually receive

Quick audit

# PDP bot view — must have title, og:tags, LD+JSON
curl -s "https://www.store.com/product/p?__decoFBT=0" | grep -E "<title|og:|ld\+json"

# PLP bot view
curl -s "https://www.store.com/category?__decoFBT=0" | grep -E "<title|og:|ld\+json"

# Check HTMX head-support
grep "head-support" .deco/blocks/site.json

Mehr aus diesem Repository

gleiches Repository

vtex-login-headless

decocms/storefront-skills

Diagnose and fix headless login issues on VTEX storefronts — covering authorized domain setup and simulating an authenticated session by copying VtexIdclientAutCookie cookies.

2026-07-0912

deco-bot-rendering

decocms/storefront-skills

Use when debugging what crawlers or bots see on a deco site, verifying if SSR is active for bots, or diagnosing firstByteThresholdMS behavior.

2026-07-0112

variants

decocms/storefront-skills

Configure deco.cx Variants — the mechanism that swaps the value of a section, page, image, message, or ANY custom-typed prop based on a matcher rule (device, cookie, date, A/B test, geo, path, query string, etc.). Use when the user asks to A/B test a section, personalize a page per audience/segment, show different banners per device or location, schedule a promotion by date/cron, add a new variant-able type (promotion, VTEX segment, product list, menu items), write a custom matcher, or generally wire up `website/flags/multivariate*` in `.deco/blocks/*.json`. Covers the JSON shape (`variants: [{ value, rule }]`), the resolution order (first match wins, catch-all last), every built-in matcher (`always`, `never`, `device`, `date`, `cron`, `random`, `cookie`, `host`, `pathname`, `queryString`, `userAgent`, `location`, `site`, `environment`, `multi`, `negate`), how to compose them with `multi` (and/or) and `negate`, the 8-line boilerplate to create your own `flags/multivariate/<type>.ts`, the shape of a custom `ma

2026-07-0112

setup-blog

decocms/storefront-skills

Install and configure the Blog Manager on a deco-site storefront. Covers the blog app, page routes, sections, Blog Manager MCP connection in Studio, and first-run brand context initialization.

2026-06-2912

deco-ecommerce-qa

decocms/storefront-skills

Use when inside a deco.cx ecommerce repository (deco.ts present, decobot in PR history) and the user wants automated QA for purchase-journey correctness — set up E2E coverage, test the add-to-cart / checkout flow, or scaffold a CI gate for the store with the @decocms/qa engine. NOT for load/cache performance testing (use deco-e2e-testing) or hand-written Playwright spec files.

2026-06-2912

troubleshooting

decocms/storefront-skills

Quick fixes for common, isolated issues in deco.cx storefronts. Use when the user reports a specific symptom that doesn't warrant a full skill. This is a growing knowledge base — add new entries as they're discovered.

2026-06-2512

name	seo-sections
description	Use when a site's SEO metadata (title, og:tags, LD+JSON) is missing, incomplete, or handled by a weak custom component. Covers configuring the apps SEO sections for general pages, PDPs, and PLPs via the deco admin.

Three page types, three SEO sections

All three are configurable via the deco admin under SEO Type:

Admin label	Page type	Data source to connect
General pages	Home, institutional, etc.	Manual title/description
Product details	PDP	Same loader as the product section
Product listing	PLP/category pages	Same loader as the listing section

Select the correct type in the admin and connect the same data loader already used by the page — the section generates <title>, og:tags, and LD+JSON automatically from that data.

Render mode: async (deferred)

HTMX head-support is required

Without this extension, <title> and og:tags never reach <head> for regular users:

{
  "htmx": {
    "version": "1.9.12",
    "extensions": ["head-support"]
  }
}

Common mistakes

Mistake	Symptom	Fix
Wrong loader connected	LD+JSON has missing/wrong data	Use the same loader as the product/listing section
HTMX missing `head-support`	Users don't get `<title>` or og:tags	Add `"head-support"` to HTMX extensions in site.json
Custom component without LD+JSON	`<title>` works but 0 rich snippets	Replace with the apps SEO section for that page type
PLP SEO not noindexing empty results	Empty category pages get indexed	This is handled automatically — ensure the data source is correctly connected
Auditing without `?__decoFBT=0`	Metadata appears absent in curl	Use `?__decoFBT=0` to see what bots actually receive

Quick audit

# PDP bot view — must have title, og:tags, LD+JSON
curl -s "https://www.store.com/product/p?__decoFBT=0" | grep -E "<title|og:|ld\+json"

# PLP bot view
curl -s "https://www.store.com/category?__decoFBT=0" | grep -E "<title|og:|ld\+json"

# Check HTMX head-support
grep "head-support" .deco/blocks/site.json