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.
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.
Host your useful open-source SDK, CLI or example project with documentation and a canonical homepage link.
Launch your real educational podcast, complete its public site, and cite relevant tools and sources in useful show notes.
Create an authentic your tool or founder design portfolio with substantive case studies and contextual links to shipped tools.
Convert your original guide into a public flipbook and add contextual links or web embeds for cited tools and resources.
Build a secure Jenkins plugin that performs your real CI, privacy, or accessibility workflow; host it through Jenkins project infrastructure and publish maintained releases and documentation.
Package your tool developer/security utilities as a compatible JetBrains plugin and upload it.
Run a genuine privacy, online-tools or accessibility community and reference your tool only where it supports the group or event.
Submit useful your tool-related talks to relevant CFPs or run a genuine community CFP with a public event page.
Create your organization, set its official website, and publish a real free or paid digital product or subscription.
Use pretalx for your genuine community conference or submit relevant talks to events that use the platform.
Submit a reusable open-source React component extracted from your tool with repository, demo, setup docs and screenshots.
Build a legitimate Ring-device privacy/security integration, register, test, certify and publish it.
Upload a useful original presentation on privacy, accessibility, or tool workflows with your natural reference.
Pursue only if your tool launches a real cloud-connected IoT privacy product; certify it and publish a truthful product profile.
Create a founder/privacy-tool expert profile, add your tool website and pitch only genuinely relevant podcast interviews.
Publish your original guide or annual privacy report and add useful contextual website links through the Hotspot Editor.
After publishing a mature security policy and VDP, contact the Secretariat to apply as a signatory to all four principles.
Build a Homey app only if your tool adds a genuine IoT privacy or local-device workflow; package, test, validate, and submit it for certification.
Host your maintained open-source component with complete README, homepage/source metadata, releases and optional pages.sr.ht docs.
Build your useful iOS or macOS app and submit complete support, privacy, accessibility and marketing metadata through App Store Connect.
Build a production Contentful app for your tool privacy or content checks and apply through the Marketplace submission flow.
Create a portfolio for genuine your tool product/design work and use each project's external URL field for the matching live page.
Create a legitimate free or paid your tool resource or software product and publish it on a branded hosted storefront.
Apply only with a validated open-source privacy or anti-surveillance project that directly helps users facing repressive censorship or surveillance.
Apply as a General Member only if your tool will meaningfully contribute engineering or resources to open-source security.
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.