Control How WordPress Describes the Site to Search Engines, Social Platforms, and Machine Readers
Meta & Schema centralizes three separate configuration jobs: Global SEO for titles, descriptions, and content scope; Social for Open Graph and social-share identity; and Schema for entity defaults, publisher identity, sitelink-readiness signals, WooCommerce structured data, and commerce discovery outputs.
TitlesSocialSchemaCommerce
Separate Search Snippets, Social Sharing, and Structured Data
The Meta & Schema tab exposes three real 2.9.4 subtabs: Global SEO, Social, and Schema. Keeping them separate makes each output easier to reason about and test.
Click a stage to expand
01Global SEOtitles + descriptions
02SocialOG + X cards
03Schema Defaultstype mapping
04Per-Page Overrideonly when needed
05Commerceownership + feeds
06Validategenerated output
Set Repeatable Metadata Defaults Without Making Every Page Identical
Global SEO controls the templates and content scope Aegisify uses when a page does not have a deliberate per-content override.
Separator + Contextual Templates
Configure the title separator and separate templates for the homepage, posts, pages, archives, WooCommerce products, and WooCommerce taxonomies. Templates let the site keep consistent brand patterns without manually editing every new URL.
Home, Post, Page & Commerce Defaults
Meta-description templates cover the homepage, posts, pages, products, and product taxonomies. Per-content descriptions can still replace the default when a page needs a more specific search snippet summary.
Smart or Manual Inclusion
The Content Scope Mode can use Smart behavior or an explicit include-only list, with separate post-type exclusions. This keeps internal or application-specific content types from automatically inheriting public SEO behavior when they should remain outside the scope.
Global SEO & Marketing Context
An optional AI Global SEO & Marketing Brief gives Aegisify Core-assisted generation additional business context. It is guidance for generation, not permission to invent product claims or guarantee ranking outcomes.
Use Real Product Variables Instead of Generic Store Templates
Aegisify 2.9.4 includes product-aware title variables and separate product/taxonomy metadata controls for commerce sites.
Commerce-Aware Variables
Product title templates can use supported values such as product name, SKU, GTIN, MPN, brand, price, sale price, currency, stock status, product category, and product attributes when those values actually exist.
Category-Level Search Snippets
WooCommerce taxonomy templates support term, term description, site name, and separator variables so product-category pages do not have to inherit the same wording as individual products.
Never Invent Commerce Attributes
The plugin’s schema settings explicitly treat values such as MPN as real product evidence. Missing identifiers should remain missing or be populated from a verified store field rather than being fabricated for SEO.
Control How Content Is Represented When It Is Shared
Search snippets and social previews are different outputs. Aegisify keeps social metadata in its own configuration surface.
Enable Social Graph Metadata
Open Graph can be enabled independently, allowing supported social platforms and messaging surfaces to read page title, description, URL, image, and related metadata without relying only on generic HTML title tags.
Summary or Large Image
Enable Twitter Card metadata and choose between summary and summary_large_image output. Site and creator handles can be configured separately where those identities are maintained.
Default Social Image
A default social image provides a fallback when page-specific media is unavailable. High-value pages should still use relevant imagery rather than forcing one generic brand graphic onto every shared URL.
Connect Brand Identity
Social profile URLs, Facebook App/Admin identifiers, and optional article metadata give the sharing layer additional identity and publishing context. Output should match real profiles and ownership information.
The Social subtab also has a separate AI Social / AI Discovery Brief. This helps assisted generation understand social and discovery context while remaining separate from Global SEO and Schema briefs.
Define the Site Identity and Default Structured-Data Model
Aegisify uses a connected graph model instead of unrelated schema fragments.
Schema Defaults by Content Type
Map registered post types to supported schema defaults. Aegisify’s schema engine supports templates including WebPage, Article, BlogPosting, FAQPage, HowTo, Product, LocalBusiness, Organization, Person, Event, and JobPosting.
Organization or Person
Select the publisher model, set the Organization or Person name, attach the site logo, and optionally define a real alternate site name. This establishes stable entity identity across the generated graph.
Use Evidence, Not Keywords
When enabled, Aegisify can detect FAQPage from Q/A pairs, HowTo from numbered steps, and Product from the product post type. Higher-risk rich-result types such as Event or JobPosting require explicit structured evidence rather than keyword guessing.
Navigation Signals, Not Sitelink Guarantees
Optional SiteNavigationElement output can describe eligible primary-navigation destinations and trigger IndexNow when navigation changes. The setting itself states that search engines still choose sitelinks algorithmically.
Control Product Schema Ownership and Commerce Discovery
WooCommerce settings live inside the Schema subtab because product identity, offers, policies, and commerce feeds are structured-data decisions.
Product Schema Ownership can operate in Auto mode, explicitly replace WooCommerce Product schema with Aegisify, enhance WooCommerce Product schema, or disable Aegisify Product output. Auto mode is designed to avoid duplicate ownership when another SEO provider is detected.
Administrators can identify the brand taxonomy and optional MPN meta key, define a truthful default product condition, and specify the meta key used to mark discontinued products. Aegisify also supports an optional paginated public AI Commerce Catalog and an XML Merchant Product Feed with eligible simple products or variations.
Separate store-wide shipping and return schema controls include country, currency, flat shipping rate, handling/transit ranges, return-policy country, return window, return method, and return shipping fees. The UI explicitly tells administrators to leave these blank unless the policy truly applies store-wide.
Let Global Defaults Handle the Common Case, Then Override With Evidence
The WordPress editor metabox can override the global schema default and store type-specific supporting fields when a page genuinely needs a different model.
Product overrides can store price, currency, availability, brand, and SKU. LocalBusiness can use telephone, address, and optional geo coordinates. Event can use start/end dates and location data. The schema engine validates supported required fields and detects FAQ/HowTo patterns from actual content.
Aegisify’s schema graph connects publisher identity, WebSite, WebPage, author, and the primary Article/Product/content node through stable relationships. Breadcrumb and other supported filters can enrich that graph, while Schema Intelligence provides the separate audit layer for coverage, broken references, and connectivity.
Set the Baseline Once, Then Override Only Where the Page Needs It
Use Aegisify SEO to keep metadata, social identity, schema defaults, and commerce facts consistent without replacing accuracy with automation.
Common Questions About the Three Subtabs
What are the Meta & Schema subtabs in 2.9.4?
Global SEO, Social, and Schema. WooCommerce SEO and shipping/return structured-data settings are sections inside Schema, not separate top-level subtabs.
Does changing a global title template overwrite every custom SEO title?
The global template is a default. Per-content metadata can provide a more specific value where the page has been intentionally optimized.
Can Aegisify automatically detect every schema type?
No. FAQPage, HowTo, and Product have supported evidence-based autodetection paths. Higher-risk types require explicit structured evidence rather than keyword inference.
Do sitelink-readiness signals guarantee sitelinks?
No. The setting itself states that search engines choose sitelinks algorithmically. Aegisify can describe eligible navigation destinations but cannot force their display.
How can Aegisify AI help?
Ask about Aegisify or WordPress: errors, plugins, security, SEO, compatibility, troubleshooting, comparisons, or launch a free website scan.