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.
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 public digital-privacy magazine, curate reputable third-party resources, and occasionally add strong your tool guides with commentary.
Create a comprehensive tutorial around a reusable privacy, file-processing, accessibility, or security technique, with your tool only as a natural example.
Publish an original, human-verified privacy or accessibility benchmark with complete methodology, provenance, schema, license, and a relevant project citation.
Publish a carefully annotated collection of trustworthy privacy, accessibility, and safety resources, including only your tool pages that genuinely fit each section.
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 an accessible, openly licensed handbook or course text with structured chapters, exercises, citations, and relevant links, then make the webbook public for directory discovery.
Create a public Tool Trust Notes newsletter site with original privacy, accessibility, founder, and engineering field reports, using your tool links only where they directly support each issue.
Pitch an original standards, accessibility, privacy, or responsible-web essay based on first-hand product engineering experience.
Curate a thoughtful public channel on local-first privacy, scam safety, or accessible-tool design, adding your tool only among diverse high-quality resources with original annotations.
Register a real founder or engineer profile and publish an original code-backed tutorial on privacy-safe browser tooling, mentioning your tool only where it is part of the implementation.
Submit a substantial implementation article with code samples for a local privacy or document-processing technique used in your tool.
Publish #showdev article about client-side privacy tools.
Write an original Japanese developer tutorial or benchmark that uses your tool and cite the relevant tool or source only where it helps readers.
Publish your original research, privacy or accessibility deck with useful citations and contextual links.
Pitch a practical privacy-by-design, accessibility, frontend-security, or local-first tooling article backed by real your tool lessons.
Pitch a rigorous developer-facing article about secure file handling, browser privacy, accessibility testing, or tool architecture.
Create company page and publish case-study posts.
Submit your founder-written product or privacy case study with concrete decisions, evidence, failures, and lessons for product practitioners.
Create your publication or original Japanese engineering article with reproducible examples and contextual links to source or documentation.
Submit a 600–1,000 word practitioner article on secure CI/CD, dependency privacy, or local-first developer tooling based on real engineering experience.
Pitch a timely, deeply researched Linux or open-source security story with primary sources and explain the author's direct expertise before drafting.
Apply with a named security practitioner, writing sample, biography, and a concrete proposal based on defensible privacy or scam-protection research.
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.