<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Safak Tepecik</title>
    <description>The latest articles on DEV Community by Safak Tepecik (@safak_tepecik_bc95fdaea2b).</description>
    <link>https://dev.to/safak_tepecik_bc95fdaea2b</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4103946%2Fe01c58b1-2cc5-47ad-a661-44e2325885a0.png</url>
      <title>DEV Community: Safak Tepecik</title>
      <link>https://dev.to/safak_tepecik_bc95fdaea2b</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/safak_tepecik_bc95fdaea2b"/>
    <language>en</language>
    <item>
      <title>I measured the link value of 101 directories and launchpads. One free dofollow link came out of it.</title>
      <dc:creator>Safak Tepecik</dc:creator>
      <pubDate>Tue, 08 Sep 2026 13:13:39 +0000</pubDate>
      <link>https://dev.to/safak_tepecik_bc95fdaea2b/i-measured-the-link-value-of-101-directories-and-launchpads-one-free-dofollow-link-came-out-of-it-4pj2</link>
      <guid>https://dev.to/safak_tepecik_bc95fdaea2b/i-measured-the-link-value-of-101-directories-and-launchpads-one-free-dofollow-link-came-out-of-it-4pj2</guid>
      <description>&lt;p&gt;Everyone who ships a side project eventually reads the same advice: submit it to directories, list it on launchpads, get your backlinks. I wanted to know how much of that advice survives contact with the actual HTML, so I spent a few days measuring instead of guessing. The result is a dataset of 101 platforms, and it is less encouraging than the advice suggests.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I actually measured
&lt;/h2&gt;

&lt;p&gt;A backlink only passes authority if four things are true at the same time, and most write-ups on this topic check exactly one of them. So I checked all four for every platform.&lt;/p&gt;

&lt;p&gt;The first layer is the &lt;code&gt;rel&lt;/code&gt; attribute on the outgoing link itself. A link carrying &lt;code&gt;nofollow&lt;/code&gt;, &lt;code&gt;sponsored&lt;/code&gt; or &lt;code&gt;ugc&lt;/code&gt; is a visit, not an endorsement. The second layer is the &lt;code&gt;meta robots&lt;/code&gt; element of the page holding that link, because a page marked &lt;code&gt;noindex&lt;/code&gt; never enters the index and its links are therefore moot. The third layer is the &lt;code&gt;X-Robots-Tag&lt;/code&gt; HTTP header, which can do the same job as the meta element while staying invisible in the page source. The fourth layer only applies when the platform routes outgoing clicks through its own redirector, and there the question is whether that redirect path is blocked in &lt;code&gt;robots.txt&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Two rules kept the data honest. I always measured an existing listing belonging to somebody else, never my own, so that the result describes the platform rather than my account. And when a page could not be retrieved at all, I recorded it as not verifiable rather than inferring a verdict from a screenshot or a blog post.&lt;/p&gt;

&lt;h2&gt;
  
  
  The headline number
&lt;/h2&gt;

&lt;p&gt;Of the 101 platforms in the dataset, ten carry a genuinely dofollow link on an indexable page, and exactly one of those ten looked reachable without paying or trading something for it. That one came with a condition I did not see until I tested it on my own account, and I come back to it at the end. Thirteen actively devalue the link with a &lt;code&gt;nofollow&lt;/code&gt; attribute. Three sit on pages that are &lt;code&gt;noindex&lt;/code&gt; outright, so the attribute never gets to matter. Ten deliver no link to the listed vendor's website at all. The detail page mentions the product, links its own social channels and the CDN, and simply never points at the company behind it.&lt;/p&gt;

&lt;p&gt;The remaining sixty-five came back as not verifiable, and I want to be precise about what that means, because it is the single most important caveat in this dataset. Seventeen of them answered a plain HTTP request with a 403, which is bot defence rather than an SEO decision. Others are JavaScript applications whose links only exist in the rendered DOM. Not verifiable is not a synonym for bad; it means I refused to write down a number I had not seen.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pattern behind the paid nine
&lt;/h2&gt;

