WordPress Plugins Scraper

Export structured public WordPress.org WordPress plugins for discovery, comparison, monitoring, and governance.

What you get

Search the public WordPress.org catalog and save one deduplicated row per WordPress plugin. Results include plugin slug, version, active installs, ratings, compatibility, support resolution, author, tags, and update time. Use discovery inputs for market maps and exact-name inputs, when available, for stable monitoring cohorts.

Output fields

Field group	Description
Identity	Canonical slug, display name, and source URL.
Release evidence	Current version or tag data and source timestamps when published.
Adoption signals	Public download, install, pull, star, or rating metrics available from the source.
Ownership and links	Public author, owner, project, repository, documentation, or homepage references.
Classification	Public tags, categories, keywords, packaging, or status values.
Provenance	Search query and named upstream source for traceable analysis.

Example output

{"slug":"wordpress-seo","name":"Yoast SEO","version":"25.0","activeInstalls":10000000,"rating":96,"ratingCount":28000,"testedWordPress":"6.8","lastUpdated":"2026-07-18","url":"https://wordpress.org/plugins/wordpress-seo/"}

Input parameters

Parameter	Required	Description
queries	No	Up to five WordPress.org plugin search phrases.
pluginSlugs	No	Up to 25 exact directory slugs.
maxResultsPerQuery	Yes	Maximum plugins requested per search; defaults to 25.
maxResults	Yes	Maximum unique plugins across both modes; defaults to 100.

At least one discovery or exact-name input is required. Result limits apply after cross-input deduplication, and only saved unique rows are charged.

Use cases

• Developers: discover alternatives and compare public release evidence.
• Platform teams: monitor versions, tags, compatibility, and activity for a fixed portfolio.
• Security teams: build an evidence inventory before joining vulnerability and deployment data.
• Product researchers: map a developer ecosystem with repeatable queries and dated snapshots.

Limitations

The Actor covers public WordPress.org directory metadata, not plugins sold only outside the directory. Active installs are bucketed by the source, and missing optional author or support fields remain null.

Compared to alternatives

Current Apify Store alternatives include apivault_labs/wordpress-plugins-scraper and nexgendata/wordpress-plugin-scraper. Thirdwatch combines discovery and bounded monitoring inputs where the source permits them, saves canonical evidence URLs, deduplicates before charging, provides exactly four PPE tiers, and ships ten ready-to-save Task recipes plus a five-article workflow library. Compare current Store listings directly because competitor features and pricing can change.

FAQ

Does this Actor access private packages or accounts?

No. It collects only metadata available from the public source and does not sign in, bypass access controls, or request private registry credentials.

How should I monitor a fixed portfolio?

Use exact names where supported, keep result limits explicit, save the input as an Apify Task, and retain dated datasets. Do not let an empty or failed run overwrite the previous successful snapshot.

Are popularity metrics quality or security scores?

No. Downloads, installs, pulls, stars, and ratings help prioritize review, but they do not replace vulnerability, provenance, license, maintainership, or internal deployment evidence.

Where can I find more workflows?

Visit Thirdwatch developer-data scrapers and the related GitHub, npm, and OSV Actors.

Last verified: 2026-07