<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Migration on vanityURLs</title><link>https://vanityurls.link/en/tags/migration/</link><description>Recent content in Migration on vanityURLs</description><generator>Hugo</generator><language>en-CA</language><lastBuildDate>Sun, 07 Jun 2026 18:08:29 -0400</lastBuildDate><atom:link href="https://vanityurls.link/en/tags/migration/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating from Cloudflare Pages redirects to vanityURLs Workers</title><link>https://vanityurls.link/en/blog/migrating-from-cloudflare-pages-redirects/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://vanityurls.link/en/blog/migrating-from-cloudflare-pages-redirects/</guid><description>&lt;p&gt;The first vanityURLs instances were intentionally simple: a domain, a &lt;code&gt;_redirects&lt;/code&gt; file, and Cloudflare Pages. That was a good starting point. It made short links easy to keep in Git, easy to review, and easy to deploy.&lt;/p&gt;
&lt;p&gt;The current runtime keeps the same spirit, but moves the redirect decision into a Cloudflare Worker. That change gives the instance a stronger runtime: protected operational pages, generated policy, localized public pages, server-side analytics, scanner protection, and a clearer split between product defaults and instance-owned files.&lt;/p&gt;</description></item></channel></rss>