WordPress.org

WordPress.org is publishing and optimizing a plugin/theme in the official WordPress.org catalog (wordpress.org/plugins | /themes): checking compliance with strict guidelines (code, security, GPL-compatible license, absence of paid content in the .org repository plugin itself, theme requirements), preparing the readme/listing (title, description, tags/keys, screenshots, banner/icon), passing the manual review by the WordPress.org team (can be lengthy/iterative), optimizing the page for repository search, recommendations on the freemium model (a free core in .org + paid extensions outside the repository), working with rating/genuine reviews and support, tracking rules. The work: guidelines/GPL compliance, listing, review, optimization. Honestly about 'a ready plugin/theme and GPL are needed', this is key and fundamental: WordPress.org is an open-source repository; for publishing a ready product compliant with the guidelines and the GPL license is needed (or this is separate development, not part of the listing). 'We will simply list you' without a ready product = a lie. Honestly about 'the repository is free': you cannot sell in the .org repository itself — the products are free; monetization is only via freemium (paid features/support outside the repository), and this must be set up correctly without violating the rules. Honestly about 'strict manual review': the WordPress.org team manually checks code/security/compliance; the review can be lengthy and iterative, they may reject/require fixes — the decision and timelines are beyond our control; 'we guarantee approval' = a lie. Honestly about 'a listing ≠ installs': optimization increases visibility/conversion, but installs depend on the usefulness of the plugin/theme, demand, competition, reviews — not on the fact of publishing. Honestly about 'no inflation': installs/reviews are only genuine. Honestly about the effect: it prepares and publishes a ready plugin/theme in WordPress.org (guidelines/GPL compliance, review support, optimization, freemium model, analytics, genuine reviews), increasing the chances of visibility/installs, but a ready product is needed (development separate); the repository is free (monetization — freemium outside .org); the review is strict/lengthy, can reject; a listing ≠ installs; only genuine reviews. Honestly about access: a ready plugin/theme (or development), GPL/guidelines compliance are needed. An important boundary: this is publishing in WordPress.org (not plugin/theme development); Chrome Web Store — 605; Figma Community — 609. The base price starts from 25,000 ₽ for preparation/review/optimization (plugin/theme development — separate).

• You have a plugin/theme but it is unclear how to publish in WordPress.org (guidelines, GPL, manual review, readme/listing).
• A misconception that you can 'list' without a ready product or that you can sell in the .org repository.
• Not knowing about the strict lengthy manual review (rejection/fixes) and about the GPL license.
• Expecting installs from the fact of publishing; a desire to inflate installs/reviews.

• Checking plugin/theme compliance with guidelines and the GPL license, a security/code audit per requirements
• Preparing the readme/listing (title/description/tags/screenshots/banner/icon)
• Supporting the WordPress.org team's manual review, help with fixes per feedback
• Optimizing the page for repository search, recommendations on the freemium model (monetization outside .org)
• An honest assessment: whether the product is ready/GPL-compliant and what depends on usefulness/demand
• Honest boundaries (a ready product+GPL is needed — development separate; the repository is free, monetization freemium outside .org; the review is strict/lengthy, can reject; a listing ≠ installs; only genuine reviews)
• Documentation and handover
• Review with you

• A prepared listing + (if review is passed) a published plugin/theme in WordPress.org + optimization/analytics
• Guidelines/GPL compliance, a set-up freemium model and increased chances of visibility/installs
• An honest assessment: whether the product is ready and what depends on usefulness/demand/competition (or what to fix)
• Honest boundaries (a ready product+GPL is needed; approval is not guaranteed; a listing ≠ installs; only genuine reviews)

• We check plugin/theme compliance with guidelines/GPL (or indicate what to fix/develop)
• We prepare the readme/listing, support the manual review, help with fixes; set up freemium
• We optimize the page/analytics; we honestly set boundaries (the review is strict; a listing ≠ installs) and hand over

• Can you just list the plugin in WordPress.org?

  Only with a ready product, honestly: this is an open-source repository, and for publishing a ready plugin/theme compliant with the guidelines and the GPL license is needed. If there is no product or it is non-compliant — this is separate development/fixes. Plus you cannot sell in the .org repository itself (only free + freemium outside the repository). We will honestly check and say what is needed.

• Do you guarantee approval and installs?

  No, honestly: the WordPress.org team manually and strictly checks code/security/compliance; the review can be lengthy and iterative, they may reject or require fixes — the decision and timelines are beyond our control. And a listing increases visibility, but installs depend on the product's usefulness, demand, competition. We do not give approval/install guarantees.

• How then to earn on a plugin from .org?

  Via freemium, honestly: in the WordPress.org repository itself the products are free, you cannot sell there. Monetization is a free core in .org + paid features/support/a PRO version outside the repository (on your own site). We will honestly help set up this model per the rules, without violations. We do not inflate installs/reviews.