FREE RESOURCE / PRODUCT DISTRIBUTION
19 places to get your product discovered.
A practical directory of backlink and distribution opportunities for SEO and AI discovery. Find the platforms that fit what you’ve already built.
19 opportunities
| Platform | What you need | How to get listed | Before you start |
|---|---|---|---|
| 01EmDash Plugins ↗Plugins | Working sandboxed EmDash plugin | Build a useful CMS integration, validate its manifest and publish using an Atmosphere account. Include accurate author and website metadata.Official site / guidance ↗ | Publishing documented; listing acceptance and link attributes still need checking.Original post ↗ |
| 02Make ↗Automation | Tested custom app for your API | Build a connection and useful modules. Test real scenarios, then request app review. Plan for ongoing support.Official site / guidance ↗ | Review required before the app is available to all users.Original post ↗ |
| 03Firefox Add-ons ↗Extensions | Firefox-compatible browser extension | Package and test your extension, provide source and reproducible build instructions where required, and submit for signing and public distribution.Official site / guidance ↗ | Porting a Chrome extension still requires compatibility and policy checks.Original post ↗ |
| 04ChatGPT plugin directory ↗AI & MCP | Useful plugin package; verified publisher | Prepare the plugin ZIP, upload it through the platform, resolve automated findings and submit for review. Connect and test your MCP server if included.Official site / guidance ↗ | Current submission docs differ from the original post. Approval is required; citation preference is not established.Original post ↗ |
| 05n8n ↗Automation | Community node wrapping your API | Build and test nodes and credentials. Publish to npm using GitHub Actions with provenance, then submit through the Creator Portal for verification.Official site / guidance ↗ | An npm package alone is not a verified n8n listing.Original post ↗ |
| 06Microsoft Edge Add-ons ↗Extensions | Tested Edge-compatible extension | Register in Partner Center, upload your package and complete store, privacy and certification details. Submit for review.Official site / guidance ↗ | Test your Chromium extension in Edge before submitting it.Original post ↗ |
| 07Notion Marketplace ↗Automation | Public OAuth connection | Build a useful workflow for Notion users. Choose the appropriate installation scope when creating the public connection, then complete Marketplace security review.Official site / guidance ↗ | Public connections can exist without Marketplace approval; those are different milestones.Original post ↗ |
| 08Fern Agent Score ↗Documentation | Public product documentation | Assess your documentation with Agent Score and improve readability, discovery and authentication access. Check whether a public report is available for your submission.Official site / guidance ↗ | Assessment tool confirmed. The thread’s public-report backlink claim was not independently verified.Original post ↗ |
| 09Postman API Network ↗API & packages | Public API collection and team profile | Make your team profile public, create a public workspace and publish useful API collections and examples. Remove credentials before sharing.Official site / guidance ↗ | A public team profile appears on the API Network. Confirm your website link on the published profile.Original post ↗ |
| 10Chrome Web Store ↗Extensions | Useful browser extension | Register a developer account, upload the extension ZIP and complete listing, privacy and test instructions. Submit for review.Official site / guidance ↗ | Registration may involve a fee. The directory is free to use; not every opportunity is free to execute.Original post ↗ |
| 11npm ↗API & packages | Maintained CLI or SDK | Package a useful API client or CLI with a clear README, homepage and repository. Test it, configure secure publishing and publish a public package.Official site / guidance ↗ | Libraries.io and npm.io aggregate packages. Extra listings are not guaranteed or separate submissions.Original post ↗ |
| 12RapidAPI ↗API & packages | Working, documented API | Create an API Project in Studio, import your API specification and complete the Hub Listing. Check current access, authentication and commercial settings before making it public.Official site / guidance ↗ | Do not assume the post’s free-plan or bring-your-own-key setup fits every API.Original post ↗ |
| 13ClawHub ↗AI & MCP | Useful agent skill or plugin | Prepare instructions that explain a real product workflow, authentication and safe use. Review current publisher and moderation requirements before uploading.Official site / guidance ↗ | Registry confirmed. Exact commands, no-review claims and backlink treatment remain unverified.Original post ↗ |
| 14Smithery ↗AI & MCP | Working MCP server | Prepare clear tool descriptions and a product homepage. Use the current publishing flow and test connectivity and authentication after listing.Official site / guidance ↗ | Platform has changed since the post; recheck gateway and authentication instructions rather than copying them.Original post ↗ |
| 15Glama ↗AI & MCP | Working MCP server or public repository | Find an existing listing or submit your server. Verify ownership where available, document authentication and check the listing’s health and tool descriptions.Official site / guidance ↗ | Directory confirmed. Registry ingestion timing and link attributes are not guaranteed.Original post ↗ |
| 16Official MCP Registry ↗AI & MCP | Publishable MCP server metadata | Prepare accurate server metadata and use the registry’s publishing documentation to authenticate ownership and publish a version.Official site / guidance ↗ | A registry entry is distribution metadata; downstream directory links are not guaranteed.Original post ↗ |
| 17Claude community directory ↗AI & MCP | Eligible account and supported connector | Check the directory management page in your account for current eligibility and submission options before building around this opportunity.Official site / guidance ↗ | Needs verification: account-gated route. The author reports a noindex page; do not count this as an indexed SEO backlink.Original post ↗ |
| 18Vercel Connect ↗AI & MCP | Supported API or MCP integration | Review the connector catalogue and onboarding route. Describe the product clearly and provide the authentication and connection details requested.Official site / guidance ↗ | Catalogue confirmed. Approval time and acceptance are not guaranteed.Original post ↗ |
| 19Zapier ↗Automation | Useful integration with tested actions | Use the developer platform to build and test your app’s triggers and actions, then follow the public integration review route.Official site / guidance ↗ | Do not confuse connecting to Zapier MCP with getting your own app publicly listed.Original post ↗ |
No matches. Try a different search or category.
Make the listing worth having.
- Choose platforms your customers actually use.
- Use a consistent product name, clear description and relevant website link.
- Test the integration and provide documentation, privacy information and support.
- Inspect your live listing: does it link to the right page, and is that page publicly accessible?
- Track referral visits, activated users and conversions—not just the number of listings.
Backlinks, SEO and AEO
These are potential places to earn a product mention or link, not guaranteed ranking improvements. Link attributes and indexability vary by listing. The thread’s domain-rating scores and “dofollow” claims have not been independently audited and are not used to rank this directory.
For Google’s AI Overviews and AI Mode, the usual SEO fundamentals still apply: helpful content, crawlability and index eligibility. There is no extra technical requirement that makes a listing automatically eligible for an AI citation. Read Google’s guidance ↗
Sources and review notes
Adapted from Taras Shynkarenko’s series. All 19 posts in the quoted chain were reviewed, from Zapier through EmDash, along with the available replies to the linked post. Each row links to the original post and platform guidance. Platform pages were checked where publicly accessible; account-gated and unverified details are flagged above. This is a source review, not a test submission to each platform.
The series also mentions Libraries.io, npm.io, jsDelivr and deps.dev as package discovery surfaces. Treat these as potential downstream coverage, not four guaranteed submissions. It also links to Awesome MCP Servers; check its contribution rules before suggesting your repository.