메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Diagnose and fix headless login issues on VTEX storefronts — covering authorized domain setup and simulating an authenticated session by copying VtexIdclientAutCookie cookies.
Use when debugging what crawlers or bots see on a deco site, verifying if SSR is active for bots, or diagnosing firstByteThresholdMS behavior.
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
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.
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.
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.
| 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.
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.
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]].
Without this extension, <title> and og:tags never reach <head> for regular users:
{
"htmx": {
"version": "1.9.12",
"extensions": ["head-support"]
}
}
| 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 |
# 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