Skip to content

Fix SEO issues: add redirects for three deleted pages - #338

Open
mintlify[bot] wants to merge 1 commit into
masterfrom
mintlify/9dc23222
Open

Fix SEO issues: add redirects for three deleted pages#338
mintlify[bot] wants to merge 1 commit into
masterfrom
mintlify/9dc23222

Conversation

@mintlify

@mintlify mintlify Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Summary

SEO/metadata audit of the ~44 pages changed in the last 30 days found no metadata defects; the only fixes are redirects for three pages deleted in that window that were serving live 404s.

Changes

  • Added /changelog/getting-started/introduction
  • Added /getting-started/collaborating/getting-started/introduction
  • Added /integrations/vercel/getting-started/introduction

All three pages were deleted since 2026-07-31 with no redirect. No surviving page covers their material, so each points at /getting-started/introduction, the destination this repo's existing redirects consistently use when retiring pages without a successor (60+ precedents, including /other-topics/fitting-large-models-on-small-gpus, deleted in this same window). The five other pages deleted in the window (aiVoiceAgents, langchain, mistral-vllm, streaming-falcon-7B, fitting-large-models-on-small-gpus) already had redirects.

Audit result

Every changed page passes all hard checks: titles present and ≤60 chars, descriptions present, unique across the repo, and 131–152 chars. No page metadata was edited. All pages are in the navigation (no orphans), and none carry noindex, hidden, or groups.

Findings not fixed

  • The three redirect destinations above follow repo convention rather than covering the deleted content. If a changelog, team-management, or Vercel-integration page returns, these redirects should be repointed.
  • performance/checkpointing.mdx has a pre-existing MDX parse warning (HTML comment at line 138, introduced in docs: explain why a checkpoint failed and how to fix it #335); left untouched as it is unrelated to metadata.

Context

The local clone was shallow (depth 1) and could not be deepened, so history-based checks (scope, deletions, prior-run churn detection) were reconstructed from the GitHub API by diffing the 2026-07-31 tree against HEAD.

@mintlify
mintlify Bot requested review from kylegani and milo157 as code owners September 1, 2026 15:39
@mintlify

mintlify Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
cerebrium 🟢 Ready View Preview Sep 1, 2026, 3:40 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants