Find per-type SEO settings

⏱ ~3 min read · a wayfinding page — no settings live here, only links to them.

In short. Post Type SEO is a hub with one link per content type — Blogs SEO, Events SEO, Store SEO, Pages, and Custom Post Types. Click the link for the type you want; change settings in the destination form; hit Save. The hub itself stores nothing.

On this page: What is this for? · Priority order · Steps · Examples · Troubleshooting

How to navigate to the right SEO screen for blogs, events, store, pages, or custom content types

Post Type SEO is a small hub page — one link per content type. It exists so you can jump straight to the right SEO screen without hunting through the left nav.

SGEN has five content types with SEO defaults: blogs, events, products (Ecommerce sites), pages, and custom content types (Custom Objects). Each type has its own defaults screen, but those screens live in different parts of the admin. The hub pulls every link together.

The five per-type SEO screens this hub links to

Blogs 1 Events 1 Store 1 Pages 1 Custom 1

How the five links differ:

Blogs SEO, Events SEO, Store SEO — archive-defaults forms with SEO Title, Meta Description, and type-specific fields.
Pages — no shared default exists for static pages. The hub link drops you on the Pages list; edit each page individually.
Custom Post Types — routes into Custom Objects, where custom content types and their SEO are managed.

The hub is a routing screen. There is no form on it, no Save button. You always click through to change anything.

What is this for?

Post Type SEO is the one screen that knows about all five content types and gives you a labeled link to each. Use it when you cannot remember which sub-page holds the defaults for a specific type, or when you want to work through every type in a single sweep.

For settings that apply to your whole site — the indexing toggle, title separator, fallback site title — use Global SEO instead.

For per-page SEO on individual pages, use SEO Manager — the inline grid across every content type.

Per-type defaults vs site-wide defaults vs per-page values

When SGEN renders a public page, it walks this order and uses the first value it finds:

Global SEO — site-wide fallbacks. The base layer.
Per-type defaults — what this hub points to. Overrides the Global SEO fallback for content of one specific type.
Per-page values — set in an individual page, post, event, or product editor. Overrides everything else.

seo_priority_order: description: >- When SGEN builds a page&#39;s  tag, it checks these</span> levels in order and uses the first one that has a value. levels: 1_per_item: label: Per-item SEO title set_in: Item editor (post/page/event) or SEO Manager inline edit wins_over: archive defaults and global defaults 2_type_archive: label: Type archive title pattern set_in: Post Type SEO → Blog/Events/Products panel wins_over: global defaults loses_to: per-item title 3_global: label: Global SEO title pattern set_in: Global SEO fallback: used when no per-item or type title is set common_mismatch: symptom: &<span class="cmt">#<span class="num">39</span>;Archive default changed but some posts still show old title&#<span class="num">39</span>;</span> cause: those posts have a per-item SEO title set fix: clear the per-item title in post editor or via SEO Manager</pre>

The most common mismatch: you set a new archive default, but a specific post still shows the old title. That post has a per-page SEO Title winning over the archive default. Clear it in the post editor, or use SEO Manager inline edit.

Scope

What this covers:

A single list of every content type with a direct link to its SEO panel.
Providing the sequence for an initial SEO setup sweep.
Explaining the priority order: per-item > type archive defaults > global defaults.

What this does not cover:

Editing SEO fields — the hub is navigation only. Editing happens inside each type's panel or the SEO Manager.
Per-item SEO overrides — set in the item editor or SEO Manager.
Global SEO settings — see Global SEO.
Schema / structured data — that is per-item in the Schema Editor.

Reference

Content type	Archive SEO panel	Per-item override location
Blog Posts	Blog Archive SEO	Post editor → SEO tab, or SEO Manager inline
Events	Events Archive SEO	Event editor → SEO tab, or SEO Manager inline
Products	Products SEO	Product editor → SEO tab, or SEO Manager inline
Pages	Global SEO (pages use global defaults)	Page editor → SEO tab, or SEO Manager inline
Custom Post Types	Post Type SEO → Custom type link	Custom item editor → SEO tab

Examples

