Moving off Ghost usually starts with one narrow question: can I keep my domain working while I change where my blog actually lives? The short answer is yes, but the mechanics take some care. This post walks through what actually happens when you change a URL, what to check before you migrate, and how to move your posts and domain together without a blackout.
Why people search for "change Ghost URL" in the first place
Most people searching "change Ghost URL" aren't trying to rename a blog post. They're trying to move their whole site, either to a new domain, a new subdomain structure, or off Ghost entirely to another platform, and they want to know if their existing links and domain survive the move.
The underlying worry is almost always the same three things: will my search rankings survive, will my RSS subscribers still get my posts, and will my custom domain keep pointing at my content once I'm done. "Ghost custom domain" and "change Ghost URL" are both phrases people actively search for, which tells you this is a real, recurring pain point, not an edge case. Ghost ties your site URL to specific settings and, on a self-hosted install, to config files, so changing it isn't as simple as editing a text field and moving on.
What breaks when you change a URL on a hosted blog
Changing a URL breaks anything that has the old address hardcoded into it: internal links, image paths, canonical tags, your sitemap, RSS feed entries, and any external backlinks pointing at your old pages.
Search engines index a URL, not a piece of content. When the URL changes without a redirect in place, the search engine sees a missing page at the old address and a new, unranked page at the new one. It has to recrawl and re-evaluate the new URL from close to zero, which can mean a visible dip in traffic while that happens.
RSS feeds are similarly literal. Most feed readers track posts by their URL or by a GUID tied to the URL. If those change without a proper redirect or a preserved GUID, some readers will treat every post as new and either flood subscribers with reposts or silently stop pulling new content, since the feed URL itself changed.
Email subscriptions are the least forgiving part. A newsletter platform sends from your domain and often authenticates using DNS records tied to that domain (SPF, DKIM). If the domain changes hands or the DNS records aren't recreated exactly, outgoing mail can start landing in spam or fail to send altogether.
Custom domain setup: what differs from platform to platform
Every hosted blogging platform ties a custom domain to your account through the same basic DNS mechanism, but where you configure it and what record types it expects differs.
A custom domain, in practice, is just a DNS record pointing your domain at the platform's servers. Usually that's an A record (pointing at an IP address) for the root domain, or a CNAME record (pointing at another hostname) for a subdomain like www or blog. The platform then checks for that record and serves your content once it finds it.
On Ghost, custom domain setup depends heavily on whether you're on Ghost(Pro) or self-hosting. A managed, Pro-style plan typically has you add the DNS record and update your site URL through a dashboard. A self-hosted install generally means editing the site's config file directly and restarting the server process, a manual step most fully hosted platforms don't require of their users.
Floggy handles this the same basic way (you point a DNS record at Floggy and add the domain in your account settings) but there's no config file to touch and no server to restart. You add the domain, verify the DNS record, and Floggy serves your blog from it. That's the whole setup, whether you're moving one blog or provisioning domains for many collections at once.
What to check before you migrate: redirects, RSS, subscriber emails
Before you touch anything, get a full list of your current post URLs, your RSS feed URL, and your subscriber export. Migrating without this list is how people lose rankings and readers they didn't have to lose.
Redirects. For every post URL that will change, you need a 301 redirect (a permanent redirect instructing browsers and search engines that a page has permanently moved to a new address) from the old URL to the new one. A 301 passes most of the page's accumulated ranking signal to the new URL, which is why redirecting matters more than just leaving the old page to 404. If you're changing your domain, not just your URL structure, you'll want redirects at the domain level too, not just for individual posts.
RSS. Check whether your new platform lets you keep the same feed URL, or at least redirect the old feed URL to the new one. If subscribers pull from yourdomain.com/rss/, that address needs to keep working, or point somewhere that does, for their reader to keep finding your posts.
Subscriber emails. Export your subscriber list before you start. Most hosted blogging platforms offer some form of CSV export for your member or subscriber list from account settings, though the exact location varies. Confirm the export includes email addresses and subscription status, not just names, and store it somewhere safe before you begin any domain changes.
Moving your posts across while keeping your domain live
The sequencing that avoids downtime is: set up the new platform and import your content first, verify everything renders correctly, then repoint your domain last.
Most platforms, including Floggy, support importing posts from an export file, commonly Ghost's JSON export or a generic CSV. Do this on the new platform under a temporary address (a Floggy subdomain, for instance) so you can check formatting, images, and links before anything public-facing changes. Fix broken image links and formatting issues at this stage. It's much easier to fix them while the old site is still live for comparison.
Once the new site looks right, set up your 301 redirects for the URLs that are changing. Then move the DNS record for your custom domain from the old platform to the new one. This is the step that actually cuts your domain over, and it's also the point where downtime, if any, happens.
Keep the old platform account active for a short overlap period if the platform allows it. That gives you a fallback if you find an issue with the new setup after the domain has already moved.
What to expect from DNS propagation and downtime
DNS propagation is the time it takes for the internet's DNS servers, and the browsers and devices that cache their answers, to pick up your new DNS record and stop returning the old one. It's not a single event, it's a gradual replacement across many independent caches.
How long it takes depends mostly on the TTL (time to live) set on the DNS record before you changed it. TTL is the number of seconds a DNS resolver is told to cache an answer before checking again. A record with a one-hour TTL will generally propagate within a few hours; a record with a 24-hour or longer TTL can take a full day or more, because caches holding the old answer won't recheck until their TTL expires.
If you can, lower the TTL on your domain's DNS record a day or two before you plan to migrate. That shortens the caching window on the old record, so when you make the actual switch, the new record replaces it faster.
During propagation, some visitors will see your new site and some will still see the old one, depending on which DNS answer their resolver has cached. This is normal and not something you can fully control from your end. It's not downtime in the sense of your site being unreachable, it's a temporary split in who's seeing which version. Once propagation completes, everyone sees the new site consistently.
If you're moving away from Ghost, Floggy gives you a real editor, a custom domain, a newsletter, and analytics on the free tier's blog basics, with the CMS, API, and AI-assisted publishing available on Pro if you're building out more than a single blog. Import your Ghost export, point your domain at Floggy once you're happy with how it looks, and your posts, redirects, and subscribers can move over without losing the ground you've already built.