A new theme can change more than the appearance of a page. It can also change titles, headings, navigation and the links that help people find important content.
Before approving an upgrade, ask for evidence that these parts have been checked. A promise that everything will be fine is not a migration plan.
1. How is the preview protected?
Agree how access and indexing are controlled. Use authentication where the preview must be private. Noindex is not access control, and a robots.txt block can prevent a crawler from seeing a noindex directive. Verify that preview restrictions will not accidentally carry into production.
2. Which existing URLs are being kept?
Reconcile crawls, sitemaps and historical search evidence. Include subdomains and old published areas where relevant. Don’t retire content or change addresses solely to make the directory structure shallower.
3. What is the baseline?
Record important pages, queries, traffic and commercial outcomes. For seasonal businesses, include appropriate year-on-year context alongside recent evidence. Keep the reporting period and definitions visible.
4. What changes to content and navigation?
Compare titles, headings, useful content and internal links. URL depth is not the same as the number of clicks needed to reach a page. Preserve useful routes through the site and test proposed changes rather than assuming they cannot hurt.
Before sign-off, check that important words remain readable page text rather than existing only inside graphics. Headings should describe the content that follows, and page titles should distinguish the pages accurately. A visually polished design is not evidence that these checks were done.
5. Have redirects been tested?
Prepare relevant permanent redirects for moved pages before cutover and activate them with the move. Keep unchanged URLs intact. Test final destinations and avoid redirecting everything to the homepage.
6. Does the sitemap reflect the intended site?
Generate it from indexable canonical pages and verify it in the new environment. Agree the Search Console submission and monitoring plan. Don’t assume a sitemap must be deleted simply because it contains old addresses during a transition.
7. Who monitors and decides on rollback?
Name the person responsible for checking responses, indexing, forms and commercial outcomes after launch. Define the escalation and rollback process before an incident. A few sample rankings are useful warning signals, but they do not prove what happened across every query.
Use the seven-step migration checklist for the implementation sequence, or discuss the review through our SEO service.