There really is not an easy technical solution that we can apply for everyone on this. Mostly I wrote this task so we could point people at it if they are experiencing this problem. The steps they could take are:

1. Clear local browser cache entirely or at least for the techblog.wikimedia.org host
2. Add something to the URL that will make it unique (and thus avoiding local cache matching) which the new WordPress site will ignore. A common technique for this is appending a query string as a "cache busting" token. For example: https://techblog.wikimedia.org/?T248598 should not match local cache for anyone anywhere.

• Chrome: https://www.ryadel.com/en/clear-google-chrome-redirect-cache-for-single-url-page-howto/
• Firefox: https://superuser.com/questions/467999/clear-301-redirect-cache-in-firefox/661767#661767

This cached 301 behavior may also extend to web crawlers. We should try to keep an eye on google and other search engine activity related to new blog posts to see if that is true. There maybe interventions that can be done through proprietary tools for particular crawlers to act as the equivalent of cache clearing.

In T248598#6005986, @bd808 wrote:

This cached 301 behavior may also extend to web crawlers. We should try to keep an eye on google and other search engine activity related to new blog posts to see if that is true. There maybe interventions that can be done through proprietary tools for particular crawlers to act as the equivalent of cache clearing.

GoogleBot at least seems to be doing ok with this. I searched for "Saying no to proprietary code in production is hard work: the GPU chapter" and as hoped the top hit is https://techblog.wikimedia.org/2020/04/06/saying-no-to-proprietary-code-in-production-is-hard-work-the-gpu-chapter/

GoogleBot at least seems to be doing ok with this. I searched for "Saying no to proprietary code in production is hard work: the GPU chapter" and as hoped the top hit is https://techblog.wikimedia.org/2020/04/06/saying-no-to-proprietary-code-in-production-is-hard-work-the-gpu-chapter/

I tried this with Bing, DuckDuckGo, Yahoo, AOL search, Ask.com, Baidu and Yandex.

It seems they all have the post as the top result apart from Baidu and Yandex which both haven't indexed that post but have index others (you can see them if you search for 'site:techblog.wikimedia.org')