Skip to content

SEO weekly: fix developerapi 404 redirect - #875

Closed
CahidArda wants to merge 2 commits into
mainfrom
seo/weekly-2026-09-28
Closed

CahidArda wants to merge 2 commits into
mainfrom
seo/weekly-2026-09-28

Conversation

@CahidArda

@CahidArda CahidArda commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Ahrefs evidence

/docs/howto/developerapi — 404 (Ahrefs Site Audit, crawl 2026-09-27, project "Upstash" 9854245), with a DR91 backlink from pkg.go.dev/github.com/upstash/terraform-provider-upstash/v2 (Ahrefs Site Explorer broken-backlinks for upstash.com). docs.json already redirects /redis/howto/developerapi and /redis/account/developerapi to /common/account/developerapi, but was missing this bare path — a gap, not a new break.

Change

Add one entry to docs.json's redirects array: /howto/developerapi → /common/account/developerapi (matches the existing sibling redirects, exact 1:1 mapping to the current page).

No body copy changed, no pages deleted, no existing URLs changed.

Expected effect

Removes one confirmed 404 from Site Audit's error count and recovers the DR91 backlink's link equity onto the current Developer API page.

Revision history

This PR originally also added 23 /kafka/* redirects to a generic /introduction page. Copilot's review correctly flagged that mass-redirecting many discontinued pages to one unrelated destination risks being treated as a soft 404 by search engines and drops the Kafka-specific context those links/visitors expect — better SEO practice is a genuine 404 (or a per-topic landing page) over a blanket redirect to somewhere irrelevant. Kafka has no successor product in our current lineup, so there's no single correct destination per page. Reverted those 22 entries back to 404 (unchanged from before this PR); a proper Kafka retirement/migration page is tracked as a content opportunity in DX-3085, and redirects can be re-added pointing at it once it exists.

This also resolves Copilot's second finding about /docs/kafka/pricing — that entry no longer exists in this PR. (For the record: that finding was based on an inaccurate note in this PR's original description, which incorrectly said /docs/kafka/pricing was owned by upstash-web; it was actually one of the 22 entries in this file. The upstash-web companion fix only ever covered the bare /kafka marketing path, not any /docs/* path. Both are moot now that the Kafka redirects are reverted.)


🤖 Generated with Claude Code

https://claude.ai/code/session_01W7qK3pnSv744agMxGprgNc

22 /kafka/* doc paths 404 (Ahrefs Site Audit, crawl 2026-09-27) with no
existing redirect; several carry high-authority backlinks (DR90-97 from
github.com/upstash/kafka-js, medium.com/upstash, auth0.com, archive.org)
that currently land on a 404. Redirect them to /docs/introduction.

/howto/developerapi also 404s (Ahrefs Site Audit) with a DR91 backlink
from pkg.go.dev/github.com/upstash/terraform-provider-upstash/v2;
docs.json already redirects /redis/howto/developerapi and
/redis/account/developerapi to /common/account/developerapi but was
missing this bare path.
@mintlify

mintlify Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

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

Project Status Preview Updated
upstash 🟢 Ready View Preview Sep 29, 2026, 3:20 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@context7

context7 Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Docs7 for upstash.com

Result Status Action
Deployment ✅ Ready Open preview
Content review ⏳ In progress —

Commit 11b871f · Updated 2026-09-29 15:23 UTC · View build details

Copy link
Copy Markdown
Contributor Author

The Mintlify Validation (upstash) - link-rot check is failing, but it's not this PR's failure: all 52 broken links it reports are pre-existing, in qstash/* and workflow/* API reference pages (e.g. qstash/features/callbacks.mdx → qstash/api-reference/messages/publish-a-message, workflow/howto/cancel.mdx → workflow/api-reference/runs/cancel-workflow-run, etc.) — content this PR never touches. This PR only adds entries to docs.json's redirects array (23 new /kafka/* and /howto/developerapi redirects); none of the reported broken links reference any path this diff adds or changes.

This looks like leftover link rot from an earlier API-reference restructuring (the referenced qstash/api-reference/... and workflow/api-reference/... slugs don't currently resolve), unrelated to the SEO redirect work here. I don't have a fix for it — restructuring/regenerating those API reference pages is out of scope for this PR — and this check is posted by the Mintlify GitHub App rather than a repo Actions workflow, so I don't have a way to re-run it from here. Flagging for whoever owns the QStash/Workflow API reference docs; happy to rebase once it's fixed on main.


Generated by Claude Code

@context7
context7 Bot temporarily deployed to Docs7 Preview: seo/weekly-2026-09-28 September 28, 2026 06:22 Destroyed
@CahidArda
CahidArda marked this pull request as ready for review September 28, 2026 12:46
@CahidArda
CahidArda requested a balanced review from Copilot September 29, 2026 15:12

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

Generic Kafka redirects undermine the stated SEO goal, and the pricing redirect conflicts with the documented repository ownership.

Review effort: Balanced
Findings: 2 Medium severity

Open (2)
What changed in this PR

Adds redirects for discontinued Kafka documentation and a missing Developer API route.

Changes:

  • Adds 22 Kafka redirects to /introduction.
  • Redirects /howto/developerapi to the current Developer API page.
File Description
docs.json Adds 23 documentation redirects.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread docs.json Outdated
Comment thread docs.json Outdated
Copilot correctly flagged that mass-redirecting 22 discontinued
/kafka/* paths to one unrelated page (/introduction) risks being
treated as soft 404s by search engines, and drops the Kafka context
those backlinks/visitors were expecting. Google's own guidance prefers
a genuine 404 over a soft-404-style mass redirect when no relevant
replacement exists.

Kafka has no successor product in the current lineup, so there's no
single correct redirect target per page. Reverting these 22 entries
back to 404 (their current, unchanged behavior) until there's a real
destination - e.g. a Kafka retirement/migration page - to point them
to instead. Tracked as a content opportunity in DX-3085.

Keeps the /howto/developerapi -> /common/account/developerapi fix,
which is an exact 1:1 mapping to the current page and unaffected by
this concern.
@CahidArda CahidArda changed the title SEO weekly: redirect discontinued Kafka docs + fix developerapi 404 SEO weekly: fix developerapi 404 redirect Sep 29, 2026
@context7
context7 Bot temporarily deployed to Docs7 Preview: seo/weekly-2026-09-28 September 29, 2026 15:23 Destroyed
@CahidArda CahidArda closed this Sep 29, 2026

This branch was successfully deployed

1 active deployment
Docs7 Preview: seo/weekly-2026-09-28 — 11b871fe Deployed Sep 29, 2026 by context7[bot]
staging — 11b871fe Deployed Sep 29, 2026 by mintlify[bot]
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.

3 participants