WPGEARED2.0.
Weekly Brief

WPGeared Weekly Brief: WordPress 7.1 Media Changes, AI Alt Text, Plugin Review & SEO Updates

Published Updated WPGeared
Share Report:

Executive take: The most consequential work this week is WordPress 7.1 compatibility testing, especially for plugins touching media uploads, the Media Library, editor components, custom blocks, or image metadata. For Alt Text Pro, the new client-side media pipeline and decorative-image handling deserve priority over adding more generic AI-writing features.

1. WordPress 7.1 Beta 3 narrows what will actually ship

What changed: WordPress 7.1 Beta 3 shipped on July 22. The release schedule puts Beta 4 on July 29, RC1 on August 5, and the final WordPress 7.1 release on August 19, 2026. The cycle is now moving from broad feature development toward compatibility testing and release-blocker cleanup. See the official WordPress 7.1 schedule for the current roadmap.

Why it matters: Compatibility problems found during beta can still be fixed before RC1. After August 5, the cycle largely shifts toward regressions and release blockers, leaving less room for extensions that discover problems late.

WPGeared actions:

  • Test custom blocks, editor extensions, media workflows, and WooCommerce product images on Beta 3.
  • Retest image rotation, GIFs, HEIC uploads, and bulk-media actions.
  • Record failures in Chromium, Safari, and Firefox because the new media path varies by browser.
  • Prepare a client-facing WordPress 7.1 readiness checklist before August.

2. Gutenberg 23.6 changes both the editor experience and developer surface

What changed: Gutenberg 23.6 adds cropping controls to the Media editor, brings more controls to the Cover block, expands responsive style states, makes the Playlist and Tabs blocks stable, and introduces icon collections plus a custom icon-registration API. The Post Editor is now always iframed, aligning its rendering more closely with the Site Editor.

WordPress 7.1 also makes 40-pixel form controls the default across many @wordpress/components controls. Deprecated editor APIs and assumptions about global admin CSS therefore deserve another pass.

WPGeared actions:

  • Remove obsolete __next40pxDefaultSize props where they exist.
  • Search plugin repositories for the deprecated Navigation component.
  • Test plugin sidebars, modals, and block controls inside the iframed editor.
  • Explicitly enqueue editor styles instead of assuming admin-page CSS reaches the canvas.
  • Keep a WordPress 6.9 test installation because Gutenberg 23.6 cannot be used to test older Core versions.

3. WordPress image uploads are being fundamentally reworked

What changed: WordPress 7.1 introduces client-side media processing using WebAssembly and wasm-vips. In supported browsers, compression, resizing, thumbnails, format conversion, and EXIF rotation happen in the browser before the resulting files are uploaded. Browsers and devices that do not meet the requirements fall back to normal server-side processing.

The official Core dev note explains an important compatibility detail: wp_generate_attachment_metadata still fires, but it may run once during creation and again after client-side sub-sizes are finalized. Server-image-editor hooks such as wp_image_editors, image_memory_limit, and image_make_intermediate_size do not run on the browser-processing path.

Why it matters for Alt Text Pro: A plugin that assumes one metadata event per upload could generate twice, consume duplicate credits, or send duplicate API requests.

Alt Text Pro actions:

  • Make metadata-triggered generation idempotent.
  • Store a generation job identifier against each attachment.
  • Run generation only after the attachment and its metadata are sufficiently complete.
  • Test original uploads, generated sub-sizes, HEIC conversion, external-image imports, and browser fallback.
  • Verify that CDN or optimization plugins do not make regenerated sizes look like new attachments.
  • Test content-security policies that allow blob: in worker-src when browser processing is enabled.

This is probably the single most important technical compatibility item for the plugin right now.

4. Media Library infinite scrolling returns by default

What changed: WordPress 7.1 enables infinite scrolling by default in the Media Library grid and Media Modal. Individual users can disable it through their profile, while the existing media_library_infinite_scrolling filter can override the setting site-wide. The current WordPress 7.1 testing guide includes the related media workflows.

Why it matters: Bulk-media plugins should not assume that every displayed attachment is present in the DOM or that a “Load more” action controls pagination.

