@ChrisMarsh82 Would like to discuss this in the afternoon call

We identified that this is almost certainly due to browser caching 301 permanent redirects.

The general consensus online seems to be that for most of our common purposes 302 redirects are actually better. Our most common use cases involve promotions, testing, shortening for QR codes, etc, rather than permanently relocating a resource on the website. We do sometimes permanently relocate resources on the website, ie moving Pages, but the right way to handle that would be to offer the user an option to create a 301 redirect when the move the Pages.

Maybe the biggest issue is that Admins are shown that they have the ability to change or delete a permanent redirect, but this won't work for users that already accessed the link.

Let's change the settings so that by default redirects are NOT permanent.

Can we please change the text below permanent check box:

Recommendation: Do not use permanent redirects if you are setting up a promotion, QR code, or similar. Use permanent redirects if you are permanently moving the location of content on your site.
Cons: If you change or even delete a permanent redirect after you create it, the users who already accessed it will still continue to behave as if the original redirect is in place. This is because permanent redirects are normally stored by the user's browser until they delete their browser cache. Your browser may also store the permanent redirect until you clear its cache.
Pros: Permanent redirects ensure search engines forget the old page (the 'Redirect from') and index the new page instead.