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.
Create a founder expert profile and submit substantive talks about privacy-first tools, accessibility or web security.
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.
Create a genuine founder profile and share a useful build story or tutorial with a relevant link.
Create a useful StackStorm integration or automation pack for your workflow, then submit it through the official Exchange Incubator pull-request process.
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.
Publish a maintained Terraform provider for your tool stable API, or a genuinely reusable deployment module, with signed releases, generated documentation, examples, tests, and semantic versions.
Add your tool’s real company, founder, and team structure with website and role details to create a trustworthy organization profile.
Build a production-quality Traefik middleware plugin for your privacy or security use case and publish it to the public catalog.
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 and publish a real Crossplane provider, function, configuration or add-on that integrates your capability and exposes accurate project documentation.
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.
Submit your tool widgets plugin after /embed is live.
Package your reproducible privacy or redaction workflow, join or create a team, and register it with rich metadata and source links.
Submit your public API with docs link, SDKs and authentication details.
Build your working automation Actor, publish it to the Store and include contextual project/documentation links.
Package your legitimate desktop app as an official AppImage, then file the requested issue or pull request for inclusion.
If your property genuinely uses Astro, use the Submit site action to propose it for the public showcase.
Submit only after public privacy policy and client-side privacy proof.
Suggest your JavaScript or TypeScript project through their GitHub issue process.
Curate a tagged public collection of authoritative privacy, accessibility, and safety resources with your tool included only where substantively relevant.
Register your genuinely life-science-focused resource with stable homepage, scientific operations, inputs, outputs, licence, and documentation.
Build your useful Budibase component or data-source plugin, publish the package or repository, and seek inclusion in community plugin resources.
Create a tested CapRover one-click definition for your real self-hosted service and contribute it to the linked official community repository.
Create a tested Chef cookbook for supported your tool deployment or hardening, add complete metadata and source, then share it to Supermarket.
Release a genuine Clojure or JVM client library with a POM, description, homepage and source metadata.
Create your public package repository for genuine releases and complete its namespace, description, licence and source/homepage metadata.
Publish a genuine iOS or macOS your tool SDK and set homepage/source URLs in its podspec.
Build a genuine CWL validator, security tool, or implementation and propose its inclusion with compliance evidence.
Create a real developer profile, publish your original engineering tutorial or project, and join only relevant privacy or developer communities.
Build a functional Contao bundle for your site-audit use case, publish tagged releases on Packagist with contao-bundle and manager-plugin metadata, and let the official index discover it.
Publish a genuine Perl module or CLI through PAUSE with project URLs and clear distribution documentation.
Submit relevant your tool utilities under AI, web, or developer categories.
Share Cursor rules or list your MCP server, linking back to your project.
Submit your site if it has a polished dark design.
Build a genuine free challenge solution, publish the deployed project and repository, and use the finished privacy or accessibility implementation as a portfolio case study.
Enter a relevant live hackathon with your working project, complete its story and demo, and include the project website where allowed.
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.