August 2026 brought parallel developments, not one industry-wide CMS migration release: WordPress changed site-building tools, Contentful expanded exports, and Google revised search documentation. For teams moving content management systems—a CMS migration transfers content, URLs, templates, and settings—the key takeaways are to patch first, check dependencies, and preserve URL signals. These updates affect different parts of a project. WordPress changes how teams build sites, Contentful changes how they extract data and query usage, and Google clarifies how publishers should manage discovery and site moves.
Official resources:
- Register through WordPress’s official page — Use this page to review requirements and register directly.
- Read the official guidance from Google — Use this primary source to verify the official guidance.
Table of Contents
- What changed in WordPress?
- How does Contentful support migration work?
- What changed in Google's documentation?
- What should a site-migration plan include?
- Key takeaways for project planning
What changed in WordPress?
WordPress 7.1 arrived on August 19 with responsive block styling in the Site Editor, a redesigned media editor, richer collaborative Notes, and new Playlist and Tabs blocks. The WordPress 7.1 release announcement also says block themes can define mobile and tablet breakpoints in `theme.json`. Theme developers can register custom SVG icon collections. Expanded Abilities APIs also provide more options for automation-oriented integrations.
Before adopting these features, teams should check whether their themes, custom blocks, and editorial workflows depend on older editor behavior. Security belongs at the start of migration planning. WordPress released version 7.0.4 on August 12 and recommended that affected site owners update immediately. A team preparing a migration should not leave the source site exposed while concentrating on the replacement.
How does Contentful support migration work?
Contentful released its Content Exporter app on august 17. It can bulk-export more than the web app's 40-entry limit, with filtering, previews, and downloads in CSV, JSON, XLSX, XML, or YAML, according to the Contentful developer changelog. That makes the app useful for migration inventories, archives, and offline analysis.
For example, a team can filter a content set, preview the result, and select a format suited to either human review or machine processing. Contentful also made a public Usage API available while deprecating two legacy usage endpoints. Scripts must move to `/metric` and `/usages-detailed` before February 28, 2027. Teams should search deployment tools, reporting jobs, and internal dashboards for calls to the retired endpoints.
What changed in Google's documentation?
On August 20, Google updated its Preferred Sources documentation with a custom interactive button. Publishers can place the button on their sites so readers can mark them as preferred sources and then return to their previous reading position, as recorded in Google Search Central's documentation updates. This is a publisher-facing discovery feature, not a replacement for migration controls.
It may require front-end implementation and testing, but it does not change the need for redirects, canonical URLs, sitemaps, or Search Console monitoring. The same updates page records a June 17 clarification for domain moves. Google says teams should submit Change of Address requests for every verified subdomain and www/non-www variant involved in the migration.
What should a site-migration plan include?
Google recommends mapping every old URL to its new destination and using server-side permanent redirects where possible. Its site-move documentation also calls for updated canonical tags and robots rules, a new sitemap, and monitoring of both properties in Search Console.
A practical migration checklist should include: Temporary ranking fluctuations are expected. Google says medium-sized sites commonly need weeks or longer for new URLs to appear, while larger sites can take more time depending on URL volume and server speed.
- Create a one-to-one map from old URLs to appropriate new destinations.
- Configure and test permanent redirects at the server level where possible.
- Replace old canonical references and review robots restrictions.
- Submit the new sitemap.
- Monitor the old and new sites for indexing and redirect problems.
Key takeaways for project planning
Separate security maintenance, feature adoption, content transfer, and domain changes into distinct workstreams. A WordPress security update may be urgent, while adopting new blocks or responsive controls can wait for compatibility testing.
Treat domain, CMS, and layout changes as separate steps, following Google's recommendation. This reduces the number of variables under investigation if redirects, rendering, content, or indexing behave unexpectedly. Before launch, confirm that the team can answer four concrete questions: Is the source platform patched? Can all required content be exported? Have deprecated API calls been replaced? Does every old URL have a tested destination?.
