<?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: Sam</title>
    <description>The latest articles on DEV Community by Sam (@gamesprig).</description>
    <link>https://dev.to/gamesprig</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%2F4257401%2F1bb60656-ffa5-4fd8-8512-4ffe08a80daa.png</url>
      <title>DEV Community: Sam</title>
      <link>https://dev.to/gamesprig</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/gamesprig"/>
    <language>en</language>
    <item>
      <title>I sent 48 cold emails for backlinks. Zero replies, six bounces.</title>
      <dc:creator>Sam</dc:creator>
      <pubDate>Sat, 21 Nov 2026 13:43:12 +0000</pubDate>
      <link>https://dev.to/gamesprig/i-sent-48-cold-emails-for-backlinks-zero-replies-six-bounces-5b79</link>
      <guid>https://dev.to/gamesprig/i-sent-48-cold-emails-for-backlinks-zero-replies-six-bounces-5b79</guid>
      <description>&lt;p&gt;I sent 48 cold emails in three days trying to get my site listed somewhere. Zero positive replies. Six bounces. Three offers to pay.&lt;/p&gt;

&lt;p&gt;I'm writing this up because the "how to get backlinks" advice I read before starting was almost entirely wrong about what would happen, and the numbers are more useful than the advice.&lt;/p&gt;

&lt;h2&gt;
  
  
  The shape of the attempt
&lt;/h2&gt;

&lt;p&gt;The site is a free browser game portal — no downloads, no accounts, no paywall. The target was any page that already lists similar sites, plus directories and teacher/parent resource pages.&lt;/p&gt;

&lt;p&gt;48 emails over three days, sent from a normal Gmail account, each one written by hand, each referencing something specific on the recipient's page.&lt;/p&gt;

&lt;p&gt;Results:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Outcome&lt;/th&gt;
&lt;th&gt;Count&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Positive reply&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Paid offer (guest post / listing fee)&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Auto-reply / "we'll get back to you"&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hard bounce&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Silence&lt;/td&gt;
&lt;td&gt;38&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  The bounces are three different problems
&lt;/h2&gt;

&lt;p&gt;This was the most useful thing I learned, because I'd assumed "bounce" was one failure mode.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Address doesn't exist.&lt;/strong&gt; Two cases. Fine, delete and move on.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. The recipient's server rejects the sender.&lt;/strong&gt; Two cases, and this one is worse than it looks. The message is not "no such user" — it's a spam verdict on &lt;em&gt;me&lt;/em&gt;. A Gmail address sending near-identical cold mail to strangers gets filtered at the server level, and that reputation is shared across everything else I send from that account. Continuing to increase volume makes this worse, not better.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Their mail server is unreachable.&lt;/strong&gt; Two cases. One domain's MX didn't answer on either IPv4 or IPv6 for a day. Nothing to fix on my side.&lt;/p&gt;

&lt;p&gt;So: 12.5% bounce rate, and only a third of it is my fault in a way I can fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the three paid offers cost
&lt;/h2&gt;

&lt;p&gt;For the record, since it's useful for calibration:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;$65 for a "sponsored mention" in a listicle&lt;/li&gt;
&lt;li&gt;$149 for a guest post&lt;/li&gt;
&lt;li&gt;$50/month for a directory listing&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All three were cheap, all three were from sites I would not want to be associated with, and all three would have been a nofollow link on a page full of other paid links. The fact that the only replies I got were sales pitches tells you what the inbox looks like from the other side: most people emailing site owners are selling something.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I changed after day two
&lt;/h2&gt;

&lt;p&gt;Instead of asking to be added to someone's list, I wrote the article first and offered that. A finished 800-word piece is a different proposition from "please consider my site" — one requires the recipient to do work, the other requires them to do nothing.&lt;/p&gt;

&lt;p&gt;Response rate on that approach so far: also zero. But it's early, and the asymmetry is obvious enough that I'm keeping it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The thing that actually worked
&lt;/h2&gt;

&lt;p&gt;Publishing this post, on a platform that lets me link out without asking anyone's permission.&lt;/p&gt;

&lt;p&gt;That's not a clever insight, but it reframes the problem: I spent three days on a channel where every single action required another person to say yes, and got 0 yeses. The channel where I needed nobody's permission took twenty minutes.&lt;/p&gt;

