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.
Add standards-valid CycloneDX support, then submit your structured entry through the official contribution workflow.
Make your tool generate or consume valid SPDX, document validation, then file the requested supplier-information issue with its canonical URL.
Create a vendor account and submit your tool under the closest B2B software categories with an accurate feature summary.
Submit the production web app, then verify domain ownership to manage its official listing, assets, and analytics.
Email your strongest developer-focused feature with a self-service demo, documentation, privacy model, and concise reason it is novel.
Submit your tool with homepage URL, privacy-first positioning, logo, screenshots and accurate pricing.
Register your tool as a B2B product, choose relevant categories, and complete the vendor profile in English.
List product under software categories.
Propose your qualifying open-source privacy project through the official contribution process.
Build a tool that genuinely interacts with Wikimedia, publish accurate toolinfo.json metadata, and register it through Toolhub UI, crawler, or API.
Build and verify your Discord app, then enable Discovery in the Developer Portal.
Publish your containerized research workflow or tool using CWL, WDL, Nextflow, Galaxy, or a supported notebook descriptor.
Apply with a signed, downloadable open-source or qualifying freeware build that needs reliable binary hosting, malware scanning, and a public project page.
Create your company profile using your official email.
Submit your tool as a polished tool website with its strongest public page and a concise explanation of the design system.
Suggest your tool and complete its B2B software profile.
Post only a self-contained initial announcement of a substantial open-source defensive tool, a major update, or a properly coordinated OSS vulnerability disclosure.
Contact PeerSpot with your tool enterprise use cases and real-customer evidence to request inclusion.
Submit one mature privacy tool, disclose ownership, publish its exact threat model and limitations, and engage transparently with the community review.
Submit your desktop or mobile app through their developer contact so it gets a download page.
Create your real OSPO function or a tool that materially supports OSPO work, then contribute the logo and canonical URL by issue or pull request.
Build a reusable Typst privacy, accessibility, or document-checking package with a valid manifest, docs, examples, and tests, then submit it to the official packages repository.
Register as a developer and upload your app or ask the team to list it.
Publish your genuine open dataset, benchmark, software release, poster, or reproducible research artifact and connect its related identifier to your tool.
Create seller profile and list product if eligible.
Package your legitimate desktop app as an official AppImage, then file the requested issue or pull request for inclusion.
Register your genuinely life-science-focused resource with stable homepage, scientific operations, inputs, outputs, licence, and documentation.
Create a tested CapRover one-click definition for your real self-hosted service and contribute it to the linked official community repository.
Build a genuine CWL validator, security tool, or implementation and propose its inclusion with compliance evidence.
Publish a privacy-respecting open-source Android companion app, then file a packaging request or merge request.
Create software vendor listing.
Submit B2B software listing.
Archive your genuine public source repository and add its resulting SWHID permalink to release and citation metadata.
Add your tool if accepted; create company stack.
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.
If your component is open source and genuinely targeted at public administration, add valid publiccode.yml metadata so the catalogue crawler can discover it.
Build a generic DHIS2 health-data de-identification or permission-audit app and submit it to App Hub for core-team review.
Contact them to have your Windows or Mac software added to the catalogue.
Send your Windows or Mac software for review via their submission or contact page.
Release your genuinely free-software desktop or self-hosted component with free documentation and transparent downloads, then submit a custom directory entry.
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.