Podcast: Play in new window | Download | Embed
The Weeks Discussions:
WordPress Drama:
Life time license bait an switch buddy boss example
Plugin Pulse Show Notes: Lifetime License Bait-and-Switch Trends in the WP Ecosystem (BuddyBoss Example)
In the WordPress plugin space, “lifetime” licenses have long appealed to site owners seeking cost predictability—especially nonprofits, small agencies, and long-term builders avoiding recurring billing anxiety. You pay a premium upfront for ongoing updates and support tied to the product. However, a recurring pattern has users frustrated: core or expected functionality gets carved out over time and moved behind new annual subscription tiers. This effectively erodes the value of the original lifetime purchase, turning what felt like a stable foundation into a base layer requiring ongoing add-on payments.Reddit
A clear recent example comes from BuddyBoss, a popular platform for building community, membership, and social sites on WordPress (built on top of BuddyPress foundations). One longtime lifetime license holder (a nonprofit) detailed how gamification—a key engagement feature for community platforms with points, badges, rankings, and achievements—now sits behind a $199/year paywall as part of the new “Plus” bundle or add-on. While BuddyBoss honors the original lifetime access to the core Platform Pro and Theme (with updates for the life of those products), new modules and expanded functionality introduced later require additional licensing. Support responses on this have been described as dismissive, and some users regret passing on competitor lifetime deals (like Fluent Community) at the time. BuddyBoss positions many new features as part of scalable bundles, and they have offered special grandfathering upgrade paths for existing lifetime customers (time-limited), but the shift still stings for buyers who expected all future platform evolution under the original deal.
This highlights broader risks with “lifetime” deals in the WP ecosystem—read the fine print carefully, as they often cover the product/version at purchase time rather than unlimited future features. BuddyBoss isn’t alone; similar complaints have hit plugins like Slider Revolution (new major versions treated as separate products). Lifetime options can provide upfront cash for developers and stability for buyers, but sustainable development needs ongoing revenue. Buyers should weigh expected feature roadmaps, consider version-locked expectations, and evaluate alternatives with clearer bundling or true grandfathering (e.g., Elegant Themes’ approach). Always factor in potential future add-on costs for “core” community tools.
Further Reading / Links:
-
Original Reddit discussion: https://www.reddit.com/r/Wordpress/comments/1u1y8kp/plugin_lifetime_license_holders_are_getting/ (active comments with varied developer and user perspectives).
-
BuddyBoss Licenses page: https://buddyboss.com/licenses/ (clarifies lifetime scope).
-
BuddyBoss Pricing & Plus intro: https://buddyboss.com/pricing/ and https://buddyboss.com/blog/introducing-plus/.
-
Related patterns: Search WP forums or Reddit for Slider Revolution v7 lifetime issues, WP Rocket complaints, etc.
WordPress Best Practices:
When to run cron discussions
A recent X discussion kicked off by plugin developer Robin Pietersen (@robinpietersen) asked a practical question many site owners and builders face: How often should WP-Cron run on an ecommerce site with subscriptions? Options floated included every 5 minutes, 30 minutes, hourly, or daily. The thread quickly converged on a clear recommendation from experienced developers including Danny van Kooten and Remkus de Vries: run it every minute.
The reasoning is straightforward. WP-Cron is a pseudo-cron system—it only checks and executes scheduled tasks when pages load (with basic locking to avoid excessive runs). On sites with time-sensitive operations like subscription renewals, payment processing, status updates, or automated emails (often handled via WooCommerce Subscriptions + Action Scheduler), delays or missed windows hurt reliability. Running the cron check every minute via a real server-level job (disable WP_CRON in wp-config.php and trigger wp-cron.php or wp-cli via crontab) keeps execution smooth and distributed. If nothing is queued, it’s essentially a no-op with minimal overhead. Many in the thread noted this avoids the CPU spikes or backlogs that can occur with less frequent runs, and the consensus was strong enough that the original poster plans to test the 1-minute interval.
Broader community discussions on WordPress.org, Reddit, Stack Exchange, and dev blogs reinforce this. WP-Cron’s core limitation is its dependence on traffic—low-traffic sites can miss schedules entirely, while high-traffic or cached sites may see inconsistent timing. For production environments, especially anything involving recurring billing or automation, the standard advice is to disable the default behavior and replace it with a proper system cron hitting every 1–15 minutes (1-minute intervals are increasingly favored for smoothness when the server can handle it). WooCommerce’s own Subscriptions documentation stresses that recurring payments and scheduled actions rely on reliable cron execution and includes testing steps. Plugins like WP Crontrol help developers and site admins inspect, edit, or debug events. Custom intervals beyond core (hourly, twice daily, daily, weekly) are easy to register, but the real win comes from consistent triggering rather than the exact recurrence value.
Summary:
For most modern WordPress sites—particularly ecommerce, membership, or subscription-driven ones—treat WP-Cron as “best effort” only. The reliable path is disabling the default pseudo-cron and wiring up a real server cron job (every minute is the current dev sweet spot for responsive execution with low risk of compounding load). This keeps scheduled tasks (renewals, cleanups, updates, plugin-specific events) on track without depending on visitor traffic. Plugin developers should document cron dependencies clearly and consider offering setup guidance or health checks. Always monitor with tools like WP Crontrol or server logs, especially after adding new scheduled events. The X thread shows the community has largely settled on frequent, reliable triggering over conservative pacing.
Further Links & Resources:
-
Original X thread: https://x.com/robinpietersen/status/2065356285495660988 (and replies).
-
WordPress Developer Handbook – Cron: https://developer.wordpress.org/plugins/cron/
-
WooCommerce Subscriptions – Requirements & Scheduled Events: https://woocommerce.com/document/subscriptions/requirements/ and https://woocommerce.com/document/subscriptions/develop/complete-guide-to-scheduled-events-with-subscriptions/
-
Practical guides: SpinupWP on Understanding WP-Cron, various hosting docs on replacing with real cron jobs.
-
Plugin for inspection: WP Crontrol (free on WordPress.org).
This makes a solid, actionable Plugin Pulse segment—real-world dev consensus meeting practical site-building advice. Plenty of room to expand with listener setups, common plugin cron pitfalls, or your own experiences with scheduled events in PeTracker or other tools. Let me know how you want to shape the final notes or add visuals!
Plugin Reviews
Plugin 1
Zero Blocks Given
The Lowdown:
Most WooCommerce stores ship 80-150 KB of block CSS and JS that the store never actually renders. The WC
BlockPatterns scanner is the one that bugs me most – it hits the filesystem on every request to scan a directory of pattern templates you don’t use. Then add core WP global-styles, wp-block-library and font-faces on top, and you’re loading a Gutenberg frontend you probably switched off a long time ago.Zero Blocks Given turns it off at the source, through WooCommerce’s own dependency injection container. No CSS dequeue band-aid, no UI checkboxes, no PRO upsell. One constant in
wp-config.php, pick a tier, done.Here’s the thing – WC registers its block hooks as closures wrapping instance methods on container-managed objects. So you can’t
remove_action() them by string. You have to fetch the same instance back from the DI container and pass it in as the callable. That’s what this does:$bp = \Automattic\WooCommerce\Blocks\Package::container()->get( BlockPatterns::class );
remove_action( ‘init’, [ $bp, ‘register_block_patterns’ ] );
The DI-container path is the one that survives WC upgrades cleanly. String-callback matching and dequeue tricks tend to drift every release, so I went with the container.
Four modes. Three ways to set them.
Mode What it turns off When to use it
patterns WC BlockPatterns directory scanner only Block-based Cart/Checkout – keeps all blocks rendering, just skips the file-I/O scanblocks patterns + BlockTypesController + Notices styles + wc-blocks-style handle Classic-shortcode WC storesall blocks + WP global-styles pipeline + theme.json + font-faces + head <style> strip Sites with no Gutenberg frontend at allnuclear all + unregister_block_type() for every core block Page-builder sites – strips the editor inserter cleanDefault is
all. Set the mode you want with any of these:-
The
<dialog>settings – click the Settings link on the Plugins screen. Native HTML dialog, four radios, save. No menu items, nothing else added to your admin. -
A constant in
wp-config.php–define( 'ZEROBLG_MODE', 'patterns' );. This wins over the dialog. Good devops escape hatch. -
A filter in a theme or mu-plugin –
add_filter( 'zeroblg/mode', fn() => 'blocks' );. Used when neither the constant nor the dialog set a value.
Resolution order: constant, then settings, then filter, then
all. An invalid value at any step just falls through to the next.Rating: 5 Dragons 🐉🐉🐉🐉🐉
Some SEO Stuff:
AI Mode over views
More on google official guide on AI overviews
What’s One SEO Strategy That Still Works Surprisingly Well in 2026?
AI Overviews, AI Mode & What Still Works in 2026 SEO
The intersection of Google’s AI Overviews / AI Mode and broader AI chatbot citations (ChatGPT, etc.) continues to reshape search visibility in 2026. Recent data from Ahrefs (analyzing over 1 billion data points across 14 studies) and Google’s own guidance, alongside practitioner discussions, paint a consistent picture: technical tweaks alone deliver diminishing returns, while original, non-replicable content and foundational SEO practices remain powerful. AI search operates as a somewhat separate discovery layer with its own citation logic, often reducing clicks to traditional #1 organic results by as much as 58% (up significantly in recent months).
Key takeaways from the Ahrefs analysis include the dominance of “Best X” listicle-style content in AI citations (nearly 44% for ChatGPT), the outsized role of non-influenceable sources like Wikipedia and homepages (over 50% of top citations), and the limited impact of schema markup on AI visibility. YouTube brand mentions showed the strongest correlation with AI brand visibility across both Google and OpenAI products. Notably, many highly cited pages have zero traditional Google organic visibility, highlighting a parallel discovery path. AI Overviews appear almost exclusively on informational queries, and while Google’s AI Mode and Overviews often reach similar conclusions, they cite largely different sources. Google’s official documentation on AI answers reinforces this by explicitly downplaying hype around llms.txt files, over-optimization of Schema.org, and chunking techniques—pushing instead for “non-commodity” content: original measurements, real tests, firsthand experience, and unique insights that models cannot easily generate themselves. Generic, AI-replicable summaries get ignored.
Community threads on enduring strategies echo these points while grounding them in practical WP realities. Updating existing content (rather than constantly publishing new posts), natural internal linking, technical SEO fundamentals (speed, crawlability, indexing), and building topical authority through pillar/cluster structures continue to deliver results. Quality and E-E-A-T signals matter more than volume, especially as AI-generated content floods informational niches. Brand mentions across reviews, directories, news sites, and YouTube provide additional lift that AI systems appear to value. Many report that core on-page and technical work still accounts for the majority of gains, with AI traffic remaining a smaller but growing (and harder-to-attribute) channel.
Summary for the Show:
In 2026, SEO success under AI Overviews and chatbots rewards substance over optimization theater. “Best of” listicles and original, experience-driven content (real data, tests, client patterns, lived insights) get cited far more reliably than generic or self-promotional material. Google itself calls out that llms.txt, heavy schema focus, and chunking are not magic bullets. Meanwhile, timeless practices—regularly updating content, strong internal linking, technical health, and topical structure—remain surprisingly effective. YouTube and broader brand signals add meaningful correlation. For WordPress site owners and plugin developers, this means prioritizing content that only
you can create, maintaining site foundations, and viewing AI visibility as a complementary layer rather than a replacement for traditional search. Plugins that help audit for uniqueness, surface update opportunities, or support clean technical SEO continue to provide real value; llms.txt support is useful context but not a standalone strategy.
Further Links & Resources:
-
Tim Soulo / Ahrefs AI search optimization thread & linked studies: https://x.com/timsoulo/status/2061796432534003866 (includes direct links to 14 analyses on AI Overviews vs. Mode, brand visibility, listicles, schema impact, etc.).
-
Reddit discussion on Google’s official AI guidance: https://www.reddit.com/r/SEO_Xpert/comments/1u1yac0/google_published_its_official_guide_on_getting/
-
Reddit thread on strategies still working in 2026: https://www.reddit.com/r/SEO_Xpert/comments/1u6cbze/whats_one_seo_strategy_that_still_works/
-
Google’s documentation on appearing in AI answers (referenced across discussions).
-
Related WP context: Developer resources on llms.txt and content structuring for AI agents.
This segment ties current data, official guidance, and on-the-ground tactics into actionable advice—perfect for Plugin Pulse listeners running WP sites or building SEO-related tools. It also connects naturally to ongoing conversations around AI readiness for content and plugins. Let me know if you want to expand any section, add listener questions, or pull in more WP-specific examples!
Some SEO info for the new LLMs.txt standard:
Specific llms.txt Implementation Tactics for WordPress Sites in 2026
Building on our recent discussion of AI Overviews, AI Mode, and enduring SEO strategies, llms.txt is an emerging (proposed) standard file designed as a “welcome mat” for large language models. Placed at your domain root (e.g., https://yourdomain.com/llms.txt), it uses simple Markdown to provide a curated index of your site’s most important public URLs, grouped by section, with optional titles, short descriptions, and context. Unlike robots.txt (which controls access/crawling with Allow/Disallow directives), llms.txt focuses on curation and comprehension — helping AI tools like ChatGPT, Claude, Perplexity, and others quickly understand structure, priorities, and key content without sifting through everything. It’s additive rather than restrictive and pairs well with strong sitemaps and technical foundations.
Practical Implementation Tactics for WP Sites:
-
Plugin-Based (Easiest & Recommended for Most Users):
-
Install dedicated plugins like WPProAtoZ LLMs.txt for WP auto-generates from published posts/pages, respects noindex/nofollow, pulls titles/descriptions). https://github.com/Ahkonsu/wpproatoz-llms-txt-for-wp
-
Major SEO suites now include built-in generators: AIOSEO, Yoast SEO, SEOPress PRO offer one-click or admin textarea editing with dynamic placeholders (site name, latest posts, search URL, etc.).
-
These tools handle virtual generation via rewrites (no manual root file needed in many cases) and keep the file updated automatically.
-
-
Manual or Custom PHP Approach (More Control):
-
Create a plain Markdown file with sections like # Site Overview, ## Key Pages, ## Documentation, ## Products/Services. Use H2 headers for grouping, bullet lists with [Title](URL): Brief description.
-
For dynamic WP sites, add a custom PHP snippet or mu-plugin that generates the file on-the-fly (leveraging WP rewrites or a physical file updated via cron/hook). Include business-specific details like hours, services, or unique insights.
-
Advanced: Offer llms-full.txt variants with richer flattened content or Markdown versions of key pages for deeper context. Keep files human-readable and regularly refreshed.
-
-
Best Practices & Optimization Tactics:
-
Prioritize high-value, non-replicable content (original research, case studies, firsthand experience) — align with Google’s emphasis on substance over hacks.
-
Use clear, consistent structure; start with brand/site description; limit to essential links to avoid overwhelming context windows.
-
Combine with strong internal linking, updated pillar content, schema, and fast crawlable architecture. Test by validating the file and checking AI tool outputs.
-
Monitor impact via logs or AI citation tracking; update when launching new features (e.g., https://PeTrackers.com dashboards or plugin docs).
-
Note: Google’s official AI guide downplays llms.txt for their Overviews/AI Mode (not a ranking factor), but it can still aid other LLMs and agentic tools. Treat it as complementary to proven SEO, not a replacement.
-
Summary for the Show:
llms.txt implementation in WordPress is straightforward in 2026 thanks to mature plugins and SEO suite integrations — no heavy coding required for solid results. Focus on curation of your best, unique content with clean Markdown structure, dynamic generation for freshness, and pairing it with timeless tactics like content updates and technical health. While not a magic bullet for Google AI features, it provides a proactive signal for broader LLM visibility and future agentic search. For plugin developers and site builders, adding llms.txt support (auto-generation, customization, validation) is a smart, low-effort feature that positions tools as AI-ready. Listeners should experiment on a staging site, measure any shifts in AI citations, and view this as one tool in a broader content + SEO strategy.
Further Links & Resources:
-
Official proposal & spec: https://llmstxt.org/
-
WordPress Plugin: Website LLMs.txt on WordPress.org.
-
Yoast, AIOSEO, and SEOPress llms.txt guides.
-
Examples from major sites (Anthropic, Stripe, etc.) via searches on llmstxt.studio or similar validators.
-
Google AI Optimization Guide for balanced perspective.
V for V for the show
Make mention here about the “Revival of The Tavern at the Oasis” Podcast fid the episodes here https://theroguesoasis.com/tavern-talk-podcast-show/ or find us in your favourite podcast app.
If you get any value out of this show then donate that value back to the show. You can do so through time, talent, or treasure – or all 3!! – through our website wppluginsatoz.com.
Click on the ‘Treasure Donations’ link on the left-hand menu, or on the ‘Time, or Talent‘ pages to find out more!
Sign up for newsletter https://wppluginsatoz.com/news
Tip of The Day:
Best ways to promote your WP Plugin
Best Ways to Promote Your WordPress Plugin in 2026
The WordPress plugin directory grows daily, making visibility a real challenge even for solid, problem-solving tools. A fresh discussion in r/WordPressPlugins highlights exactly this: with so much noise, how do you generate genuine word-of-mouth and reach the right users? Key community suggestions include reaching out to smaller WordPress-focused YouTube channels (under ~20k subscribers) for honest reviews and demos — these creators are often more approachable via email in their About sections and deliver highly targeted exposure.
Beyond that, proven tactics in 2026 blend organic community building, content marketing, and strategic partnerships. Strong options include consistent blogging and SEO-optimized “how-to” content around your plugin’s use cases, guest posting or reviews on established WP sites, active participation in forums like Reddit’s r/Wordpress and r/WordpressPlugins, and leveraging social proof through case studies or user testimonials. YouTube remains powerful for demos, while email lists and affiliate programs turn happy users into promoters. Paid routes like targeted Facebook/Google ads or sponsored newsletter spots can accelerate reach when paired with a polished landing page and free tier or lite version for easy trials. Don’t overlook directory optimization: compelling descriptions, screenshots, video embeds, and regular updates boost organic discovery in the .org repo itself.
A standout channel for plugin promotion continues to be WP Plugins A to Z (and its Plugin Pulse segments). With 16+ years and 1000+ episodes, the show delivers honest, in-depth coverage of plugins — from quick spotlights to full author interviews and practical demos. Submitting your plugin for consideration can lead to dedicated airtime, show notes, and exposure to a dedicated audience of site builders, developers, and agency owners. The podcast’s unplugged style and focus on real-world utility make it an authentic promotional avenue that aligns perfectly with community-driven growth.
Summary for the Show:
Promoting a WP plugin in 2026 rewards consistency, authenticity, and multi-channel execution over quick hacks. Start with YouTube outreach to niche creators, optimize your .org listing and website for conversions, build community through forums and content, and layer in strategic partnerships like podcast features. WP Plugins A to Z offers a trusted platform for reaching engaged listeners — whether through a standard review, author interview, or Plugin Pulse deep dive. Combine this with SEO fundamentals, user-generated proof, and smart paid amplification for sustainable growth. The goal isn’t just downloads; it’s building lasting relationships and word-of-mouth that compounds over time.
Further Links & Resources:
-
WP Plugins A to Z submission / feature info: https://wppluginsatoz.com/ (reach out via site or podcast channels).
-
Classic guides: Freemius list of high-DA promo sites, plugin marketing case studies.
-
Tools: RafflePress for giveaways, affiliate plugins like AffiliateWP to incentivize shares.
This segment gives listeners practical, battle-tested steps while highlighting the value of shows like WP Plugins A to Z. Great tie-in to our earlier SEO and llms.txt conversations — promotion starts with discoverability.
Upcoming Interviews and Available times:
Reminder that we have more interviews coming up in the coming weeks with more developers and community members https://wppluginsatoz.com/book-an-interview-on-wp-plugins-a-to-z-podcast/
Upcoming Interviews: Marcus Burnette on July 27
Available interview dates: July 13th, Aug 10th & 24th 2026.
Other Shows and places to get WP Info & Training
The WP Builds Podcast
WP Roads
WP-Tonic
Worlds Worst Web Developer
WP Mayor
wp Minute
The WP Week newsletter
Kitchensink WP
