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.
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.
Create your truthful /founder profile or content page and add the website link where allowed.
Add your Mac app and keep version updates current so users get notified.
Submit your Windows utility with a PAD file or download link for editorial review.
Have a qualified founder or senior team member apply as a privacy, accessibility, product, or engineering mentor and add your tool only as truthful experience/personal-site evidence.
Build a safe MISP import, export, hover, expansion, or workflow module for a legitimate privacy or scam-analysis use case, document it, test it, and submit a PR.
Contribute a working collector or alert integration for measurable your tool service/privacy signals with metadata and documentation.
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.
Develop a safe, useful Nmap NSE script related to your security check and include accurate author or homepage metadata.
Use ORCID to publish genuine research stages—problem, method, data or analysis—with contextual your tool code/data links.
Create a maintained Omeka S module for collection metadata privacy, accessibility or link auditing, package it correctly and register the add-on with project and author links.
Build a working OnePageCRM integration and apply for testing, verification and a dedicated marketplace page.
Suggest your personal or independent blog through the site's suggestion option.
Publish a real OCaml library or CLI integration and use opam's homepage field for its canonical your tool project page.
Create a rigorous structured comparison of published privacy, redaction, or accessibility studies and include your tool only when supported by research.
Create your genuine study, reproducibility project or benchmark workspace with project links and public materials.
Open-source your component, then add its website and repositories through the official oss-directory PR.
Build a secure OpenCTI connector that imports or exports your legitimate -supported CTI workflow, add tests and documentation, and contribute it for library integration.
Publish an open-source Lua/OpenResty package that integrates your privacy or security workflow and includes honest package metadata.
Contribute a functional privacy/security integration, dashboard or ingestion-to-visualization content pack through the OpenSearch Catalog workflow.
Package your useful browser feature as an Opera extension and submit it for moderation.
Create a public reproducibility project for your tool research, datasets, test methods, or privacy benchmarks and link the genuine project/site.
Build a useful ownCloud app that invokes or embeds your privacy, document or URL-audit workflow, code-sign it and publish it through the official marketplace.
Create a public searchable board that teaches a privacy workflow and links to supporting standards, guides, and relevant your tool utilities.
Build and test a Particle Device OS privacy, local-processing, or credential-safety library with examples, license, README, and repository URL, then publish it via the CLI.
Create a structured collection about privacy-preserving web utilities and mix selected your tool pages with respected references.
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.
Develop an OJS/OMP/OPS plugin for a genuine accessibility, privacy or publication-validation workflow, release it with gallery metadata and submit through PKP's review flow.
If you blog about PostgreSQL, register your feed so your Postgres posts are syndicated on the planet.
Ask to have your Python-tagged blog feed added so your Python posts appear on the aggregator.
Build a working mini-project showing your browser-side feature and publish its indexed share page with useful documentation.
Join the community and submit product management articles to the publication on Medium.
Create high-confidence defensive templates for authorized checks of privacy leaks or misconfigurations, include safe matchers and test evidence, then submit them for review.
Create your maintained exporter or native Prometheus metrics integration and submit it to the official exporters list.
Apply as an author and publish original privacy, security or accessibility articles with contextual your tool references.
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.
Build and test a Puppet module for supported your tool setup or security policy, complete metadata.json, package it, and publish through a Forge account.
Post to relevant subs with context: SideProject, SaaS, webdev.
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.