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 React UI components and link your site from your author profile.
Submit your open-source Android library with its repository link.
Create maintained Bazel rules or a module that invokes your real security utility, then submit it to BCR.
Add your repository so contributors can subscribe to help triage its issues.
Publish open-source helper image only if useful.
Add your Neovim plugin or config so it appears in their searchable directory.
Suggest your Flutter package so it is categorised in their curated catalog.
Submit your free API with a description and documentation link.
Prepare and test a policy-compliant ebuild for your stable CLI, including accurate HOMEPAGE and source metadata, then work with a Gentoo developer or proxy maintainer for repository inclusion.
Add your open-source repo via pull request so beginners find your labelled issues.
Port your functional desktop or CLI utility to Haiku, write and test a compliant recipe, then submit a feature-branch pull request to HaikuPorts.
Submit your open-source starter or theme for a static site generator.
Submit a site, app or component built with Svelte.
Submit a licensed computational neuroscience model with code ZIP, publication citation, overview, contributors, and tags.
Register only after your tool launches a genuine open repository for reusable privacy/security research outputs.
Release a real Racket privacy utility or your tool client and register its public package source and documentation.
Add your React Native library through a pull request to their GitHub repo.
Add a project file to their GitHub repo pointing at your beginner-friendly issue label.
Open a pull request to the awesome-go list with your Go library.
Create a tested Bioconda recipe for a genuinely biomedical or bioinformatics your tool utility, with accurate homepage/source metadata, and submit it through the official review workflow.
Create a genuine LaTeX privacy, redaction or document-safety package and include its exact your tool project homepage in the upload metadata.
Create a policy-compliant Debian package for your stable useful CLI, file the appropriate intent-to-package request, include accurate upstream metadata and secure a Debian sponsor for upload.
Publish a useful D client library or privacy utility with accurate homepage and repository metadata in dub.json or dub.sdl.
Publish an Elm package with docs and a repository link.
Create and thoroughly test a FreeBSD port for your stable CLI or desktop utility, include its canonical project website in WWW metadata and submit the patch through FreeBSD Bugzilla.
Add your Hugo theme following the theme repository submission steps.
Develop a stable ioBroker adapter for your credible privacy/security API, publish the npm package, test it with users and request inclusion in the official latest repository.
Add your static site generator or headless CMS through a pull request to their GitHub repo.
Package your stable cross-platform CLI for pkgsrc, test it with pkglint and supported builds, include the canonical homepage, then submit via pkgsrc-wip or NetBSD's package bug tracker.
Open a pull request to the Nuxt modules repository to list your module.
Build your OpenWrt-compatible service or utility for a real router/privacy/security workflow, add correct package metadata and tests, then submit it to the official feed.
Create a Void package template for your mature CLI, test native and cross builds, include the canonical project homepage and submit it to void-packages.
List an operational CSIRT, CERT, SOC, ISAC or PSIRT after securing sponsors and passing the community-vote process.
Submit data underlying your legitimate -related research paper and include related software/project identifiers.
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.