Why Your WordPress Plugin Has 10 Installs
🔗 **Source:** [Why Your WordPress Plugin Has 10 Installs](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> [!note]+ Document Notes
> tags: [WordPress, Plugins, Growth]
> author: [MISSING]
> source: iconick.io
> reference: [https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/]
> date created:
>
> # 🏷️ Title: Why Your WordPress Plugin Has 10 Installs (And How to Fix It)
>
<!-- deep-read:sections start -->
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- The article explains WordPress.org plugin search ranking.
- It matters because installs depend on visibility, not only quality.
- Stakeholders: plugin developers, users, reviewers, support teams.
- Risks: over-optimizing titles, neglected support, stale releases.
- Bottom line: optimize findability, support fast, and ask for reviews.
## 📖 Main Content
- Rankings occur in two phases: match, then re-rank with signals.
- Match checks seven readme fields, with titles weighted most.
- Re-rank uses installs, ratings, support resolution, freshness, compatibility.
- Early installs and first reviews move rankings quickly.
- Cold start penalties exist but can be offset with process.
### 🗒️ Notes
### [H1] Ranking uses two-phase match and quality signals
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed .
> “They use a two-phase system that’s actually pretty clever once you understand it.”
Two-phase: text match, then quality-based re-rank. Source outlines both.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #xref #articleseed ID:rw_[MISSING]
### [H2] Seven readme fields drive text matching
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “WordPress scans seven specific fields in your readme.txt file: ...”
Ensure queries’ words appear in title, excerpt, description, tags, slug, authors.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #xref ID:rw_[MISSING]
### [H3] Titles carry outsized ranking weight
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Your plugin title alone has more weight than your description, tags, and everything else combined.”
Use exact search phrases in titles to increase discoverability.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #articleseed ID:rw_[MISSING]
### [H4] Ranking formula mixes installs, reviews, support, freshness
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Score = text_relevance × 0.375 × log2(active_installs) × 0.25 × log2(support_threads_resolved) × 0.25 × √(rating) × freshness_decay × compatibility_decay”
Signals are logarithmic and decay-based; early gains matter more.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #xref ID:rw_[MISSING]
### [H5] New plugins face default rating and support penalties
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “plugins with zero reviews default to 2.5 stars… New plugins default to 50% resolution score.”
Overcome early penalties by earning reviews and resolving threads.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #xref ID:rw_[MISSING]
### [H6] Early installs and first reviews shift rankings most
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Each early install gives you a disproportionate boost… Get even one 5-star review and you immediately jump higher…”
Prioritize first 1,000 installs and first reviews.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #articleseed ID:rw_[MISSING]
### [H7] Support resolution improves ranking and creates content
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Mark threads resolved… support responses are indexed by Google and WordPress.org search.”
Respond thoroughly, resolve, and build searchable answers.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #xref ID:rw_[MISSING]
### [H8] Regular updates prevent freshness decay
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Update recency penalizes plugins that haven’t been updated in 180+ days.”
Ship small updates and keep “Tested up to” current.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #articleseed ID:rw_[MISSING]
### [H9] Reviews are earned via ethical, timely asks
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “25% conversion rates—one review for every four satisfied users you help and then politely ask.”
Ask after solving issues or at meaningful milestones.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #articleseed #share ID:rw_[MISSING]
### [H10] One-week optimization plan jumpstarts growth
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Day 1: Research… Day 2: Expand… Day 3: Choose 5 tags… Day 4: Update… Day 5: Support… Day 6: Translations… Day 7: Reminders…”
Timebox seven days for foundational improvements.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #articleseed ID:rw_[MISSING]
## 📚 References
- [Plugin Directory Search – WordPress.org documentation, 2017 formula](
https://make.wordpress.org/meta/2017/01/26/near-term-changes-to-the-plugin-directory/)
- [Plugin Reviewer Handbook](https://developer.wordpress.org/plugins/wordpress-org/)
- [Support Guidelines](https://make.wordpress.org/support/handbook/)
- [Internationalization (i18n)](https://developer.wordpress.org/plugins/internationalization/)
- [Popup Maker case discussions](
https://wordpress.org/support/plugin/popup-maker/) // May not detail metrics; forum threads are public.
## 🗣️ Paraphrase
- WordPress ranks plugins by text match, then by quality.
- You can improve ranking by titles, docs, support, and updates.
## 📰 Newsletter
- Many plugins stall at 10 installs due to ranking basics.
- Fix titles, expand docs, pick five strong tags, and update.
- Respond fast on support and ask for reviews after wins.
- Try the seven-day plan to move from invisible to findable.
- Learn more from the WordPress.org directory guidance.
## ✅ Action Items
#### DevRel
- Publish a “write better plugin titles” guide — context/iconick.io #articleseed
- Run office hours on support resolution tactics — context/iconick.io #share
- Create example readme templates with keyword coverage — context/iconick.io #xref
- Track a before/after search visibility metric — context/iconick.io #articleseed
- Record a demo on milestone-based review prompts — context/iconick.io #share
#### OSPO
- Define contribution response SLAs for support queues — context/iconick.io #xref
- Add update cadence to internal compliance checks — context/iconick.io #addendum
- Establish translation priorities by locale size — context/iconick.io #xref
#### Community
- Host a readme optimization clinic for maintainers — context/iconick.io #share
- Pair reviewers with new plugin authors for 30 days — context/iconick.io #articleseed
- Publish review-ask ethics guidelines — context/iconick.io #addendum
#### WordPress
- Plugins: advocate clearer weighting docs and examples — context/make.wordpress.org #xref
- Meta: expose search analytics to maintainers — context/make.wordpress.org #articleseed
- Training: add course on directory SEO — context/learn.wordpress.org #articleseed
- Support: promote “resolve properly” campaigns — context/make.wordpress.org #share
#### The WPOCC
- Programs: microgrants for documentation sprints — context/iconick.io #articleseed
- Projects: support playbooks and review-ask scripts — context/iconick.io #share
- Funding experiments: stipends for translation pushes — context/iconick.io #articleseed
### FAIR
- Policies: publish transparent review-ask norms — context/iconick.io #addendum
- Artifacts: readme title checklist and scorecard — context/iconick.io #product
## 🧪 Hypotheses
- Title exact-match increases impressions for target terms.
- First five tags aligned to user queries improve clicks.
- Resolving >80% support threads boosts ranking within four weeks.
- One 5-star review raises CTR more than 200 new installs.
- 90-day update cadence prevents rank decay and preserves CTR.
### 📊 Methodology
- A/B test titles across sandbox listings where possible.
- Track impression/clicks via .org analytics if available.
- Time-series analysis of rank vs. support resolution rate.
- Cohort study for review timing prompts vs. baseline.
- Interrupted time series on updates affecting rank.
### ❓ Questions
- How strong is freshness decay after 180 days?
- Do locale translations affect non-locale rankings?
- What CTR lift follows the first 5-star review?
### 🔮 Future Research
- Model diminishing returns of installs vs. rating shifts.
- Build open dashboard templates for plugin metrics.
- Study ethical review prompts across plugin categories.
### 💡 Implications
- Focus on controllables to beat incumbents.
- Community support quality compounds visibility.
- Ethical asks for reviews can be standardized.
### 🧠 Learning Styles Assessment
- Reading level estimate: Flesch-Kincaid Grade ~8–9 (visual estimate).
#### 👀 Visual learners
- Present: step plan and examples referenced.
- Improve: diagrams of ranking flywheel and formula.
#### 🔊 Aural learners
- Present: none.
- Improve: 3-minute audio summary and Q&A.
#### 🗣️ Verbal learners
- Present: concrete definitions and steps.
- Improve: glossaries for directory terms.
#### 🧩 Kinesthetic learners
- Present: seven-day task list.
- Improve: checklists and templates to fill.
#### 🧠 Logical learners
- Present: formula and causal chain.
- Improve: decision trees for title/tag choices.
#### 🧑🤝🧑 Social learners
- Present: support forum practices.
- Improve: peer review clinics and pairing.
#### 🧘♀️ Solitary learners
- Present: self-paced plan.
- Improve: reflection prompts and self-checks.
#### 🌿 Naturalistic learners
- Present: none.
- Improve: lifecycle diagrams of maintenance.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: headings inferred.
- Improve: landmark roles and alt text in examples.
#### Keyboard navigation
- Present: N/A to content.
- Improve: include focus guidance in plugin UIs.
#### Contrast and readability
- Present: adequate text contrast assumed.
- Improve: specify color and spacing standards.
#### Text resizing and reflow
- Present: N/A.
- Improve: include reflow-friendly code samples.
#### Media and captions
- Present: none.
- Improve: add captions to any future videos.
#### Forms and interactions
- Present: support examples only.
- Improve: provide accessible prompt UI patterns.
#### Standards reference
- Map improvements to WCAG 2.2 AA criteria.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: mentions Spanish and German translations.
- Improve: add more locales and regional examples.
#### Inclusive language
- Present: clear and direct.
- Improve: define jargon consistently.
#### Neurodiversity support
- Present: chunked steps by day.
- Improve: consistent icons and summaries.
#### Representation
- Present: developer-focused.
- Improve: include user perspectives and diverse credits.
#### Psychological safety
- Present: respectful, encouraging framing.
- Improve: add community guidelines references.
### ✅ Logical Validity
#### Strong reasoning
- Causal chain from optimization to installs is coherent [H6].
- Weighted formula interpretation aligns with sources [H4].
#### Fallacies
- Risk: survivorship bias in case mentions. Mitigate with broader data.
#### Tone of voice
- Motivational and practical, with clear instructions.
### 🛡️ DARVO Analysis
- Deny: none observed.
- Attack: none; competitors not maligned.
- Reverse victim/offender: none; frames system neutrally.
## 🎯 Conclusion
- Treat growth as a process: match queries, prove quality, stay fresh.
- Next steps: rewrite titles, expand docs, pick tags, update, resolve, and ask.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: H3.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] Titles drive plugin discoverability
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed .
> “Your plugin title alone has more weight than your description, tags, and everything else combined.”
Use exact phrases users search. Test variations.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Early installs and reviews shift rankings
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Each early install gives you a disproportionate boost… Get even one 5-star review…”
Prioritize first wins to overcome cold start.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: H4.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Title exact-match increases impressions
- When titles mirror high-intent queries.
- Links: [[Plugin-Directory-SEO]] [[Readme-Optimization]]
#### [Z2] Support resolution improves ranking
- When resolution exceeds the default threshold.
- Links: [[Support-Ops]] [[Community-Health]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: Select one line → Refactor.
- [F1] Draft title patterns for five target keywords — context/URL #fleeting #inbox
- [F2] Build a 2,500-word readme outline — context/URL #fleeting #inbox
- [F3] Configure review-ask milestone notices — context/URL #fleeting #inbox
<!-- deep-read:sections end -->
[[3. Resources/Readwise/Full Document Contents/Articles/Why Your WordPress Plugin Has 10 Installs|Full Document Contents]]
## Document Notes
---
tags: #WordPress #Plugins #Growth
author: [MISSING]
source: iconick.io
reference: [https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/]
date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
---
# 🏷️ Title: Why Your WordPress Plugin Has 10 Installs (And How to Fix It)
## 🧭 Table of Contents
- [[#📝 Summary]]
- [[#📖 Main Content]]
- [[#🗒️ Notes]]
- [[#📚 References]]
- [[#🗣️ Paraphrase]]
- [[#📰 Newsletter]]
- [[#✅ Action Items]]
- [[#🧪 Hypotheses]]
- [[#📊 Methodology]]
- [[#❓ Questions]]
- [[#🔮 Future Research]]
- [[#💡 Implications]]
- [[#🧠 Learning Styles Assessment]]
- [[#📊 Accessibility Assessment]]
- [[#🌍 DEIB Assessment]]
- [[#✅ Logical Validity]]
- [[#🛡️ DARVO Analysis]]
- [[#🎯 Conclusion]]
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- The article explains WordPress.org plugin search ranking.
- It matters because installs depend on visibility, not only quality.
- Stakeholders: plugin developers, users, reviewers, support teams.
- Risks: over-optimizing titles, neglected support, stale releases.
- Bottom line: optimize findability, support fast, and ask for reviews.
## 📖 Main Content
- Rankings occur in two phases: match, then re-rank with signals.
- Match checks seven readme fields, with titles weighted most.
- Re-rank uses installs, ratings, support resolution, freshness, compatibility.
- Early installs and first reviews move rankings quickly.
- Cold start penalties exist but can be offset with process.
### 🗒️ Notes
### [H1] Ranking uses two-phase match and quality signals
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed {{date:YYYY-MM-DD}}.
> “They use a two-phase system that’s actually pretty clever once you understand it.”
Two-phase: text match, then quality-based re-rank. Source outlines both.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #xref #articleseed ID:rw_[MISSING]
### [H2] Seven readme fields drive text matching
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “WordPress scans seven specific fields in your readme.txt file: ...”
Ensure queries’ words appear in title, excerpt, description, tags, slug, authors.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #xref ID:rw_[MISSING]
### [H3] Titles carry outsized ranking weight
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Your plugin title alone has more weight than your description, tags, and everything else combined.”
Use exact search phrases in titles to increase discoverability.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #articleseed ID:rw_[MISSING]
### [H4] Ranking formula mixes installs, reviews, support, freshness
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Score = text_relevance × 0.375 × log2(active_installs) × 0.25 × log2(support_threads_resolved) × 0.25 × √(rating) × freshness_decay × compatibility_decay”
Signals are logarithmic and decay-based; early gains matter more.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #xref ID:rw_[MISSING]
### [H5] New plugins face default rating and support penalties
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “plugins with zero reviews default to 2.5 stars… New plugins default to 50% resolution score.”
Overcome early penalties by earning reviews and resolving threads.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #xref ID:rw_[MISSING]
### [H6] Early installs and first reviews shift rankings most
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Each early install gives you a disproportionate boost… Get even one 5-star review and you immediately jump higher…”
Prioritize first 1,000 installs and first reviews.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #articleseed ID:rw_[MISSING]
### [H7] Support resolution improves ranking and creates content
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Mark threads resolved… support responses are indexed by Google and WordPress.org search.”
Respond thoroughly, resolve, and build searchable answers.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #xref ID:rw_[MISSING]
### [H8] Regular updates prevent freshness decay
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Update recency penalizes plugins that haven’t been updated in 180+ days.”
Ship small updates and keep “Tested up to” current.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #articleseed ID:rw_[MISSING]
### [H9] Reviews are earned via ethical, timely asks
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “25% conversion rates—one review for every four satisfied users you help and then politely ask.”
Ask after solving issues or at meaningful milestones.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #articleseed #share ID:rw_[MISSING]
### [H10] One-week optimization plan jumpstarts growth
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Day 1: Research… Day 2: Expand… Day 3: Choose 5 tags… Day 4: Update… Day 5: Support… Day 6: Translations… Day 7: Reminders…”
Timebox seven days for foundational improvements.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) #articleseed ID:rw_[MISSING]
## 📚 References
- [Plugin Directory Search – WordPress.org documentation, 2017 formula](
https://make.wordpress.org/meta/2017/01/26/near-term-changes-to-the-plugin-directory/)
- [Plugin Reviewer Handbook](https://developer.wordpress.org/plugins/wordpress-org/)
- [Support Guidelines](https://make.wordpress.org/support/handbook/)
- [Internationalization (i18n)](https://developer.wordpress.org/plugins/internationalization/)
- [Popup Maker case discussions](
https://wordpress.org/support/plugin/popup-maker/) // May not detail metrics; forum threads are public.
## 🗣️ Paraphrase
- WordPress ranks plugins by text match, then by quality.
- You can improve ranking by titles, docs, support, and updates.
## 📰 Newsletter
- Many plugins stall at 10 installs due to ranking basics.
- Fix titles, expand docs, pick five strong tags, and update.
- Respond fast on support and ask for reviews after wins.
- Try the seven-day plan to move from invisible to findable.
- Learn more from the WordPress.org directory guidance.
## ✅ Action Items
#### DevRel
- Publish a “write better plugin titles” guide — context/iconick.io #articleseed
- Run office hours on support resolution tactics — context/iconick.io #share
- Create example readme templates with keyword coverage — context/iconick.io #xref
- Track a before/after search visibility metric — context/iconick.io #articleseed
- Record a demo on milestone-based review prompts — context/iconick.io #share
#### OSPO
- Define contribution response SLAs for support queues — context/iconick.io #xref
- Add update cadence to internal compliance checks — context/iconick.io #addendum
- Establish translation priorities by locale size — context/iconick.io #xref
#### Community
- Host a readme optimization clinic for maintainers — context/iconick.io #share
- Pair reviewers with new plugin authors for 30 days — context/iconick.io #articleseed
- Publish review-ask ethics guidelines — context/iconick.io #addendum
#### WordPress
- Plugins: advocate clearer weighting docs and examples — context/make.wordpress.org #xref
- Meta: expose search analytics to maintainers — context/make.wordpress.org #articleseed
- Training: add course on directory SEO — context/learn.wordpress.org #articleseed
- Support: promote “resolve properly” campaigns — context/make.wordpress.org #share
#### The WPCC
- Programs: microgrants for documentation sprints — context/iconick.io #articleseed
- Projects: support playbooks and review-ask scripts — context/iconick.io #share
- Funding experiments: stipends for translation pushes — context/iconick.io #articleseed
### FAIR
- Policies: publish transparent review-ask norms — context/iconick.io #addendum
- Artifacts: readme title checklist and scorecard — context/iconick.io #product
## 🧪 Hypotheses
- Title exact-match increases impressions for target terms.
- First five tags aligned to user queries improve clicks.
- Resolving >80% support threads boosts ranking within four weeks.
- One 5-star review raises CTR more than 200 new installs.
- 90-day update cadence prevents rank decay and preserves CTR.
### 📊 Methodology
- A/B test titles across sandbox listings where possible.
- Track impression/clicks via .org analytics if available.
- Time-series analysis of rank vs. support resolution rate.
- Cohort study for review timing prompts vs. baseline.
- Interrupted time series on updates affecting rank.
### ❓ Questions
- How strong is freshness decay after 180 days?
- Do locale translations affect non-locale rankings?
- What CTR lift follows the first 5-star review?
### 🔮 Future Research
- Model diminishing returns of installs vs. rating shifts.
- Build open dashboard templates for plugin metrics.
- Study ethical review prompts across plugin categories.
### 💡 Implications
- Focus on controllables to beat incumbents.
- Community support quality compounds visibility.
- Ethical asks for reviews can be standardized.
### 🧠 Learning Styles Assessment
- Reading level estimate: Flesch-Kincaid Grade ~8–9 (visual estimate).
#### 👀 Visual learners
- Present: step plan and examples referenced.
- Improve: diagrams of ranking flywheel and formula.
#### 🔊 Aural learners
- Present: none.
- Improve: 3-minute audio summary and Q&A.
#### 🗣️ Verbal learners
- Present: concrete definitions and steps.
- Improve: glossaries for directory terms.
#### 🧩 Kinesthetic learners
- Present: seven-day task list.
- Improve: checklists and templates to fill.
#### 🧠 Logical learners
- Present: formula and causal chain.
- Improve: decision trees for title/tag choices.
#### 🧑🤝🧑 Social learners
- Present: support forum practices.
- Improve: peer review clinics and pairing.
#### 🧘♀️ Solitary learners
- Present: self-paced plan.
- Improve: reflection prompts and self-checks.
#### 🌿 Naturalistic learners
- Present: none.
- Improve: lifecycle diagrams of maintenance.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: headings inferred.
- Improve: landmark roles and alt text in examples.
#### Keyboard navigation
- Present: N/A to content.
- Improve: include focus guidance in plugin UIs.
#### Contrast and readability
- Present: adequate text contrast assumed.
- Improve: specify color and spacing standards.
#### Text resizing and reflow
- Present: N/A.
- Improve: include reflow-friendly code samples.
#### Media and captions
- Present: none.
- Improve: add captions to any future videos.
#### Forms and interactions
- Present: support examples only.
- Improve: provide accessible prompt UI patterns.
#### Standards reference
- Map improvements to WCAG 2.2 AA criteria.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: mentions Spanish and German translations.
- Improve: add more locales and regional examples.
#### Inclusive language
- Present: clear and direct.
- Improve: define jargon consistently.
#### Neurodiversity support
- Present: chunked steps by day.
- Improve: consistent icons and summaries.
#### Representation
- Present: developer-focused.
- Improve: include user perspectives and diverse credits.
#### Psychological safety
- Present: respectful, encouraging framing.
- Improve: add community guidelines references.
### ✅ Logical Validity
#### Strong reasoning
- Causal chain from optimization to installs is coherent [H6].
- Weighted formula interpretation aligns with sources [H4].
#### Fallacies
- Risk: survivorship bias in case mentions. Mitigate with broader data.
#### Tone of voice
- Motivational and practical, with clear instructions.
### 🛡️ DARVO Analysis
- Deny: none observed.
- Attack: none; competitors not maligned.
- Reverse victim/offender: none; frames system neutrally.
## 🎯 Conclusion
- Treat growth as a process: match queries, prove quality, stay fresh.
- Next steps: rewrite titles, expand docs, pick tags, update, resolve, and ask.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: H3.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] Titles drive plugin discoverability
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed {{date:YYYY-MM-DD}}.
> “Your plugin title alone has more weight than your description, tags, and everything else combined.”
Use exact phrases users search. Test variations.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Early installs and reviews shift rankings
> [!quote] [Why Your WordPress Plugin Has 10 Installs (And How to Fix It)](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/)
> “Each early install gives you a disproportionate boost… Get even one 5-star review…”
Prioritize first wins to overcome cold start.
[view highlight](https://iconick.io/why-your-wordpress-plugin-has-10-installs-and-how-to-fix-it/#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: H4.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Title exact-match increases impressions
- When titles mirror high-intent queries.
- Links: [[Plugin-Directory-SEO]] [[Readme-Optimization]]
#### [Z2] Support resolution improves ranking
- When resolution exceeds the default threshold.
- Links: [[Support-Ops]] [[Community-Health]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: Select one line → Refactor.
- [F1] Draft title patterns for five target keywords — context/URL #fleeting #inbox
- [F2] Build a 2,500-word readme outline — context/URL #fleeting #inbox
- [F3] Configure review-ask milestone notices — context/URL #fleeting #inbox
## 🧰 Template Library (paste into Note Refactor → Refactored Note Template)
<!-- Copy ONE template at a time into the plugin before running each batch. -->
### 📝 Fleeting — Refactored Note Template (Konik-ready)
---
type: fleeting
status: inbox
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
process_by: {{date:YYYY-MM-DD}} # review within 24–48 hrs
source_title: [MISSING]
source_link:
author: [MISSING]
source_type: article|paper|video|podcast|thread
reading_stage: inspectional|analytical|syntopical
project:
tags: #fleeting #inbox
---
# 📝 Fleeting Note — {{title}}
## 🧠 One-liner (my words)
- State the single idea in one short sentence.
## 🧭 Context & cue
- Where did this arise? Page/timecode/speaker.
- Trigger: quote, data point, claim, or question.
## 🧪 Adler checks (quick)
- What is this about as a whole?
- What is said in detail, and how?
- Is it true? Evidence for or against?
- So what? Impact or next move.
## 🔎 Bias & reliability snapshot
- Possible bias or framing?
- What evidence would change my view?
## 🧩 Konik bridge
- Draft a claim header for promotion.
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{source_link}}) by [[{{author}}]]. Accessed {{date:YYYY-MM-DD}}.
> “Short quote under ~25 words.”
One line on why this matters.
[view highlight]({{source_link}}) #xref ID:rw_[MISSING]
## 🧰 Next moves (pick 1–2)
- [ ] Promote to Literature with citation.
- [ ] Draft Atomic claim from [H1].
- [ ] Park as testable question.
## ✅ Processing checklist
- [ ] Rewrote in my words.
- [ ] Decided: trash | keep | convert.
- [ ] Linked to at least one related note.
- [ ] Tagged and moved out of inbox.
---
### 📚 Literature — Refactored Note Template (Konik-ready)
---
type: literature
status: draft
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
adler_level: inspectional|analytical|syntopical
reading_stage: inspectional|analytical|syntopical
source_title: [MISSING]
author: [MISSING]
year:
publisher_or_journal:
edition_or_volume:
doi:
url:
accessed: {{date:YYYY-MM-DD}}
citekey:
project:
tags: #literature #reading
---
# 📚 Literature Note — {{title}}
## 🧰 Action Inbox
- [H1] Short action — context/{{url}} #articleseed
- [H2] Short action — context/{{url}} #xref
- [H3] Short action — context/{{url}} #share
## 🧭 Bib Capsule
- Title, author, year, venue, and link.
- One-line scope: what the work attempts.
## 🧠 Author’s Thesis (their words)
- Core claim briefly. Include page/timecode.
## 🧩 Key Arguments
- Argument A — method/evidence — page/time.
- Argument B — method/evidence — page/time.
- Argument C — method/evidence — page/time.
## 🧪 Evaluation (Adler)
- What is this about as a whole?
- How is it argued? Fairly and clearly?
- Is it true or plausible? Why?
- So what? Practical or theoretical impact.
## 🗒️ Notes (Konik CEE units)
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H2) #xref ID:rw_[MISSING]
## 🔖 Zettel Candidates
#### [Z1] 5–10-word present-tense claim
- One-line context and page/time.
#### [Z2] 5–10-word present-tense claim
- One-line context and page/time.
## 🏷️ Tag Coverage
#articleseed: 0 • #xref: 0 • #share: 0 • #bmf: 0 • #addendum: 0
## ✅ Processing Checklist
- [ ] Thesis captured in my words.
- [ ] 1–3 Zettel candidates drafted.
- [ ] Action Inbox pruned to high-signal items.
- [ ] Cross-links added and filed.
---
### 🔖 Atomic (Zettel) — Refactored Note Template (Konik-ready)
---
type: atomic
id: {{date:YYYYMMDDHHmm}}-{{title}}
status: evergreen
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
origin: reading|thinking|experiment
proof_state: conjecture|working|supported|refuted
source_literature: [[Source-Literature-Note]]
citekey:
project:
tags: #zettel #idea
---
# 🔖 {{title}} <!-- 5–10 words, present tense, specific -->
## 🧠 Claim
- One idea only. Clear and testable.
## 🧾 Evidence & Pointers (Konik)
- [H#] from [[{{source_literature}}]] — page/time — brief rationale.
- ID:rw_[MISSING] — link to highlight or dataset.
> [!quote] Evidence snippet (≤25 words) if essential.
> Cite page/time. Keep it minimal.
## 🔍 Scope & Conditions
- When this holds. Boundaries and exceptions.
## 🔗 Links
- Broader: [[Parent-Concept]]
- Narrower: [[Specific-Case]]
- Related: [[Parallel-Idea]]
## 🧪 Tests / Falsifiers
- One check that could disconfirm the claim.
- Simple study or observation plan.
## 🧰 Implications
- Practice, policy, or design moves in one line each.
## 🔙 Backlinks
- From: [[{{source_literature}}]] • Context line.
## ✅ Maintenance
- [ ] Links in and out.
- [ ] Title still precise?
- [ ] Proof state updated.
## Highlights
- The Secret’s Out: How WordPress.org Actually Decides Rankings
The plugin directory processes 100,000 searches every single day. When someone types “contact form” or “image optimizer,” WordPress has to decide which plugins to show first, second, third—and which ones never appear at all.
They use a two-phase system that’s actually pretty clever once you understand it.
Phase 1: “Does This Plugin Match What They’re Searching For?”
WordPress scans seven specific fields in your readme.txt file:
1. **Your plugin title** (this matters WAY more than everything else)
2. **Your excerpt** (the short description)
3. **Your full description** (including FAQ and changelog)
4. **Your tags** (but only the first five)
5. Your plugin slug
6. Your author name
7. Your contributor names ([View Highlight](https://read.readwise.io/read/01k6wzrmvmmp8r4wh1ej8164b8))
- But here’s what makes this encouraging: 57% of all WordPress plugins have zero reviews. 64% have fewer than 5 ratings. You’re not alone in facing this. And most developers never overcome it simply because they don’t know what they can actually control. ([View Highlight](https://read.readwise.io/read/01k6wzgq1zjmsv3mjxrkytv9a8))
- Tags: 👻 ai highlighted
- One plugin documented getting 600 five-star reviews in 18 months by simply asking satisfied users after helping them with support. Another saw their review count increase by 700% by implementing smart milestone notifications. These aren’t magic—they’re discipline applied consistently. ([View Highlight](https://read.readwise.io/read/01k6wzgq2s5rdtfmfeefhpvma7))
- Tags: 👻 ai highlighted