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 or design your useful privacy report and add contextual external links before public sharing.
Write and publish a substantial original handbook on local-first privacy, web safety, or accessible-tool engineering, including reproducible examples and relevant your tool references.
Create a sequenced, classroom-ready module on practical browser privacy or accessible web testing, with learner activities, instructor notes, and your relevant resource link.
Submit a sharp founder-authored opinion based on real privacy or security evidence discovered while building your tool.
Launch a human-reviewed Privacy & Accessibility Field Notes newsletter with original experiments, implementation lessons, and contextually relevant links to your tool resources.
Send a concise exclusive angle on your new security feature, dataset, vulnerability study, or expert commentary.
Pitch a vendor-neutral security article using original your tool tests, threat-model findings, or privacy research.
Pitch a short, beginner-friendly, human-authored accessibility post through an issue, or submit one established free your tool accessibility resource under the correct Resources category.
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 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.
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.
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.
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.
Build and test a Particle Device OS privacy, local-processing, or credential-safety library with examples, license, README, and repository URL, then publish it via the CLI.
Upload your original research-backed guide and reference relevant tools naturally in the document.
Create a useful public learning list with annotations about privacy, accessibility, and scam prevention, placing relevant your tool resources beside independent references.
Propose a vendor-neutral, reproducible cloud-native security tutorial or case study, then write it in Markdown and submit the draft by pull request after community discussion.
If the maker qualifies as a mentor, build a credible technical profile and publish a useful privacy or browser-safety tutorial.
Publish your original privacy or accessibility guide and add contextual clickable links within the document.
Publish an original, useful privacy or digital-safety guide and mention your resource only when it directly supports the guidance.
Apply with a genuine technical portfolio and propose an original mobile privacy tutorial aligned with Kodeco's listed subject areas.
Build a focused public portfolio for your real designer/team and publish one detailed product, privacy, or accessibility design case study with the project link.
Publish an original, media-rich tutorial or founder case study with useful screenshots and your contextual reference, using a complete real profile.
Run a clearly disclosed campaign for your tool’s developer and security tools across relevant Changelog podcasts or newsletters.
Use a real writer or designer identity, add authored your tool work as a properly credited clip or case study, and include the personal website link in the profile.
Upload an unpublished evaluation study or research poster about your privacy or accessibility method with supporting code and data.
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.