Skip to content

docs(seo): clarify the SEO panel is only honored if the page wires getSeoMeta #1519

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DavidPivert wants to merge 2 commits into
base: main
Choose a base branch
from
+26 −0
Open

docs(seo): clarify the SEO panel is only honored if the page wires getSeoMeta #1519

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9e7d243
docs(seo): clarify the SEO panel is only honored if the page wires ge…
DavidPivert Jun 17, 2026
7b7239e
Merge branch 'main' into docs/seo-panel-honored-on-all-pages
DavidPivert Jun 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions skills/building-emdash-site/references/site-features.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -257,6 +257,14 @@ Search requires per-collection enablement:

## SEO Meta

> [!IMPORTANT]
> The admin **SEO panel** (SEO title, meta description, OG image, canonical URL,
> "hide from search engines"/noindex) lives on `entry.data.seo` and is **only
> honored if your page reads it**. A page that hand-rolls
> `<title>{entry.data.title}</title>` silently bypasses the entire panel —
> including the `noindex` toggle. **Every content detail page must wire
> `getSeoMeta` (or `getContentSeo`), not just the scaffolded `posts` page.**

Generate SEO meta from content entries:

```typescript
Expand All @@ -282,6 +290,24 @@ Use in your layout's `<head>`:
{seo.robots && <meta name="robots" content={seo.robots} />}
```

### Composing panel overrides with custom defaults

`getSeoMeta` only falls back to `data.title` / `data.excerpt`. If a page computes
its own title or description (e.g. `"Maeta — {title} (cover of {artist})"`), read
the raw panel with `getContentSeo` and let it take precedence over your default:

```ts
import { getContentSeo } from "emdash";

const panel = getContentSeo(entry); // { title, description, image, canonical, noIndex } | undefined
const title = panel?.title || myComputedTitle;
const description = panel?.description || myComputedDescription;
const robots = panel?.noIndex ? "noindex, nofollow" : null;
```

This keeps editor-supplied SEO fields authoritative while preserving sensible
per-page defaults.

## Comments

Built-in comments system:
Expand Down
Loading