&lt;p&gt;Nine of the ten dofollow results do not form a group of generous platforms. They form a price list.&lt;/p&gt;

&lt;p&gt;StartupBase states in its own comparison table that the backlink is "not included" in the free tier, and the free listing additionally expects a badge on your site. Its paid tier at 39 USD advertises the dofollow link as the product. MicroLaunch sells the same thing at the same price. Fazier wants either 29 USD or a badge plus three public comments on other launches. OpenTools has no free path at all; the submit button is labelled "Continue to Subscription". Onlinestreet, a German directory, gives one link to your homepage for free and three links for 49 euro a month.&lt;/p&gt;

&lt;p&gt;So the honest summary of the dofollow column is not "nine platforms give you a link". It is "nine platforms sell you a link, and I measured the version somebody else had already bought." The tenth is the developer profile described further down.&lt;/p&gt;

&lt;h2&gt;
  
  
  The mistake I made halfway through, and how it was caught
&lt;/h2&gt;

&lt;p&gt;For the first half of the measurements I assumed that a dofollow link found on a stranger's listing proved the platform hands out dofollow links. That assumption is wrong, and I only noticed because of a listing I happened to own.&lt;/p&gt;

&lt;p&gt;On Cylex, a German business directory, my own free listing links my site with &lt;code&gt;rel="nofollow"&lt;/code&gt;. On the same day, two other Cylex listings linked their companies with no &lt;code&gt;rel&lt;/code&gt; attribute at all. Same platform, same day, opposite results. The difference is not technical, it is commercial: the free entry gets the devalued link and the paid entry gets the real one.&lt;/p&gt;

&lt;p&gt;This means a measurement taken on somebody else's listing tells you what the platform is capable of, not what the free path delivers. Every claim about a free backlink needs a second piece of evidence, namely that the listing you measured was itself free. Half the SEO advice circulating about directories fails exactly here, and mine did too until that one entry contradicted me.&lt;/p&gt;

&lt;h2&gt;
  
  
  Browser extension stores are not a backlink strategy
&lt;/h2&gt;

&lt;p&gt;This one deserves its own paragraph, because it is repeated constantly and it is measurably false.&lt;/p&gt;

&lt;p&gt;The Chrome Web Store links the developer's website with &lt;code&gt;rel="ugc nofollow"&lt;/code&gt;. The Edge Add-ons store does not put the vendor's website into the delivered HTML at all. Firefox AMO routes the link through &lt;code&gt;prod.outgoing.prod.webservices.mozgcp.net&lt;/code&gt; and attaches &lt;code&gt;nofollow&lt;/code&gt; on the way out; eleven of the twelve outgoing links on the listing I checked carried it.&lt;/p&gt;

&lt;p&gt;Publishing an extension is a fine way to reach users and to distribute your work. It is not a way to acquire authority, and the three largest stores agree on that.&lt;/p&gt;

&lt;h2&gt;
  
  
  The large knowledge platforms are settled
&lt;/h2&gt;

&lt;p&gt;Wikipedia, Wikimedia Commons and Wikidata devalue every external reference, which is well known but still worth having in a table. Less commonly stated: GitHub, Hugging Face and Zapier do the same. A GitHub repository's homepage field carries &lt;code&gt;nofollow&lt;/code&gt;, and so does the link in a Hugging Face model card.&lt;/p&gt;

&lt;p&gt;These platforms are still worth being on, because a language model reading the web forms its picture of your project from them. That is a different goal from passing authority, and conflating the two is how people end up disappointed by a strategy that worked exactly as designed.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did survive
&lt;/h2&gt;

&lt;p&gt;Two free channels held up under the same four-layer test, and both are ordinary rather than clever.&lt;/p&gt;

&lt;p&gt;The first is a developer profile on this very platform, and it comes with a catch I only found by making an account of my own.&lt;/p&gt;

