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.
Release your genuinely free-software desktop or self-hosted component with free documentation and transparent downloads, then submit a custom directory entry.
Publish a substantive Glide template for privacy-safe records, evidence organization, or accessibility audits and link its your tool documentation where permitted.
Create a narrowly useful GNOME Shell extension, provide metadata and homepage or source information, and submit it for review.
Join a working group and contribute a substantive building-block specification, use case, reference implementation or new proposal.
Ship a genuinely useful Gradle plugin for your developer check such as secret, licence, or configuration auditing; publish with your tool documentation and support URLs.
Build a GRASS GIS add-on for location anonymization, sensitive-zone generalization, or privacy-safe geospatial export, include docs and tests, then submit it to the official add-ons repository.
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 research-level open-source component or related preprint/report with accurate project and source links.
Deposit your genuine benchmark, evaluation dataset or reproducibility bundle with project URL in the description/metadata.
Register as source for B2B content quote opportunities.
If your tool ships a macOS CLI or desktop helper, create a maintained tap with a real release, version, checksum, and official homepage 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.
Join an approved organization and publish a documented humanitarian privacy/safety dataset with licence and responsible-access settings.
Apply as the actual designer and publish a manually designed, consistent privacy or accessibility icon pack with an accurate public author profile.
Archive your authentic release, manual or research artifact with accurate metadata and official source URL.
Request writer access for the publication and submit engineering, cloud or DevOps articles via Medium.
If your tool releases a suitable open-source Android app, request inclusion with public source, tagged APK releases, Fastlane metadata and website links.
Apply to become a writer for the In Plain English publications and submit clear programming tutorials.
Release your useful JVM or Android library from GitHub with a working build, release tag, README and canonical project links.
Package a complete computational privacy or accessibility learning module and submit its reusable artifact plus Markdown paper.
Create a focused educational demo for one your tool technique and share the public bin from an authentic profile.
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.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Publish a genuinely useful KDE or Plasma asset or integration with accurate project and homepage details.
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.
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.