WPGEARED2.0.
Weekly Brief

WPGeared Weekly Brief: WordPress 7.1 RC, Client-Side Media, AI Alt Text & Search Visibility

Published WPGeared
Share Report:

Executive take: The immediate priority is WordPress 7.1 compatibility testing before RC1 on August 5. The largest engineering risk for Alt Text Pro and other media plugins is WordPress's new browser-side image-processing pipeline. The strongest agency opportunity is expanding client reporting from traditional rankings into AI-search visibility and social-content discovery.

1. WordPress 7.1 reaches Release Candidate this week

What changed: WordPress 7.1 Beta 4 was released on July 29 with more than 114 Core and Editor fixes since Beta 3. The official 7.1 schedule puts RC1 on August 5, RC2 on August 12, and the final release on August 19, 2026. RC1 also begins the hard string freeze and publication of the developer Field Guide.

Why it matters: RC1 is effectively the point where the feature set stabilizes. Compatibility problems discovered after this point are more likely to become release-day support issues rather than changes that can be addressed comfortably during development.

WPGeared actions:

  • Test custom blocks, editor extensions, plugin sidebars, and theme integrations against RC1.
  • Run client staging sites with both classic and block themes.
  • Test WooCommerce product editing, galleries, uploads, and bulk-media workflows.
  • Record issues by browser, plugin version, and theme rather than treating them as generic WordPress problems.
  • Prepare a short WordPress 7.1 client advisory before August 19.

2. Client-side media processing is the biggest plugin compatibility change

What changed: WordPress 7.1 can use WebAssembly and wasm-vips to process images inside the browser before uploading them. Supported browsers may handle resizing, compression, format conversion, EXIF rotation, and thumbnail generation locally, while unsupported environments fall back to normal server-side processing. The official Core dev note describes the new pipeline and its browser/device fallback behavior.

The attachment workflow also changes. wp_generate_attachment_metadata may run during both creation and finalization, while server-specific hooks such as wp_image_editors, image_memory_limit, and image_make_intermediate_size do not run when the browser path is used. Content Security Policies that prevent blob workers can force a fallback to server processing.

Why it matters: Image optimization, watermarking, CDN syncing, and AI alt-text plugins may receive different events depending on the browser. A plugin that assumes one metadata event per upload could generate alt text twice, deduct duplicate credits, or analyze an attachment before its final metadata is ready.

Alt Text Pro actions:

  • Make every generation job idempotent using the attachment ID and a unique processing state.
  • Prevent the create and update metadata events from charging twice.
  • Start AI analysis only after the final attachment metadata is available.
  • Test Chromium's browser-processing route and Safari/Firefox fallback routes separately.
  • Test HEIC, AVIF, animated GIFs, regenerated thumbnails, and custom image sizes.
  • Verify compatibility with optimization, CDN, offload, and security/CSP plugins.
  • Store the original image's generation status separately from its generated sub-sizes.

This deserves priority over adding another generic AI-writing feature.

3. Gutenberg and editor integrations need a UI compatibility pass

What changed: Gutenberg 23.6 makes the Tabs and Playlist blocks stable, expands media cropping, introduces dynamic Gallery behavior, adds icon registration APIs, and supports configurable preview widths through theme.json. The Gutenberg plugin now consistently iframes the Post Editor; WordPress 7.1's Core rollout applies enforced iframe behavior to block-theme editing environments.

WordPress 7.1 also makes 40-pixel controls the default across many @wordpress/components components. The old __next40pxDefaultSize opt-in is ignored, the deprecated Navigation component is being removed, and developers should migrate to Navigator.

Why it matters: A plugin can remain technically functional while developing clipped fields, inconsistent spacing, missing editor CSS, or broken selectors. Extensions that access the parent document directly are particularly vulnerable in an iframe.

Plugin-builder actions:

  • Search codebases for __next40pxDefaultSize, deprecated Navigation usage, and direct document selectors.
  • Explicitly enqueue editor-canvas styles instead of relying on general admin CSS.
  • Test focus management, popovers, modals, and keyboard navigation inside the iframe.
  • Check plugin toolbars and sidebars at mobile and tablet preview widths.
  • Verify that custom icons inherit color and scale correctly under the updated icon system.

4. Infinite scrolling changes how bulk-media tools should work

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

Why it matters: A bulk-processing plugin should no longer assume that every attachment is represented in the visible DOM or that clicking a “Load more” control handles pagination. Selection counters and filters may also break when additional attachments load automatically.

Alt Text Pro actions:

  • Keep scanning and processing API-driven rather than DOM-driven.
  • Do not calculate total attachment counts from visible thumbnails.
  • Preserve selections when more items load.
  • Test bulk generation with infinite scrolling both enabled and disabled.
  • Make filters and progress indicators reflect the full query, not just rendered items.

5. Plugin submissions remain near record levels

