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.
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.
Create startup profile linking canonical homepage.
Suggest one mature your tool utility through the official Codeberg issue path only if it is an easy-to-use, privacy-respecting replacement for a clearly identified invasive service.
Publish a public Webmix of trustworthy privacy resources with clearly labeled your tool tiles among independent sources.
Contribute a substantive accessibility role template, translation or toolkit improvement with useful source attribution.
Ask the TechSpot team to add your app to the downloads section, with version notes.
Create your truthful /founder profile or content page and add the website link where allowed.
Build your Trello Power-Up, register it, sign the developer agreement, and submit it.
Create a secure Docker Compose-based your tool self-hosted deployment, test it against TrueNAS app tooling and submit it to the official community catalog with useful documentation/resources.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Build and test your useful Visual Studio or Azure DevOps extension, then publish it with truthful homepage, repository and overview metadata.
Create a reproducible Tale containing your evaluation's data, code, environment, outputs, and narrative, then publish through a supported repository.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Submit a validated manifest for an installable Windows release with PackageUrl, PublisherUrl and support metadata.
Build an XWiki extension for a useful privacy, accessibility or link-audit workflow, release it as a valid XAR/JAR and publish or import it into the official extension repository.
Submit/claim software alternative listing if available.
Package your privacy, file-safety, or accessibility assistant for a supported Autodesk product.
Publish a Canadian-ready, openly licensed privacy or digital-citizenship textbook and use Contribute → Suggest a Textbook.
Create one authentic your tool brand page; link the homepage and a few key tool collections with clear labels.
Submit product for startup discovery listing.
Request a free business profile for your registered company; accreditation is a separate paid option.
Launch your real educational podcast, complete its public site, and cite relevant tools and sources in useful show notes.
Publish a polished original guide, research brief, or accessibility zine as a public document, with useful references and your relevant link inside the editorial content.
Build a substantive product-design case study covering your tool system, flows, and outcomes, then add the canonical site through supported navigation or project links.
Create an authentic your tool or founder design portfolio with substantive case studies and contextual links to shipped tools.
If the maker qualifies as a mentor, build a credible technical profile and publish a useful privacy or browser-safety tutorial.
Claim your tool’s company page and complete its verified website, company description, leadership, and employer information.
Build a robust Concrete CMS package for your privacy, accessibility or site-audit workflow, package it correctly and submit the add-on through the official marketplace manager.
Create your complete product case study and add the canonical URL naturally within project text or a linked image.
Create vendor account and submit software.
Publish your genuine benchmark, dataset, software artifact, poster, or methods report with the canonical project URL in metadata.
Claim a basic vendor profile and invite verified existing customers to leave honest reviews.
Publish your original privacy or accessibility guide and add contextual clickable links within the document.
Submit only AI-facing your tool features, not whole toolbox if too broad.
Claim your tool employer profile and verify website, headquarters, logo, company mission, and benefits.
Submit your tool landing/design pages.
Create company/software listing.
Convert your original guide into a public flipbook and add contextual links or web embeds for cited tools and resources.
Claim your tool’s page and add the verified website, social profiles, logo, location, industry, and accurate employer story.
Submit AI tools for directory inclusion.
Build a secure Jenkins plugin that performs your real CI, privacy, or accessibility workflow; host it through Jenkins project infrastructure and publish maintained releases and documentation.