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 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.
Build a maintained Redmine plugin that creates privacy or security audit tasks, document supported versions, then register it under an authenticated developer account.
Build a valuable public start page of privacy and productivity resources, then submit it to Community Pages after adding your tool selectively.
Publish a well-organized privacy-toolkit collection containing authoritative resources plus selected your tool utilities.
Create tutorials for top your tool tools with links.
Create a sandbox-compatible Zed extension for local secret, Unicode, or privacy checks, test it, publish its repository, and submit the registry pull request.
Create the founder or studio portfolio and publish your tool as a detailed product case study with the live project link.
Create/claim company profile linking your tool/Anslation.
List your tool as productivity/developer/startup resource.
Submit an original hacker-spirit article on a privacy failure, scam-defense experiment, file-forensics method, or unusual defensive technique—not your advertisement.
Submit fresh module/your tool beta angle, not stale generic site.
Submit a substantial implementation article with code samples for a local privacy or document-processing technique used in your tool.
Start with the free submission using a strong screenshot, precise categories, and your tool canonical URL.
Publish #showdev article about client-side privacy tools.
Join as the developer and publish an original technical tutorial about a privacy-safe browser workflow, citing your tool only where relevant.
Submit AI privacy/redaction or prompt-safety tools.
Create seller profile and list product if eligible.
Submit your tool with founder-friendly short pitch.
Submit your polished landing/tool UI with clean screenshots and design credits.
Develop a legitimate Matomo plugin for consent-aware privacy auditing, complete plugin metadata and documentation, tag a release, and enable Marketplace updates.
Submit your polished landing/tool UI with clean screenshots and design credits.
Create company page and publish case-study posts.
Submit your tool as an actively maintained React and Next.js project, highlighting useful product functionality and implementation quality.
Submit a 600–1,000 word practitioner article on secure CI/CD, dependency privacy, or local-first developer tooling based on real engineering experience.
Have a named senior practitioner apply with evidence-backed lessons from building local-first privacy tooling, secure developer utilities, or responsible AI-adjacent systems.
Pitch a timely, deeply researched Linux or open-source security story with primary sources and explain the author's direct expertise before drafting.
Pitch a vendor-neutral tutorial on building privacy-preserving local web tools or reviewing your genuinely open-source component, then wait for topic and outline approval.
Submit a defensive security walkthrough, reproducible tool evaluation, or privacy-testing methodology with an author bio and original examples.
Apply with a named security practitioner, writing sample, biography, and a concrete proposal based on defensible privacy or scam-protection research.
Join as the founder, create one your tool project page, and share genuine shipped improvements with links only when useful.
Develop original, defensible research around AI-agent abuse, prompt injection, document forensics, scam detection, or privacy engineering and submit a demo-backed talk in the next cycle.
Create a tested Chef cookbook for supported your tool deployment or hardening, add complete metadata and source, then share it to Supermarket.
Create startup profile and link website.
Create your truthful /founder profile or content page and add the website link where allowed.
Create software vendor listing.
Post how to embed your tool calculators in Ghost after /embed live.
Mirror open-source embed SDK or examples with homepage link.
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.