Skip to content

fix(seo): drop trailing slashes from mergify.com canonical URLs#75

Merged
jd merged 1 commit into
mainfrom
devs/jd/feat/drop-trailing-slash-canonicals/drop-trailing-slashes-mergify-com-canonical-urls--aed63ca0
May 19, 2026
Merged

fix(seo): drop trailing slashes from mergify.com canonical URLs#75
jd merged 1 commit into
mainfrom
devs/jd/feat/drop-trailing-slash-canonicals/drop-trailing-slashes-mergify-com-canonical-urls--aed63ca0

Conversation

@jd
Copy link
Copy Markdown
Member

@jd jd commented May 18, 2026

mergify.com runs trailingSlash: "never" (standardized in
mergify.com#466). The canonical tags added in #62 point at
https://mergify.com/learn/merge-queue/ etc. with trailing slashes,
which forces Google to follow a 301 to the no-slash form. Cleaner to
point directly at the canonical URL the destination actually emits.

Affects all 7 canonicalized pages:
/ -> /learn/merge-queue
/introduction/what-is-a-merge-queue
/introduction/how-merge-queues-work
/features/batching
/features/parallel-queues
/features/speculative-merging
/features/two-step-ci

Verified by inspecting dist/*/index.html after build.

Co-authored-by: Claude Opus 4.7 (1M context) noreply@anthropic.com

mergify.com runs trailingSlash: "never" (standardized in
mergify.com#466). The canonical tags added in #62 point at
https://mergify.com/learn/merge-queue/ etc. with trailing slashes,
which forces Google to follow a 301 to the no-slash form. Cleaner to
point directly at the canonical URL the destination actually emits.

Affects all 7 canonicalized pages:
  /              -> /learn/merge-queue
  /introduction/what-is-a-merge-queue
  /introduction/how-merge-queues-work
  /features/batching
  /features/parallel-queues
  /features/speculative-merging
  /features/two-step-ci

Verified by inspecting dist/*/index.html after build.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Change-Id: Iaed63ca0c1c7ef6d6b0d3ae6ecc6a0f217621292
@mergify mergify Bot had a problem deploying to Mergify Merge Protections May 18, 2026 21:20 Failure
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 18, 2026

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 👀 Review Requirements

Waiting for

  • #approved-reviews-by >= 1
This rule is failing.
  • #approved-reviews-by >= 1

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?:

🟢 🔎 Reviews

Wonderful, this rule succeeded.
  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

Wonderful, this rule succeeded.
  • body ~= (?ms:.{48,})

@jd jd marked this pull request as ready for review May 19, 2026 07:13
@jd jd merged commit 0ab26c6 into main May 19, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant