Back to GrowthDex
Growth idea action plan

WordPress plugin assets match the readme install story

Treat icons, banners, and screenshots as part of the setup explanation, with image files and screenshot order that match the readme.

rare tacticfree budget

Why this can grow a startup

The WordPress plugin page is not just a text shelf. Search results, sidebars, and the plugin detail page all pull from asset files that have strict naming rules and long cache behavior. The docs also say there should be one screenshot for every line in the readme screenshot list. That is a useful operating constraint. If the icon is generic, the PNG fallback is missing, or the screenshot order does not match the story in the readme, the page looks less maintained than the code may actually be.

Company example

WordPress says SVG icons require a PNG fallback, plugin assets live in the top-level `assets` directory, screenshots should map one-for-one to the readme list, and image CDN updates can take from a few minutes to as long as six hours under load.

Source and metric

Source: WordPress Plugin Handbook: How Your Plugin Assets Work

WordPress requires one screenshot per readme screenshot line and says cached asset refreshes can take up to 6 hours under heavy load.

MarketplacesBrandUXplugin assetsscreenshotsicon fallbackvisual trust
GrowthDex operator note

When to use it

Use this when Marketplaces, Brand, UX is relevant to plugin assets, screenshots, icon fallback and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

Founder checklist

  1. Read WordPress Plugin Handbook: How Your Plugin Assets Work and identify what is directly supported.
  2. Choose one channel context: Marketplaces, Brand, UX.
  3. Define the test around WordPress requires one screenshot per readme screenshot line and says cached asset refreshes can take up to 6 hours under heavy load..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

AI Visibility and Search GrowthMarketplacesBrandUX

Related tactics

Figma Community team handle before multi-creator publishing

Create the team or organization Community profile early and claim a stable handle before multiple creators start publishing, so every resource compounds into one branded catalog instead of scattering across personal profiles.

rareMarketplaces, Brand, Creator Growth

Firefox Add-ons name earns the slug

Pick a descriptive add-on name early, because AMO turns that choice into the public slug and a vague title makes both search and trust weaker.

rareMarketplaces, SEO, Brand

Safari extension Extensions category is a real shelf

Treat the App Store Extensions category as a first-class acquisition shelf, because Apple actively spotlights Safari extensions there instead of hiding them behind a generic utility search.

rareMarketplaces, SEO, Brand

Chrome Web Store category choice follows the browsing job

Pick the category that matches the buyer’s browsing job, because Chrome requires one category and category shelves shape who discovers the extension in the first place.

uncommonMarketplaces, SEO, Brand

Firefox review rejection falls back to the last approved version

Treat every AMO submission like a public branch cut, because if the new version is rejected Mozilla shows the last approved version instead, or suspends the listing entirely when no approved version exists.

epicMarketplaces, SEO, Brand

Google Workspace metadata clarity before keyword stuffing

Write the Marketplace metadata for clarity and fit instead of repeating keywords, brand names, or anonymous testimonials until the page reads like spam.

epicMarketplaces, SEO, Brand
Advisory bridge

Apply this with an operator

Turn isolated search tactics into a crawlable visibility system tied to demand and proof.

Work with Ian