Uncategorized

Your WordPress membership content could be circulating on public forums for free right now, and you wouldn’t know it until your revenue starts to drop. Many site owners rely on simple password protection, which does nothing to stop a member from sharing direct download links with non-paying users. The good news is that you don’t need to build custom security systems or hire a developer. The right combination of WordPress plugins and a few straightforward settings can dramatically reduce the risk of your content being stolen or redistributed. In this guide, I will show you exactly how to protect your site and keep your premium content exclusive to paying members. 🔐 TL;DR: Prevent membership content theft by following these tips: Restrict content to logged-in members and enforce access rules with MemberPress. Put key material behind a paywall and protect downloads with MemberPress Downloads or Easy Digital Downloads. Use content dripping to limit mass copying and improve retention. Watermark images and limit your RSS feed to excerpts to reduce scraping. Monitor the web with Google Alerts and Copyscape to catch unauthorized use early. Back everything up with copyright notices and a Creative Commons license to give yourself legal standing if you need to act. Why Content Protection Is Important for Membership Sites Content is the biggest asset for any membership site — it’s what people pay or sign up for. Whether that’s online courses, premium tutorials, downloadable resources, or a members-only community, your content is the reason people stick around. I’ve seen firsthand how quickly unprotected content can spread. Once someone shares your premium material outside your site, it becomes nearly impossible to remove it from the internet. That’s why protecting your content from the start is far easier than trying to recover it later. The good news is that a few smart strategies can go a long way. Here’s why content protection should be a priority for your membership site: 💰 Protect your revenue — If your premium content is freely available elsewhere, then potential members have little reason to pay for access. For example, a leaked online course can cost you dozens of lost subscriptions. 🌟 Maintain the value of your membership — If a paying member can find your premium content with a quick Google search, they will cancel. Keeping content genuinely exclusive is what makes the membership fee feel worth paying month after month. 🛑 Stop content scrapers and copycats — As your membership site grows and your content gains visibility, it becomes a more attractive target for content scrapers and copycats. Getting protections in place early means you are not scrambling to recover later. ⏱️ Protect the time and effort you invest — Building a quality online course or resource library can take hundreds of hours. If that material leaks and circulates for free, you lose the ability to charge for it, effectively giving away all that work with nothing in return. 🕹️ Control how your content is shared — Even well-meaning members may share content without realizing it’s a problem. Clear restrictions and licensing help set expectations from the start. There are also legal and ethical considerations to keep in mind. Unauthorized use of your content may violate copyright law, and having protections in place gives you a stronger foundation if you ever need to take action against someone who misuses your work. Here is an overview of the topics I will cover in this post: Tip 1. Restricting Content to Logged-In Members Tip 2. Putting Premium Content Behind a Paywall Restricing Access to Downloadable Files Tip 3. Setting Up Content Dripping Tip 4. Protecting Images with Watermarks Tip 5. Customizing Your RSS Feed Tip 6. Monitoring the Web for Unauthorized Content Usage Tip 7. Using a Plagiarism Checker to Search for Copies Tip 8: Setting Up Copyright Notices Applying for Copyright Adding the Copyright Notice to Your Site Making Your Copyright Dynamic Tip 9. Getting Creative Commons Licenses Getting Your License Badge Placing the License Prominently on Your Site Bonus Tip: How to Improve Your WordPress Site Security Frequently Asked Questions About Protecting Membership Content Next Steps to Grow Your Membership Site Tip 1. Restricting Content to Logged-In Members One of the most effective ways to protect your membership content is to make sure only registered members can access it. This prevents casual visitors, bots, and most scrapers from viewing your gated content in the first place. Think of it like a lock on the door. If someone can’t even see your premium content, then they can’t copy it, download it, or share it without your permission. For this, we recommend using MemberPress. It’s one of the best and most popular membership plugins available for WordPress, and it gives you powerful tools to control exactly who can access what on your site. At WPBeginner, we actually use MemberPress to run our video membership site. It’s been working really well for us, and you can learn more about it in our complete MemberPress review. To do this, you’ll need MemberPress installed and activated on your site. You can see ourbeginner’s guide to installing a WordPress plugin for a step-by-step guide. 💡 Note: MemberPress is a premium plugin. Make sure to create an account on the MemberPress website, download the zip file, and upload it to your WordPress website. Then, you’ll verify your license key. Once the plugin is active, go to MemberPress » Rules in your WordPress dashboard to start creating access rules. This is where you control which content is visible to which membership levels. With MemberPress, you can restrict pages, posts, videos, and downloadable resources so that only registered members can access them. For example, you might restrict all posts in a specific category to paying members. You could also limit access to individual pages, such as member-only forums, resource libraries, or private communities. This flexibility means you can tailor your content restrictions to match exactly how your membership site is structured. Even better, you can set up recurring payments so that members are billed automatically and maintain

