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.
An eligible active researcher can publish genuine your tool studies, code or datasets and add the official website where appropriate.
Publish and maintain a tested Scoop manifest for your actual portable Windows CLI or app.
Archive your genuine public source repository and add its resulting SWHID permalink to release and citation metadata.
Build a functional privacy, accessibility or security add-on, publish it on Packagist and create its Marketplace product page.
If your tool maker genuinely offers related services, add the project as a detailed portfolio item with role, outcomes, visuals, and permitted project links.
Create your accurate startup profile and complete its product, team, traction and website details.
Submit a tested your app for compatible Amazon devices with complete descriptions, support links, privacy details and store assets.
Submit your original -related technical paper and cite your tool only where it is genuinely the software or study subject.
If your tool ships a real tool that reads, validates, generates, visualizes, or otherwise supports AsyncAPI documents, add the required .asyncapi-tool metadata file and submit it for the public tools dashboard.
Build and openly maintain a Backstage plugin that gives platform teams your real workflow, then announce it through the community-plugins process and meet directory metadata requirements.
If your component is open source and genuinely targeted at public administration, add valid publiccode.yml metadata so the catalogue crawler can discover it.
If your tool documentation genuinely runs on Docusaurus, add the polished docs site through the official showcase discussion.
Submit a mature graphical Linux your app with verified metadata, screenshots, homepage and source links.
Create a useful Grav privacy or security plugin and request inclusion through the official repository issue process.
Create a substantive public tutorial or implementation note that uses your tool and includes a contextual source/product link.
Deposit your genuine benchmark, evaluation dataset or reproducibility bundle with project URL in the description/metadata.
After releasing your real CLI or native app, submit a tested formula or cask with its canonical homepage.
Publish your Android app through AppGallery Connect with official site, support and privacy URLs.
Archive your authentic release, manual or research artifact with accurate metadata and official source URL.
If your tool releases a suitable open-source Android app, request inclusion with public source, tagged APK releases, Fastlane metadata and website links.
Release your useful JVM or Android library from GitHub with a working build, release tag, README and canonical project links.
After your tool has a stable, commonly used JSON or YAML configuration format, contribute its accurate schema and test fixtures so editors can provide validation, completion, and tooltips.
Build your metadata-cleaning, accessibility or privacy plugin and submit its repository and cover image.
Build your real kubectl privacy or security scanner and submit its release manifest with a canonical project homepage.
Package your real CLI or desktop utility, set accurate homepage metadata, test it, and submit the Nixpkgs pull request.
Apply with your concrete privacy, security or user-autonomy FOSS work package, milestones, budget and public repository.
Build a working OnePageCRM integration and apply for testing, verification and a dedicated marketplace page.
Publish a real OCaml library or CLI integration and use opam's homepage field for its canonical your tool project page.
Create your genuine study, reproducibility project or benchmark workspace with project links and public materials.
Package your useful browser feature as an Opera extension and submit it for moderation.
Submit only original, deep security research or a durable technical guide with reproducible evidence; your tool may be mentioned solely as the research implementation when material.
Publish a real multi-language Pulumi provider or component for deploying or configuring your tool, with binaries, SDK packages, schema, documentation, examples, tests, and a registry pull request.
Distribute your Android or Galaxy app and add its official website and support information.
Create a truthful author account and submit your substantive privacy, security or accessibility working paper with legitimate citations.
Build your Trello Power-Up, register it, sign the developer agreement, and submit it.
Build and test your useful Visual Studio or Azure DevOps extension, then publish it with truthful homepage, repository and overview metadata.
Publish genuine authored your tool research and add matching project or supporting-material URLs in the paper metadata.
Use an authentic maker profile to publish your portfolio piece containing original images, article, code, video, or audio samples.
Create your public repository and distribute real signed DEB, RPM, npm, Maven, Helm or other supported packages with accurate metadata.
Contact the curator with your maintained self-hostable edition, repository, documentation and project website.
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.