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.
Create account, wait cooldown if new, submit your tool as platform alternative.
Request an Analyst Briefing and complete the company survey with product, customer, growth, funding, and market evidence.
Deploy your maintained MCP server from GitHub, Docker, npm, or PyPI, verify maintainer ownership, and switch it public only after production testing.
Launch your platform first; prepare maker comment and assets.
Submit platform, add competitor alternatives, verify domain email.
Publish a genuine hosted, external, or stdio MCP server exposing a small set of consent-based your tool utilities with complete metadata and documentation.
Submit the company website and concise product, market, founder, funding, and traction details for analyst review.
Package a narrow, safe your tool plugin with a public repository, validate it with the Claude plugin validator, and submit it through the in-app directory flow.
Build and test a free Dify plugin for your distinct privacy or file-analysis capability, package it, add a privacy policy, and submit the required pull request.
Create your tool company profile with accurate product, team, media, and website details, then submit it for verification.
Submit as Show HN: your tool - privacy-first toolbox people can try instantly.
Build a maintained Linear integration that sends approved your tool audit findings into issues, then submit its listing and assets.
Create a supported Mattermost plugin or app that scans user-approved text for sensitive data before sharing, with docs and a public issue tracker.
Create a vendor account and submit your tool under the closest B2B software categories with an accurate feature summary.
Submit the production web app, then verify domain ownership to manage its official listing, assets, and analytics.
Build and test your useful piece with real actions, publish the package under a unique organization scope, and maintain version compatibility.
Create a tested Ansible collection for supported your tool deployment or audit automation, complete galaxy.yml, version it, and publish with a Galaxy token.
List product under software categories.
Create a transparent human profile and publish a beginner-friendly build log or tutorial showing how one your tool privacy utility works and what tradeoffs it has.
Publish a small open demo that explains one your tool algorithm or UI pattern and add the product website to the founder profile links.
Complete the founder's developer profile, add your tool as real project experience, and publish useful privacy or security engineering posts with contextual links.
Create the founder developer profile, add your tool as a real project, and link the live product and supporting repository where applicable.
Create org/repo README linking your tool; submit to relevant awesome lists.
Audit every your tool subdomain, stage HSTS safely, then submit the base domain only after long-term HTTPS readiness is proven.
Add product and post build-in-public story with honest numbers.
Build and test a Joplin plugin that locally detects or removes sensitive note content, provide a valid manifest and publish a maintained release for discovery.
Create the founder Keybase profile and cryptographically prove control of your tool so the public identity record links the verified domain.
Register the legal company and complete a global B2B profile with accurate IT services, contact data, and your tool website.
Create maker profile and launch your tool as project.
Submit your tool widgets plugin after /embed is live.
Build a polished Alfred workflow that opens or securely sends selected content to your relevant utility, then submit it through the official Gallery forum flow.
Create a tested Auth0 Action that invokes your relevant privacy or security workflow and submit through the Marketplace Partner Portal.
Build a small founder-written knowledge blog with genuinely useful local-first privacy and file-safety guides.
Create a public digital-privacy magazine, curate reputable third-party resources, and occasionally add strong your tool guides with commentary.
Open-source a meaningful component and prepare a community-focused talk, demo, or joint stand proposal for the next FOSDEM CFP rather than a company sales presentation.
Run the website and email tests, fix IPv6, DNSSEC, HTTPS, security headers, DMARC/DKIM/SPF, STARTTLS/DANE, and RPKI gaps, then retain a 100% score.
Submit your tool as a polished tool website with its strongest public page and a concise explanation of the design system.
Build a signed Nextcloud app for local document sanitization or privacy checks, publish releases, and maintain App Store compatibility.
Publish @your tool/embed or utility package with homepage.
Submit one mature privacy tool, disclose ownership, publish its exact threat model and limitations, and engage transparently with the community review.
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.