First, I want to say how great the jazz scene is in New York. I caught a little Latin at my go-to Guantamera last night, but the band seemed to be phoning it in a bit, so I walked over to Dizzy’s and heard an amazing big band performance by the Diva all-women Jass Orchestra, they had Clint Holmes leading vocals and I got Frank Sinatra / Count Basie vibes, so great to see such a tight big band. In WordPress, last week it was fun to see the company some call parasitic WP Engine acquire WPackagist. So a popular way to use WordPress with Composer, previously maintained by an awesome co-op agency in London, was now in the clutches of a company using its capital advantage to try to openwash its alleged bad behavior, probably in a process that wasn’t ideal for the sellers. Four days later, an awesome independent organization roots.io released WP Composer (renamed to WP Packages, in OpenClaw fashion) with 17x faster cold resolves than WPackagist. Check out their comparison page. It’s beautiful to see how resilient and nimble the antibodies in the WordPress community are. Major hat tip to Ben Word. In another type of antibody, Sid Sijbrandi, whom I previously talked about going into founder mode on his cancer, gave an incredible presentation at the Open AI Forum about how he ran a bunch of N-of-1 experiments and therapies to cure his terminal osteosarcoma. He’s also open-sourced 25TB of his data for cancer research. Incredible! If you want to see the future of health care, give Sid’s presentation a watch.

A week ago, I put together a quick tech demo, showing how an MCP server could be created for Claude Code that hooked directly into Gutenberg’s Collaborative Editing feature, allowing it to act as a digital collaborator on a post. The demo focused primarily on text generation, but that’s not really the benefit that I see coming with this kind of tool. Anyone can generate text, then copy/paste it into the editor. The real power comes from directly hooking into the entire post creation and editing process. What’s New? Since last week’s release, I’ve added a host of editing and review tools: /edit {tell the LLM how you want this post adjusted}Automatically make simple (or even not so simple!) edits on your post, giving your writing a little extra polish. /proofreadFind and automatically fix simple spelling, grammatical, and punctuation issues. /reviewRead the post, and leave notes (using Gutenberg’s Notes feature!) about suggested improvements to your post. This doesn’t touch your post content, leaving you to make use of the suggestions as you see fit. /respond-to-notesIf you’re happy with the notes left in the review, you can also have it automatically apply them, too! On top of that, I’ve also added an experimental /translate tool, to automatically translate a post into a different language. LLM translation quality varies significantly, though Claude is regularly considered to be quite good. It’s worth remembering that, like any LLM, the output is only as good as its input. If you’re translating to a language that it didn’t have much training data on, it’ll do a lot worse. Behind The Scenes The MCP server now does a much better job of making use of the REST API, too: it now handles all block types (and does a pretty good job of guessing how to use blocks provided by plugins!). It can upload media, and it can handle all the post metadata, like categories, tags, excerpt, etc. Getting It Running Inspired by the recently released WordPress.org MCP server, the install process got a refresh, too. If you’re running WordPress 7.0, you won’t even need to copy/paste the application password to connect to your site: just click the connect button in your browser, and your site will send credentials back to the installer! And if you’d prefer to avoid the magic, there’s still a –manual option to let you set it up the old-fashioned way. Connect Authorise Install What’s Next? This release shows how easy it is for an LLM to talk to your WordPress site. What about the other way? If you’re working on a post, you don’t want to have to switch to a terminal to get spell checking done, so how can we provide this kind of functionality directly from the block editor? Let’s experiment and find out!

