Create README.md #1
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
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? 🔗