A shorter template can make the most useful line in an old travel guide disappear. The title and photos survive, but the note that a boat trip depends on sea conditions is gone. Before changing the design, record what each page contains, where it lives, and what a traveler needs from it.
Set the boundaries before anyone rebuilds a page
Write down what the redesign is meant to improve, such as mobile navigation, readability, image handling, or the way destination guides are grouped. In a separate list, name what must remain available. For a Thailand travel blog, that may include route descriptions, practical caveats, firsthand observations, photo credits, and reader comments that add useful context.
Put someone in charge of approving content changes and someone in charge of checking the technical move, even if a small team handles both. Agree that a page will not be deleted or merged just because it fits poorly in the new design. That calls for a content review, not a template decision.
Make an inventory you can actually use
Export the current URLs, then check the list against the live site. Include posts, pages, category archives, downloadable files, and older pages missing from the main menu. A sitemap or CMS export is a starting point; a manual check can catch what it leaves out. Before work begins, save a complete backup of the database and uploaded files, and confirm that you can restore it.
A spreadsheet is enough. Give it columns for the current URL, title, page type, main destination or subject, owner, last review date, image and file dependencies, proposed new URL, planned action, and review status. Add a note about anything that cannot be lost. For a beach guide, write down the difference between arriving by road and arriving by boat; a label like “transport” is too vague to help during review.

Give every existing page a destination
Mark each URL as keep, revise, merge, redirect, or retire. “Keep” means the substance moves intact, though the wording can still be edited. “Revise” flags accuracy or formatting work. For a merge, name the receiving page. For a redirect, record where the old address should lead. If you retire a page, record why and decide what should happen to its URL.
Two island guides should not be merged simply because they use the same layout. One might help readers choose a quiet overnight stay; the other might explain a day trip. Keep both if they answer different questions. If a paragraph seems unreliable, flag it for verification rather than carrying it over without checking.
Map old content to the new page structure
Shorter cards, reusable information boxes, and new heading levels may look fine in a mock-up. Try them with real posts before approving the templates: a long destination guide, a short café note, a photo-heavy story, and a page with tables or downloads. Move copies to the staging site and see what fits.
Look beyond the main article body. Captions, map notes, accordions, custom fields, author updates, and embedded media may still be in the database but fail to appear in the new template. Map each field to a place in the new version. If it has no home, either make one or work the information into the article text.
Check the page on a narrow phone screen, too. A tide or weather warning beside the trip description on desktop should not end up several screens below the route or booking details on mobile. For entry-related information, retain a clearly dated note reminding travelers to check the destination country’s current official requirements before departure. A callout in the new design cannot replace that check.
Protect URLs, relationships, and media
Keeping an existing URL is simpler than changing it. When a change is necessary, map each old address to the most relevant new one and use a permanent redirect. Do not send every removed post to the homepage. Someone following an old link to a waterfall guide should reach that guide or a genuinely equivalent resource, not a general destinations page.
Record internal links to moved pages. Once redirects work, update links on the site to point straight to the final addresses rather than relying on redirects indefinitely. Check navigation, related-post modules, image links, and downloads as well as links in the text. A packing note, for instance, may still point to an old island address after the menu has been fixed.
Give media a separate check. Count the images and files on a test group of pages before and after the move. Confirm that full-size images, thumbnails, captions, alt text, credits, and usage restrictions have transferred correctly. A post can look complete until someone opens a broken route map or spots a caption attached to the wrong photo.

Review content in two separate passes
First, check that the move was faithful
Compare each staging page with its original, section by section. Check headings, paragraphs, lists, tables, captions, links, and media. Log omissions with the page URL, missing element, person responsible, and fix status. This pass is about the move, not rewriting every sentence.
Then, check whether the advice still holds
Once everything is in place, review details that can change: opening arrangements, ferry routes, access rules, and prices. Record what you checked and when. If you cannot verify a claim, remove the unsupported certainty or flag the page for a later update. Keep useful firsthand details where they still apply. A note about shade along a walking path may help a visitor more than a polished but generic introduction.
Keeping the passes separate helps you trace mistakes. If a transport warning is missing, you can tell whether it failed to move or was deliberately edited. When you revise a page during the redesign, keep a copy of the original until the new version passes review.
Test the launch as a traveler would
Before launch, crawl the staging site or sample it manually for broken links, missing images, duplicate pages, and pages that cannot be reached through navigation. Test search, menus, headings, and filters on desktop and mobile. Then open the site without an editor login: a page may look fine to the team while remaining unpublished or inaccessible to visitors.
Use a few realistic tasks instead of checking only the homepage:
- Find a specific island guide through the main navigation and site search.
- Open an older saved URL and check that it reaches the intended page.
- Follow a link from a destination guide to its transport information.
- Read a long post on a phone and find its practical access warning.
- Open a map or download and check that it is the right file.
Keep the old site backup, URL inventory, redirect map, and review log close at hand during launch. After publishing, check high-use pages and a sample of changed URLs on the live site. Redirects, caching, and media paths may behave differently than they did on staging. Watch error reports and reader messages for the first few weeks, and record fixes in the inventory.
For one final check, choose an older guide with several photos and a practical warning. Open its old URL in a private browser window, follow the redirect, find the warning, and open each referenced file. You will see whether the guide still works for a traveler, not just whether the new design loads.
