Apply SEO and metadata best practices - #6755
Merged
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
ethanpalm
approved these changes
Jul 27, 2026
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
2 participants
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
Make the Route 53 and CloudFront page title describe its specific purpose (subpath deployment) so it isn't a generic product-name title in search snippets.
Changes
deploy/route53-cloudfront.mdx: title changed from "AWS Route 53 and CloudFront" (27 chars, generic) to "Deploy at a subpath with AWS Route 53 and CloudFront" (52 chars), matching the parallel Cloudflare Workers page.Context
Audited the two files in scope for PR #6687 (
deploy/cloudflare.mdx,deploy/route53-cloudfront.mdx). All descriptions were unique and within 130–160 characters. Only the Route 53 title was flagged as insufficiently specific; the Cloudflare page metadata already passes all checks.Note
Low Risk
Documentation frontmatter-only SEO title tweaks with no runtime or deployment behavior changes.
Overview
Updates only the frontmatter
titleon the Route 53 + CloudFront deploy guide so search snippets and nav metadata spell out subpath deployment, not a generic AWS product pairing.English changes from a short generic title to "Deploy at a subpath with AWS Route 53 and CloudFront", aligned with sibling guides like
deploy/cloudflare.mdxanddeploy/vercel.mdx. The same intent is applied in es, fr, and zh locale copies ofroute53-cloudfront.mdx. Descriptions, keywords, and page body are unchanged.Reviewed by Cursor Bugbot for commit f5ed907. Bugbot is set up for automated code reviews on this repo. Configure here.