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.
Deploy your maintained MCP server from GitHub, Docker, npm, or PyPI, verify maintainer ownership, and switch it public only after production testing.
Publish a genuinely reusable privacy or accessibility lesson on your tool, give it a stable URL and open license, then add its educational metadata to MERLOT.
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.
Offer a substantial free privacy checklist, accessibility workbook, or safety template from a branded storefront and link your tool only as supporting documentation.
Host a genuine public accessibility learning or testing event and submit its dates, description and your tool event URL.
Search for and claim your real podcast, then keep its RSS-supplied website and episode metadata accurate.
Audit every your tool subdomain, stage HSTS safely, then submit the base domain only after long-term HTTPS readiness is proven.
Submit your real podcast RSS feed whose show website and episode notes naturally reference relevant tools.
Implement a scoped open-source compliance or security-assurance program, self-certify honestly, then request your tool Community of Conformance listing.
Submit your genuine podcast RSS feed or Apple Podcasts URL with accurate show-website and episode metadata.
Submit your real public podcast RSS feed whose metadata and episode notes reference the official site naturally.
Submit your tool MCP repository or public server URL, preferably after publishing it to the official MCP Registry.
First pass PWA checks, then submit the installable HTTPS app with manifest, service worker, offline behavior, icons, and screenshots.
Publish an open-source Sensu check/handler for your tool, create GitHub releases and bonsai.yml, then register it with description and tags.
Create a useful StackStorm integration or automation pack for your workflow, then submit it through the official Exchange Incubator pull-request process.
Publish a genuine browser or desktop your tool utility with screenshots, documentation and an official-site link.
Document a real participatory public-decision deployment as a Case, Method or Organization entry with evaluations and project URL.
Build a ProcessWire admin module for external URL, metadata, accessibility or security audits, register as a module author and submit it to the official directory.
List your legitimate documented API in the relevant developer category using the normal or Pro review queue.
Register a stable, genuinely research-used your tool software, service, or database with accurate maintainer and version metadata.
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.