vanityURLs' secret sauce is a JSON ledger
Why vanityURLs keeps a structured Cloudflare dashboard capture beside the documentation, and where to watch for Workers, domain protection, and Zero Trust changes.
Why vanityURLs keeps a structured Cloudflare dashboard capture beside the documentation, and where to watch for Workers, domain protection, and Zero Trust changes.
The Cloudflare products vanityURLs documents as non-baseline, and why they stay outside the default setup.
Which Cloudflare dashboard features a vanityURLs instance should leave alone unless there is a specific operational reason.
Comparison of vanityURLs, hosted URL shorteners, and self-hosted alternatives for operators who want branded short links as code.
When to review Cloudflare Access settings and where to look when private vanityURLs paths are blocked
How to keep wrangler.toml boring, align Worker names with GitHub and local directories, and avoid painful Cloudflare Worker rebuilds
How to choose between One-Time PIN, GitHub, Google, and other identity providers to secure your vanityURLs operational pages
Why vanityURLs keeps the Worker small, blocks raw runtime assets, and uses Cloudflare edge controls around the redirect path.
A compact production checklist for launching or upgrading a vanityURLs instance on Cloudflare.
Move an older vanityURLs instance from Cloudflare Pages _redirects to the current Cloudflare Workers runtime without losing the link inventory.
Why a vanityURLs instance should use Cloudflare edge controls before traffic reaches the Worker.
How the current Worker, defaults, custom overrides, analytics, and Cloudflare security model fit together.
Search docs…