The download icon is not the finish line.
A website export can exist on your computer while important media, settings, forms, redirects, or affiliate links still depend on the old host. Before canceling anything, prove that the website—not merely the file—survived.
Quick Answer: How Do You Check a Website Export Before Canceling Hosting?
Restore or import the export somewhere you control, then test a representative set of pages, posts, images, downloads, forms, affiliate links, redirects, and administrative functions. Confirm that the database, site files, domain, DNS, email, analytics, and Search Console verification are accounted for. Point traffic to the new host, monitor both environments, and cancel the old hosting only after the new site is serving visitors correctly and no required asset or service still depends on the old account.
Do not treat a WordPress XML file as proof of a complete site backup. WordPress documents its standard export as a WXR file containing content data. Its backup guidance says a typical full restore requires both the database and the site files.
This Is the Question the Reader Journey Left Open
OnlineAffiliate.net’s recent guides follow the real life of a recommendation: setup, first use, troubleshooting, optimization, reassessment, migration, and offboarding. The latest guide on turning reader questions into useful content uses one especially practical example: “I downloaded the export. Am I finished?”
This article answers that question directly. The affiliate migration guide helps work survive a move, while the offboarding guide helps close the old relationship. Export verification is the bridge between them: evidence that the destination works before the old access disappears.
Website Export, Backup, Migration Package, or Working Copy?
The word “export” can describe very different things. Name what you downloaded before deciding what it proves.
| Item | What it may contain | What it does not prove | Best next check |
|---|---|---|---|
| WordPress WXR export | Posts, pages, comments, custom fields, terms, menus, users, and supported custom content in an XML file. | That themes, plugins, uploaded files, configuration, or host-level settings are independently restorable. | Import into a test WordPress site and verify every required content type and attachment. |
| Database export | Posts and many settings, relationships, plugin records, users, and other data stored in database tables. | That themes, plugins, images, downloads, configuration files, or custom code came with it. | Pair it with a matching file backup and perform a controlled restore. |
| Site-files archive | WordPress core, themes, plugins, uploads, configuration, redirects, and other server files—depending on the archive scope. | That the database is included or synchronized to the same point in time. | Check the archive contents and match it to the correct database copy. |
| Host or plugin migration package | A database-and-files bundle, installer, or provider-managed transfer. The exact contents vary. | That every excluded file, integration, license, scheduled task, mailbox, DNS record, or external service moved. | Read the current package documentation, inspect exclusions, and test the restored result. |
| Working destination | A restored site that can be opened, administered, crawled, and used. | That all visitors reach it yet, or that email, forms, tracking, and old-server traffic are settled. | Run functional checks, move traffic carefully, and monitor before shutdown. |
For WordPress, the official Tools → Export documentation lists the content stored in a WXR file. WordPress’s backup guidance separately explains that a typical complete restore needs both the database and files. That is why file size, a “success” message, or an XML download alone cannot establish migration readiness.
Use the Five-Part CLEAR Website Export Check
CLEAR puts the irreversible step last. The old hosting stays available while you define the scope, inspect the export, exercise the restored site, and audit the jobs readers depend on.
Prove the destination before releasing the source
1. Catalog What Must Still Work
Start with the website’s job, not the archive’s filename. A small affiliate site can depend on more than its published posts.
Content and media
Posts, pages, drafts, categories, tags, comments, images, featured images, PDFs, downloadable worksheets, author details, and reusable blocks.
Presentation and functions
Theme settings, menus, widgets, templates, plugins, forms, search, redirects, scheduled actions, and custom code.
Trust and monetization
Affiliate disclosures, tracked destinations, comparison tables, buttons, link attributes, policy pages, contact routes, and consent controls.
Discovery and ownership
Permalinks, canonicals, sitemaps, robots rules, analytics tags, Search Console verification, HTTPS, DNS, domain control, and email routing.
Create a sample set before the move: the homepage, one high-traffic guide, one old post, one recent post, one category archive, one author archive if used, one image attachment, one PDF, one form, one redirected URL, and one affiliate recommendation. Add any unusual content type your site relies on.
2. Locate Every Part of the Transfer
Inventory the pieces without copying secrets into a shared checklist. For a typical WordPress move, ask whether you have a database export, site files, uploaded media, theme and plugin files, configuration, redirect rules, and any provider-specific package or installer. Record where each item is stored, when it was created, and which official instructions explain how it is restored.
Also separate services that may only look like part of the host. The domain registration, authoritative DNS, mailbox service, analytics account, affiliate dashboards, and form-delivery service may have different owners or billing dates. Do not cancel or transfer one merely because another is moving.
If WordPress’s standard importer is part of the plan, its official importing instructions explain how a WXR file is uploaded and how attachments may be imported. Test the actual result while the source files are still available; do not infer that every attachment arrived because the post text did.
3. Exercise the Restored Website
A backup becomes evidence only after a restore or import succeeds. Use a staging environment, temporary hostname, hosts-file method, or provider-approved preview that lets you inspect the destination before sending normal traffic there. If the test environment is publicly reachable, follow the platform’s instructions for preventing premature indexing, and remove those blocks before launch.
Do not stop at the homepage. Open the sample URLs from your catalog and complete normal tasks:
- Load pages on both a phone-sized screen and a desktop browser.
- Open featured images, inline images, and downloadable files.
- Use navigation, site search, category links, and a known redirect.
- Submit a clearly labeled test through each important form and confirm where it arrives.
- Open the WordPress dashboard and edit a disposable draft or test page.
- Check that the correct theme, templates, plugins, and reusable elements are active.
- Inspect error logs or provider reports for failed imports, missing files, or server incompatibilities.
Use non-sensitive test data. Do not generate a real affiliate conversion merely to test a link. Confirm that the destination and disclosure are correct, and use the program’s permitted test method if it provides one.
4. Audit the Paths Readers and Search Engines Use
The new server can display a page while still serving the wrong canonical, blocking crawlers, losing analytics, or breaking the form that turns a question into a conversation. Check the rendered result, not just the WordPress editor.
- URLs: Confirm the intended domain, HTTPS version, permalink paths, canonicals, redirects, and sitemap entries.
- Crawl controls: Remove temporary
noindexrules or staging blocks only when the destination is ready. Check the live robots.txt rules. - Search ownership: Make sure the Search Console verification method remains present and use URL Inspection on representative pages.
- Tracking: Confirm the intended analytics code loads once, consent behavior remains appropriate, and internal tests are labeled or filtered according to your setup.
- Affiliate trust: Open a sample of buttons and text links, verify the landing page matches the promise, and confirm disclosure remains clear near the recommendation.
- Communication: Test contact forms and any address attached to the domain. A website move and an email move are not automatically the same task.
When the visible URLs stay the same and only the hosting changes, Google’s hosting-change guidance says to prepare and test the new infrastructure, update DNS, monitor traffic on the new and old servers, and shut down the old host only when the new infrastructure is serving users correctly. If the domain or URL paths change, use Google’s separate site-move guidance for URL changes.
5. Release the Old Host Only After Monitoring
Point the domain to the new infrastructure using the provider’s supported process. Then monitor. If both hosts expose traffic or server logs, watch the old environment decline and the new one take over. Check uptime, crawl behavior, important URLs, forms, downloads, and unexpected errors over a period appropriate to the site and the provider’s cancellation deadline.
The right shutdown date is evidence-based, not universal. A quiet brochure site and a busy site with sales, memberships, mailboxes, or scheduled jobs do not carry the same risk. Keep an independent verified backup after the move, record the official cancellation confirmation privately, and note any domain, email, or account access that remains active.
If billing, renewal, identity, refund status, account deletion, or access depends on private records, use the host’s authenticated account area or official support. An affiliate article can explain what to verify; it cannot confirm an individual account outcome.
Worked Example: The XML File Looked Complete
The situation
A solo publisher has 140 WordPress posts, a few downloadable checklists, a contact form, affiliate comparison tables, and several redirects. They download “All content” through Tools → Export and see a successful XML file.
What the file proves
It proves that WordPress produced a content export. It does not, by itself, prove that the theme, plugins, uploaded binaries, redirect rules, configuration, or database-dependent settings can be rebuilt after old hosting access ends.
The safer verification
The publisher keeps the old site available, obtains the appropriate database-and-files backup or supported migration package, and restores the destination. They test the homepage, ten representative articles, two old images, a PDF, the contact form, an affiliate button, a redirected URL, the sitemap, and WordPress editing.
The gap discovered
Posts display, but the downloadable PDFs return errors and one comparison-table style is missing. The publisher retrieves the missing uploads and identifies the required styling before DNS changes. The export did not fail; it simply answered a narrower question than the publisher first assumed.
The responsible ending
After the corrected destination passes, traffic is moved and monitored. The old host is canceled only after no required function or file relies on it. This scenario is illustrative; it is not a claim about a specific host, plugin, or reader result.
A Fast “Ready or Not?” Comparison
| Signal | Not ready to cancel | Stronger evidence of readiness |
|---|---|---|
| Export | A file downloaded without errors. | The required files and data are identified, inspected, and restorable. |
| Content | The homepage opens. | Representative old, new, media-rich, and downloadable pages pass. |
| Functions | The site looks familiar. | Forms, search, redirects, editing, and other essential tasks work. |
| SEO | The domain resolves. | HTTPS, canonicals, crawl rules, sitemaps, and verification are correct. |
| Affiliate links | Buttons are visible. | Samples reach the intended current destination with disclosures intact. |
| Shutdown | The new host says migration finished. | Traffic has moved, old dependencies are resolved, and a verified independent backup remains. |
Move from assumption to evidence
Build Your Website Export Verification Plan
Use this planner to define the proof you need before shutdown. It makes no network requests. “Save my plan” uses this browser’s local storage when available; it does not connect to your host, calendar, analytics, or OnlineAffiliate.net. Do not enter credentials or private account data.
Define the move
Clarify whether the public URLs, platform, or hosting infrastructure will change.
Name what must survive
List the reader-facing work and the transfer pieces that should preserve it.
Build the verification test
Choose a representative sample and record what passes, fails, or remains uncertain.
Set the cancellation rule
Write the evidence that must exist before access to the old hosting can safely end.
Fallback worksheet: If the interactive controls do not work in your browser, copy the field labels into a private note and complete them manually.
Keep the Recommendation After the Reader’s Safety Checks
A hosting move is not the moment to imply that a new purchase will automatically repair an incomplete export. First help the reader define, restore, and verify the website. If they still need a platform, explain the fit, limitations, current terms, and work that remains.
Paid referral disclosure: OnlineAffiliate.net may earn a commission if you later purchase through the Wealthy Affiliate link, at no additional cost to you. The CLEAR process does not require that platform.
Four-Question Knowledge Check
Choose one answer for each question, then check your result.
Read the answer explanations
- B. A WXR file is a content export. Test the import and account for the other assets and services your site needs.
- C. A representative functional test can expose missing files, broken routes, and tasks a homepage check will miss.
- A. For a hosting-only change with stable public URLs, prepare, test, update DNS, monitor, and then shut down the old infrastructure.
- C. Billing and renewal status depend on private account records and the provider’s authority.
Frequently Asked Questions
Is the WordPress Tools → Export file a full backup?
No. WordPress describes it as a WXR content export. A typical fully restorable WordPress backup requires both the database and the relevant site files. Confirm the exact method and contents with your host or migration tool.
How can I tell whether my images moved?
Open a representative group of old and recent images on the destination, inspect their URLs, test featured and inline images, and confirm the files remain available without the old host. Also test PDFs and other uploads; a working thumbnail does not prove every original file arrived.
Should I cancel my old hosting as soon as DNS changes?
No. DNS changes start the traffic move; they do not prove that every visitor, crawler, form, file, or service is using the new environment. Monitor the new and old infrastructure and follow the providers’ current timing guidance before shutdown.
Do I use Google’s Change of Address tool when only the host changes?
No. Google says the Change of Address tool is for moves from one domain or subdomain to another, not a hosting-provider change with the same user-visible URLs. Follow the hosting-change guidance instead.
What affiliate elements should I test after a website move?
Sample text links, buttons, disclosures, comparison tables, redirect links you control, and the final merchant destination. Confirm that the recommendation still matches the landing page. Do not make a real purchase or create a prohibited self-referral just to test tracking.
Does moving hosting also move my domain and email?
Not necessarily. Hosting, domain registration, authoritative DNS, and email can be supplied or billed separately even when one dashboard displays them together. Identify the owner and migration requirement for each service before changing or canceling the hosting account.
Continue the Reader-First Journey
If the migration exposed outdated claims or broken recommendations, use the affiliate content refresh checklist before calling the project complete.
What Did Your Test Catch?
Did your website export miss an image, download, redirect, form, template, or setting? Share the type of gap and the check that revealed it in the comments. Leave out domain-control details, credentials, account numbers, private support messages, and customer information.
Your experience may help another publisher test the right thing before old hosting access disappears.
Sources and review: WordPress Tools → Export, WordPress importing and backup documentation, Google Search Central guidance for hosting changes and site moves with URL changes, OnlineAffiliate.net’s recent reader-question, migration, and offboarding guides, and the approved Wealthy Affiliate referral destination were reviewed September 4, 2026. Platform interfaces, backup contents, migration tools, and account terms can change. Check current official instructions for the source and destination involved in your move.
