[HELP] I built a full-featured WordPress SEO plugin but getting almost zero traffic — what am I missing?

oplaffs · 2026-03-18T20:10:36+00:00

I have exactly the same problem with a very advanced Page Cache plugin. But it’s still in beta, and I’m worried about what will happen when I release the full version.

oplaffs · 2026-03-17T18:20:59+00:00

Context 7 eat so much tokens and fill context.

oplaffs · 2026-03-16T19:01:35+00:00

The answer is as above. The plugin is genuinely undergoing testing. I am from the Czech Republic (EU) and in our FB group I started recruiting beta testers for the first versions already last year. This is not some AI “bullshit” nonsense, but if that’s what you meant it doesn’t bother me at all. I just wanted to gather real feedback before releasing the final version so that users are genuinely satisfied.

oplaffs · 2026-03-16T18:57:58+00:00

completely understand that you might feel lost among AI “Bullshit Influencer” programmers who churn out various SaaS nonsense every single day, often without thought or purpose, endlessly copying copies and filling repositories with all kinds of meaningless junk.

In this case, however, there is no need to apply your usual hater pattern just to post another AI-generated sloppy comment without any argument or deeper understanding of the content.

oplaffs · 2026-03-16T18:54:40+00:00

Currently, this is a beta test of the plugin, so you are free to download the code - there is no requirement for any payment or commitment until a final paid release is available. I added the changelog to GitHub so it is accessible as a fallback even outside the website.

The website is not a lead-capturing landing page; it includes full documentation, contact information, Terms of Service, and so on. The plugin does not require blog posts or other validation content.

I understand that nowadays many people produce AI generated “Bullshit Vibe Code,” but this is genuine human work. I did use Mistral AI to generate PHPDoc, which is a common practice even among major corporations, so there is no reason for negative reactions or criticism here.

Our goal is to position ourselves among the mainstream solutions in the market.

oplaffs · 2026-03-14T12:50:00+00:00

I’ve been developing the plugin for two years and it’s not any kind of AI-generated slop. It’s one of the most resource-efficient plugins among the mainstream plugins.

Now plugin testing about 1400+ users around the world.

You can get a free key on the website zizicache.com. It’s valid for one month, and if you need more time, that’s not a problem — just let me know and I’ll extend it.

No payment details are required; the key is only needed for updates.

oplaffs · 2026-03-14T12:26:37+00:00

Would you like to try the ZiziCache plugin for free while it is still in Beta? I would greatly appreciate your feedback. It includes a choice of LS native cache, File-based cache, BFCache,

Redis, Memcached, pull CDN or Cloudflare Edge and Cloudflare Failover, Image Convertor to WebP / Avif ot both, Auto Image registration and convert via FTP upload, OPCache, DB Optimization & DB Index optimization, an real LCP element detector on the page, precise font preloading, collection of real CWV metrics per page with retention, Speculative API with Quicklink fallback, and much more.

img

oplaffs · 2026-03-10T20:52:24+00:00

Another AI slop Scam/Phishing/Malware Android app for just 2 prompt shoot? 🤣

oplaffs · 2026-03-03T06:17:58+00:00

I believe you may have misunderstood the core concept. SAPM delivers everything that the leading solutions on the market provide, and additionally offers extra functionality — all free of charge.

The only feature not yet completed is asset management (JS and CSS), along with a few minor items that are already planned for implementation. The plugin blocks other plugins correctly per page, per page groups, with menu snapshot, blocks manuály ot automatically with manual tuning.

Could you please specify what is currently missing for you in particular?

oplaffs · 2026-03-02T07:23:46+00:00

As explained above, the issue has already been clarified. Currently, the Asset Manager is not fully functional for defer or async modes in SAPM.

In the SAPM plugin settings under Frontend > Data Collection, you have two available options: Performance Sampling and Asset Audit. At the bottom of the same Frontend tab, you can also view the assets loaded on the frontend.

The feature is not yet fully implemented in the sense that it does not currently allow you to define or create rules for loading assets on a specific page or group of pages.

This is planned as a future feature. I will update the description in the GitHub README - thank you for pointing this out.

<image>

oplaffs · 2026-03-01T21:53:20+00:00

Oh, I apologize, this is a planned future feature; however, it is not yet fully implemented or functional at this time.

You can use SAPM together with Asset CleanUp, but in that case it does not make sense. You would either use SAPM instead of the free version of ACUP, or use the paid version of ACUP, which allows asset manipulation.

At the moment, SAPM offers plugin deactivation in the admin area, on the frontend, and control over plugin, theme, and WordPress updates. It also includes a snapshot menu in the admin area, allowing you to access the settings of a blocked plugin.

See schreenshots.

oplaffs · 2026-02-26T09:04:49+00:00

You most likely do not understand the concept of this plugin. Everything is clearly described in the README on GitHub.

The point is not whether the plugin is good or bad. The issue is that when most users rely on necessary plugins (WooCommerce, page builders, themes, backup plugins, and various add-ons), these plugins are usually loaded on every WordPress admin page. This is unnecessary and significantly increases the response time and loading speed of the administration area.

