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.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Package your stable CLI or self-hosted helper as a tested APKBUILD, add it under Alpine testing and submit an aports merge request with accurate project metadata.
Submit a tested your app for compatible Amazon devices with complete descriptions, support links, privacy details and store assets.
Join the writer community and publish data science or ML articles, which go through a light editorial review.
Answer Android questions properly and add your site to your profile.
Publish an original UI/UX visual case study showing your tool interaction design, accessibility states, and design process, with a contextual project URL.
Submit your original -related technical paper and cite your tool only where it is genuinely the software or study subject.
Answer Mac and iPhone questions in full, linking your own page only when it adds detail the answer cannot hold.
If your tool ships a real tool that reads, validates, generates, visualizes, or otherwise supports AsyncAPI documents, add the required .asyncapi-tool metadata file and submit it for the public tools dashboard.
Build and openly maintain a Backstage plugin that gives platform teams your real workflow, then announce it through the community-plugins process and meet directory metadata requirements.
Build a deployable edge privacy utility or reusable block, add balena.yml metadata, public source, configuration and multi-device tests, then publish it on balenaHub.
Package your maintained self-hosted deployment as a Juju charm with canonical documentation, source, and support links.
Build a maintained Cinnamon applet that launches or monitors your useful local privacy workflow and submit it by pull request.
Create an age-appropriate digital-citizenship or privacy FlexBook chapter with practical your tool exercises.
Create and fully test your Docker Compose service template, add metadata, logo, and documentation, then submit it to Coolify's next branch.
Upload a finished HTML5 game through the developer portal; it goes through a playtest phase before a full release, and the game page credits you as the developer.
Apply as a designer and publish an original template, icon pack or printable that genuinely complements your workflow.
Apply with a strong portfolio and sell your original -compatible template or design kit, using permitted shop branding and product documentation.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Build a useful dbt package for privacy classification, redaction tests or data-governance macros and add it to the Hub index by pull request.
If your component is open source and genuinely targeted at public administration, add valid publiccode.yml metadata so the catalogue crawler can discover it.
Participate as a real developer with original lessons and honest build stories; reference your tool only if a specific discussion genuinely calls for the working example.
Build a generic DHIS2 health-data de-identification or permission-audit app and submit it to App Hub for core-team review.
Use a real developer profile and contribute tested solutions on Discourse integrations, accessibility, or privacy only when the team has genuine implementation experience.
If your tool documentation genuinely runs on Docusaurus, add the polished docs site through the official showcase discussion.
Build your Ecwid app, propose it, sign the partner agreement, and submit it for review with website and support links.
Create a structured open handbook on digital privacy or accessibility with reproducible your tool labs.
Create a genuinely useful package of tested security-header, HTML-meta, JSON-LD and webhook snippets with your tool validation examples, then submit it to the official Hub.
Submit your genuine -maintained database, reusable reporting standard, or data policy with complete stewardship metadata.
Create a COPR project, build maintained RPMs and add your official homepage and package documentation.
Contact them to have your Windows or Mac software added to the catalogue.
Send your Windows or Mac software for review via their submission or contact page.
Publish privacy/helper extension.
Submit a mature graphical Linux your app with verified metadata, screenshots, homepage and source links.
Build an open-source FreeCAD privacy/metadata or document-cleanup workbench, add package.xml metadata, and submit it to the curated Addons index.
Release your genuinely free-software desktop or self-hosted component with free documentation and transparent downloads, then submit a custom directory entry.
Publish a substantive Glide template for privacy-safe records, evidence organization, or accessibility audits and link its your tool documentation where permitted.
Create a narrowly useful GNOME Shell extension, provide metadata and homepage or source information, and submit it for review.
Ship a genuinely useful Gradle plugin for your developer check such as secret, licence, or configuration auditing; publish with your tool documentation and support URLs.
Build a GRASS GIS add-on for location anonymization, sensitive-zone generalization, or privacy-safe geospatial export, include docs and tests, then submit it to the official add-ons repository.
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.