Ghost Website Migration Checklist

A Ghost migration usually goes wrong in quiet ways. Not with a dramatic outage, but with missing authors, broken internal links, duplicate tags, malformed images, or a homepage that suddenly feels off-brand. That is why a solid ghost website migration checklist matters. It helps you protect not just content, but structure, presentation, search visibility, and the reader experience that makes a publication feel credible.

For independent publishers and editorial teams, migration is not just a technical task. It is a publishing decision. You are moving archives, taxonomies, visual systems, and subscription paths - all the pieces that shape how readers discover and trust your work. The checklist below is designed for that reality.

What a ghost website migration checklist should cover

A useful migration plan goes beyond exporting posts and importing them into a new install. It should account for content integrity, URL continuity, design consistency, member flows, and post-launch quality control.

That matters because Ghost is opinionated in the right ways. Its publishing model is clean, but migrations into Ghost often come from less structured platforms. If your old site has inconsistent categories, overloaded page builders, or years of ad hoc formatting, the migration process is where those issues surface.

The goal is not to carry every legacy decision forward. The goal is to move what deserves to stay, clean up what no longer serves the publication, and launch with a setup that is easier to manage.

Before you migrate, decide what is actually moving

Start by defining the scope. Are you moving only posts and pages, or also authors, tags, members, custom landing pages, newsletter signup paths, and archived assets? If the answer is “everything,” pause there. Most sites benefit from a selective migration rather than a literal copy.

Old content often includes formatting inconsistencies, unused taxonomies, thin landing pages, and media files that add weight without adding value. A migration is one of the few moments when cleanup is efficient. If a category has three posts and no editorial purpose, fold it into something stronger. If ten tags mean the same thing, consolidate them.

You should also define what success looks like. For one publication, success means preserving organic rankings. For another, it means replacing a cluttered site with a cleaner editorial design. For a membership publication, the highest priority may be subscriber continuity. The checklist changes slightly depending on that priority.

Pre-migration content and SEO audit

Before any export starts, create a full inventory of the current site. That includes posts, pages, authors, categories, tags, image assets, downloadable files, forms, and key templates such as the homepage, archive pages, and article layouts.

Document your top-performing URLs. Pull your highest-traffic articles, pages with backlinks, ranking category archives, and newsletter signup pages. These are the pages you cannot afford to mishandle. If your current platform uses a different permalink structure, map old URLs to new ones before launch, not after traffic drops.

This is also the right time to note title tags, meta descriptions, canonical behavior, structured content blocks, and image alt text patterns. Ghost handles a lot cleanly, but imported content can still arrive with gaps. If your site relies heavily on search traffic, do not treat SEO review as a final polish step. It belongs at the beginning.

Prepare your Ghost setup before import

A migration works better when the destination is ready. Set up your Ghost instance, define publication settings, add your branding, configure navigation, and choose the theme framework you want to build on.

This is where design decisions matter more than many teams expect. If your old site was assembled with one-off templates and visual exceptions, a thoughtfully structured Ghost theme gives you a chance to standardize the publication. Typography, post cards, featured images, author pages, and membership prompts should all feel intentional.

It helps to decide early which page types you need: a clean homepage, a strong post template, tag archives, author archives, and any custom pages for newsletters, about content, or resources. If you are moving to a premium Ghost theme, test those templates with real migrated content, not placeholder text. Real content exposes spacing problems and structural gaps quickly.

Export and transform content carefully

Not every platform exports content in a Ghost-friendly format. In some cases, you can use a migration tool or structured import path. In others, content needs cleanup before it is ready for Ghost.

This is where formatting issues tend to appear. Shortcodes, unsupported embeds, custom HTML blocks, callout modules, and page-builder leftovers may not translate cleanly. The safest approach is to identify repeat patterns and fix them systematically rather than editing every article by hand.

