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 a functional Hexo plugin for your relevant capability, publish the package, then add its record to Hexo's official plugin data repository.
Audit every your tool subdomain, stage HSTS safely, then submit the base domain only after long-term HTTPS readiness is proven.
Add product and post build-in-public story with honest numbers.
Build and test a Joplin plugin that locally detects or removes sensitive note content, provide a valid manifest and publish a maintained release for discovery.
Create the founder Keybase profile and cryptographically prove control of your tool so the public identity record links the verified domain.
Register the legal company and complete a global B2B profile with accurate IT services, contact data, and your tool website.
Submit your real podcast RSS feed whose show website and episode notes naturally reference relevant tools.
Build a Singer SDK tap that incrementally extracts your tool audit runs and findings, then add it through MeltanoHub's official issue-assisted or self-service contribution path.
Create your functional Node-RED node, publish it to npm, and add it to the Flow Library with documentation and support metadata.
Publish a real .NET library or CLI package with ProjectUrl, readme, repository and license metadata.
Build an installable privacy or accessibility NVDA add-on and submit it through the official add-on datastore workflow.
Build a unique and useful Obsidian plugin, create valid releases and submit it to the community plugin directory.
Add or claim your genuine open-source project and complete its description, code locations, tags and official homepage.
Publish your useful editor extension whose marketplace metadata links to its homepage and documentation.
Implement a scoped open-source compliance or security-assurance program, self-certify honestly, then request your tool Community of Conformance listing.
Add native OpenTelemetry support or build your useful instrumentation or utility, then submit its registry metadata and documentation links.
Build a useful Sublime Text integration for your developer workflow, document it publicly and submit the package for review.
Create maker profile and launch your tool as project.
Build your tool triggers/actions, submit them to the public registry by GitHub PR, and address review feedback.
Build a Pipedrive OAuth integration for safe note export, duplicate cleanup, or PII auditing and submit your unique listing.
Package a real embedded privacy or security library for supported boards, add complete PlatformIO manifest and examples, test it, and publish it publicly.
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.
Publish your stable module or script with ProjectURI, LicenseURI, tags, help and examples.
Propose your qualifying open-source privacy project through the official contribution process.
Publish your Dart package with homepage, repository, issue tracker, documentation and a complete readme.
Build a public RingCentral integration around call-note privacy or safe file sharing and complete the profile with your tool documentation, privacy, and support links.
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 founder expert profile and submit substantive talks about privacy-first tools, accessibility or web security.
Upload an original conference-quality PDF deck explaining privacy-safe tooling or accessibility testing, with a useful description, correct category, references, and an honest profile link.
Create a genuine founder profile and share a useful build story or tutorial with a relevant link.
Join a relevant chapter, complete the founder profile, attend suitable events, and share your tool only in genuine networking context.
Publish an original dashboard using public your tool benchmark or ecosystem data and add an appropriate project permalink in workbook details.
Publish a maintained Terraform provider for your tool stable API, or a genuinely reusable deployment module, with signed releases, generated documentation, examples, tests, and semantic versions.
Add your tool’s real company, founder, and team structure with website and role details to create a trustworthy organization profile.
Build a production-quality Traefik middleware plugin for your privacy or security use case and publish it to the public catalog.
Build a TYPO3 backend extension for selected content or media PII, metadata, and accessibility checks.
Create your Umbraco integration package and point its NuGet project URL plus documentation to your tool.
Register your concrete ongoing initiative with measurable milestones, dates, resources, SDG targets, partners and website evidence.
Build a production Webex integration or bot for deliberate sharing of your tool checklists or sanitized files, then submit its branded App Hub profile.
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.