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.
Request an audit for your mature open-source security component, providing maintainer contacts, architecture, threat model, scope, tests, and a remediation commitment.
Build a genuine Kubernetes Operator for your self-hosted service, test its bundle and submit it through Community Operators.
Publish your real PHP SDK or integration from a public repository and set the canonical homepage in composer.json.
Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.
Publish your well-documented public API workspace with runnable collections, examples and the canonical API website.
Publish your real Python SDK, CLI, or integration package and set Homepage, Documentation, Source, and Issues URLs in package metadata.
Publish a secure, documented container for your open service and add its official site in the repository description or README where supported.
Package a genuinely useful open model or reproducible AI utility, publish it publicly with examples and cite your related documentation naturally.
Publish and maintain your genuine Ruby client, CLI, or integration gem with accurate homepage, source, documentation, and changelog metadata.
Build your production-ready Slack app for safe file/text utilities, then submit it from the app configuration page for Marketplace review.
Make your tool generate or consume valid SPDX, document validation, then file the requested supplier-information issue with its canonical URL.
Create or import your genuine show, keep it public, set its official Website field and publish useful episodes.
Register and apply with accurate your tool entity, innovation, workforce and website details if Odisha criteria are met.
Create a vendor account and submit your tool under the closest B2B software categories with an accurate feature summary.
Search for your tool, verify ownership with official-domain OTP, and claim or request an accurate privacy/security/AI profile.
Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.
Submit the production web app, then verify domain ownership to manage its official listing, assets, and analytics.
First publish a fresh, human-authored accessibility case study or tutorial with real lessons and disabled-user perspective where available, then suggest that single article by email.
Email your strongest developer-focused feature with a self-service demo, documentation, privacy model, and concise reason it is novel.
Propose a text-based, interactive course on web privacy, security headers, local-first tools, or accessible frontend testing, with practical code exercises and clear outcomes.
Send a concise exclusive angle on your new security feature, dataset, vulnerability study, or expert commentary.
Submit your tool with homepage URL, privacy-first positioning, logo, screenshots and accurate pricing.
Pitch a vendor-neutral security article using original your tool tests, threat-model findings, or privacy research.
Submit your tool with homepage URL, privacy-first positioning, logo, screenshots and accurate pricing.
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.
Submit your tool with homepage URL, privacy-first positioning, logo, screenshots and accurate pricing.
Submit a useful AI privacy, local processing, prompt-security, or responsible-tooling tutorial with reproducible examples.
Submit one polished your tool web utility that is directly useful to front-end developers, programmers, or designers, with a precise one-line explanation and working URL.
Build and test your useful piece with real actions, publish the package under a unique organization scope, and maintain version compatibility.
Build a privacy-safe macOS Alfred workflow that opens or runs useful your tool actions, publish it on the forum, gather feedback, and seek Gallery inclusion.
Build a useful Anki privacy, study-safety, or accessibility add-on, package it as .ankiaddon, and upload it through AnkiWeb.
Create a tested Ansible collection for supported your tool deployment or audit automation, complete galaxy.yml, version it, and publish with a Galaxy token.
Create your real Airflow provider with hooks/operators and documentation metadata, publish it, then add it to Airflow’s Ecosystem page by PR.
Recommend your official API with its documentation URL, concise Markdown description, category, and technical details.
When your tool exposes a stable public API, host an official OpenAPI definition at a permanent URL and submit it with accurate ownership, category, logo, and metadata.
Submit your mature self-hosted edition using the required YAML entry and canonical website/source links.
Build a pipeline plugin that runs your tool checks on selected artifacts and posts configurable pass, warn, or fail annotations.
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.
Build an original interactive demo of your utility, document the use case in Pen Details, and add your tool as one of the public profile links.
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.