Boost search ranking for hub pages by nav level - #160
Draft
hywel-mixpanel wants to merge 2 commits into
Draft
Conversation
Contributor
|
Too many files changed for review (148 files, 100 file limit). Bypass the limit by tagging |
Search ranked hub pages below their own children because relevance scoring normalizes by field length: "SDKs: Send data from your application into Mixpanel" scores worse for "SDKs" than the twelve child pages titled "Mixpanel SDKs: <language>". Adds frontmatter boost 3 to sidebar level 1 pages and boost 2 to level 2 across Docs and Guides, so a hub outranks its descendants without changing any visible title. API Docs, changelogs and FAQs are excluded. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
hywel-mixpanel
force-pushed
the
tof-396-boost-search-ranking-by-nav-level
branch
from
August 11, 2026 22:57
490f56f to
2545eec
Compare
hywel-mixpanel
changed the base branch from
tof-396-remove-unsupported-tags-frontmatter
to
main
August 11, 2026 22:57
Shortens the title from "Lexicon: Describe your events and data using a dictionary" to "Lexicon" and moves the clause into description, which Mintlify renders as a visible subtitle beneath the H1. Relevance scoring normalizes by field length, so "lexicon" now matches the full title rather than one word of eight. Reader-visible text is unchanged in wording and order. Trial run for a house-style pattern used by 77 pages in docs/ and guides/; not yet applied more broadly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Hub pages rank below their own children in docs search. Relevance scoring normalizes by field length, so
"SDKs: Send data from your application into Mixpanel"loses the querySDKsto twelve children titled"Mixpanel SDKs: <language>"— the parent has more body mentions and still loses. Adds frontmatterboost3 to sidebar level 1 pages and 2 to level 2 across Docs and Guides, so hubs outrank descendants with no visible change to any page.Excludes API Docs, whose group roots are endpoint pages that would then beat conceptual docs, plus
changelogsand FAQs.Test / Rollout plan
SDKs—Tracking Methods > SDKsshould now appear above the per-language pages.autocapture—Tracking Methods > Autocaptureshould beatQuickstart > Capture Events > Autocapture.cohorts,events,funnels— API reference pages should be unchanged.lexicon— expect this to look worse;docs/cohort-syncis level 1 and carries aFrom Lexicontab. Fixed separately by demoting the Cohort Sync group.