Skip to content

Update from code changes: document seo.paths folder-scoped meta tags - #7462

Merged
ethanpalm merged 4 commits into
mainfrom
mintlify/c48e3342
Sep 24, 2026
Merged

ethanpalm merged 4 commits into
mainfrom
mintlify/c48e3342

Conversation

@mintlify

@mintlify mintlify Bot commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Documents the new seo.paths config option and the related frontmatter override behavior for custom meta tags. seo.paths lets you scope meta tags to a folder (for example, versioned docs or a product area) on top of site-wide seo.metatags. Page frontmatter still wins on predefined SEO fields and can now also override any custom meta tag that seo.metatags or a matching seo.paths entry declares. canonical remains site-scoped.

Changes

  • organize/settings-seo.mdx: added seo.paths field with schema, precedence rules, and an example.
  • optimize/seo.mdx: added a "Folder-scoped meta tags" subsection under Global meta tags, and clarified in "Page-specific meta tags" that frontmatter can override custom tags declared under seo.metatags or seo.paths (non-empty string values only; frontmatter cannot introduce undeclared keys).
  • Mirrored all additions in es/, fr/, and zh/.

Update history


Note

Low Risk
Documentation-only changes with no runtime or config schema edits in this repository.

Overview
This PR documents the seo.paths option and related frontmatter behavior across English, Spanish, French, and Chinese.

seo.paths lets teams set folder-scoped meta tags in docs.json (for example noindex on guides/v1 or a different og:image on guides/v2) without repeating frontmatter on every page. The new organize/settings-seo reference describes the schema (path + metatags), precedence (seo.metatags → matching seo.paths, with longer paths winning → page frontmatter), locale-specific URL matching, and that canonical is ignored inside path entries.

optimize/seo adds a “Folder-scoped meta tags” guide with an example and clarifies that page frontmatter can override custom tags already declared in seo.metatags or a matching seo.paths entry (non-empty strings only; no new undeclared keys).

Reviewed by Cursor Bugbot for commit 4a6db64. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify

mintlify Bot commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
mintlify 🟢 Ready View Preview Sep 24, 2026, 5:41 PM

@mintlify

mintlify Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor Author

Update from code changes updated this PR.

Noted frontmatter can override custom meta tags declared in seo.metatags or seo.paths

Source PRs

  • mintlify/mint#11422 — feat(client): let frontmatter override metatags declared in docs.json

- Replace "canonical is always sourced from seo.metatags", which
  contradicted per-page canonical, with the actual behavior: a canonical
  key in seo.paths entries is ignored.
- Note that paths match page URLs, so language folders need their own
  entries.
- Note that seo.paths metatag values must be non-empty strings.
- Simplify path rules; the validation error lists every constraint.
- Dedupe precedence rules in the SEO guide and link to the reference.
- Move the frontmatter override paragraph after the page-specific tag
  list and example.
- Link to #param-seo-metatags and #param-seo-paths instead of #seo.
- Mirror all changes in es, fr, and zh.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@ethanpalm
ethanpalm merged commit 019431a into main Sep 24, 2026
4 checks passed
@ethanpalm
ethanpalm deleted the mintlify/c48e3342 branch September 24, 2026 18:06

This branch was successfully deployed

1 active deployment
staging — 4a6db642 Deployed Sep 24, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant