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.
Create account, wait cooldown if new, submit your tool as platform alternative.
Request an Analyst Briefing and complete the company survey with product, customer, growth, funding, and market evidence.
Complete the current CAIQ or AI-CAIQ truthfully and submit your tool real cloud service to the STAR Registry.
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 public workspace with sanitized API collections, examples, documentation, and a canonical homepage link on the publisher profile.
Launch your platform first; prepare maker comment and assets.
List your stable API with OpenAPI definitions, clear endpoints, health checks and its official website in the permitted listing field.
Submit platform, add competitor alternatives, verify domain email.
Submit the company website and concise product, market, founder, funding, and traction details for analyst review.
Package a narrow, safe your tool plugin with a public repository, validate it with the Claude plugin validator, and submit it through the in-app directory flow.
Publish your genuine Rust client, CLI, parser, or privacy library and set homepage, repository, README, license, and documentation metadata.
Create or claim your tool, add its verified website, product description, sector, founding details, team, and milestones.
Create your tool company profile with accurate product, team, media, and website details, then submit it for verification.
Upload or design your useful privacy report and add contextual external links before public sharing.
Create your original interactive privacy or accessibility guide and add relevant external actions to cited live tools.
Create a useful Godot editor add-on or privacy-safe asset pipeline tool, release it under an accepted license and submit its repository.
Build your add-on for Drive, Docs, Sheets, Gmail, or another Workspace product and publish it.
Submit as Show HN: your tool - privacy-first toolbox people can try instantly.
Register your genuine open-source component, complete its project summary and link its official homepage and source repository.
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.
Build a maintained Linear integration that sends approved your tool audit findings into issues, then submit its listing and assets.
Create a supported Mattermost plugin or app that scans user-approved text for sensitive data before sharing, with docs and a public issue tracker.
Package your real MCP server, verify its namespace, create server.json and publish it with mcp-publisher.
Register in Partner Center and publish your SaaS or Microsoft-integrated offer.
Publish your open Privacy Framework mapping, template, tutorial, or implementation tool and submit it for repository review.
Create a sequenced, classroom-ready module on practical browser privacy or accessible web testing, with learner activities, instructor notes, and your relevant resource link.
Publish your real PHP SDK or integration from a public repository and set the canonical homepage in composer.json.
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.
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.
Create or import your genuine show, keep it public, set its official Website field and publish useful episodes.
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.
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.