Hi, In less than two weeks, WordPress 7.0 is scheduled to be released. Are you ready? Or are you someone I used to be who waits two to three weeks to see what quirks early adopters find and if they warrant an early point release? Be that as it may, waiting only delays the inevitable, though, sooner or later you get to benefit from the new features and quality of life improvements to the Admin, Editor and Blocks. The first version of the WordPress 7.0 Source of Truth has been published. It’s again a mammoth post of 4500 words, including 21 images and ten videos. I hope you enjoy the list of all the big and small feature and updates. Next week, I will be on my way to Mumbai. The next weekend edition will arrive in your inbox after WordCamp Asia, on April 17th, 2026. Yours, Birgit PS: Should you be in Mumbai, grab a coffee of lunch spot from my public calendar, I’d love to meet you! WordPress 7.0 WordPress 7.0 Release candidate 1 was moved to this week. The WordPress 7.0 RC2 was still on schedule for Thursday, though. Meanwhile, more Dev Notes were published. Pattern Overrides in WP 7.0 is your heads-up to act before the release lands. WordPress 7.0 lifts the old restriction — Pattern Overrides now work with any block attribute that supports Block Bindings, not just a hardcoded Core block list. You opt in via the block_bindings_supported_attributes filter, and the post walks you through edge cases for static blocks where a render_callback may still be needed. Pattern Editing in WordPress 7.0 explains that ContentOnly mode for unsynced patterns is now the default, meaning block structure and style controls are hidden from editors by default. Block authors need to audit “role”: “content” attributes in block.json, theme authors should test their patterns, and plugin developers should verify UI components still render correctly under the new, more broadly applied editing modes. Block Visibility in WordPress 7.0 dev note is relevant if your theme or plugin touches block markup server-side. The new viewport key inside blockVisibility metadata lets users show or hide blocks per device — mobile, tablet, desktop — via CSS, not DOM removal. If your code assumes blockVisibility is always a boolean, you’ll need to update it to handle an object too. No changes are needed if your blocks don’t interact with markup server-side. Anne McCarthy walks through one of WordPress 7.0’s most-requested features: viewport-based block visibility. You’ll see exactly how showing or hiding any block by screen size works in practice — no extra plugins or CSS workarounds needed — and why it is relevant for responsive design. If you’ve been waiting for a native way to tailor content for mobile, tablet, and desktop separately, this is your preview before the April 9th release. The Dimensions Support Enhancements in WordPress 7.0 comprise width and height as first-class block supports. Block builders and theme designer opt in with a single line in block.json, set defaults in theme.json, and the sidebar UI comes for free. Themes can also define named dimensionSizes presets, giving users a consistent palette rather than free-form inputs. If your block has custom width/height attributes today, this is a good moment to consider migrating. A long-requested feature finally lands in WordPress 7.0. The dev note on Custom CSS for Individual Block Instances hold all the details. The new customCSS block support — enabled by default for all blocks — adds a Custom CSS field in the Advanced panel of the block inspector, scoped automatically to that instance via a generated class. Block authors whose blocks wrap raw or opaque content should explicitly opt out via block.json. If your render_callback is in play, make sure your block’s outermost element is a standard HTML tag. A typography feature requested since 2021 finally arrives in WordPress 7.0, the dev note on the new textIndent block support has all the details for developers working on blocks or themes. Opt in with a single line in block.json, and a Line Indent control appears automatically in the Typography panel. Theme authors get theme.json configuration too, including a thoughtful subsequent vs all toggle that respects both LTR and RTL typographic conventions. No breaking changes — purely additive./ WordPress 7.0 ships a new Connectors API — and if you build AI-adjacent plugins, this dev note belongs on your reading list. The new framework standardizes how WordPress registers and manages connections to external services — starting with AI providers — giving you a consistent admin UI, API key management, and auto-discovery via the WP AI Client. Three providers ship out of the box: Anthropic, Google, and OpenAI. The wp_connectors_init action is your hook for registering additional connectors or overriding existing metadata. Felix Arntz details the new AI Client landing in WordPress 7.0 — a provider-agnostic PHP API that lets your plugin send prompts for text, images, speech, or video without touching credentials or provider logic. You chain methods on wp_ai_client_prompt(), declare model preferences, and WordPress routes to whatever the site owner has configured. Three official provider plugins cover Anthropic, Google, and OpenAI. Client-side JS exists but remains admin-only for now. Jorge Costa details the client-side Abilities API arriving in WordPress 7.0, the JavaScript counterpart to the PHP Abilities API introduced in 6.9. Two new packages handle it: @wordpress/abilities for pure state management and @wordpress/core-abilities for the WordPress integration layer that auto-fetches server-registered abilities via REST. You can register abilities with input/output schemas, permission callbacks, and annotations — laying the groundwork for browser agents and WebMCP integration. Gutenberg 22.8 Gutenberg 22.8 release lead Dean Sas highlighted in his post What’s new in Gutenberg 22.8? (25 March) the following features: Real-time Collaboration improvements Button pseudo-state styling in Global Styles Site Logo & Icon in the Design panel Connectors extensibility Other Notable Highlights The real-time collaboration improvements and the Connectors extensibility will make it into the WordPress 7.0 release. I had a blast chatting with Beth Soderberg from Bethink Studio on the recording of

