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.
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.
Submit one released evaluator such as WCAG Quick Auditor with accurate standards, scope, license, release date, and accessibility-statement details.
Submit a genuine international cyber-capacity-building project, tool, publication or webinar with evidence and a live resource URL.
Build a tool that genuinely interacts with Wikimedia, publish accurate toolinfo.json metadata, and register it through Toolhub UI, crawler, or API.
Build a current CodeMeta validator, privacy linter, or integration and propose inclusion through the official website repository.
Publish your containerized research workflow or tool using CWL, WDL, Nextflow, Galaxy, or a supported notebook descriptor.
Create your company profile using your official email.
Suggest your tool and complete its B2B software profile.
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.
Publish your genuine open dataset, benchmark, software release, poster, or reproducible research artifact and connect its related identifier to your tool.
Submit your polished landing/tool UI with clean screenshots and design credits.
Submit your tool with homepage URL, privacy-first positioning, logo, screenshots and accurate pricing.
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.
Submit relevant your tool utilities under AI, web, or developer categories.
Publish a privacy-respecting open-source Android companion app, then file a packaging request or merge request.
Request access, then publish your rich research-software page with source, getting-started URL, DOI, contributors, and research mentions.
Answer real end-user software or privacy questions in depth and reference your specific page only when it materially completes the answer.
Build a generic DHIS2 health-data de-identification or permission-audit app and submit it to App Hub for core-team review.
Deposit your research-level open-source component or related preprint/report with accurate project and source links.
Package a complete computational privacy or accessibility learning module and submit its reusable artifact plus Markdown paper.
Suggest one mature your tool utility through the official Codeberg issue path only if it is an easy-to-use, privacy-respecting replacement for a clearly identified invasive service.
Contribute a substantive accessibility role template, translation or toolkit improvement with useful source attribution.
Register a real bioimage privacy, de-identification, or analysis tool with accurate scientific functions, documentation, and maintainers.
Publish your genuine benchmark, dataset, software artifact, poster, or methods report with the canonical project URL in metadata.
Publish a clinical-data de-identification or quality tool with source, installation steps, dependencies, documentation, and tests.
Open-source your reusable research-focused component, archive it with a persistent identifier, and submit a software metapaper with project/code links.
Develop an open statistical/privacy-analysis component, then submit a reproducible English LaTeX software paper linking its code and your tool project page.
Build a genuine RO-Crate validator or privacy linter and submit a technical developer article using the official blog template.
Submit your -related astronomy utility only after it has been used in research submitted to or published by a refereed journal.
Open-source a relevant geoscience model or component, complete the model questionnaire, and provide its code archive for CSDMS testing.
Organize a rigorous life-science privacy-tool benchmark or participate with your eligible method and publish validated results.
Submit a mature scientific Python package related to your privacy or accessibility workflow for public review and listing.
If your tool produces a research-grade R package, submit a presubmission inquiry and the package for open review.
Build a real ROS package for your robotics/privacy/safety workflow, release it through rosdistro and expose maintained README, documentation and source links in ROS Index.
Submit your qualifying open research-software component and short software paper after it has mature public development history.
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.