&lt;p&gt;Two links in two days, one of them dofollow, versus zero after 48 emails.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd tell someone starting this
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Count the yes-gates before you start.&lt;/strong&gt; If every step requires a stranger's approval, your throughput is their inbox behaviour, not your effort.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check whether your bounce reason is about you.&lt;/strong&gt; "Blocked" and "no such user" look similar in a mail client and mean completely different things.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do the free channel first.&lt;/strong&gt; It costs an afternoon and it's the only one where the result is deterministic.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write down the stop condition.&lt;/strong&gt; Mine is: if the reply rate is still zero after 30 days, the channel is wrong, not the volume.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The 48 emails weren't wasted — I learned what the inbox looks like, and I got a post out of it. But I'd have started with the writing.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I build &lt;a href="https://gamesprig.com/?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=outreach-2026-11"&gt;GameSprig&lt;/a&gt;, a free browser game site with no downloads and no accounts.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>marketing</category>
      <category>seo</category>
      <category>sideprojects</category>
      <category>startup</category>
    </item>
    <item>
      <title>244 pages, zero indexing movement: my sitemap was lying to Google</title>
      <dc:creator>Sam</dc:creator>
      <pubDate>Sat, 21 Nov 2026 13:34:51 +0000</pubDate>
      <link>https://dev.to/gamesprig/244-pages-zero-indexing-movement-my-sitemap-was-lying-to-google-4j28</link>
      <guid>https://dev.to/gamesprig/244-pages-zero-indexing-movement-my-sitemap-was-lying-to-google-4j28</guid>
      <description>&lt;p&gt;I shipped body copy to 244 pages in one night. Three days later, Search Console hadn't moved a single page from "Crawled - currently not indexed" into the index. Not a slow crawl. Zero movement.&lt;/p&gt;

&lt;p&gt;The pages were fine. The problem was that my sitemap was lying to Google, and it had been lying since August.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the sitemap said
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;$ curl -s https://gamesprig.com/sitemap.xml &lt;span class="o"&gt;|&lt;/span&gt; grep -o &lt;span class="s1"&gt;'&amp;lt;lastmod&amp;gt;[^&amp;lt;]*'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; sort &lt;span class="o"&gt;|&lt;/span&gt; tail -1
&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;lastmod&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;2026-08-19T03:09:34.000Z
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;411 URLs, 382 of them game pages. Every single &lt;code&gt;lastmod&lt;/code&gt; was on or before 2026-08-19. The body copy on 244 of those pages changed on 2026-11-17.&lt;/p&gt;

&lt;p&gt;So for three days, every time Googlebot fetched the sitemap, it was told: nothing here has changed since August.&lt;/p&gt;

&lt;p&gt;It believed me.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this happens
&lt;/h2&gt;

&lt;p&gt;The sitemap was generated from a field that stopped moving — a &lt;code&gt;createdAt&lt;/code&gt;, or a build timestamp that got frozen when the generator was refactored, or a hardcoded date that was correct the day it was written. The mechanism doesn't matter much. What matters is that &lt;code&gt;lastmod&lt;/code&gt; is a &lt;strong&gt;claim&lt;/strong&gt;, and once it stops tracking reality, the sitemap becomes actively harmful: it tells the crawler to deprioritise exactly the pages you just improved.&lt;/p&gt;

&lt;p&gt;The other failure mode is worse. Once you notice this, the temptation is to stamp everything with today's date. Don't:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Google learns per-host how often &lt;code&gt;lastmod&lt;/code&gt; changes without the content changing&lt;/li&gt;
&lt;li&gt;If your sitemap says all 400 pages changed today, every day, the signal stops being useful and gets discounted&lt;/li&gt;
&lt;li&gt;You cannot un-ring that bell quickly&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The rule I settled on: &lt;code&gt;lastmod&lt;/code&gt; should equal the last time the &lt;em&gt;content a user sees&lt;/em&gt; changed. Nothing else. Not the deploy, not the build, not the template.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix
&lt;/h2&gt;

&lt;p&gt;In a Next.js App Router project, this is one line if each record carries a real timestamp:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;sitemap&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;games&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;getAllGames&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// each needs a real updatedAt&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;games&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;g&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`https://gamesprig.com/games/${g.slug}/`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;lastModified&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nb"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;g&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;updatedAt&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;changeFrequency&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'weekly'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;priority&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;0.8&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you don't have per-record timestamps yet, the interim move is to set the changed records to the date they actually changed and leave everything else alone. It's imprecise, but it's true, and true is what the crawler needs.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to check yours in ten seconds
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s https://your.site/sitemap.xml \
  &lt;span class="o"&gt;|&lt;/span&gt; grep -o &lt;span class="s1"&gt;'&amp;lt;lastmod&amp;gt;[^&amp;lt;]*'&lt;/span&gt; \
  &lt;span class="o"&gt;|&lt;/span&gt; sort &lt;span class="o"&gt;|&lt;/span&gt; tail -3
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If the newest date is older than your most recent content deploy, you have the same bug. If the newest date is today and yesterday and the day before, you have the other one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd do differently
&lt;/h2&gt;

&lt;p&gt;I spent three days watching a number that couldn't move, and the number was behaving correctly — it was just being fed a lie. The diagnostic I should have run first took ten seconds.&lt;/p&gt;

&lt;p&gt;Two things I now check before assuming a crawl problem is a content problem:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;code&gt;lastmod&lt;/code&gt; max vs. last content change date&lt;/li&gt;
&lt;li&gt;Whether the pages I care about are in the sitemap at all (mine had 411 URLs while the site served 425)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Neither requires Search Console, an SEO tool, or a week of waiting.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I build &lt;a href="https://gamesprig.com/?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=outreach-2026-11"&gt;GameSprig&lt;/a&gt;, a free browser game site with no downloads and no accounts. This post is the postmortem of a mistake I made on it last week.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>debugging</category>
      <category>seo</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
