[I/O] Meta refresh redirect for https://developer.newrelic.com/instant-observability/ changed to a 301

[jpvajda]

Issue

There is a meta redirect that redirects to a 301 (which is basically a stacked redirect). Ideally https://developer.newrelic.com/instant-observability/ would be a 301 redirect to https://newrelic.com/instant-observability

Status Code	URL	IP	Page Type	Redirect Type	Redirect URL	
200	https://developer.newrelic.com/instant-observability/	151.101.22.22	client_redirect	meta	https://developer.newrelic.com/instant-observability/'https://www.newrelic.com/instant-observability'
301	https://www.newrelic.com/instant-observability	151.101.22.217	server_redirect	permanent	https://newrelic.com/instant-observability
200	https://newrelic.com/instant-observability	151.101.66.217	normal	none	none (edited) 

Impacts

• This approach adds to the engines' crawl budget.
• it looks basically like a stacked redirect to crawlers.

Expected

Instead of using a meta redirect that eventually goes to a 301, we ideally should be doing a direct 301 redirect.

[jpvajda]

For some context, in our epic plan to migrate the I/O site we said it was possible to set the redirect to a 301, but perhaps we need to double check our implementation

Domain & Redirects

• Redirect all requests to https://developer.newrelic.com/instant-observability > the new destination at https://newrelic.com/instant-observability
• All old URLS for the previous site need to be 301 redirected to their respective locations at the new domain.
• Gatsby has built in functionality for routing on a non-apex domain https://www.gatsbyjs.com/docs/how-to/previews-deploys-hosting/path-prefix/

[jpvajda]

Also after some googl'ing I found

From an SEO point of view it's not recommended to use HTML redirects because:

• Search engines are slow to pick up on them than they would on 301 redirects, because they need to parse the HTML to find the HTML redirect.
• There's no guarantee the redirect is picked up correctly, therefore it's unsure if you'll see the same amount of authority being passed on as you'd see with a 301 redirect.
• HTML redirects make for a slower user experience than for instance a 301 redirect.