adapto-seo-wire

Solid

Make stored SEO metadata actually render — a one-time, consent-gated, framework-aware setup that wires a head-render layer (title, meta, OG/Twitter, JSON-LD) reading the _adapto_seo collection, plus generates llms.txt / llms-full.txt from your content inventory. Edits your app templates (never the read-client), only after you approve the exact changes.

Data & Documents 1 stars 0 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
10
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# adapto:seo-wire `adapto:content-upload` **stores** SEO metadata in `_adapto_seo`, but the starters render only `<title>`. This skill **makes it render**: a **one-time, per-project** setup that installs a head-render layer reading `_adapto_seo` (emitting `<title>`, meta description, OG/Twitter tags, and JSON-LD) and generates `llms.txt` / `llms-full.txt` from your inventory. It is **consent-gated** and **only edits your own app templates** — **never the read-client** ([forbidden-actions.md](../../shared/forbidden-actions.md); see [seo-standards.md](../../shared/seo-standards.md) for what's rendered). ## When to use - "Make my SEO/meta render", "wire up the head tags", "generate llms.txt", "the OG tags aren't showing". - Once per project, after `adapto:content-upload` has written `_adapto_seo` items (or alongside the first upload). ## When not to use - Storing metadata (that's `adapto:content-upload`, into `_adapto_seo`). - Writing or uploading content → the content pipeline. - Just checking the environment → `adapto:doctor`. ## Inputs - The **scaffolded frontend** in the cwd, and its **framework** (Next / Astro / SvelteKit — detected as `adapto:doctor` does). - The **`_adapto_seo`** collection (read at render time, by `target_slug`). - **`inventory.md`** — the content list `llms.txt` is generated from. ## Outputs - A **head-render layer** in the app's own templates (per framework: Next `generateMetadata` / Astro `<head>` in the layout / SvelteKit `<svelte:head>`) th...

Details

Author
adaptocms
Repository
adaptocms/adapto-cms-agent-skills
Created
1 months ago
Last Updated
4 days ago
Language
JavaScript
License
MIT

Integrates with

Svelte · Frontend

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

adapto-content-upload

Push approved content drafts to Adapto — convert each reviewed Markdown draft to HTML, create or update the Article/Page/collection item (one-way push via the ledger id-map), mirror its SEO metadata into _adapto_seo, and drift-guard against out-of-band CMS edits. Schema-gated; everything lands as draft. Plan-then-apply.

1 Updated 4 days ago
adaptocms
Web & Frontend Solid

adapto-scaffold

Create a new Adapto-ready frontend by wrapping `npx create-adapto-app` — choose a framework (Next/Astro/SvelteKit), scaffold the project (the Adapto read-client is included), and wire up `.env`. Consent-gated — shows the exact command and runs it only after you approve. New projects only.

1 Updated 4 days ago
adaptocms
Web & Frontend Listed

seo-bootstrap

Use on day 1 of a project to ship sitemap, robots.txt, OG image, and JSON-LD schema in a single PR. Auto-detects Next.js, Astro, or SvelteKit, audits what's already there, and only generates what's missing. Triggers on "set up SEO", "SEO bootstrap", "configure SEO", "add sitemap", "add robots.txt", "make my site SEO-ready", or "I just shipped a site, help me with SEO."

0 Updated 3 days ago
benskamps