Setting up a new content type. You set up blogs last week; now you want to do events. Open Post Type SEO, click Events SEO, fill the archive title and meta description, save. Done — no hunting through the left nav.

First-time SEO sweep on a new site. Work down the list: Blogs SEO → save. Events SEO → save. Store SEO → save. Pages → set per-page inside each editor. The hub makes the sequence systematic.

Per-type SEO coverage after the first pass

Blog Posts 12 Events 4 Products 18 Pages 2 Custom Objects 0

Auditing an inherited site. Open Post Type SEO, click each link, review what the previous admin set, move on.

All content types — what each Post Type SEO link manages

What each Post Type SEO link manages, summarised

+ Add New

Content type	Where SEO lives	Items affected	Default fallback
Blog Posts	Blogs SEO archive screen	12 posts	Inherits archive default; per-post override available
Events	Events SEO archive screen	4 events	Inherits Events archive default
Products	Store SEO archive screen	18 products	Inherits Store archive default; per-product override in product editor
Pages	Each page editor (no shared screen)	2 pages	No shared fallback — set per page
Custom Post Types	Custom Objects module	0 (none configured)	Set up inside Custom Objects

Pre-launch SEO sweep. Click each of the first three links — Blogs, Events, Store — confirm each archive has a sensible SEO Title and Meta Description, save if anything is empty. Linear, nothing gets skipped.

What NOT to use this for

Do not look for edit controls on this page. It is a list of links — click through to a sub-page to change anything.
Do not expect per-post SEO editing here. Per-post SEO lives in each post's own editor or the SEO Manager grid.
Do not use this hub to change site-wide SEO defaults. Site-wide defaults live on Global SEO.
Do not treat the Pages link as a defaults screen. It opens the Pages list — each page's SEO is set inside its own editor.
Do not assume the hub controls indexing. The indexing toggle is on Global SEO. Per-type screens control title and description only.
Do not look here for schema markup. Structured data lives on the Schema Editor screen.

How this connects to other features

Blogs SEO — archive defaults for blog posts plus permalink structure for /blog/<slug> URLs.
Events SEO — archive defaults for events and the events archive page.
Store SEO — archive defaults for the products listing and per-product fallbacks. (Ecommerce sites only.)
SEO Manager — per-page SEO grid across every content type. Per-page values here always win over per-type defaults.
Global SEO — site-wide defaults that per-type screens override.
Custom Objects — custom content type SEO lives inside that module.
Robots.txt — crawler access at file level; per-type SEO has no effect on paths disallowed there.
Google Search Console — after saving per-type changes, submit the relevant archive URL (/blog, /events, /shop) for a fresh crawl.

Before you start

You are signed in to SGEN as an admin.
You know which content type you want to set SEO for. If unsure, open SEO Manager and scan for gaps.
Store SEO requires the Ecommerce module to be enabled. If the Store link is missing, Ecommerce is off.
Custom Post Types requires at least one custom type configured in Custom Objects.

Where to go

Open the left navigation.
Click SEO → Post Type SEO, or open /sg-admin/seo/post_type directly.

You land on the Post Type SEO page with breadcrumb Dashboard → SEO → Post Type SEO.

The left rail keeps every sibling SEO panel one click away — Global SEO, Blogs SEO, Events SEO, Store SEO, Post Type SEO, Google Search Console, Schema Editor, Robots.txt.

Steps

1. Pick the content type you want

The page shows a single card with five list-group links:

Blogs SEO

Permalink structure + archive SEO defaults for blog posts.

Events SEO

Archive SEO defaults for events.

Store SEO

Archive SEO defaults for store / product pages.

Pages (per-page SEO)

Opens the Pages list. Edit each page individually for its SEO.

Custom Post Types

Opens Custom Objects where custom content types are managed.

Blogs SEO — permalink structure + default SEO title, description, and canonical for the blog archive and a fallback for individual posts.
Events SEO — default SEO for the Events archive plus a fallback for individual events.
Store SEO — default SEO for the store / product archive plus a fallback for individual products.
Pages (per-page SEO) — opens the Pages list. Static pages do not have a shared default screen — you edit SEO inside each page's own editor.
Custom Post Types — opens Custom Objects, where you manage any custom content types and their SEO.

