SEO

Clog ships a Yoast / RankMath-grade SEO surface that runs across every content entity (Post, Page, Category, Tag, Author) plus a workspace-level defaults page. This is the longest page in the dashboard guide because the SEO surface is the most-featured part of Clog.

You'll meet five distinct pieces here:

1. The per-entity SEO meta group — title, description, canonical, focus keyword, robots, OG, Twitter — sitting in a tab on every content edit page.
2. The create-time type wizard (Posts only) — picks the Schema.org variant when you create a new post.
3. The Post details structured-content section — type-specific fields (recipe ingredients, how-to steps, event dates, ...) that ship as both reader-facing content and crawler JSON-LD.
4. The live score engine — 25 checks (12 SEO + 12 readability + 1 overlap) that grade your post as you type.
5. The Workspace SEO defaults page — site name, title template, publisher Organization, social handles, search-console verification codes.

Permission gating

The SEO surface gives an SEO specialist most of what they need without touching content. Two scopes apply:

In practice: hand seo:write to your SEO specialist and they can tune titles, descriptions, robots, and social metadata across every entity. To let them touch a recipe's ingredients or a how-to's steps, you'd also need to give them posts:write — at which point they're a content editor too.

The per-entity SEO meta group

Every content entity (Post, Page, Category, Tag, Author) carries the same SEO meta object. On the Post and Page edit pages it lives in a right-hand drawer opened by the SEO icon in the top bar; on Category, Tag, and Author edit dialogs it's a dedicated tab in the same dialog.

Three sub-tabs:

General

Social

If a Twitter or OG field is empty, the consumer falls back to the General tab's title / description and the workspace's defaultOgImageMediaId.

Analysis

Only present on Posts. Shows the live score — see The live score engine below.

Schema.org variants (Posts)

A Post carries a schemaType (defaults to BlogPosting) selected at create time via a 3-step wizard. v1 covers a ~50-variant catalogue spanning Article, How-to / Recipe, Review, Announcement (Event, JobPosting, Course, Product, ...), Profile (Movie, Book, MusicAlbum, ...), and List families.

Pages have a simpler 5-variant pageType enum: WebPage (default), AboutPage, ContactPage, LearningResource, MedicalWebPage — picked from a dropdown on the page editor.

The create-time wizard (Posts)

When you click New post, the wizard opens with three steps (max — Step 3 may be skipped):

1. Pick intent. Six high-level cards: Story, How-to, Review, Announcement, Profile, List. Hit Skip at any step to ship as a plain BlogPosting.
2. Narrow within the intent. A grid of sub-types relevant to the intent picked in Step 1 (e.g. Story → BlogPosting / Article / NewsArticle / TechArticle / ScholarlyArticle / Report; How-to → HowTo / Recipe; etc.).
3. (Optional) Wrap with a media format. If your post is fundamentally a video or audio piece on top of the chosen type, wrap with VideoObject or AudioObject. Most posts skip this step.

All 50+ variants are reachable in ≤3 taps. Pick the closest match — Clog's content authors don't need to know Schema.org. Hover any card for a one-line description.

The chosen type is editable later via a "Change type" button on the post editor. Switching preserves overlapping structuredData fields; field-loss is surfaced in a confirmation modal before commit.

Smart suggestions

For posts that defaulted to BlogPosting (clicked Skip), a banner appears on the editor when Clog detects strong signals for a richer type:

Click the banner to switch types in one step, or Dismiss to ignore (per-post; the same signal won't surface again on this post).

Post details — structured content

Posts with a non-trivial schemaType get a Post details section in the editor. The fields depend on the type:

• HowTo / Recipe — step list, ingredients, prep / cook / total time, yield, nutrition, cuisine, diet, keywords.
• Event family — start / end date, location (Place or VirtualLocation), organizer, performer, offers.
• Product / Review — brand, SKU, GTIN, MPN, offers, aggregate rating, item reviewed, review rating.
• JobPosting — hiring organization, job location, base salary, employment type, validThrough.
• LocalBusiness / Restaurant / Hotel / Store — address, telephone, openingHours, priceRange, geo coordinates.
• Movie / TVSeries / Book / MusicAlbum — director, actor, ISBN, by-artist, episode/season numbers, etc.

This data is content, not metadata. It serves consumers three ways from one source:

Edit it once, get all three. See API → Rendering content and API → SEO and JSON-LD for the integrator's view.

Type-specific SEO overrides

The General tab's Schema overrides sub-section lets you override structuredData values for crawlers only. Example: shorten step names in seo.schemaData.step for richer SERP snippets while leaving the rendered recipe card untouched. Empty fields fall through to the underlying structuredData — overriding one step doesn't blank the rest.

The live score engine

The Post editor's SEO drawer has an Analysis tab with two scores out of 100: SEO and Readability. Both recompute as you type. Scores are also persisted on save and exposed on the Posts list page so you can sort and filter by them.

SEO checks (12)

Each check returns good / ok / bad:

Readability checks (12)

Click any check in the Analysis tab to jump to the part of the post that's failing — typing more, breaking a long sentence, adding alt text — and watch the score recover live.

The scores are persisted as seoScore and readabilityScore on the post and surface on the Posts list page. You can sort by them (orderBy=seoScore) or filter on a minimum (minSeoScore) — useful for finding all posts under 80 that need a pass before quarter-end.

Workspace SEO defaults

Open Settings → SEO defaults (in the workspace sidebar, under Settings). This page configures defaults that apply to every content entity unless overridden per-entity. Editing requires both settings:write and seo:write.

Three tabs:

Site & defaults

Social

Publisher & verification

The Publisher section configures the Organization (or Person) node embedded as publisher in every JSON-LD payload — what search engines treat as the entity that owns the content.

The Site verification section stores codes for search-console verification:

The codes come back on GET /external/workspace for consumer sites to stamp. They're stored only — Clog doesn't call the search consoles for you.

What an integrator gets

Briefly, so editors know what's going out — full detail lives on the API → SEO and JSON-LD page:

• Every content read response carries the seo meta group as a typed JSON object.
• Posts also carry schemaType, structuredData, the derived structuredBlocks, and seoScore / readabilityScore.
• A pre-assembled jsonLd field on every content read response — drop into <script type="application/ld+json"> to ship structured data to crawlers in one round-trip.
• GET /external/workspace returns the publisher Organization + site verification codes + default OG image URL for site-wide <head> injection.

Where to next

• Posts — the SEO drawer and Post details section in context.
• Redirects — what to do when changing a slug. Slug changes auto-create 301 redirects.
• API → SEO and JSON-LD — the integrator's view of everything authored here.