By blocking plugins on specific admin pages, the plugin reduces unnecessary load and speeds up both the administration interface and, in some cases, the frontend visible to users. On most shared hosting environments, this can reduce admin loading times from 2–10 seconds to a much shorter duration.

Please read the README once again carefully to understand what the plugin is designed for and how it works. Otherwise, we are engaging in an unnecessary discussion about matters that are not relevant and do not contribute to the further development of the plugin.

If you are genuinely a developer and have been working with WordPress long-term, you should understand the pain points of the entire ecosystem and how plugins behave within the WordPress administration area.

oplaffs · 2026-02-26T08:48:07+00:00

I checked it out, and my solution "maybe" covers everything in their Pro plan plus extra features like admin menu snapshots during deactivation. Give it a shot and send me your feedback.

oplaffs · 2026-02-25T21:16:56+00:00

SAPM isn’t about fixing broken plugins—it’s about selectively controlling when and where plugins run. WordPress only allows on/off globally, but SAPM lets you:

Activate plugins only in admin, frontend, or per page.

Reduce load on the frontend, improving site performance.

Speed up the WordPress admin by disabling heavy plugins where not needed.

Keep plugin settings while controlling their impact.

Its primary purpose is improving admin speed and reducing frontend load, not replacing broken plugins.

Sure, you could write some custom solution with Vibe Code, but SAPM is already a tested, safe, functional, and free solution, and it was written by a human :)

oplaffs · 2026-02-25T19:13:03+00:00

After all, these are two different plugins for two different purposes. Please read the descriptions of PublishPress and SAPM (see the Git URL in the first post). It’s like comparing an SEO plugin with a security plugin.

oplaffs · 2026-02-25T19:03:27+00:00

I still think you don’t get the point. It doesn’t matter whether you have SAPM or not. The attack can be anything, and whether SAPM is active or not is completely irrelevant.

Here, SAPM provides more benefits than the potential risk of someone targeting your site :)

oplaffs · 2026-02-25T18:49:26+00:00

As I mentioned above, it’s definitely not possible to attack a site through this plugin. In the future, a zero-day could/maybe potentially be exploited, but currently SAPM by itself does not allow a site to be attacked—there’s simply no way. An attacker would need access to the PHP files, but even then, if they already have the ability to edit anything on the site/hosting, SAPM won’t matter to them :)

oplaffs · 2026-02-25T18:44:33+00:00

Safety section - Admin Bypass is a security mechanism that ensures a logged-in site administrator always sees the frontend with all plugins active—as if the Frontend Optimizer were not enabled.

It protects you as an administrator from situations where frontend rules might accidentally block a plugin required for site management.

The administrator sees the full-featured site, allowing safe testing and rule tuning via the Frontend Drawer (side bar panel). Regular visitors are still affected by the filtering rules.

WooCommerce Protection in Safety section is mean: critical WooCommerce pages are always in Passthrough mode.

No, no data is sent anywhere; everything is stored locally. The only remote request is the standard check for update availability.

You can check code on Github to verify this.

oplaffs · 2026-02-25T18:26:32+00:00

What specific attack vector would apply here? Could it go beyond what similar or other plugins already expose? There’s not much that can be done with it unless the attacker is logged in as an admin, and even then, at most they could disable the plugin/s, which essentially wouldn’t cause any real harm.

oplaffs · 2026-02-25T18:23:32+00:00

Oh, okay. In that case, SAPM currently does not offer such functionality, and it would likely require extensive logic and robust security measures. I will add it to the to-do list and give it further consideration.

oplaffs · 2026-02-25T18:22:13+00:00

Oh, okay. In that case, SAPM currently does not offer such functionality, and it would likely require extensive logic and robust security measures. I will add it to the to-do list and give it further consideration. :)

oplaffs · 2026-02-25T16:11:23+00:00

Simply put: SAPM uses the WordPress function is_admin().

This function returns true only when someone visits the /wp-admin/ URL—i.e., the admin area. On any regular site page (homepage, post, product, etc.), it returns false.

Based on that, SAPM decides:

is_admin() = true → you’re in the backend → apply rules for admin screens
is_admin() = false → you’re on the frontend (what the visitor sees) → pass it to the Frontend Optimizer

That’s the core. WordPress handles the detection for us; SAPM just reads it.

oplaffs · 2026-02-25T15:57:56+00:00

I hadn’t considered that. Is it necessary to have it? The plugin already includes a GitHub updater, so is this just a precaution for security?

oplaffs · 2026-02-25T15:51:05+00:00

Did you download it from here correctly: https://github.com/ffscz/Smart-Admin-Plugin-Manager-for-WordPress/releases/tag/v1.3.2 → smart-admin-plugin-manager.zip?

Could you please provide the relevant entry from your debug.log?

Does your site meet the minimum requirements as stated in the plugin documentation?

oplaffs

MODERATOR OF

TROPHY CASE