Closed Bug 784923 Opened 12 years ago Closed 12 years ago

In-article redirects should be 301 redirects, not 302 redirects

Categories

(developer.mozilla.org Graveyard :: Editing, defect)

Product:
developer.mozilla.org Graveyard
Component:
Editing
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: teoli, Unassigned)

References

Details

We can add REDIRECT in the wiki using the Kuma REDIRECT syntax. It looks that these redirects become 302 Temporary REDIRECT instead of 301. They are semantically 301 Permanent Redirect. Also this impairs SEO as search engines consider both pages as different and don't merge links. We still have -moz-* pages in Google (at a better position) instead of the "new" unprefixed pages. And some pages were renamed last year.
Summary: REDIRECT defines inside a wiki page lead to a 302 instead of a 301 → REDIRECTs defined inside a wiki page lead to a 302 instead of a 301
Summary: REDIRECTs defined inside a wiki page lead to a 302 instead of a 301 → In-article redirects should be 301 redirects, not 302 redirects
I'm not sure, but it may be that we only need to change: https://github.com/mozilla/kuma/blob/master/apps/wiki/views.py#LC325 from return HttpResponseRedirect(url) to return HttpResponsePermanentRedirect(url)
Blocks: 783527
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/da76009c60ed67b63e493b4f0b3acdbf97a20df5 fix bug 784923 - Make redirects 301s instead of 302s https://github.com/mozilla/kuma/commit/6460241dbd4d94a62624f068c293a85cca713cd3 Merge pull request #550 from darkwing/301-redirects-784923 fix bug 784923 - Make redirects 301s instead of 302s
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
verified fixed https://developer.allizom.org/en-US
Status: RESOLVED → VERIFIED
Blocks: 788451
Version: Kuma → unspecified
Component: Docs Platform → Editing
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.