Skip to content

Conversation

@Fbenitez97
Copy link
Owner

What problem is this solving?

A Temporary Redirect is very essential part of the SEO actions a Merchant can take to address different kinds of scenarios, such as:

  • To accommodate for an outage or while the site is undergoing maintenance
  • Implementing A/B testing
  • Updating a site without disruption
  • Creating a page without impacting SEO

At the current state, VTEX lets the users manage Temporary Redirects and set up an expiration date to this regard.
Unfortunately, this demand is partially addressed by the Rewriter App. Whenever a temporary redirect is configured, the app will delete the internal route, generating a 404 page, and then create the redirect. This will make the previous page not available anymore generating UX inconsistency and negatively impacting SEO performance.

With these changes, the APP will be able to create redirects without needing to delete the internal routes.

How to test it?

You can test the APP by simply creating new redirects, through the import feature or manually in the admin. You can also delete them, access the redirects to see if they are working, checking if they are expiring or not in the due date.

Workspace

Related to / Depends on

Related to this KI: (https://vtexhelp.zendesk.com/agent/tickets/898062)

How does this PR make you feel? 🔗

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants