The big horizontal marketplaces (Salesforce, Slack, Adobe) get all the attention. Some of the easiest high-authority links, though, sit in niche platforms that serve one industry or one kind of product. There are fewer competitors there, the audience is already looking for exactly what you build, and the listing page links straight back to your site.
3 High-DR Platform Directories That List Your Integration for Free
A listing on someone else's official catalog is still one of the cleaner ways to pick up a high-authority page that points back to your site. You are not filling in a generic directory form. You build a plugin, an incident-response app, or an MCP-powered "Power," then you submit it for review. If it is approved, the platform publishes a dedicated page for your product.
This guide covers three of those catalogs that appeared in posts on X: Figma Community, PagerDuty, and Kiro's Powers directory. The posts report Domain Ratings of 92, 84 and 81. Only the PagerDuty post describes the outbound link as dofollow. The Figma post says you get a dedicated page linking to your site; the Kiro post does not describe the rel attribute. Those numbers and link claims come from the posts (the Figma and PagerDuty posts also include Ahrefs screenshots), not from a fresh crawl of our own. Domain Ratings move, and you should check a live listing before you treat the link as dofollow.
All three channels expect a real integration, not a one-line blurb. Figma is for plugins that run inside its editors. PagerDuty is for apps that connect to its incident platform, and official developer docs say it is free to join. Kiro is for MCP servers packaged as Powers that agents can install on demand. None of these is a five-minute submission.
At a glance
| Directory | Reported DR | What links to you | Main requirement | Best fit |
|---|---|---|---|---|
| Figma Community | 92 | A dedicated page linking to your site, according to the source post | A working plugin, published from the Figma desktop app and reviewed by Figma | Tools that extend Figma, FigJam or related editors |
| PagerDuty | 84 | Dofollow links to your site, according to the source post | A free developer account, a built app, and a review that the post says takes about five business days | Monitoring, ticketing, security and other tools used during incidents |
| Kiro Powers | 81 | Not described in the source post | An MCP server packaged as a Power, a public GitHub repo, a local test, and a registry review | SaaS products that can expose tools or skills to Kiro agents |
Figma Community
What it is
Figma Community is Figma's public catalog of plugins and other resources that people can install inside Figma's editors. The source post points builders to Figma's Plugin API introduction, which is the official starting point for creating a plugin. Publishing itself happens from the Figma desktop app; Figma documents that flow in Publish classic plugins to the Figma Community and in its plugin publishing developer docs.
What link you get
The source post reports a Domain Rating of 92 and says an approved listing includes "a dedicated page linking to your site." The Ahrefs screenshot attached to the post shows a DR of 92. The post does not call the link dofollow. Figma's own docs also do not describe the rel attribute, so confirm it on a live Community page.
How to get listed
- Go to the Plugin API docs and build a plugin (JavaScript and HTML, plus a
manifest.json). - Publish it from the Figma desktop app. Figma's help article says you open a file, go to Plugins → Manage plugins, then choose Publish. You will be asked for a name, tagline, description, category, icon and thumbnail.
- Put your site in as the support contact. Figma's developer docs say you must add a support contact when you submit a plugin for approval, and that this can be an email address or a link to a website or help center.
The source post compresses this to those three steps and notes that "Figma reviews it first." That matches official documentation: Figma reviews a plugin before it is listed in Community, and it contacts you through your Figma account email with the decision.
Watch-outs
A Community listing is not a self-serve upload. Official docs say you need the desktop app, two-factor authentication, and a plugin that already runs in development. Approval times "vary depending on current volume and the team’s availability"; the help center also notes that a security disclosure form, when required, may take up to two weeks to review. After the first approval, later version updates can be published without another review. Paid plugins are a separate path and require being an approved creator, which is outside what the source post describes.
PagerDuty
What it is
PagerDuty's developer platform is the official way to build apps and integrations that show up for PagerDuty users. The source post starts at the developer account sign-up page. That page describes a free developer account limited to three users. PagerDuty's developer overview also says the partner program is "free to join" with "no fees to develop integrations."
What link you get
The source post reports a Domain Rating of 84 and says an approved listing includes dofollow links to your site. The Ahrefs screenshot in the post shows a DR of 84. Confirm the rel attribute on a live app or integration page; official developer docs do not document it.
How to get listed
- Sign up at docs.pagerduty.com/developer/signup.
- Register and build your app.
- Submit it for review.
The source post says review takes about five business days. Official pages describe a self-service developer account and a partner path for connecting users to your solution, but they do not independently restate that five-day SLA, so treat the timeline as coming from the post.
Watch-outs
The free developer account is a starting point, not a listing. You still need a working integration that belongs on an incident platform — monitoring, ticketing, security, deployment or similar. Plan time for the build and for the review queue. If you already have a regular PagerDuty account, the sign-up page tells you to log in rather than create a second one.
Kiro Powers
What it is
Kiro Powers is the registry of installable packages that give Kiro agents specialized tools and instructions on demand. A Power is a directory with a plugin.json manifest, optional mcp.json connection settings, and skills that explain how to use your product. Official docs are at kiro.dev/docs/powers, and submissions go through kiro.dev/registry/submit. The submit page asks you to share a Power or MCP server in a public GitHub repository and says Kiro will be in touch if it is a good fit.
What link you get
The source post reports a Domain Rating of 81. It focuses on discovery inside Kiro rather than on the rel attribute of any outbound link, so this guide does not treat the listing as a confirmed dofollow backlink. Check a live Power page after you are accepted.
How to get listed
The source post lays out five steps, which line up with Kiro's own registry and docs:
- Package your MCP server as a Kiro Power with a
plugin.jsonmanifest,mcp.jsonconnection settings, and a skill that explains how to use your SaaS. The post suggests asking Claude to help build the package. - Publish it in a public GitHub repo. A subfolder in an existing repo is enough. Add a README with setup instructions, your privacy policy, and a support contact.
- In Kiro, go to Powers → Add Custom Power → Import power from GitHub. Test sign-in and a tool call.
- Open kiro.dev/registry/submit, select Power, and add your contact details, a short use case, the GitHub URL and a logo.
- Submit it for review. The post says Kiro will contact you if it is a good fit, which matches the language on the official submit page.
Watch-outs
Kiro reviews for fit; a public repo alone does not guarantee a registry listing. Official docs also distinguish Powers (dynamic packages that load tools when relevant) from standalone skills and from Kiro-specific steering, so submit a real Power rather than a loose prompt file. Test the import in Kiro before you apply — broken sign-in or a failing tool call is something you can catch locally. The post notes that Powers load only the instructions and tools that are needed for the current task, which is the product idea behind the directory, not a shortcut around review.
How to prioritize
Start with the directory that already matches something you can ship, not the highest reported DR.
- Figma Community if you can build a plugin that designers would actually run. The reported DR is the highest of this set, but you need the desktop app, a review, and a real plugin — not just a marketing page.
- PagerDuty if your product already sits in the incident workflow. The post is the one that explicitly calls the link dofollow, official docs confirm a free developer account, and the stated review window is about five business days.
- Kiro Powers if you already have an MCP server or can wrap your API as one. The packaging work is specific (
plugin.json, skills, a public repo), and acceptance depends on fit.
A short checklist before you submit: make sure the integration actually works in the host product, gather the assets the form asks for (logo, support contact, privacy policy or security notes), follow the official docs rather than stopping at the social post, and inspect a live listing's rel attribute after you go live.
These three catalogs are worth the build when the integration is something your users would want anyway. The listing page is a side effect of being in the official directory, not a substitute for a product that belongs there.
Sources
More Posts
Discover the best image generation models in 2025, ranked by quality, realism, and prompt accuracy. See why Nano Banana Pro leads the field and how to use it instantly at bananakit.ai.
Marketplaces run by large SaaS companies give every approved integration its own page, and that page links back to the developer. This guide covers the Asana App Directory. One post on X reports that it is a DR 91 domain with a dofollow link. A second post from an indie builder who inspected a live listing adds more detail and a step-by-step process.