Loading page
A maintained list of 1,854 legitimate backlink sites: directories, profile creation sites, guest posting sites, launch platforms, registries and marketplaces. 1,532 are free or have a free tier, 44 usually give a dofollow link, and 772 have an estimated DA of 70 or more. Every row shows authority, link type, cost and effort, and links straight to the submit page.
Complete the current CAIQ or AI-CAIQ truthfully and submit your tool real cloud service to the STAR Registry.
Publish a genuine hosted, external, or stdio MCP server exposing a small set of consent-based your tool utilities with complete metadata and documentation.
Create a valid Helm, OPA, Tekton or supported repository for your deployment and add it through the control panel.
Publish your genuine Rust client, CLI, parser, or privacy library and set homepage, repository, README, license, and documentation metadata.
Publish your standards-based JavaScript or TypeScript SDK with generated docs, readme and project links.
Create a useful Julia client or data utility, register it in Julia General and provide complete package docs with your source link.
Package your real MCP server, verify its namespace, create server.json and publish it with mcp-publisher.
Publish your open Privacy Framework mapping, template, tutorial, or implementation tool and submit it for repository review.
Build a genuine Kubernetes Operator for your self-hosted service, test its bundle and submit it through Community Operators.
Publish your real PHP SDK or integration from a public repository and set the canonical homepage in composer.json.
Publish your real Python SDK, CLI, or integration package and set Homepage, Documentation, Source, and Issues URLs in package metadata.
Publish a secure, documented container for your open service and add its official site in the repository description or README where supported.
Publish and maintain your genuine Ruby client, CLI, or integration gem with accurate homepage, source, documentation, and changelog metadata.
Create a tested Ansible collection for supported your tool deployment or audit automation, complete galaxy.yml, version it, and publish with a Galaxy token.
Create org/repo README linking your tool; submit to relevant awesome lists.
Create your functional Node-RED node, publish it to npm, and add it to the Flow Library with documentation and support metadata.
Publish a real .NET library or CLI package with ProjectUrl, readme, repository and license metadata.
Package a real embedded privacy or security library for supported boards, add complete PlatformIO manifest and examples, test it, and publish it publicly.
Publish your stable module or script with ProjectURI, LicenseURI, tags, help and examples.
Publish your Dart package with homepage, repository, issue tracker, documentation and a complete readme.
Publish a maintained Terraform provider for your tool stable API, or a genuinely reusable deployment module, with signed releases, generated documentation, examples, tests, and semantic versions.
Create and maintain a PKGBUILD for your installable Linux release with the upstream URL and correct source checksums.
Build your useful privacy or security Caddy module, publish the Go package, then register it for module docs and custom builds.
Package your genuine Windows desktop or CLI release and set project, documentation and package-source URLs.
Ship your real CLI or desktop utility as a tested package with homepage, project and support metadata.
Publish your tested public orb for privacy, secret, or document-safety checks with a homepage URL and usage examples.
Publish a useful C/C++ SDK or client for your API and contribute its tested recipe to ConanCenter.
Submit a tested recipe for your real package with upstream homepage, source archive, license and tests.
Submit a useful R package with URL and BugReports metadata pointing to its official project and documentation pages.
Publish your maintained CLI or server image with source, documentation, descriptions and canonical homepage links.
Create a functional Drupal integration or reusable module and publish a maintained project page with documentation and official links.
Tag and publish a public Go module with module docs and repository metadata so pkg.go.dev indexes it.
Publish your useful package to a supported registry with accurate source and homepage metadata so Open Source Insights can index it.
Publish a maintained Elixir client or utility with package links, description, license and documentation.
Submit an open-source CLI formula or a qualifying macOS app cask with your canonical homepage.
Create and test a Portfile for your open-source CLI or desktop app, including its canonical homepage.
Release a useful Java or Kotlin SDK and include the project homepage, source control, license and developer metadata in the POM.
Create a useful Emacs client for your public API, host its source openly and submit a MELPA recipe pull request.
Add and test a Nix expression for your genuine release with description, homepage, license and maintainer metadata.
Publish @your tool/embed or utility package with homepage.
Four steps that work for a new site, a SaaS or a side project. No paid link packages, nothing that risks a penalty.
Before submitting anywhere, have a one-line description, a 150-word description, a square logo and two or three screenshots ready. Every form asks for some mix of these.
Start with the free, quick rows: profile creation sites and free directories. They are one form each and build the entity signals search engines use to understand who you are.
Then pick a handful of high DA and dofollow sites that fit your niche, and write proper guest posts or launch posts for them. Ten relevant links beat a hundred random ones.
Note where you submitted and when. Recheck after a month, update stale descriptions, and never pay for bulk link packages: they put the whole site at risk.
Behind the list
Every row here starts as a line in a sheet, gets normalised into one of 16 groups, scored for cost, effort and impact, and written up with the steps to actually submit. The floor below represents that pipeline.
Open the sheet viewAn illustration of the AltF Backlinks floor: opportunities sourced at the back, vetted for cost and effort by the engineering pod, written up for outreach by the design pod, then tracked to placement along a line.
One-shot launches where timing and preparation decide the outcome.
Publications that accept contributed articles. Slow and editorial, but the links are earned.
Fast-growing listings specifically for AI-powered tools.
Extension, plugin and integration stores. Real review processes, real distribution.
Startup listings, beta lists and founder media.
General tool and software catalogues with real search traffic.
B2B review sites. Slow to approve, strong once live.
Package, image and docs hosting that carries real authority.
Showcases judged on craft. A good screenshot matters more than copy.
Write once, link back. Editorial standards vary widely.
Get quoted or distribute a release. Slower, higher ceiling.
Company and local listings. Unglamorous, consistently indexed.
Owned pages you control: company, founder, knowledge-panel entities.
Answer real questions. Never drop a bare link.
Brand surface and referral traffic more than link equity.
Everything that does not fit the buckets above.