# WordPress Plugin Review Pain Packet Proof-of-process artifact for WordPress plugin vendors with public support or review friction. ## What this is This is a public-signal triage format for plugin vendors. It reviews WordPress.org plugin pages, public support threads, reviews, docs and vendor-visible surfaces, then groups recurring friction into a practical support/product/docs handoff. It is not a claim that any plugin is currently broken. It is not private plugin access, merchant testing, a vulnerability report, review manipulation, or legal advice. ## Sample target shape - Plugin type: WooCommerce product feed / shopping feed plugin - Commercial surface: free plugin with paid/pro upgrade path - Public signal source: WordPress.org plugin page, support forum, reviews and public vendor docs - Useful buyer: founder, product lead, support lead, growth lead, or operator responsible for support load and upgrade trust ## Sample public pain buckets | Priority | Public theme | Why it matters | Suggested packet output | | --- | --- | --- | --- | | `high` | Empty or stuck feed generation | Can create merchant support urgency and ad-channel friction | Diagnostic macro, repro/context questions, docs gap | | `high` | Google taxonomy or category mapping | Can block Merchant Center readiness and confuse setup | Mapping checklist, docs cluster, support routing note | | `medium` | GTIN, sale price, URL and validation details | Can become repeated support load even when core plugin is strong | Merchant Center readiness checklist | | `medium` | Scheduler, refresh and duplicate feed symptoms | Can point to recurring environment/setup patterns | Release-risk watchpoint and triage script questions | ## What the buyer receives - Public review/support taxonomy. - Repeated pain clusters by theme. - Likely context and repro questions. - Docs/help-center gaps. - Support macro suggestions. - Product/support action queue. - Release and changelog watchpoints. - What not to overreact to from public complaints. ## Input needed - WordPress.org plugin URL or slug. - Vendor docs/help center/support URLs. - Optional known product priorities or release areas. ## Fixed-scope price test - USD 149 for a one-plugin public pain packet. - USD 299 for one plugin plus comparator/competitor read. - USD 499+ for a small vendor portfolio scan. ## Guardrails - Public data only unless the vendor provides private context. - No contact with plugin users, reviewers, forum posters, or merchants. - No testing plugin flows, stores, payment flows, APIs, or merchant sites without vendor authorization. - No claim that public complaints prove current production defects. - No fake reviews, no review suppression, no spam. ## Why this exists Plugin vendors do not only lose time answering repeated tickets. Public support and review friction can affect installs, paid upgrades, merchant confidence, docs quality and release prioritization. This packet turns visible public signal into a clean first-pass action map without needing private data first.