WPGeared actions:

  • Test Alt Text Pro's bulk selection and filtering with infinite scrolling enabled and disabled.
  • Avoid deriving the total attachment count from rendered grid items.
  • Preserve selections when additional pages load.
  • Make scanning and bulk processing API-driven rather than dependent on the visible Media Library DOM.

5. WordPress's AI layer is becoming useful infrastructure

What changed: The canonical WordPress AI plugin's 1.2.0 release adds bulk content-summary generation, a suggested-reply experiment, permission-aware core/read-content and core/read-users Abilities, and a filter for adjusting long-running AI request timeouts. The official AI 1.2.0 release note also describes accessibility and developer-extensibility improvements.

Why it matters: WordPress is developing reusable AI infrastructure rather than bundling every specialized workflow into Core. That creates an opportunity for Alt Text Pro to expose controlled abilities such as:

alt-text-pro/generate-alt-text
alt-text-pro/review-image
alt-text-pro/process-media-library

Practical direction: Keep Alt Text Pro provider-independent internally. Separate the image-analysis service, prompt and context builder, credit check, and WordPress-writing operation so they can later be exposed safely through an Ability or REST endpoint.

6. Accessibility: “No alt text” can be the correct result

What changed: WordPress 7.1 testing includes a Mark as decorative option for Image blocks. When enabled, the image receives an empty alt attribute or equivalent presentation treatment so screen readers skip it. The WordPress testing instructions describe the toggle and expected behavior.

Why it matters for Alt Text Pro: The plugin must distinguish between a missing alt attribute and an intentionally empty one. Automatically replacing alt="" would undo a valid accessibility decision.

Recommended safeguards:

  • Never overwrite intentionally decorative images during bulk generation.
  • Record whether an empty alt value was selected by a person or merely left unreviewed.
  • Classify images as informative, functional, decorative, or complex before generating.
  • Flag charts, infographics, and screenshots for human review.
  • Use linked-image destinations and surrounding content when generating functional alt text.

7. Plugin submissions remain high, but authors are causing most delays

What changed: In the week reported July 20, the Plugins Team recorded 816 plugin requests and 625 approvals. Its queue report showed 4,075 submissions waiting on authors compared with 449 waiting on reviewers. The full figures are available in the official Plugins Team update.

Why it matters: The large headline queue does not mean every new plugin faces the same initial delay. For many developers, the bigger launch problem is submitting incomplete work or responding slowly to reviewer feedback.

WPGeared actions:

  • Run Plugin Check before every directory submission.
  • Test the exact release ZIP rather than only the Git repository.
  • Explain external AI services, credit systems, telemetry, and data transmission clearly in the readme.
  • Keep one person responsible for answering directory-review emails quickly.
  • Resolve reviewer points in one comprehensive response where possible.

8. SEO/search: no new confirmed Google ranking rollout

What changed: Google's official Search Status Dashboard showed no crawling, indexing, ranking, or serving incident through July 26. The latest confirmed ranking event remained the June 2026 spam update, which started June 24 and completed roughly two days later.

Google also continues to state that appearing in AI Overviews or AI Mode does not require special AI schema, llms.txt, or separate technical optimization. Pages still need normal SEO fundamentals: crawlability, internal linking, useful textual content, page experience, helpful media, and accurate structured data.

WPGeared actions:

  • Do not attribute late-July volatility to an unconfirmed algorithm update.
  • Review page-level changes, indexing, competitors, seasonality, and technical deployments first.
  • Combine website, social-search, and AI-visibility reporting rather than treating them as separate channels.
  • Avoid selling invented “AI schema” or magic GEO markup; sell stronger content structure, authority, freshness, and technical accessibility.

Three adaptable LinkedIn post angles

1. “WordPress 7.1 could make your image plugin run twice”

Explain how browser-side processing changes the upload sequence and why metadata hooks must be idempotent. Close with a checklist for watermarking, optimization, CDN, and AI alt-text plugins.

2. “An empty alt attribute is not an SEO mistake”

Show how decorative images should be intentionally ignored by screen readers. Contrast a missing decision with a correct alt="", then explain why bulk AI tools must preserve human accessibility choices.

3. “The plugin-review backlog is not what the headline number suggests”

Use the latest directory figures to show that most pending submissions are waiting on authors. Share practical lessons: test the ZIP, disclose external services properly, and answer reviewer feedback completely.