SEO: index all pages, not only those in the navigation - #792
Draft
mintlify[bot] wants to merge 1 commit into
Draft
SEO: index all pages, not only those in the navigation#792mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
- Updated docs.json Mintlify-Source: dashboard-editor
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
What
One line in
docs.json:seo.indexingfrom"navigable"to"all".metatags.og:imageis unchanged. It appears in the diff only becauseupdate_configreplaces a top-level key rather than deep-merging, so it had to be restated to preserve it.Why
36 routable pages sit outside the
docs.jsonnavigation tree. Becauseseo.indexingis"navigable", search engines and AI crawlers have been told not to index any of them.To be clear about blame: this is not a regression from #787.
"navigable"is Mintlify's default, so that PR's explicit"indexing": "navigable"line was a no-op that made the existing default visible. The exclusion has been in force all along, which is why it went unnoticed.Counting
pagesentries plus grouprootkeys gives 319 navigable references against 356.mdxfiles. Excludingsnippets/(includes, not routable), the 36 affected pages are:None of them carry deliberate
noindexfrontmatter, so the exclusion looks like a byproduct of nav omission rather than an editorial choice.This matters more than a normal indexing gap. Per Mintlify's own analytics for this deployment, ChatGPT and Claude Code are about 79 percent of agent traffic to these docs, and agent traffic is roughly 70 percent of all docs traffic. SDK reference and SDK tutorials are precisely what coding agents consume, and right now they are the pages being withheld.
Trade-off worth a reviewer's judgement
"all"also indexes the two auto-generatedapi-reference/docs/GET/*pages, which are thin. If those are not wanted in the index, the cleaner fix isnoindex: truein their frontmatter rather than reverting this setting.The alternative approach is adding the valuable pages to the navigation on their merits, which is better for human readers too. That is a content-architecture decision for the docs team, and it is not mutually exclusive with this change.
Verification
Diff reviewed before opening: exactly one changed value,
metatagsintact. No content, navigation, or redirect changes.Generated by Claude Code
Mintlify
0 threads from 0 users in Mintlify