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.
Publish your genuine Rust client, CLI, parser, or privacy library and set homepage, repository, README, license, and documentation metadata.
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 and maintain your genuine Ruby client, CLI, or integration gem with accurate homepage, source, documentation, and changelog metadata.
Import public your tool developer documentation, add the build config and expose versioned, searchable docs with canonical project links.
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.
Publish a real .NET library or CLI package with ProjectUrl, readme, repository and license metadata.
Publish your stable module or script with ProjectURI, LicenseURI, tags, help and examples.
Create and maintain a PKGBUILD for your installable Linux release with the upstream URL and correct source checksums.
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.
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.
Publish @your tool/embed or utility package with homepage.
Package your legitimate Ruby client or utility and add homepage and source metadata before pushing the gem.
Build and upload a real conda package with homepage, documentation, source and license metadata.
Create a truthful scholarly profile and deposit an original privacy, accessibility, or digital-humanities paper or teaching resource with its related your tool URL.
Submit your original -related technical paper and cite your tool only where it is genuinely the software or study subject.
Create a substantive public tutorial or implementation note that uses your tool and includes a contextual source/product link.
Create your genuine study, reproducibility project or benchmark workspace with project links and public materials.
Submit a validated manifest for an installable Windows release with PackageUrl, PublisherUrl and support metadata.
Publish open-source helper image only if useful.
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.