Pay special attention to images. Confirm whether media files are being imported into Ghost, referenced remotely, or left behind entirely. Broken featured images damage trust fast, especially on editorial sites where visual rhythm matters. Check captions, inline image alignment, and image dimensions across several article types.

Author attribution also deserves a deliberate review. If the old site used inconsistent author records, fix them before or immediately after import. Clean bylines and archive pages are part of the publication’s credibility.

The practical ghost website migration checklist

At this stage, the process becomes operational. A strong ghost website migration checklist includes these core checks before launch:

• Back up the full old site, including database and media files.
• Export all content and validate what the export actually contains.
• Create a URL map for all important posts, pages, and archives.
• Set up Ghost publication details, navigation, and core settings.
• Install and configure the chosen theme.
• Import content into a staging environment first.
• Review posts for formatting issues, embeds, galleries, and callouts.
• Confirm featured images, inline media, author profiles, and tags.
• Rebuild key pages such as home, about, newsletter, and landing pages.
• Add redirects for changed URLs.
• Test membership flows, newsletter signup forms, and email capture points.
• Review SEO fields, social sharing previews, and canonical behavior.
• Check mobile layouts, page speed, and template consistency.
• QA internal links, navigation, search, and related content blocks.
• Launch during a low-risk window and monitor errors immediately after.

That list is the baseline. Larger publications may add custom integrations, sponsorship modules, ad placements, analytics events, or multilingual concerns.

Design QA is not cosmetic

A migration can preserve every post and still make the site feel worse. That usually happens when content structure and design framework are out of sync. The homepage may become too dense, article pages may lose hierarchy, or archive pages may flatten everything into one repetitive grid.

Treat design QA as part of functional QA. Check whether featured stories read as featured. Check whether longform articles still feel comfortable on desktop and mobile. Check whether your signup prompts appear at the right moments instead of interrupting the reading flow.

This is one reason many Ghost publishers prefer a theme built specifically for editorial clarity rather than a generic multipurpose layout. A clean visual system reduces migration friction because you are fitting content into a structure designed for publishing. That is often more durable than recreating every legacy pattern.

Redirects, search visibility, and launch timing

If URLs are changing, redirects are mandatory. Not just for obvious high-traffic posts, but for category or tag pages, author archives, and evergreen resources that may have backlinks from years ago. Missing redirects rarely announce themselves right away. They show up later as traffic decay, indexing noise, or confused readers.

After launch, submit your sitemap, monitor crawl behavior, and watch the pages that matter most. Small fluctuations are normal. Sharp drops often point to redirect gaps, blocked assets, missing metadata, or template-level indexation issues.

Launch timing matters too. Avoid launching right before a major campaign, newsletter push, or product announcement unless the migration itself supports that moment. Even well-managed moves create a short monitoring period, and you want room to catch issues without pressure.

What to check after the site is live

The first 48 hours are for verification, not celebration. Open your most important pages on desktop and mobile. Test menus, article cards, internal links, forms, search, membership access, and social preview behavior. If your publication sends newsletters through Ghost, send test emails and confirm branding, formatting, and post links.

Then check analytics and search performance with restraint. Do not overreact to every early fluctuation. Instead, look for patterns. Are some page types underperforming? Are redirects resolving correctly? Are archived posts missing images or excerpts?

It also helps to gather editorial feedback quickly. Writers and editors often spot structural issues that a technical checklist misses, especially around reading flow, content hierarchy, and archive usability.

A better migration is usually a more selective one

The strongest migrations are rarely the ones that move every legacy decision intact. They are the ones that protect what readers value and remove what made the old site harder to run. That may mean trimming taxonomies, simplifying page templates, refining navigation, or moving into a more focused Ghost setup with a thoughtfully crafted theme.

If you approach migration as a publishing reset rather than a file transfer, the result is usually cleaner, faster, and easier to maintain. And that pays off long after launch, when the real work returns to writing, editing, publishing, and growing an audience with less friction.