2. Click the link you want

Each link opens the matching sub-page directly.

For Blogs SEO, you land on the archive defaults form:

Dashboard / SEO / Blogs SEO

←

Blogs SEO

Archive defaults inherited by every blog post

For Store SEO on an Ecommerce site, the same shape applies but with product-specific fields:

Dashboard / SEO / Store SEO

←

Store SEO

Archive defaults inherited by every product page

For Pages, the link goes to the Pages list — there is no shared form because each page's SEO is set inside its own editor.

For Custom Post Types, the link goes to Custom Objects.

3. Confirm the change shows on your live site

Per-type SEO defaults take effect immediately when you save. The linked archive page picks up new values on its next request.

For a blog post with no per-post SEO Title set, the rendered <head> inherits the per-post fallback title format from Blogs SEO:

Inherited from Blogs SEO — blog post with no per-post SEO Title sethtml

<title>Example Post | Your Sitetitle><meta  name="description"  content="The post excerpt appears here when no per-post meta description is set."><meta  name="robots"  content="index, follow"><meta  property="og:title"  content="Example Post | Your Site"><meta  property="og:type"  content="article">

This blog post has no per-post SEO Title set. The title falls back to the per-post fallback format from Blogs SEO — %title% | Your Site — populated with the actual post title.

A product page with no per-product SEO Title set similarly inherits from Store SEO:

Inherited from Store SEO — product with no per-product SEO Title sethtml

<title>Example Product — Your Sitetitle><meta  name="description"  content="Product short description. From $30.00"><meta  name="robots"  content="index, follow"><meta  property="og:title"  content="Example Product — Your Site"><meta  property="og:type"  content="product"><meta  property="product:price:amount"  content="30.00">

The product title and meta follow the formats set on Store SEO. The From $30.00 suffix comes from the Include product price in meta toggle.

4. Move on to the next content type

Click the back button to return to the hub and pick the next link. Each per-type screen is independent — saving Blogs SEO does not touch Events SEO or Store SEO.

A practical rhythm: open Post Type SEO → click the first uncovered type → set archive defaults → save → back → next. Five content types take around ten to fifteen minutes if you have the copy ready in advance.

What success looks like

The hub loads with five visible links.
Clicking a link navigates to the expected sub-page (or to Custom Objects, for Custom Post Types).
After saving on the sub-page, the green confirmation banner appears at the top of that page.
Public pages of the relevant content type pick up the new defaults on their next render.

Blogs SEO saved

Apr 22, 2026 14:03

Blogs SEO defaults have been successfully updated! All blog posts will inherit these defaults unless overridden per post.

Updated: blog_seo[archive_title]blog_seo[archive_meta]blog_seo[post_title_format]

To spot-check: open a post in a fresh tab and use View Source to look at the rendered <head>. A per-page SEO Title overriding the new archive default will be visible here.

What to do if it does not work

A link shows "Page not found." That content type may not be enabled. Check the left nav for the corresponding module (Events, Store, Custom Objects).
The Store link does not load. Ecommerce may be disabled. Enable it under Ecommerce → Configuration.
The Custom Post Types link opens an empty Custom Objects screen. No custom types have been configured yet.
I clicked Pages and there is no SEO field. Expected — Pages is a list, not a defaults form. Click any individual page, then look for the SEO panel in the right rail.
I saved on a per-type screen but the public page still shows the old SEO. Hard-reload the page (Ctrl+F5 / Cmd+Shift+R). If the new SEO still does not show, check that the per-page SEO Title is empty — per-page values always win over per-type defaults.
The hub looks empty or has fewer than five links. Confirm you are signed in as an admin. If you are an admin and still see fewer links, some modules may be intentionally disabled.
I want to see SEO across every content type in one table. Open SEO Manager — the hub is for jumping to per-type defaults; the Manager is for auditing per-page values across all types.

Next step

Set blog archive SEO defaults — fill in the Blogs SEO screen the hub links to.
Set events archive SEO defaults — same idea for the Events archive.
Set site-wide SEO defaults — site-wide fallbacks that every per-type screen sits on top of.
Audit SEO across your whole site — the SEO Manager grid across every content type.