Experiment: trailing-slash canonical on 20 top docs pages (+ canonical base fix)#422
Merged
Merged
Conversation
- seo.metatags.canonical -> https://www.checklyhq.com/docs so Mintlify's auto-generated canonicals keep the /docs mount (bare origin dropped it). Supersedes #421. - Remove the temporary trailing-slash canonical from cli/overview.mdx so it rejoins the control group. This makes every non-experiment page emit www + /docs + no-slash — the control baseline for the trailing-slash canonical experiment. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add an explicit per-page `canonical:` (full www + /docs + trailing-slash URL, matching the served/indexed URL) to the 20 highest-keyword-coverage docs pages. The rest of the site keeps the auto-generated no-slash canonical as the control group. Goal: over ~3 weeks, see whether byte-exact trailing-slash canonicals change how Google canonicalizes/indexes these pages vs. the no-slash canonical (which 308s to the served slash URL). Evaluate ~2026-07-27. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
Trailing-slash canonical experiment (20 pages) + canonical base fix
A/B-style test: give the 20 top docs pages an explicit trailing-slash canonical and leave everything else on the auto-generated no-slash canonical as a control. Evaluate in ~3 weeks (~2026-07-27).
Baseline fix (commit 1) — supersedes #421
docs.jsonseo.metatags.canonical→https://www.checklyhq.com/docs(the bare origin was dropping the/docsmount, emittingchecklyhq.com/detect/overview).cli/overview.mdxso it rejoins the control.www + /docs + no-slash— the control baseline.The experiment (commit 2)
20 pages get a per-page
canonical:equal to their own served URL (www + /docs + trailing slash). Chosen by keyword coverage (organic traffic is ~0 across docs, so keywords is the best "importance" proxy):How to evaluate (~2026-07-27)
Primary signal is how Google canonicalizes/indexes the test pages, not traffic (docs traffic is tiny):
If the trailing-slash pages behave better (or the same with cleaner signals), roll out per-page canonicals more broadly; if no difference, the
docs.jsonno-slash baseline stands on its own and we skip the per-page maintenance.Verified:
docs.jsonvalid, all 20 frontmatter blocks parse,mint broken-linksclean.🤖 Generated with Claude Code