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 installable Haystack component, provide examples and docs, then submit it to the Haystack integrations repository.
Package an installable Haystack component or tool for your tool read-only URL, security and metadata checks, then submit a draft integration page with runnable examples.
Publish a maintained Elixir client or utility with package links, description, license and documentation.
Submit an open-source CLI formula or a qualifying macOS app cask with your canonical homepage.
Publish a real Icinga-compatible check, module or integration and synchronize its public Git repository, releases and README.
Apply with a real designer portfolio and publish your original -themed privacy, safety, accessibility, icon, illustration, 3D, or Lottie pack.
Build an Intercom app for intentional conversation privacy scanning or sanitized export generation and include your clear install or learn-more URL.
Build a genuine Joomla extension, create a developer profile and submit a complete listing with the official project website.
Build and host a useful Jotform widget, register it with full documentation and send it for approval.
Create a genuine JavaScript SDK or demo on GitHub Pages and request an appropriate js.org subdomain that links to its official your tool documentation.
Publish your small standalone privacy or accessibility demo with explanatory comments and a stable share URL.
Implement Java tasks or triggers for submitting your tool audits and fetching structured results, complete with typed properties, examples, tests and generated documentation.
Build your standalone integration package with tests and submit the required LangChain documentation PR.
Contribute your provider bundle with useful privacy or security components and provider documentation links.
Join as your real designer and share polished, original interface explorations or accessibility improvements with useful design context and a profile website link.
Create a genuine founder profile and share a useful build story or tutorial with a relevant link.
Create and test a Portfile for your open-source CLI or desktop app, including its canonical homepage.
Build and teach a live, project-based cohort on creating local-first privacy tools or accessible web utilities, supported by a substantive public syllabus and real instructor profile.
Release a useful Java or Kotlin SDK and include the project homepage, source control, license and developer metadata in the POM.
Create a useful Emacs client for your public API, host its source openly and submit a MELPA recipe pull request.
Publish an original, human-verified privacy or accessibility benchmark with complete methodology, provenance, schema, license, and a relevant project citation.
Share your openly licensed digital-safety lesson pack or Moodle activity and curate it into an educator-focused collection.
Create a working Nagios check or addon for your API/privacy-health signal, register, and submit the project with source and website links.
Build and test a Netlify extension, publish it publicly, then submit it for review and directory listing.
Add and test a Nix expression for your genuine release with description, homepage, license and maintainer metadata.
Publish a machine-readable privacy, accessibility, or scam-pattern dataset or API and complete its evidence-based public certificate.
Publish your small local-first classifier for privacy, secret detection, or defensive content analysis.
Suggest your tool and complete its B2B software profile.
Build a functional OPA/Rego privacy-policy integration or developer tool, document it, then add its ecosystem entry and logo through the official docs repository.
Submit a complete, openly licensed privacy/digital-safety textbook already used in higher education.
Create an account and submit your tool or its qualifying AI tools.
Publish a free mini-course on privacy, redaction, scam detection, or accessibility with genuine your tool exercises in the curriculum.
Publish a documented, de-identified ML-ready benchmark such as labelled phishing, homograph, or accessibility test cases with provenance and an open license.
Create a public OBS project and package that builds your tool for supported Linux distributions with upstream links.
Publish a genuinely useful free privacy checklist, redaction template, or safety workbook that complements your tool and has standalone value.
Build a QGIS plugin that checks selected layers or exports for sensitive coordinates and metadata, then creates a safer copy.
Create a public Quarto extension for privacy, accessibility, or document checks with documentation, examples, and a license, then propose it for listing.
Publish a carefully annotated collection of trustworthy privacy, accessibility, and safety resources, including only your tool pages that genuinely fit each section.
Package your legitimate Ruby client or utility and add homepage and source metadata before pushing the gem.
Create and locally test your Runtipi app with config, Compose metadata, safe secrets, screenshots, documentation, backups, and update behavior, then submit it.
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.