/press/release/ redirect chains
Goal
We would like to prevent /press/release/
URLs from causing unnecessary redirect chains which will improve SEO.
Jobs To Be Done
- Situation: When ...
- Motivation: We want to ...
- Outcome: So we can ...
Please provide more information related to this request
Since the migration the previous /press/release/
URLs have redirect chains.
For example /press/releases/2023-07-26-gitlab-releases-inaugural-esg-and-dib-reports.html
redirect twice before resolving to /press/releases/2023-07-26-gitlab-releases-inaugural-esg-and-dib-reports.html/
as seen in the table below
This will impact our crawl budget, page performance and cause errors in our sitemap.
If this is urgent, what is the business need for the urgency?
-
Yes: what is the business need for the urgency
-
No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
Does anyone in leadership have eyes on this project?
-
Yes @personshandle
-
No
Compliance / legal / accessibility regulations to be aware of?
-
Yes: Please describe why
-
No: Please describe why
What is the ultimate end goal vision vs the MVC1 iteration?
End goal for this MVC iteration is XYZ
How do we measure success?
Please describe how success will be measured
What analytics / data will we need to set-up?
-
Yes: Please describe what analytics will need to be set up
-
No
Page(s)
Which page(s) are involved in this request?
[Page Title](URL)
DCI
-
DRI: GitLab Handle
-
Consulted: GitLab Handle
-
Informed: Everyone
In scope
What is within scope of this request?
-
Deliverable 1 -
Deliverable 2
Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
-
Copy writing -
Illustration -
Custom Graphics -
Research -
Data / Analytics -
UX Design -
Engineering