Update from code changes: document seo.paths folder-scoped meta tags - #7462
Merged
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
|
- 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
approved these changes
Sep 24, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new
seo.pathsconfig option and the related frontmatter override behavior for custom meta tags.seo.pathslets you scope meta tags to a folder (for example, versioned docs or a product area) on top of site-wideseo.metatags. Page frontmatter still wins on predefined SEO fields and can now also override any custom meta tag thatseo.metatagsor a matchingseo.pathsentry declares.canonicalremains site-scoped.Changes
organize/settings-seo.mdx: addedseo.pathsfield 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 underseo.metatagsorseo.paths(non-empty string values only; frontmatter cannot introduce undeclared keys).es/,fr/, andzh/.Update history
seo.pathsinorganize/settings-seo.mdxandoptimize/seo.mdx, pluses,fr,zhtranslations. Documents https://github.com/mintlify/mint/pull/11421.seo.metatagsorseo.paths, with the same rules mirrored toes,fr,zh. Documents https://github.com/mintlify/mint/pull/11422.Note
Low Risk
Documentation-only changes with no runtime or config schema edits in this repository.
Overview
This PR documents the
seo.pathsoption and related frontmatter behavior across English, Spanish, French, and Chinese.seo.pathslets teams set folder-scoped meta tags indocs.json(for examplenoindexonguides/v1or a differentog:imageonguides/v2) without repeating frontmatter on every page. The neworganize/settings-seoreference describes the schema (path+metatags), precedence (seo.metatags→ matchingseo.paths, with longer paths winning → page frontmatter), locale-specific URL matching, and thatcanonicalis ignored inside path entries.optimize/seoadds a “Folder-scoped meta tags” guide with an example and clarifies that page frontmatter can override custom tags already declared inseo.metatagsor a matchingseo.pathsentry (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.