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 your tool website listing.
Apply only after your tool becomes a legally registered nonprofit with software central to scalable public impact.
Eligible if your component is open-sourced.
Submit only after your tool releases a signed Windows desktop utility.
Release your genuine SDK, verify its namespace, sign artifacts, and include accurate project, SCM, license and developer URLs.
Publish an original benchmark or evaluation study of local-first privacy or security tooling with open code, data, and your tool implementation.
Organize the complete code, data, materials, and outputs behind your real evaluation study into a public citable box.
Publish your substantive privacy template, workbook, or creator resource with a complete description, original previews, and accurate licensing.
Author a freely licensed hands-on module for safe document sharing or privacy-first web use with relevant your tool examples.
If you publish beginner tech guides, suggest them for their digital-skills resources.
Build a genuine Solid privacy utility that lets users choose identity providers and stores or retrieves their data from Solid Pods, then confirm the current listing handoff with maintainers.
Pitch your tool as innovation/useful web tool platform.
If your tool helps nonprofits or libraries, reach out about their resource articles or partner programme.
If your component is built with or for a public body, publish a standards self-assessment and pursue stewardship/assessment.
Onboard your operational research-facing service through an eligible EOSC Node using the Federation Handbook process.
Only if your tool builds a real commercial FIDO2 or passkey server, complete conformance and interoperability testing and submit it.
Apply as Associate or full Member only after operating a credible incident-response team/program and completing sponsorship/review.
Consider organizational membership if your tool actively participates in privacy or AI governance; complete the member directory profile.
Apply only after operating a real civil-society digital-security help desk and meeting network operations and vetting requirements.
Apply only after your tool operates a genuine OA scholarly-book publishing program, then submit peer-reviewed privacy-tech books.
Publish real your tool film, design, illustration or product case studies and connect them to the appropriate project pages.
Build a real founder or your tool creative portfolio and link relevant case studies to the corresponding live tools.
Join only when your tool will fund and actively contribute to open-source AI or data work.
Join only to contribute substantively to relevant security or privacy technical committees and use approved organization metadata.
After releasing meaningful OSI-licensed code, consider sponsorship only when supporting OSI aligns with your tool strategy.
Use only if your tool has a genuine creator offer, guide or service; complete the storefront and connect relevant site pages.
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.