Automattic / Automattic/wp-calypso

Redirect Atomic wpcomstaging file paths to primary domain

Open
#95,049 4 comments 0 reactions 0 assignees View on GitHub
[Feature Group] Other Infrastructure [Feature] Other Atomic Infrastructure [Product] WordPress.com Enhancement Feature Request Quality Sprint: Week 2
Dominant language
TypeScript
Stars
12.6k
Forks
2k
Avg merge
1d 17h
Merged PRs (30d)
552

Description

### What

wpcomstaging file paths don’t redirect to the primary domain file path.

For example:
[https://awebsite.wpcomstaging.com/wp-content/uploads/2022/01/this-is-the-file.pdf]()
doesn’t redirect to
[https://awebsite.com/wp-content/uploads/2022/01/this-is-the-file.pdf]()

### Why

This significantly increase the chances of a 404's on the site, which is bad for SEO. Much like the instances found if the www. version of the domain doesn't redirect to non-www. version of the domain, or if the main wpcomstaging domain doesn't redirect to the main primary domain.

### How

Please see p1727689749025099/1727689749.025099-slack-C7YPW6K40

Contributor guide

Open the contributing guide

Research direction

Start with the linked Slack discussion p1727689749025099/1727689749.025099-slack-C7YPW6K40 and reproduce the example wpcomstaging file URL. Trace the existing staging-to-primary-domain redirect behavior; done means the file path redirects from the wpcomstaging host to the corresponding primary domain path without producing a 404.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.