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.
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.
Submit the company website and concise product, market, founder, funding, and traction details for analyst review.
Create a valid Helm, OPA, Tekton or supported repository for your deployment and add it through the control panel.
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 original interactive privacy or accessibility guide and add relevant external actions to cited live tools.
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.
Register in Partner Center and publish your SaaS or Microsoft-integrated offer.
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.
Publish and maintain your genuine Ruby client, CLI, or integration gem with accurate homepage, source, documentation, and changelog metadata.
Create or import your genuine show, keep it public, set its official Website field and publish useful episodes.
Build your Forge-based integration for Jira or Confluence, create a Marketplace Partner profile, and submit a compliant public listing.
Submit a sharp founder-authored opinion based on real privacy or security evidence discovered while building your tool.
Publish your real privacy, redaction, or local-AI demo Space and add your canonical URL in its README/metadata.
Publish your real episode and add contextual links to resources actually discussed in its show notes.
Import public your tool developer documentation, add the build config and expose versioned, searchable docs with canonical project links.
Submit your tool with homepage URL, privacy-first positioning, logo, screenshots and accurate pricing.
Create a substantial free or paid course on practical browser privacy and accessibility auditing, with real demonstrations, exercises, and your honest company or instructor profile.
Create a vendor portal account and request your tool under the closest eligible Gartner market category.
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.
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.
Publish a small open demo that explains one your tool algorithm or UI pattern and add the product website to the founder profile links.
Create a complete founder and startup profile for your tool and participate in relevant founder discussions or connection requests.
Complete the founder's developer profile, add your tool as real project experience, and publish useful privacy or security engineering posts with contextual links.
Build a DokuWiki privacy, redaction, accessibility, or secure-export plugin, publish its code and create the canonical plugin page used by the extension directory.
Publish a functional Eclipse plugin for your developer use case, then create a complete marketplace listing with official support and source links.
Offer a substantial free privacy checklist, accessibility workbook, or safety template from a branded storefront and link your tool only as supporting documentation.
Create a functional Framer plugin for accessibility, metadata, responsive-content, or privacy checks and publish it with your tool documentation.
Complete a relevant accessibility or privacy-themed challenge, submit its real live URL and public repository, and add your tool only as maker context or a case-study link.
Create the founder developer profile, add your tool as a real project, and link the live product and supporting repository where applicable.
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.