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.
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.
Submit a useful AI privacy, local processing, prompt-security, or responsible-tooling tutorial with reproducible examples.
Build a small founder-written knowledge blog with genuinely useful local-first privacy and file-safety guides.
Create a comprehensive tutorial around a reusable privacy, file-processing, accessibility, or security technique, with your tool only as a natural example.
Pitch an original standards, accessibility, privacy, or responsible-web essay based on first-hand product engineering experience.
Join as the developer and publish an original technical tutorial about a privacy-safe browser workflow, citing your tool only where relevant.
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.
Apply with a code-heavy observability, Node, Ruby, Python, or Elixir tutorial using your real engineering problem as the case study.
Launch a consistent Trustworthy Tools digest that mixes independent sources with occasional relevant your tool research, adding original commentary to every selected link.
Submit your founder-written product or privacy case study with concrete decisions, evidence, failures, and lessons for product practitioners.
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.
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.
Pitch a reproducible tutorial about CI checks for client-side privacy, dependency security, or accessible web tools, with your tool only as a genuine example.
Apply with a named security practitioner, writing sample, biography, and a concrete proposal based on defensible privacy or scam-protection research.
Join the writer community and publish data science or ML articles, which go through a light editorial review.
If you blog about PostgreSQL, register your feed so your Postgres posts are syndicated on the planet.
Ask to have your Python-tagged blog feed added so your Python posts appear on the aggregator.
Upload a guide, report or catalog as a public publication and add your website to the profile and description.
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.
Publish your original privacy or accessibility guide and add contextual clickable links within the document.
Post technical/product story with canonical link.
Publish your product or developer docs from a Git repo on the free tier and link to your site from the docs.
Host your API or product documentation on ReadMe and link back to your main site and app.
Pitch/write article about privacy-first browser tools.
Apply with a genuine technical portfolio and propose an original mobile privacy tutorial aligned with Kodeco's listed subject areas.
Run a clearly disclosed campaign for your tool’s developer and security tools across relevant Changelog podcasts or newsletters.
Submit a link to an Android article, library or tool through the site.
Email the curator a link to a useful DevOps article, tool or talk.
Reply to an issue or contact the editor with a link to a useful Go article or library you made.
Use the newsletter's link submission option to suggest a useful iOS or Swift article or tool.
Submit a link to a Kotlin article, talk or library you published.
Submit your Laravel tutorial or package through the site's community links or tip options.
Send the editor a link to a strong Node.js article, package or release.
Send the editor a link to a useful Postgres article, extension or tool.
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.