SEO

The SG-Admin SEO module — site-wide defaults, per-record metadata, GSC connection.

The SEO module in the admin is the per-site surface for SEO configuration. Site-wide SEO defaults (default meta title pattern, default OpenGraph image, robots configuration) live here; per-record SEO metadata is administered at the record (Pages, Blogs, Products) but can be reviewed in aggregate from the SEO module. This page is the Reference definition.

What is this for?

Read this page when you want the structural definition of the SEO module — what site-wide defaults it carries and how per-record metadata layers on top.

Good use cases

• You are scoping SEO baseline for a new site.
• You are explaining to a stakeholder how SGEN handles SEO.
• You hit a "where do I set the default meta description?" question.

What NOT to use this for

• Step-by-step procedures — open the relevant Guide.
• Per-customer SEO audit work — out of scope.
• Per-release shipped change — open What's New or Changelog.

How this connects to other features

• SG-Admin Overview — parent surface.
• Pages — per-page SEO metadata surface.
• Google Search Console — analytics consumer of SEO data.

Where to find it

Open SG-Admin for the active site. SEO is in the sidebar under the configuration or marketing group. Site-wide defaults, per-record metadata review, robots configuration, and sitemap settings are all reachable from this section. Admin access is required for site-wide changes.

Definition

The SEO module configures site-wide SEO baseline and surfaces per-record SEO metadata for review. Site-wide configuration includes default meta title pattern, default meta description, default OpenGraph image, robots.txt configuration, sitemap generation, and structured-data defaults. Per-record overrides happen at the record (Pages, Blogs, Products) but can be inspected and bulk-edited from this module.

Purpose

Define the SEO module as a Reference layer.

Scope

Covers site-wide defaults, per-record overrides, and GSC integration. Does not cover per-step procedures (Guides) or SEO audit work (out of scope).

Site-wide defaults

Meta title pattern

The pattern used to construct meta titles when per-record meta title is not set. Example: {record-title} — {site-name}.

Meta description default

Default meta description fallback for records without an explicit description.

OpenGraph image default

Site-wide OG image used when per-record OG image is not set.

Robots configuration

Site-wide robots.txt rules. Per-page noindex overrides happen at the record.

Sitemap

The platform generates sitemap.xml automatically; SEO surface allows configuration of inclusion rules.

Per-record overrides

Each record (Page, Post, Product) carries its own SEO metadata fields. When set, the per-record value overrides the site-wide default. The SEO module surfaces per-record metadata in aggregate so operators can scan for missing or thin metadata.

GSC integration

The Google Search Console integration consumes the platform's SEO output and surfaces search performance back into the admin (per the GSC Reference). The two surfaces pair: SEO module configures the output; GSC surfaces the result.

Constraints and boundaries

SEO is a Reference area for site-wide SEO configuration.

Do not use this Reference for: per-record SEO editing (open the record), GSC analytics (open GSC integration Reference), per-step procedures (Guides).

Public boundary

This page is intentionally public-safe.

Examples

Example 1 — Operator sets the meta title pattern

Operator opens SEO, sets the site-wide meta title pattern to {record-title} — SGEN. Every record without a per-record meta title now uses this pattern. The "Getting Started" post renders as "Getting Started — SGEN" in search results without the operator editing that post individually.

Example 2 — Operator audits thin meta descriptions

Operator opens the SEO module's per-record review surface, filters for records with missing or short meta description, addresses them in batch.

Example 3 — Operator updates the OG image after a brand refresh

Operator updates the site-wide OG image. Records without per-record OG override pick up the new default automatically.

Documentation guidance

Use this page as the structural definition for the SEO module.

Reading order

Open this page when scoping SEO baseline. Pair with GSC for the analytics consumer.

Related reading

• SG-Admin Overview — parent surface.
• Pages — per-record SEO metadata.
• Google Search Console — analytics consumer.

Vocabulary cross-reference

• Site-wide default is the SEO value used when per-record value is unset.
• Per-record override is the record-specific SEO value.
• Meta title pattern is the template that constructs default meta titles.
• Sitemap is the auto-generated /sitemap.xml served from the platform.

Maintenance discipline

When the SEO module changes across releases (new default field, new robots option, new sitemap config), update this Reference.

Related reading