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.
Publish your Dart package with homepage, repository, issue tracker, documentation and a complete readme.
Build a public RingCentral integration around call-note privacy or safe file sharing and complete the profile with your tool documentation, privacy, and support links.
Upload an original conference-quality PDF deck explaining privacy-safe tooling or accessibility testing, with a useful description, correct category, references, and an honest profile link.
Join a relevant chapter, complete the founder profile, attend suitable events, and share your tool only in genuine networking context.
Publish an original dashboard using public your tool benchmark or ecosystem data and add an appropriate project permalink in workbook details.
Build a TYPO3 backend extension for selected content or media PII, metadata, and accessibility checks.
Create your Umbraco integration package and point its NuGet project URL plus documentation to your tool.
Register your concrete ongoing initiative with measurable milestones, dates, resources, SDG targets, partners and website evidence.
Build a production Webex integration or bot for deliberate sharing of your tool checklists or sanitized files, then submit its branded App Hub profile.
Build a tool that genuinely interacts with Wikimedia, publish accurate toolinfo.json metadata, and register it through Toolhub UI, crawler, or API.
Create and maintain a PKGBUILD for your installable Linux release with the upstream URL and correct source checksums.
Build an OAuth Asana component that launches your audit or attaches a generated report, then submit complete company and support details.
Claim and verify your tool’s legitimate business entity or location and keep name, address, phone, and website consistent.
If your tool ships a legitimate genomics or bioinformatics utility, package it for R with complete vignettes and submit it for review.
Build a Bitrise Step that runs your tool secret, privacy, or accessibility checks on explicitly chosen build artifacts.
Build a practical Blender add-on for media privacy, metadata or workflow automation and upload its tested extension package with documentation.
Build a Canva app that sends chosen design assets to your accessibility, metadata, or privacy check and returns useful results inside Canva.
Package your genuine Windows desktop or CLI release and set project, documentation and package-source URLs.
Publish your tested public orb for privacy, secret, or document-safety checks with a homepage URL and usage examples.
Build a Kafka Connect source or sink that sends only explicitly selected records to your tool privacy or redaction checks and returns structured results.
Create a real designer profile and publish your original UX/accessibility case study with process artifacts, outcomes, and the official project link.
Submit a useful R package with URL and BugReports metadata pointing to its official project and documentation pages.
Create a functional Drupal integration or reusable module and publish a maintained project page with documentation and official links.
Create a comprehensive tutorial around a reusable privacy, file-processing, accessibility, or security technique, with your tool only as a natural example.
Create your company profile using your official email.
Tag and publish a public Go module with module docs and repository metadata so pkg.go.dev indexes it.
Build a panel, data-source or app plugin, validate and package it, then submit it with project links and test data.
Document a real hardware, privacy or security build that uses your tool, including schematics, progress logs and a natural official-project link.
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.
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.
Build your standalone integration package with tests and submit the required LangChain documentation PR.
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.
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.