# HTTP 301 redirect rules for deleted help articles

> Use server-side 301 redirect rules for deleted public help articles instead of relying on JavaScript error-page redirects when search traffic matters.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/http-301-redirect-rules-for-deleted-help-articles/
- Source: [support.zendesk.com](https://support.zendesk.com/hc/en-us/articles/4408886627866-Can-I-redirect-traffic-from-deleted-help-center-articles)
- GrowthDex source hub: [Zendesk Help](/sources/zendesk-help-support-zendesk-com/)
- Last checked: 2026-05-28
- Rarity: uncommon
- Budget: medium
- Channels: SEO, Support, Website
- Stages: redirects, migration, technical seo, brand trust
- Key metric: Zendesk explicitly recommends HTTP 301 redirects for permanent URL changes and high-traffic public articles

## Why this can grow

Docs migrations and article cleanups quietly leak authority when deleted URLs just flash a not-found page and then jump with client-side JavaScript. Zendesk warns that JavaScript redirects can hurt Google rankings and recommends HTTP 301 redirects through the redirect rules API for permanent, high-traffic public pages. That keeps existing search value attached to a useful destination and makes the archive feel maintained instead of abandoned.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where http 301 redirect rules for deleted help articles can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the SEO and Support channel.
3. Use the evidence from support.zendesk.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Zendesk warns that JavaScript redirects are not suitable for long-term or large-scale deployment and recommends the redirect rules API to create HTTP 301 redirects when SEO matters.

## Adjacent tactics in the same lane

- [Source-filtered multi-brand help-center search](/growth-ideas/source-filtered-multi-brand-help-center-search/) - same source, 2 shared channels, 1 shared stage
- [Frontload the answer inside the first 10,000 characters](/growth-ideas/frontload-answer-inside-first-10000-characters/) - same source, 2 shared channels, 1 shared stage
- [Same-workspace 301 map after help-center migration](/growth-ideas/same-workspace-301-map-after-help-center-migration/) - 3 shared channels, 3 shared stages
- [Search dashboard segmented by brand, locale, and role](/growth-ideas/search-dashboard-segmented-by-brand-locale-and-role/) - same source, 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The help center search page is a product surface](/blog/the-help-center-search-page-is-a-product-surface/) - support-led growth, technical SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.