August 2026 brought stricter domain-migration steps, WordPress development changes, an urgent security fix, supported Drupal upgrade options, and new Contentful auditing. These updates make sequencing, redirect management, patching, accessibility testing, and operational visibility the priorities to watch. A CMS migration moves a site's content, design, or publishing workflows to a new platform or configuration. Teams should separate migration risks, update vulnerable WordPress sites immediately, and use Drupal's remaining support window to plan rather than rush.
Official resources:
- Read the official guidance from Google — Use this primary source to verify the official guidance.
- Read the official notice from WordPress — Use this primary source to verify the official announcement.
Table of Contents
- What changed for domain and CMS migrations?
- What should a migration runbook include?
- How does WordPress 7.1 change front-end work?
- Which security and platform upgrades need attention?
- What should enterprise content teams watch next?
What changed for domain and CMS migrations?
google continues to advise changing a CMS, domain, or layout one at a time. Its site-move documentation warns that rankings may fluctuate during recrawling and that medium-sized sites may need weeks or longer to show new URLs. That guidance favors staged projects. For example, a team could move to a new CMS while preserving existing URLs, validate the result, and change the domain later. Combining both changes makes it harder to identify whether a traffic problem comes from redirects, templates, content, or crawling.
Google added a procedural requirement on June 17. Its Search guidance update says domain migrations must submit Change of Address requests for every verified old-domain variant. That includes subdomains and www or non-www versions, even when a variant is inactive. Before launch, inventory every verified property connected to the old domain. An overlooked variant may otherwise leave the migration process incomplete despite a correct redirect map.
What should a migration runbook include?
Google recommends permanent server-side redirects and says they do not lose PageRank. It also recommends retaining redirects for at least one year and submitting a sitemap containing the new URLs.
A practical runbook should therefore include: Do not treat launch day as the end of the project. Recrawling takes time, so early fluctuations do not automatically prove that a migration failed. Compare expected and discovered URLs over several weeks while correcting specific redirect or indexing problems.
- A one-to-one map from each important old URL to its closest new equivalent.
- Permanent redirects implemented at the server level.
- Change of Address submissions for all verified old-domain variants.
- A new sitemap containing canonical destination URLs.
- Checks for redirected pages, missing destinations, and unintended redirect chains.
How does WordPress 7.1 change front-end work?
wordpress released version 7.1 on august 19. According to the WordPress 7.1 release announcement, responsive block styling and theme-defined breakpoints can now adapt layouts across screen sizes without custom CSS. This can reduce the amount of one-off styling attached to individual blocks. Theme teams should first define breakpoints consistently, then test how existing blocks respond before removing established CSS.
The feature simplifies common layouts, but it does not eliminate the need to inspect navigation, typography, spacing, and media on representative screens. WordPress 7.1 also moves image compression, resizing, and thumbnail generation into the browser through WebAssembly and libvips. That approach reduces server work and avoids PHP memory limits or upload timeouts when processing large media. Teams should include media workflows in acceptance testing. Test large uploads, generated image sizes, browser compatibility, and the behavior of any plugin that depends on traditional server-side image processing.
Which security and platform upgrades need attention?
WordPress 7.0.4 addressed an authenticated remote-code-execution vulnerability involving malicious uploads on sites using Imagick and Ghostscript. The issue could be exploited by accounts with Author-level access or higher, and the WordPress security release urged immediate updates. Site owners should not assume that restricting administrator access removes this risk. Confirm the installed WordPress version, apply the security release, and review which users can upload media or publish content.
Drupal's current stable releases include 11.4.5 and 10.6.15, both released August 6, according to Drupal.org. Drupal 10 remains supported until December 9, 2026, so organizations have a defined bridge for testing and completing a Drupal 11 upgrade. Drupal 11.3 made the new Navigation module stable for production, but Drupal says it cannot yet replace the default Toolbar because major and critical accessibility bugs remain. PHP 8.4 is recommended, while PHP 8.3 remains the minimum. Upgrade planning should therefore cover the PHP environment and administrative accessibility, not only Drupal core.
What should enterprise content teams watch next?
Contentful began offering near-real-time audit-log streaming to Enterprise customers on August 18. Content-access and change events can reach cloud storage in about five minutes for security monitoring and security information and event management workflows. This narrows the delay between a content action and its appearance in monitoring systems.
Teams evaluating the feature should decide which events require alerts, how long logs must be retained, and who investigates unexpected access or changes. The limitation is scope: this is an Enterprise capability, and audit delivery does not replace an incident-response process. A five-minute stream is useful only when ownership, alert thresholds, and escalation steps are already defined.
