Start with access and responses

Important pages should return HTTP 200, missing pages should return 404, and permanently moved pages should use 301 redirects to a relevant replacement. Check robots.txt and page-level robots directives. A sitemap does not override a noindex instruction or make a weak page rank.

Illustrative team collaborating on a digital project
Creative thinking. Practical execution.

Check the preferred URLs

Use consistent HTTPS URLs and internal links. Each indexable page should identify the intended canonical URL. When changing slugs, build a map from old pages to useful equivalents and test for loops or chains. Do not send every retired article to the homepage.

Inspect the actual page output

Read the rendered HTML: title, description, one main heading, useful content, image alternatives and internal links. Make sure navigation is usable without relying entirely on client-side scripts. Structured data should describe content visitors can actually see.

Verify after the switch

Submit the sitemap in Search Console, inspect a sample of important URLs and monitor unexpected errors. Keep the old backup and migration map. A deployment can be technically correct while rankings still need time and competitive content to develop.

Your practical checklist

  • Test representative 200, 301 and 404 responses
  • Check robots and canonical consistency
  • Verify every sitemap URL
  • Test forms and mobile navigation
  • Review Search Console after launch
Bluemoon Creative Agency

Practical guidance from our marketing, creative and technology service areas. About the publisher.