[{"data":1,"prerenderedAt":75},["ShallowReactive",2],{"help-article-configuring-seo-defaults":3},{"data":4},{"title":5,"excerpt":6,"content":7,"help_category":8,"seo":11},"Configuring SEO Defaults (in Content Types)","SEO defaults now live on each content type in m18t. Learn every field — path prefix, schema type, robots, title template — and how a piece overrides them.","\u003Cp>\u003Cstrong>What you'll learn\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Where SEO defaults live now that there's no standalone SEO Indices page.\u003C\u002Fli>\n\u003Cli>Each field on a content type and what it controls.\u003C\u002Fli>\n\u003Cli>How a per-piece SEO value overrides a type default.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>The concept: the type is the SEO record\u003C\u002Fh2>\n\u003Cp>In m18t, the SEO defaults for a kind of content are stored \u003Cem>on the content type itself\u003C\u002Fem>. There is no separate "SEO Indices" screen anymore — the old \u003Ccode>\u002Fstudio\u002Fconfig\u002Fseo-indices\u003C\u002Fcode> route 301-redirects to \u003Cstrong>Content Types\u003C\u002Fstrong>. When you define a blog post, a help article, or a custom type like \u003Ccode>case-study\u003C\u002Fcode>, you're also defining how every piece of that type gets a URL, a title, a robots policy, and a schema.org type.\u003C\u002Fp>\n\u003Cp>Defaults are scoped per (brand × type). The same \u003Ccode>blog-post\u003C\u002Fcode> type can carry different defaults for two different brands. That's what keeps URLs and titles consistent within a brand and lets each brand keep its own conventions. The bigger picture is in \u003Ca href=\"\u002Fhelp\u002Fthe-seo-philosophy\">The SEO Philosophy\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>How to configure a content type's SEO defaults\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Go to \u003Cstrong>Configuration ▸ Content Types\u003C\u002Fstrong> (\u003Ccode>\u002Fstudio\u002Fconfig\u002Fcontent-types\u003C\u002Fcode>). If this is new to you, click \u003Cstrong>How this works\u003C\u002Fstrong> for the in-page guide.\u003C\u002Fli>\n\u003Cli>Add a type or edit an existing one. To add: click \u003Cstrong>Add Content Type\u003C\u002Fstrong> (or pick a card from \u003Cstrong>Quick-start templates\u003C\u002Fstrong> — Blog Post, Help Article, and so on). To edit an existing type, click the pencil icon on its row.\u003C\u002Fli>\n\u003Cli>Set the \u003Cstrong>Brand\u003C\u002Fstrong> the defaults apply to, the \u003Cstrong>Content Type ID\u003C\u002Fstrong> (lowercase, dashes — e.g. \u003Ccode>blog-post\u003C\u002Fcode>), and a \u003Cstrong>Display Label\u003C\u002Fstrong> (what shows in publisher pickers).\u003C\u002Fli>\n\u003Cli>Set \u003Cstrong>Path Prefix\u003C\u002Fstrong> — the URL segment entries of this type live under, e.g. \u003Ccode>\u002Fblog\u002F\u003C\u002Fcode>. This feeds the \u003Ca href=\"\u002Fhelp\u002Fcanonical-urls\">canonical URL\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Set \u003Cstrong>Schema.org @type\u003C\u002Fstrong> — the JSON-LD type for answer engines, e.g. \u003Ccode>Article\u003C\u002Fcode>, \u003Ccode>BlogPosting\u003C\u002Fcode>, \u003Ccode>FAQPage\u003C\u002Fcode>, \u003Ccode>WebPage\u003C\u002Fcode>. See \u003Ca href=\"\u002Fhelp\u002Fstructured-data-json-ld\">Structured Data & JSON-LD\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Set the \u003Cstrong>Meta Title Template\u003C\u002Fstrong>. It supports \u003Ccode>{{BRAND_TITLE}}\u003C\u002Fcode>, \u003Ccode>{{POST_TITLE}}\u003C\u002Fcode>, and \u003Ccode>{{SEPARATOR}}\u003C\u002Fcode> — the default is \u003Ccode>{{BRAND_TITLE}} | {{POST_TITLE}}\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Set \u003Cstrong>Default Keywords\u003C\u002Fstrong> (comma-separated — these also seed the \u003Ca href=\"\u002Fhelp\u002Fthe-seo-ai-prompt\">SEO AI prompt\u003C\u002Fa>), \u003Cstrong>Default Robots\u003C\u002Fstrong> (e.g. \u003Ccode>index, follow\u003C\u002Fcode>), \u003Cstrong>Supported Locales\u003C\u002Fstrong> (e.g. \u003Ccode>ar,en\u003C\u002Fcode>), and a \u003Cstrong>Fallback OG Image\u003C\u002Fstrong> for pieces that don't set their own.\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Save changes\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>From then on, every new piece of that type for that brand starts with these values pre-filled.\u003C\u002Fp>\n\u003Ch2>How overrides work\u003C\u002Fh2>\n\u003Cp>A type default is a starting point, not a lock. When you create a piece and open its \u003Cstrong>SEO\u003C\u002Fstrong> tab in the content editor, every default is editable for that piece alone:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Forgot a per-post social image? The type's \u003Cstrong>Fallback OG Image\u003C\u002Fstrong> fills in.\u003C\u002Fli>\n\u003Cli>Need a different title than the template produced? Edit it on the piece, or regenerate it with \u003Cstrong>Generate Meta with AI\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>Publishing a private piece in an otherwise-indexed type? Switch its robots to \u003Ccode>noindex, nofollow\u003C\u002Fcode> on the piece.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The piece wins over the type. The type wins over nothing — it's the floor.\u003C\u002Fp>\n\u003Ch2>Common variations\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Changing a default after pieces already exist.\u003C\u002Fstrong> Editing a type's defaults changes what \u003Cem>new\u003C\u002Fem> pieces inherit. Pieces already created keep the values they were given; already-\u003Ca href=\"\u002Fhelp\u002Fscheduling-vs-publishing\">published\u003C\u002Fa> pieces also need a re-push to update what's in your CMS — see \u003Ca href=\"\u002Fhelp\u002Fpushing-to-your-cms\">Pushing to your CMS\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>A private\u002Finternal type.\u003C\u002Fstrong> Set \u003Cstrong>Default Robots\u003C\u002Fstrong> to \u003Ccode>noindex, nofollow\u003C\u002Fcode> on the type so every piece of it stays out of the index by default.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Deleting a type.\u003C\u002Fstrong> m18t blocks deletion while content entries still use the type — archive or migrate those entries first. This avoids orphaned URLs and broken CMS pushes.\u003C\u002Fp>\n\u003Ch2>What's next\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fthe-seo-philosophy\">The SEO Philosophy\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fcanonical-urls\">Canonical URLs\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fthe-seo-ai-prompt\">The SEO AI Prompt\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fregistering-a-custom-content-type\">Registering a Custom Content Type\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>FAQ\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Where did the SEO Indices page go?\u003C\u002Fstrong>\nIt was folded into Content Types. The SEO defaults that used to live on a separate "SEO Indices" screen now live on each content type at \u003Ccode>\u002Fstudio\u002Fconfig\u002Fcontent-types\u003C\u002Fcode>. The old route 301-redirects there.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Do SEO defaults apply across all my brands?\u003C\u002Fstrong>\nNo. They're per (brand × type). The same \u003Ccode>blog-post\u003C\u002Fcode> type can have different path prefixes, titles, and robots policies for two brands. Pick the brand at the top of the form.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What variables can I use in the meta-title template?\u003C\u002Fstrong>\n\u003Ccode>{{BRAND_TITLE}}\u003C\u002Fcode>, \u003Ccode>{{POST_TITLE}}\u003C\u002Fcode>, and \u003Ccode>{{SEPARATOR}}\u003C\u002Fcode>. The default template is \u003Ccode>{{BRAND_TITLE}} | {{POST_TITLE}}\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Can I stop a content type from being indexed?\u003C\u002Fstrong>\nYes — set its Default Robots to \u003Ccode>noindex, nofollow\u003C\u002Fcode>. Every new piece of that type inherits it, and you can still override per piece.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why can't I delete a content type?\u003C\u002Fstrong>\nm18t hard-blocks deleting a type while content entries reference it. Archive or migrate those entries first, then delete.\u003C\u002Fp>\n",{"slug":9,"title":10},"seo","SEO",{"meta_title":12,"meta_description":6,"keywords":13,"canonical_url":14,"og_title":5,"og_description":15,"og_image":16,"robots":17,"json_ld":18},"Configuring SEO Defaults (in Content Types) | m18t Help","SEO defaults, content types, path prefix, meta title template, default robots, schema.org type, fallback OG image, per-piece override","https:\u002F\u002Fm18t.com\u002Fhelp\u002Fconfiguring-seo-defaults","The content type is the SEO record. Set path prefix, schema type, robots, and a title template per brand and type, then override per piece.","https:\u002F\u002Fm18t.com\u002Fog-default.png","index, follow",{"@context":19,"@graph":20},"https:\u002F\u002Fschema.org",[21,34,59],{"@type":22,"headline":5,"description":6,"articleSection":10,"inLanguage":23,"datePublished":24,"dateModified":24,"image":16,"author":25,"publisher":29,"mainEntityOfPage":32},"Article","en","2026-06-25",{"@type":26,"name":27,"url":28},"Organization","m18t","https:\u002F\u002Fm18t.com",{"@type":26,"name":27,"url":28,"logo":30},{"@type":31,"url":16},"ImageObject",{"@type":33,"@id":14},"WebPage",{"@type":35,"mainEntity":36},"FAQPage",[37,43,47,51,55],{"@type":38,"name":39,"acceptedAnswer":40},"Question","Where did the SEO Indices page go?",{"@type":41,"text":42},"Answer","It was folded into Content Types. The SEO defaults that used to live on a separate SEO Indices screen now live on each content type at \u002Fstudio\u002Fconfig\u002Fcontent-types. The old route 301-redirects there.",{"@type":38,"name":44,"acceptedAnswer":45},"Do SEO defaults apply across all my brands?",{"@type":41,"text":46},"No. They're per (brand × type). The same blog-post type can have different path prefixes, titles, and robots policies for two brands. Pick the brand at the top of the form.",{"@type":38,"name":48,"acceptedAnswer":49},"What variables can I use in the meta-title template?",{"@type":41,"text":50},"{{BRAND_TITLE}}, {{POST_TITLE}}, and {{SEPARATOR}}. The default template is {{BRAND_TITLE}} | {{POST_TITLE}}.",{"@type":38,"name":52,"acceptedAnswer":53},"Can I stop a content type from being indexed?",{"@type":41,"text":54},"Yes — set its Default Robots to noindex, nofollow. Every new piece of that type inherits it, and you can still override per piece.",{"@type":38,"name":56,"acceptedAnswer":57},"Why can't I delete a content type?",{"@type":41,"text":58},"m18t hard-blocks deleting a type while content entries reference it. Archive or migrate those entries first, then delete.",{"@type":60,"itemListElement":61},"BreadcrumbList",[62,66,70,73],{"@type":63,"position":64,"name":65,"item":28},"ListItem",1,"Home",{"@type":63,"position":67,"name":68,"item":69},2,"Help","https:\u002F\u002Fm18t.com\u002Fhelp",{"@type":63,"position":71,"name":10,"item":72},3,"https:\u002F\u002Fm18t.com\u002Fhelp\u002Fcategories\u002Fseo",{"@type":63,"position":74,"name":5,"item":14},4,1786312170141]