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.
Build an OAuth app that audits merchant exports or product assets for privacy issues, then submit tested listing assets through the Developer Portal.
Sponsor your tool’s strongest browser or JavaScript-based developer utility with copy tailored to working JS developers.
Run a clearly disclosed campaign for your tool’s developer and security tools across relevant Changelog podcasts or newsletters.
Build a production Contentful app for your tool privacy or content checks and apply through the Marketplace submission flow.
Use a real writer or designer identity, add authored your tool work as a properly credited clip or case study, and include the personal website link in the profile.
Submit your tool best landing or tools page with a strong screenshot, accurate categories, and creator details.
Publish a reusable Defold privacy-safe logging, security, or build-audit tool.
After your tool has a genuinely open-source, well-documented public-interest component, complete the eligibility assessment and nominate that specific component.
Create a portfolio for genuine your tool product/design work and use each project's external URL field for the matching live page.
Build a genuine FIWARE-powered privacy, consent, data-space, or civic-safety solution, document its architecture and data models, then submit it for expert validation.
Create a founder or product-design portfolio with your original case study and add the canonical site as an external menu link.
Create a GDevelop extension for safe local storage, consent UX, or secret-free analytics configuration.
Build your public OAuth integration, gain qualifying installs, then submit setup docs plus support, privacy, and terms URLs.
Open-source your reusable research-focused component, archive it with a persistent identifier, and submit a software metapaper with project/code links.
Create a legitimate free or paid your tool resource or software product and publish it on a branded hosted storefront.
Apply only with a validated open-source privacy or anti-surveillance project that directly helps users facing repressive censorship or surveillance.
Apply as a General Member only if your tool will meaningfully contribute engineering or resources to open-source security.
Obtain senior approval, submit the signed endorsement materials, implement the Principles and share a real case study.
Build a genuine Salesforce package or API solution for selected-record privacy or document checks and complete its company and listing profile.
Publish your genuine Android app with accurate support/privacy URLs, data-safety declarations, assets and compatible binary.
Submit a mature macOS, iOS, or web companion app that provides your privacy workflow and links to its official product documentation.
Build a Shopware admin extension for privacy and accessibility checks on selected catalog content, media, and exports.
Build a SketchUp extension for model metadata sanitization or accessibility-ready export checks.
Build and test a Snowflake Native App for privacy-safe data inspection, create its application package and listing, pass scans, and publish through an eligible provider account.
Build a Stripe app that sends selected non-sensitive invoice or export data to your clearly scoped audit and publish complete documentation.
Place your targeted campaign in TLDR Dev, InfoSec, AI, Tech, Product, or Founders with a focused landing page.
Submit AI tools/features with multilingual description.
Submit AI-facing feature; contact for verification.
Document your tool privacy, accessibility, and tool-discovery UX as a credible case study and link to the live product from relevant case-study text.
Build your VTEX IO storefront or admin privacy utility, define billing, and submit it for homologation.
Publish a secure one-click self-hosted your tool image or cloud-init deployment with documentation and support.
Start your focused field-notes blog and publish useful privacy, accessibility, and security explainers with natural source links.
If your site's uncompressed size is under 512 KB, submit it via the GitHub repo.
Apply as a designer with a portfolio to get a public profile.
Submit a strong branding, UI or illustration project for possible feature.
Answer accessibility questions where you have real expertise and link your profile to your site.
Build or list an AI agent on the network and link your product in the agent profile.
If you serve Chinese users, submit your AI tool with a Chinese description.
Submit business/site listing if form active.
Build a production-grade Camel component for your tool APIs and propose it upstream with generated component docs and tests.