&lt;p&gt;The website field on an established dev.to profile renders as &lt;code&gt;rel="noopener me"&lt;/code&gt;, with no &lt;code&gt;meta robots&lt;/code&gt; element and no &lt;code&gt;X-Robots-Tag&lt;/code&gt;. I checked seven profiles, four of them ordinary community members rather than well-known accounts, and all seven behaved that way.&lt;/p&gt;

&lt;p&gt;Then I created a profile, filled in the same field, and measured my own. It renders as &lt;code&gt;rel="noopener me ugc"&lt;/code&gt;. The &lt;code&gt;ugc&lt;/code&gt; is the difference, and &lt;code&gt;ugc&lt;/code&gt; devalues the link just as &lt;code&gt;nofollow&lt;/code&gt; does. On the same day, re-measuring three of the established profiles still returned &lt;code&gt;rel="noopener me"&lt;/code&gt; without it, so this is not a platform-wide change. A new account gets the devalued version; an account with standing does not.&lt;/p&gt;

&lt;p&gt;I do not yet know what removes it, and I am not going to guess. The obvious candidates are published posts, account age, or some reputation threshold. That is a measurable question and I will re-measure my own profile once it has posts on it. For now the honest statement is narrower than the one I set out to make: dev.to &lt;em&gt;can&lt;/em&gt; give a free dofollow profile link, and it does not give one to a brand-new account.&lt;/p&gt;

&lt;p&gt;Hashnode looks similar from the outside and does not hold up. Its profile website field carries &lt;code&gt;nofollow ugc&lt;/code&gt;, and four of the six profiles I sampled were &lt;code&gt;noindex&lt;/code&gt; at the page level. About.me devalues the link on both profiles I could retrieve.&lt;/p&gt;

&lt;p&gt;The second is editorial, and in my case it is also the most relevant one. German university career services publish curated link lists for their students, and those lists do not use &lt;code&gt;nofollow&lt;/code&gt;. A careers page at the University of Würzburg links two photographers with &lt;code&gt;rel="noreferrer"&lt;/code&gt; only. Hildesheim links about thirty external career resources the same way. Frankfurt's writing-resources page links dozens of third-party tools with no &lt;code&gt;rel&lt;/code&gt; attribute at all. None of those pages carries a robots restriction on any of the four layers.&lt;/p&gt;

&lt;p&gt;Getting onto a list like that requires being genuinely useful to the students reading it, which is slower than paying 39 USD and considerably more durable.&lt;/p&gt;

&lt;h2&gt;
  
  
  The dataset
&lt;/h2&gt;

&lt;p&gt;The full table is published under CC BY 4.0 as CSV and JSON, one row per platform, each with the exact evidence URL I measured, the four layers separately, and the verdict. If a row says not verifiable, the reason is in the row. I would rather hand over a dataset with sixty-five honest gaps than one with sixty-five confident guesses.&lt;/p&gt;

&lt;p&gt;The measurements were taken on 31 August 2026. Platforms change their link handling without announcing it, so treat every row as a dated observation rather than a permanent property. If you re-measure one and get a different answer, that is a finding, not a contradiction.&lt;/p&gt;

&lt;p&gt;I collected this while working on &lt;a href="https://profilfoto-ki.de" rel="noopener noreferrer"&gt;profilfoto-ki.de&lt;/a&gt;. The files are at&lt;br&gt;
&lt;a href="https://www.profilfoto-ki.de/downloads/linkwert-verzeichnisse-2026-08.csv" rel="noopener noreferrer"&gt;/downloads/linkwert-verzeichnisse-2026-08.csv&lt;/a&gt;&lt;br&gt;
and &lt;a href="https://www.profilfoto-ki.de/downloads/linkwert-verzeichnisse-2026-08.json" rel="noopener noreferrer"&gt;/downloads/linkwert-verzeichnisse-2026-08.json&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>indiehackers</category>
      <category>data</category>
    </item>
  </channel>
</rss>