Welcome to the Source of Truth for WordPress 7.0! Before you dive headfirst into all the big and small changes and pick your favorites, make sure to read these preliminary thoughts about this post and how to use it. If you have questions, leave a comment or email me at pauli@gutenbergtimes.com. Huge Thank You to all collaborators on this post: Anne McCarthy, Sarah Norris, Ella van Durpe, Maggie Cabrera, Ben Dwyer, Jonathan Bossenger, Justin Tadlock, Dave Smith, Courtney Robertson and a lot more. It’s takes a village… Estimated reading time 19–29 minutes at 4,579 words Table of Contents Changelog Important note/guidelines Overview  Important links: Assets  Tags Priority items for WordPress 7.0  Real-Time Collaboration (RTC) [enterprise][site admin] Navigation Overlays and more [theme builder][plugin author] [site admin] Treating patterns like a single block [all] AI in WordPress [enterprise][developers][site admin] Visual Revisions [all] New Blocks Breadcrumbs Block [all] Icon Block [all] Block Editor enhancements Custom CSS for Individual Blocks [enduser][site admin] [theme builder] Control viewport-based block visibility [all] Anchor support for dynamic blocks [developer][plugin author] Color Picker [end user][theme builder] [site admin] Dimension support for width and height [theme builder][site admin] Email notifications for Notes [all] Block Attributions Groups in the sidebar [all] Link Control validation [end user] [site admin] Improved Blocks and Block handling Pseudo Styles for Button Blocks [theme builder][site admin] Extra divs removed from blocks in the editor [theme builder][developer][site admin] Universal Text Alignment [all] Cover Block Video Embeds [site admin][end user] Gallery Block  Responsive Grid Block [site admin][end user][theme builder] Heading Block [site admin][end user] HTML Block Enhancement [site admin] [themebuilder] [end user] Image block inline editing and controls [site admin][end user] Math Block Improvements [end users][site admin] Paragraph [all] Query Loop Enhancements [all] Verse Block, renamed to Poetry [all] Admin / Workflow updates  Manage fonts for all themes in a dedicated page [site admin][theme builder] [enterprise] Command Palette in Adminbar [all] View Transitions  [all] Improved screens across WP-Admin  [all] Developer Goodies [developer][enterprise] PHP-only block registration Pattern Overrides for custom blocks DataViews, Data Form components and Fields API  UI Primitives and Components Changelog Any changes are cataloged here as the release goes on. First edition March 27, 2026 Important note/guidelines Try not to just copy and paste what’s in this post since it’s going to be shared with plenty of folks. Use this as inspiration for your own stuff and to get the best info about this release. If you do copy and paste, just remember that others might do the same, and it could lead to some awkward moments with duplicate content floating around online. Each item has been tagged using best guesses with different high-level labels so that you can more readily see at a glance who is likely to be most impacted. Each item has a high-level description, visuals (if relevant), and key resources if you would like to learn more. Overview Note: As always, what’s shared here is being actively pursued but doesn’t necessarily mean each will make it into the final release of WordPress 7.0. WordPress 7.0 introduces several new features and performance enhancements. Key new features include: Real-time collaboration: multiple users can now work on the same post. Navigation overlays: Customizable mobile menus for more flexible styling. Easier Pattern workflow: Patterns are now more like single blocks Visual revisions: new revisions screen from within the block editor to track changes to content and layout on the block level AI Foundation in WordPress: User can connect their site to an AI agent of choice, and plugin developer can register connection to external services. Furthermore, WordPress 7.0, entails: Two new blocks: the Icon block and the Breadcrumbs block Viewport-based block show/hide: Block visibility extended to customize display according to screen-sizes. Gallery lightbox navigation: improved browsing through images place in a gallery. Font management for all themes: The screen to upload and manage fonts is now available in the Appearance menu for classic and block themes. Many more quality of life changes for workflow and design tools made it into this release. You’ll find the complete list below. WordPress 7.0 is set to be released on April 9, 2026 at Contributor Day of WordCamp Asia. Of note, this release consists of features from the Gutenberg plugin version 22.0 – 22.6. Here are the release posts of those plugin releases: 22.0 | 22.1 | 22.2 | 22.3 | 22.4 | 22.5 | 22.6. Later Gutenberg releases contain bug fixes, backported to WordPress 7.0. release branches. Important links: Planning for 7.0 + update on Beta 1 WordPress 7.0 Development Cycle What’s new for developers: December, January, February, March 7.0 Field Guide Assets In this Google Drive folder you can view all assets in this document. Tags To make this document easier to navigate based on specific audiences, the following tags are used liberally: [end user]: end user focus. [theme builder]: block or classic theme author.  [plugin author]: plugin author, whether block or otherwise. [developer]: catch-all term for more technical folks. [site admin]: this includes a “builder” type. [enterprise]: specific items that would be of interest to or particularly impact enterprise-level folks [all]: broad impact to every kind of WordPress user. How can you use these? Use your browser’s Find capability and search for the string including the brackets. Then use the arrows to navigate through the post from one result to the next. Short video on how to use the tags to navigate the post. Priority items for WordPress 7.0 Real-Time Collaboration (RTC) [enterprise][site admin] Multiple users can now work on the same page at the same time, seeing each other’s changes as they happen. No more “someone else is editing this” warnings. Whether you’re co-writing a post, reviewing a layout, or making last-minute edits before publishing, everyone stays in sync without leaving the editor. It represents the biggest step toward achieving full collaborative editing, not only for newsrooms and big publishing houses. It also simplifies working on a site editing for agencies and their clients as well as designers and writers working together on a post. A presence indicator in the editor