What changed: The Plugins Team's July 20 report recorded 816 plugin requests and 625 approvals. Of 4,792 new and pending entries, 4,075 were waiting on plugin authors, while only 79 had not yet received an initial response. A broader team update reported nearly 3,000 initial reviews during May, compared with roughly 1,100 in the same month a year earlier. See the official Plugins Team update for the queue breakdown.

Why it matters: The apparent directory backlog is not primarily an initial-review problem. Many launches stall because developers submit incomplete packages, fail to address every review point, or respond too slowly.

Release-process actions:

  • Run Plugin Check, WordPress Coding Standards, and security scans before submission.
  • Test the exact ZIP that will be uploaded.
  • Clearly disclose external AI services, transmitted image data, credit systems, and telemetry.
  • Confirm that uninstall behavior and data-retention policies match the readme.
  • Answer all reviewer concerns in one structured response.
  • Avoid duplicate or lightly repackaged submissions that could be treated as directory spam.

6. AI alt text is shifting from generation to intent classification

What changed: WordPress 7.1 includes testing for a Mark as decorative option in the Image block. It intentionally gives decorative images an empty alt value or equivalent presentation treatment so screen readers skip them. The WordPress 7.1 roadmap lists the toggle as part of the release direction.

The W3C Images Tutorial distinguishes informative, decorative, functional, and complex images. Decorative images need alt=""; functional images should describe the action; complex graphics may require a fuller text equivalent rather than a short generated sentence. The correct treatment depends on why the image appears in that particular context.

Why it matters for Alt Text Pro: Automatically filling every empty alt field is not accessibility. It may overwrite a valid human decision and add unnecessary screen-reader noise.

Recommended product direction:

  • Classify images as informative, functional, decorative, or complex before generating.
  • Preserve intentionally empty alt attributes.
  • Use surrounding headings, captions, product names, and link destinations as context.
  • Flag charts, infographics, and screenshots for human review.
  • Store “AI suggested,” “human reviewed,” and “decorative” as separate states.
  • Never interpret every alt="" value as unfinished work.
  • Include confidence levels so uncertain results can enter a review queue.

The canonical WordPress AI plugin's 1.2 release also added bulk content summaries and secure read-only core/read-content and core/read-users Abilities. This shows WordPress continuing to build reusable AI infrastructure that specialized plugins can expose capabilities through, rather than replacing specialized products outright.

For future interoperability, Alt Text Pro could eventually expose controlled abilities such as:

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

Accessibility-ready theme deadline

The Accessibility Team has extended the accessibility-ready theme-review timeline while it works through the backlog; its July 23 update described the end of September as the working target while noting that formal guidance would follow. WPGeared should identify any client or internal themes using that tag and confirm the current re-review instructions before treating the target as a final compliance deadline.

7. SEO reporting is expanding, but shortcuts are not

What changed: On July 24, Google added a review-snippet guideline covering fake reviews and undisclosed incentivized reviews. Google says the purpose is to improve review transparency. The official review-snippet guidance says not to include fake or undisclosed incentivized reviews in visible content or structured data.

Why it matters: Clients offering gifts, discounts, or free products for reviews should disclose those incentives. Review schema should not be added to fabricated, self-serving, or selectively manipulated testimonials.

Action: Add review-source and incentive checks to structured-data audits. Confirm that displayed reviews, aggregate ratings, and schema represent the same visible information.

Google is also rolling out Search Console platform properties for Instagram, TikTok, X, and YouTube. They show Search and Discover performance for eligible platform content. LinkedIn is not included in the initial rollout, and availability is still gradual.

Separately, dedicated Search Generative AI performance reports are being tested with a subset of sites, showing visibility in AI Overviews, AI Mode, and generative Discover experiences. Not every Search Console account has access yet.

Agency opportunity: Add a cross-channel discovery section to suitable client reports:

  • Traditional website search performance.
  • AI-search visibility, when the dedicated report is available.
  • Google discovery of Instagram, YouTube, TikTok, and X content.
  • Conversions and engagement quality after the click.
  • Content gaps revealed by social-search queries.

Google's current AI-search guidance still says there is no special AI schema, AI text file, or separate technical requirement for AI Overviews and AI Mode. Indexability, snippet eligibility, internal links, textual content, page experience, useful media, and accurate structured data remain the foundations.

That gives WPGeared a clean positioning: sell stronger technical foundations and better evidence-rich content, not invented “GEO magic.”

Three adaptable LinkedIn post angles

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

Explain how browser-side media processing changes attachment events and why AI, CDN, watermarking, and optimization plugins need idempotent jobs. Use duplicate AI-credit consumption as the practical example.

2. “The most accessible AI alt text can be completely empty”

Show why decorative images need alt="", functional images need an action, and charts often need more than a one-line description. Position Alt Text Pro as context-aware accessibility assistance rather than a bulk field-filling tool.

3. “Google is measuring AI visibility—but says there is no magic AI schema”

Contrast the new AI and social reports with Google's unchanged technical advice. The hook: reporting is changing quickly, but successful optimization still depends on crawlability, useful content, internal linking, media, and honest structured data.