<?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: Mohammad Shazam</title>
    <description>The latest articles on DEV Community by Mohammad Shazam (@mohammad_shazam_c8450b289).</description>
    <link>https://dev.to/mohammad_shazam_c8450b289</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%2F3522005%2Fe22518b0-0a0a-4057-9f7c-29ff9a4ae6cb.jpg</url>
      <title>DEV Community: Mohammad Shazam</title>
      <link>https://dev.to/mohammad_shazam_c8450b289</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mohammad_shazam_c8450b289"/>
    <language>en</language>
    <item>
      <title>Search Console after a launch: real search opportunity or noise?</title>
      <dc:creator>Mohammad Shazam</dc:creator>
      <pubDate>Sun, 22 Nov 2026 13:07:49 +0000</pubDate>
      <link>https://dev.to/mohammad_shazam_c8450b289/search-console-after-a-launch-real-search-opportunity-or-noise-2cd5</link>
      <guid>https://dev.to/mohammad_shazam_c8450b289/search-console-after-a-launch-real-search-opportunity-or-noise-2cd5</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I write for LaunchReach, which connects GA4 and Search Console. The method below works with the raw reports too; the product is mentioned once near the end.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A week or two after a launch, Search Console starts filling up. Impressions climb, a few queries show up, and it is tempting to read that as demand. Often it isn't. Here is a way to sort the signal from the noise using only the data Search Console and GA4 give you.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you are looking at
&lt;/h2&gt;

&lt;p&gt;Search Console reports clicks, impressions, CTR, average position, queries, landing pages, countries and devices. GA4 adds sessions, engagement, events and conversions when you have configured them. The trick is reading the two together, because each one lies a little on its own.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Search Console tells you who &lt;em&gt;saw&lt;/em&gt; you and who clicked.&lt;/li&gt;
&lt;li&gt;GA4 tells you what people did &lt;em&gt;after&lt;/em&gt; they arrived.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A query is only an opportunity if both halves look healthy, or if one half tells you exactly what to fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Export queries and sort by impressions
&lt;/h2&gt;

&lt;p&gt;Open Performance, set the date range to the period since launch, and turn on clicks, impressions, CTR and position. Sort by impressions, descending.&lt;/p&gt;

&lt;p&gt;Now put each query into one of four buckets.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;High impressions, decent CTR, good position.&lt;/strong&gt; Working. Protect these pages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;High impressions, weak CTR, position 1 to 10.&lt;/strong&gt; You are visible but unconvincing. Likely opportunity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;High impressions, weak CTR, position far down the results.&lt;/strong&gt; Mostly noise. Few people ever scroll that far, so CTR is low by nature, and rewriting your title will not change much.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Very low impressions.&lt;/strong&gt; Too little data to judge. Leave it alone for now.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The common mistake is treating bucket 3 like bucket 2. A low CTR at a deep position is not a copy problem; it is a ranking problem, and it is a different job.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Ask whether the query matches your product
&lt;/h2&gt;

&lt;p&gt;Impressions with a weak CTR can also mean the query is simply not about you. After a launch, pages often rank for loosely related words because the launch post mentions them in passing.&lt;/p&gt;

&lt;p&gt;For each query in bucket 2, ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Would a person typing this be a plausible buyer?&lt;/li&gt;
&lt;li&gt;Does my page actually answer it, or just contain the words?&lt;/li&gt;
&lt;li&gt;Is it a question about my category, my problem space, or something unrelated?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you wouldn't want that person as a customer, it is noise, however large the impressions number looks. Cross it off.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Fix weak CTR only where position is competitive
&lt;/h2&gt;

&lt;p&gt;For the queries that survive, the page title and meta description are the shop window. Check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does the title contain the phrase people typed, in plain words?&lt;/li&gt;
&lt;li&gt;Does the description say what the page does and for whom, rather than a slogan?&lt;/li&gt;
&lt;li&gt;Do competing results promise something specific that you don't?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Change one thing at a time and note the date. Search Console is slow, and if you change five things you won't know which one mattered. Compare the same query over comparable periods and avoid reading anything into a few days of data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Find landing pages that attract queries but not engagement
&lt;/h2&gt;

&lt;p&gt;This is the second kind of noise. A page can collect clicks from search and still be a dead end.&lt;/p&gt;

&lt;p&gt;In Search Console, list landing pages by clicks. Then in GA4, look at the same pages and check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Engagement: do visitors stay and interact, or leave straight away?&lt;/li&gt;
&lt;li&gt;Events: do they click through to pricing, docs or signup?&lt;/li&gt;
&lt;li&gt;Conversions: if you have configured a signup event, does it fire from this page?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Three patterns are worth naming.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Clicks, little engagement, no events.&lt;/strong&gt; The page promised something the visitor didn't find. Compare the query to the first screen of the page. Usually the headline answers a different question.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Engagement, but no next step.&lt;/strong&gt; People read, then have nowhere to go. Add a clear link to the thing a reader would logically do next.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Engagement and events, few clicks from search.&lt;/strong&gt; Your best candidate for more visibility. The page works; it just needs to be found. This is where improving titles and internal links pays off.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Decide with a simple rule
&lt;/h2&gt;

&lt;p&gt;To avoid chasing everything, give each query-and-page pair one of three labels:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Act now:&lt;/strong&gt; relevant query, competitive position, weak CTR or weak engagement you can explain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Watch:&lt;/strong&gt; relevant but low volume, or too new to judge.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ignore:&lt;/strong&gt; irrelevant to your buyer, or too far down the results for copy to help.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Write the labels in a sheet with the date. Review it at a fixed interval rather than daily. The point is to stop reacting to every movement.&lt;/p&gt;

&lt;h2&gt;
  
  
  A note on honesty with the data
&lt;/h2&gt;

&lt;p&gt;Search Console data is sampled in places, anonymises some queries, and lags. GA4 depends on how you set up events. So treat both as evidence for a decision, not proof. If a conclusion needs data you don't have, say that and move on rather than inventing the missing piece.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where a tool can help
&lt;/h2&gt;

&lt;p&gt;Doing this by hand is fine for one site. If you run a portfolio, the repetition adds up. LaunchReach connects GA4 and Search Console read-only, supports several properties per workspace, and its AI recommends search opportunities and weak landing pages, citing the metrics behind each one. Those recommendations are labelled as interpretations, so you still make the call. It does not claim attribution the data cannot support, which is the right default.&lt;/p&gt;

&lt;p&gt;The method above doesn't depend on any of it. Sort by impressions, check position, check relevance, check engagement, label, and review on a schedule.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Export queries since launch, sorted by impressions.&lt;/li&gt;
&lt;li&gt;Bucket by CTR and position.&lt;/li&gt;
&lt;li&gt;Cross off queries that don't match a buyer.&lt;/li&gt;
&lt;li&gt;Fix titles only where position is competitive.&lt;/li&gt;
&lt;li&gt;Compare landing pages in GA4 for engagement and events.&lt;/li&gt;
&lt;li&gt;Label: act, watch, ignore. Review on a schedule.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;What is the most misleading query you have seen after a launch?&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mambatxhub.com/r/zx7mfe82" rel="noopener noreferrer"&gt;Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>data</category>
      <category>seo</category>
    </item>
    <item>
      <title>You have a list of 400+ directories. Here's how to shortlist them without submitting everywhere</title>
      <dc:creator>Mohammad Shazam</dc:creator>
      <pubDate>Sun, 22 Nov 2026 12:09:14 +0000</pubDate>
      <link>https://dev.to/mohammad_shazam_c8450b289/you-have-a-list-of-400-directories-heres-how-to-shortlist-them-without-submitting-everywhere-847</link>
      <guid>https://dev.to/mohammad_shazam_c8450b289/you-have-a-list-of-400-directories-heres-how-to-shortlist-them-without-submitting-everywhere-847</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I work on LaunchReach, which is mentioned near the end. The method below works with a spreadsheet and does not require our product.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A founder on r/SaaS recently described a situation many of us know. They were about to launch and had a list of 400+ directories. Their questions: do people submit by hand, pay a service, hire a freelancer, or use a Chrome extension? What is the most annoying part: logins, CAPTCHAs, retyping descriptions, tracking? And do directories bring users at all?&lt;/p&gt;

&lt;p&gt;In the research we looked at for this piece, that last question comes up repeatedly. Founders submit to anywhere from 5 to 100+ directories and say they cannot tell whether those listings deliver signups, SEO value or just a trickle of referral traffic. They worry about nofollow links, queues and paid listings. Some say they distrust tools that push a site to 200 directories at once. One founder said they would happily spend up to $300 on paid listings, but only if they knew it was worth it.&lt;/p&gt;

&lt;p&gt;I can't tell you which directories convert. Nothing in the material I have supports a ranking, and anyone who hands you one without data should be treated with caution. What I can offer is a method for deciding where to spend limited time and money, and for finding out afterwards what worked.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Cut the list by fit before you look at anything else
&lt;/h2&gt;

&lt;p&gt;A directory is only useful if the people browsing it could plausibly buy your product. Go through the list and drop anything where one of these is true:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It is for a different kind of product (mobile apps, physical goods, AI image tools) and you are a B2B SaaS tool.&lt;/li&gt;
&lt;li&gt;It is a general link dump with no categories, no editorial structure and no sign that anyone browses it.&lt;/li&gt;
&lt;li&gt;It targets a different audience from yours (for example, hobbyist makers when you sell to agencies).&lt;/li&gt;
&lt;li&gt;Its category for your product is empty or does not exist.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This step is cheap and is usually the biggest cut. You are not judging quality yet, only relevance. If you can't say in one sentence who browses this directory and why they'd want your product, it goes in the "no" pile.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Read the fee and terms before you read the traffic claims
&lt;/h2&gt;

&lt;p&gt;For every directory that survives, write down in a column:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Is listing free, paid, or free with a paid fast lane?&lt;/li&gt;
&lt;li&gt;What exactly does the fee buy: a review, a placement, a link, a badge?&lt;/li&gt;
&lt;li&gt;Is there a queue, and is the wait stated?&lt;/li&gt;
&lt;li&gt;Does the listing say whether links are nofollow? (If it doesn't say, check the page source yourself and record what you find.)&lt;/li&gt;
&lt;li&gt;Are there rules about repeat submissions, or about asking for votes?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The last point matters. Resubmitting against a directory's rules or asking friends to vote can get you removed, and that is a worse outcome than not being listed.&lt;/p&gt;

&lt;p&gt;A paid listing is a reasonable bet if the audience fits and the terms are clear. It is a poor bet if the only reason you are considering it is that the directory's own page says it gets lots of traffic. Treat self-reported traffic as a claim, not a fact.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Look for evidence you can check yourself
&lt;/h2&gt;

&lt;p&gt;This is the step most people skip. For each remaining directory, look for things you can verify without trusting the directory:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Are real products listed, and recently?&lt;/strong&gt; Look at the newest entries. A directory whose latest listing is two years old is a warning sign.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do listings show any engagement&lt;/strong&gt; (comments, saves, discussion), or are they static entries?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does the directory show up in search&lt;/strong&gt; for the kind of phrase your buyers would type? A quick search for the category plus "alternatives" or "tools" tells you something.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do other products like yours appear there&lt;/strong&gt;, and do they appear to have been placed with some care?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this proves conversion. It simply separates a living directory from an abandoned one. Mark each as strong, unclear or weak, and be honest in the "unclear" column. A blank is better than a guess.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Pick a small first batch and decide in advance what counts as success
&lt;/h2&gt;

&lt;p&gt;From what is left, choose a first batch small enough to do well, with copy that matches each directory's format. Many founders skip this: the same description pasted everywhere reads badly and sometimes breaks a directory's length or tone rules. Write each listing for the directory it goes into.&lt;/p&gt;

&lt;p&gt;Before you submit, decide what you will look at afterwards. Options include signups, trial starts, visits with real engagement, and impressions or clicks in Search Console for your own pages. Choose which you care about, because directories may deliver one and not another. A listing that sends a handful of visitors but no signups is a different result from one that sends few visitors who all sign up.&lt;/p&gt;

&lt;p&gt;Some communities, such as Show HN, expect you to post yourself. Do not try to automate those. Prepare your copy, post it as yourself, and record what happened.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Give every listing its own tracked link
&lt;/h2&gt;

&lt;p&gt;This is what turns a pile of submissions into evidence. Use a distinct UTM-tagged URL for every directory:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;https://yourproduct.com/?utm_source=directoryname&amp;amp;utm_medium=directory&amp;amp;utm_campaign=launch
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then record, in one sheet: directory, date submitted, fee paid, listing URL, status (pending, live, rejected), and the metrics you chose. Check GA4 by source/medium and look at sessions, engagement and conversions per directory.&lt;/p&gt;

&lt;p&gt;Be cautious in how you read the result. UTM links only count visits that arrive through that link. People who see you in a directory and come back later by typing your name will land as direct traffic, and SEO value from a link will never show up under your UTM. So your numbers are a floor, not a full account. Write the limitation down next to the data so you don't over-claim to yourself later.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Review after a fixed window and cut or expand
&lt;/h2&gt;

&lt;p&gt;Pick a date, say a few weeks after the listings go live, and review the sheet. Three outcomes are useful:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A directory sent visitors who engaged or signed up: consider whether a paid upgrade is justified.&lt;/li&gt;
&lt;li&gt;A directory sent nothing and looks inactive: don't renew, and don't submit similar ones.&lt;/li&gt;
&lt;li&gt;Unclear: leave it, and don't spend more until you have data.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Then go back to the original list and add a second batch, using what you learned about which kinds of directories fit your product. The 400+ list stops being a to-do list and becomes a source you draw from.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where tooling helps and where it doesn't
&lt;/h2&gt;

&lt;p&gt;All of the above can be done in a spreadsheet. The costs are the repetitive parts: retyping descriptions, making UTM links, and keeping the sheet up to date.&lt;/p&gt;

&lt;p&gt;LaunchReach is built around that same approach. You add your product once and it ranks 45 destinations by fit, with copy written per destination's rules. Where a destination has an official API, it submits through a dedicated adapter; where it doesn't, it fills the web form from your authorised session, only where the platform terms allow. It never bypasses CAPTCHA, 2FA or platform rules, and it pauses when a human is needed. For communities like Show HN, you post yourself and it prepares the copy and records the outcome. Every submission gets its own UTM link, and with GA4 and Search Console connected read-only you can see which destinations drove visitors and signups. Listing fees are shown before approval and passed through at cost.&lt;/p&gt;

&lt;p&gt;Two honest limits. First, third-party destinations decide whether to accept, publish or remove a listing, and LaunchReach does not guarantee outcomes. Second, attribution is only as good as the data: it does not claim more than the data supports.&lt;/p&gt;

&lt;p&gt;The shortlist method is the part that matters. Fit first, fees and terms second, checkable evidence third, then tracking per destination and a review date. Whether you use a spreadsheet or a tool, that order is what keeps you from submitting everywhere and learning nothing.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mambatxhub.com/r/fbudkdbw" rel="noopener noreferrer"&gt;Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>marketing</category>
      <category>saas</category>
      <category>seo</category>
      <category>startup</category>
    </item>
    <item>
      <title>SPF, DKIM and DMARC for launch emails: what each record does and how to check them before you send</title>
      <dc:creator>Mohammad Shazam</dc:creator>
      <pubDate>Sun, 22 Nov 2026 11:03:56 +0000</pubDate>
      <link>https://dev.to/mohammad_shazam_c8450b289/spf-dkim-and-dmarc-for-launch-emails-what-each-record-does-and-how-to-check-them-before-you-send-2kmc</link>
      <guid>https://dev.to/mohammad_shazam_c8450b289/spf-dkim-and-dmarc-for-launch-emails-what-each-record-does-and-how-to-check-them-before-you-send-2kmc</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I work on LaunchReach, which has guided SPF/DKIM/DMARC setup for sending from your own domain. It is mentioned near the end. The steps below work with any email provider.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You have a launch coming. You have written the announcement and built a list. Before you hit send, there is one boring job that decides whether the email reaches inboxes or ends up in spam: authenticating your sending domain.&lt;/p&gt;

&lt;p&gt;Three DNS records do this: SPF, DKIM and DMARC. This is what each one does and how to check them, written for a founder who would rather not become a mail admin.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;SPF&lt;/strong&gt; lists which servers may send mail for your domain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DKIM&lt;/strong&gt; adds a cryptographic signature to each message, so receivers can verify it was authorised by your domain and not altered.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DMARC&lt;/strong&gt; tells receivers what to do when SPF and DKIM checks fail to line up with your visible From domain, and where to send reports.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All three are TXT records (DKIM is sometimes a CNAME, depending on the provider) that you add in your DNS host: Cloudflare, your registrar, Route 53, and so on.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 0: decide what you are sending from
&lt;/h2&gt;

&lt;p&gt;Pick the exact From address, for example &lt;code&gt;hello@yourproduct.com&lt;/code&gt;. Decide also whether you will send launch mail from your root domain or a subdomain such as &lt;code&gt;mail.yourproduct.com&lt;/code&gt;. A subdomain keeps launch-campaign reputation separate from your day-to-day email. Either choice is valid; just be consistent when you set up the records.&lt;/p&gt;

&lt;p&gt;List every service that sends mail as your domain: your mailbox provider, your product's transactional email, your newsletter or campaign tool. Each one needs to be covered, and this matters most for SPF.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: SPF
&lt;/h2&gt;

&lt;p&gt;SPF is a single TXT record at the domain you send from. It looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;yourproduct.com.  TXT  "v=spf1 include:_spf.google.com include:sendprovider.example ~all"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;How to read it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;v=spf1&lt;/code&gt; marks it as SPF.&lt;/li&gt;
&lt;li&gt;Each &lt;code&gt;include:&lt;/code&gt; authorises a provider's servers. Your email provider gives you the exact value to use.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;~all&lt;/code&gt; is a soft fail for anything not listed. &lt;code&gt;-all&lt;/code&gt; is a hard fail. Many people start with &lt;code&gt;~all&lt;/code&gt; and tighten later.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Common mistakes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Two SPF records on one domain.&lt;/strong&gt; There must be only one. If you add a second provider, merge it into the existing record.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Too many lookups.&lt;/strong&gt; SPF allows 10 DNS lookups in total, and each &lt;code&gt;include:&lt;/code&gt; can consume some. If you stack many services, you can exceed the limit and SPF fails.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Forgetting a sender&lt;/strong&gt;, like your transactional mail service, so those messages start failing.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Step 2: DKIM
&lt;/h2&gt;

&lt;p&gt;With DKIM, your sending provider signs each message with a private key. You publish the matching public key in DNS so receivers can check the signature.&lt;/p&gt;

&lt;p&gt;Your provider will give you a record name and value, typically something like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;selector1._domainkey.yourproduct.com.  TXT  "v=DKIM1; k=rsa; p=MIGfMA0..."
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The part before &lt;code&gt;._domainkey&lt;/code&gt; is the selector. Different providers use different selectors, so you can have several DKIM records side by side without conflict. Some providers ask you to create CNAMEs instead, which lets them rotate keys for you.&lt;/p&gt;

&lt;p&gt;Common mistakes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pasting the key with line breaks or stray quotes added by your DNS host's editor.&lt;/li&gt;
&lt;li&gt;Putting the record on the wrong name, for example adding &lt;code&gt;yourproduct.com&lt;/code&gt; twice to a host that appends the domain automatically.&lt;/li&gt;
&lt;li&gt;Sending before the record has propagated.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 3: DMARC
&lt;/h2&gt;

&lt;p&gt;DMARC sits on top of the other two. It checks that the domain authenticated by SPF or DKIM matches the domain in your visible From address (this is called alignment), and it sets a policy.&lt;/p&gt;

&lt;p&gt;The record lives at &lt;code&gt;_dmarc.yourproduct.com&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;_dmarc.yourproduct.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@yourproduct.com"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;p=none&lt;/code&gt; means monitor only. Nothing is rejected, but you get reports.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;p=quarantine&lt;/code&gt; asks receivers to treat failures as suspicious.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;p=reject&lt;/code&gt; asks them to refuse failures.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;rua&lt;/code&gt; is where aggregate reports are sent.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A sensible path for a small team: start at &lt;code&gt;p=none&lt;/code&gt;, read the reports for a while to confirm all your legitimate senders pass, then move to &lt;code&gt;quarantine&lt;/code&gt; and eventually &lt;code&gt;reject&lt;/code&gt;. Jumping straight to &lt;code&gt;reject&lt;/code&gt; before you have found every sender is how people block their own invoices.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: check before you send
&lt;/h2&gt;

&lt;p&gt;Do not trust the green tick in a dashboard alone. Verify from the outside.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Look up the records directly:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;dig TXT yourproduct.com +short
dig TXT selector1._domainkey.yourproduct.com +short
dig TXT _dmarc.yourproduct.com +short
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Confirm you see exactly one SPF record, the DKIM key, and the DMARC policy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Send a real test message.&lt;/strong&gt; Send to a mailbox you control at a different provider and open the full message headers. Look for the &lt;code&gt;Authentication-Results&lt;/code&gt; header and check that it shows &lt;code&gt;spf=pass&lt;/code&gt;, &lt;code&gt;dkim=pass&lt;/code&gt; and &lt;code&gt;dmarc=pass&lt;/code&gt;. Also confirm that the domain in the DKIM signature (&lt;code&gt;d=&lt;/code&gt;) and the SPF-authenticated domain match your From domain, since that is what alignment means.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pre-send checklist:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;One SPF record, covering every sender.&lt;/li&gt;
&lt;li&gt;DKIM published and verified for the sending provider.&lt;/li&gt;
&lt;li&gt;DMARC record present, at least &lt;code&gt;p=none&lt;/code&gt;, with a report address.&lt;/li&gt;
&lt;li&gt;A test email shows pass for all three in the headers.&lt;/li&gt;
&lt;li&gt;The From address matches the authenticated domain.&lt;/li&gt;
&lt;li&gt;Reply-to is a mailbox someone actually reads.&lt;/li&gt;
&lt;li&gt;Your unsubscribe link works.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The last two are not DNS, but they matter for the same reason: receivers watch how people react to your mail.&lt;/p&gt;

&lt;h2&gt;
  
  
  What authentication does not do
&lt;/h2&gt;

&lt;p&gt;Passing SPF, DKIM and DMARC does not guarantee inbox placement. It removes a reason for filters to distrust you. Content, list quality, and who you send to still count. Only email people who have a reason to expect it, and keep your sending volume steady rather than jumping from nothing to a large blast on launch day.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where LaunchReach fits
&lt;/h2&gt;

&lt;p&gt;If you would rather not hand-edit DNS from documentation, LaunchReach includes email sending from your own domain with guided SPF, DKIM and DMARC setup, a drag-and-drop builder and AI-drafted launch announcements. The records themselves are the same ones described above; the guided setup is a way to be walked through them. Email has daily and monthly allowances, and sending pauses when they are used up, with no overage charges. The 7-day Growth trial is $1 and nothing renews automatically.&lt;/p&gt;

&lt;p&gt;Whichever tool you use, run the header check on a test email first. It takes a few minutes and tells you far more than a dashboard status does.&lt;/p&gt;

&lt;p&gt;If you have hit a DNS gotcha during setup that is not covered here, share it in the comments.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mambatxhub.com/r/fbabnzv9" rel="noopener noreferrer"&gt;Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>authentication</category>
      <category>infrastructure</category>
      <category>security</category>
    </item>
    <item>
      <title>Build a per-destination launch dashboard with UTM links and GA4 (field list and sanity checks included)</title>
      <dc:creator>Mohammad Shazam</dc:creator>
      <pubDate>Sun, 22 Nov 2026 10:05:20 +0000</pubDate>
      <link>https://dev.to/mohammad_shazam_c8450b289/build-a-per-destination-launch-dashboard-with-utm-links-and-ga4-field-list-and-sanity-checks-4g76</link>
      <guid>https://dev.to/mohammad_shazam_c8450b289/build-a-per-destination-launch-dashboard-with-utm-links-and-ga4-field-list-and-sanity-checks-4g76</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I write for LaunchReach, a tool in this space. The steps below work with a spreadsheet and GA4 alone. I mention our product once, near the end.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You submitted your SaaS to a handful of launch directories and communities. Traffic showed up. Some people signed up. Now: which listing did what?&lt;/p&gt;

&lt;p&gt;If your analytics say "referral" or "direct" for most of it, you can't tell. This tutorial builds a small dashboard that answers one question per listing: &lt;strong&gt;how many sessions and how many signups came from this destination?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It won't be perfect attribution. We'll cover where it breaks. But it's enough to decide where to spend your next hour.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you'll build
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;One tagged link per listing&lt;/li&gt;
&lt;li&gt;A read-only GA4 connection&lt;/li&gt;
&lt;li&gt;A table with one row per destination: sessions, signups, signup rate&lt;/li&gt;
&lt;li&gt;A short routine that catches the usual mistakes&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 1: Decide your naming convention first
&lt;/h2&gt;

&lt;p&gt;Most broken attribution comes from inconsistent names, not from tooling. Pick a convention and write it down before you create a single link.&lt;/p&gt;

&lt;p&gt;Use these UTM parameters:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;utm_source&lt;/code&gt;: the destination, lowercase, no spaces. Example: &lt;code&gt;producthunt&lt;/code&gt;, &lt;code&gt;showhn&lt;/code&gt;, &lt;code&gt;somedirectory&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;utm_medium&lt;/code&gt;: the kind of placement. Example: &lt;code&gt;directory&lt;/code&gt;, &lt;code&gt;community&lt;/code&gt;, &lt;code&gt;email&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;utm_campaign&lt;/code&gt;: the launch name. Example: &lt;code&gt;launch-2025-q1&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;utm_content&lt;/code&gt;: optional. Use it if you have two links in the same listing (say, a logo link and a text link).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Rules that save you later:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Lowercase everything. GA4 treats &lt;code&gt;Producthunt&lt;/code&gt; and &lt;code&gt;producthunt&lt;/code&gt; as different values.&lt;/li&gt;
&lt;li&gt;Use hyphens, not spaces or underscores mixed at random.&lt;/li&gt;
&lt;li&gt;One source value per destination. Never reuse one across two sites.&lt;/li&gt;
&lt;li&gt;Don't put personal data or emails in any parameter.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Step 2: Create one link per listing
&lt;/h2&gt;

&lt;p&gt;Your base URL is the page you want people to land on. For a listing, that might be your homepage or a dedicated landing page.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;https://yourapp.com/?utm_source=somedirectory&amp;amp;utm_medium=directory&amp;amp;utm_campaign=launch-2025-q1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Build these in a spreadsheet with a formula so you don't hand-type them. Columns:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Column&lt;/th&gt;
&lt;th&gt;Example&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;destination&lt;/td&gt;
&lt;td&gt;somedirectory&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;medium&lt;/td&gt;
&lt;td&gt;directory&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;campaign&lt;/td&gt;
&lt;td&gt;launch-2025-q1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;landing_url&lt;/td&gt;
&lt;td&gt;&lt;a href="https://yourapp.com/" rel="noopener noreferrer"&gt;https://yourapp.com/&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;tagged_url&lt;/td&gt;
&lt;td&gt;formula output&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;submitted_on&lt;/td&gt;
&lt;td&gt;date&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;status&lt;/td&gt;
&lt;td&gt;pending / live / rejected&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;listing_url&lt;/td&gt;
&lt;td&gt;the public page of your listing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;fee_paid&lt;/td&gt;
&lt;td&gt;amount, if any&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The &lt;code&gt;status&lt;/code&gt; and &lt;code&gt;fee_paid&lt;/code&gt; columns matter more than they look. A rejected listing with zero traffic is not a bad channel, it's a non-event. And a paid listing needs its cost next to its results.&lt;/p&gt;

&lt;p&gt;Paste each tagged URL into the matching listing's website field, not your bare homepage.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Connect GA4 read-only
&lt;/h2&gt;

&lt;p&gt;You only need to read data, so grant read-only access.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In GA4, confirm a web data stream is collecting on your site.&lt;/li&gt;
&lt;li&gt;Mark your signup as a key event (formerly "conversion"). If you don't already fire a &lt;code&gt;sign_up&lt;/code&gt; event, add one on the success state of your signup flow, not on button click.&lt;/li&gt;
&lt;li&gt;If you use a third-party dashboard, grant it Viewer access only. If you build your own in Looker Studio, connect the GA4 data source directly.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Check that the signup event fires exactly once per real signup before moving on. Test with your own account.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Build the per-source view
&lt;/h2&gt;

&lt;p&gt;In GA4 Explore (or a Looker Studio table), create a table with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Rows:&lt;/strong&gt; Session source / medium (or Session campaign, if you want to filter to this launch)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Values:&lt;/strong&gt; Sessions, Engaged sessions, Key events (your signup event)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then filter to &lt;code&gt;utm_campaign&lt;/code&gt; equal to your launch campaign name.&lt;/p&gt;

&lt;p&gt;Copy the results into a second sheet with these fields:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Field&lt;/th&gt;
&lt;th&gt;How to get it&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;destination&lt;/td&gt;
&lt;td&gt;from &lt;code&gt;utm_source&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;sessions&lt;/td&gt;
&lt;td&gt;GA4&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;engaged_sessions&lt;/td&gt;
&lt;td&gt;GA4&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;signups&lt;/td&gt;
&lt;td&gt;GA4 key event count&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;signup_rate&lt;/td&gt;
&lt;td&gt;signups / sessions&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;cost&lt;/td&gt;
&lt;td&gt;your fee_paid column&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;cost_per_signup&lt;/td&gt;
&lt;td&gt;cost / signups (blank if zero)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;notes&lt;/td&gt;
&lt;td&gt;anything odd&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Sort by signups, not sessions. A directory that sends 300 visits and no signups tells you something different from one that sends 20 visits and 4 signups. Keep in mind that small numbers are noisy: four signups is a sample, not a rule.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: The sanity-check routine
&lt;/h2&gt;

&lt;p&gt;Run this once a week during a launch and once at the end.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Click your own links.&lt;/strong&gt; Open every tagged URL in a private window. In GA4's Realtime report, confirm the source shows up with the right name.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Check for stripped parameters.&lt;/strong&gt; Some sites redirect and drop the query string. If a listing shows zero sessions after you know people visited, click through from the live listing and watch the URL you land on.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Look for case and spelling duplicates.&lt;/strong&gt; Scan the source list for near-identical values (&lt;code&gt;somedirectory&lt;/code&gt; vs &lt;code&gt;some-directory&lt;/code&gt;). Merge them in your sheet.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Compare totals.&lt;/strong&gt; Add up sessions across your tagged sources and compare with total sessions in the same period. A big gap means traffic is arriving untagged: people copied your URL, a listing used your plain homepage link, or a site strips tags.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Check the signup event.&lt;/strong&gt; Signups in GA4 should be roughly in line with new accounts in your product database. If they differ a lot, fix the event before trusting any ranking.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. Watch for browser-side loss.&lt;/strong&gt; Consent banners and blockers mean GA4 undercounts. Treat the numbers as a lower bound and compare destinations against each other, not against your database.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7. Write down what you can't attribute.&lt;/strong&gt; Someone might see you on a directory, then come back later by typing your URL. That's a "direct" visit in GA4. Note it, don't force it into a row.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where this approach breaks
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Last-touch bias.&lt;/strong&gt; GA4 credits the session's source. A visitor who found you through a directory and signed up days later via a bookmark shows up as direct.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Listings you can't edit.&lt;/strong&gt; Some directories lock the URL or add their own redirect. Note these as "untagged" and rely on referral data as a rough guide.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backlink value.&lt;/strong&gt; This dashboard measures visitors and signups. It says nothing about search benefit from a link. Keep that as a separate question.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Small samples.&lt;/strong&gt; One launch is one data point.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Doing it with a tool instead
&lt;/h2&gt;

&lt;p&gt;If you'd rather not maintain the sheet, LaunchReach (our product) generates a separate UTM link for each submission, connects GA4 and Search Console read-only, and rolls traffic and signups up to the destination. Its attribution doesn't claim more than the data supports, so the same limits above apply: it can't see what GA4 can't see. It's one option; the manual route works fine for a handful of listings.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Naming convention written down&lt;/li&gt;
&lt;li&gt;[ ] One tagged URL per listing, lowercase&lt;/li&gt;
&lt;li&gt;[ ] Signup key event fires once per real signup&lt;/li&gt;
&lt;li&gt;[ ] GA4 access is read-only&lt;/li&gt;
&lt;li&gt;[ ] Table sorted by signups, with cost beside it&lt;/li&gt;
&lt;li&gt;[ ] Weekly sanity check done&lt;/li&gt;
&lt;li&gt;[ ] Unattributed traffic noted, not guessed&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;After a launch, you should be able to say "these three destinations sent signups, these five sent visits only, and these two never went live". That's enough to plan the next round.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mambatxhub.com/r/2ykqnhnc" rel="noopener noreferrer"&gt;Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>marketing</category>
      <category>saas</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Reading Search Console per product when you run a portfolio: queries, landing pages, CTR and position</title>
      <dc:creator>Mohammad Shazam</dc:creator>
      <pubDate>Sun, 22 Nov 2026 09:54:12 +0000</pubDate>
      <link>https://dev.to/mohammad_shazam_c8450b289/reading-search-console-per-product-when-you-run-a-portfolio-queries-landing-pages-ctr-and-5hm5</link>
      <guid>https://dev.to/mohammad_shazam_c8450b289/reading-search-console-per-product-when-you-run-a-portfolio-queries-landing-pages-ctr-and-5hm5</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I work on LaunchReach, and this article uses its Search Console reporting as the worked example. The method applies with the raw Search Console UI too.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If you ship one product, Search Console is simple: one property, one list of queries. If you ship three or six, it gets awkward quickly. Each site is its own property, possibly under different Google accounts. You open tabs, export, compare by hand, and by the second week you stop doing it.&lt;/p&gt;

&lt;p&gt;This article is about a reading routine that keeps each product separate, so you can answer a few plain questions per product without mixing numbers.&lt;/p&gt;

&lt;h2&gt;
  
  
  The four metrics, and what each is actually for
&lt;/h2&gt;

&lt;p&gt;Search Console reports clicks, impressions, CTR and average position. LaunchReach's Search Console reporting shows these along with queries, landing pages, countries and devices, plus trend analysis. Here is how I would read them:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Impressions&lt;/strong&gt;: how often a page showed up in results. This is visibility, not interest.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Clicks&lt;/strong&gt;: how many people came through. This is the outcome.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CTR&lt;/strong&gt;: clicks divided by impressions. It tells you whether the listing is persuasive when it is seen.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Average position&lt;/strong&gt;: where you showed up on average. It is an average across queries and days, so treat it as a direction, not a precise rank.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of these is meaningful alone. High impressions with low CTR is a different problem from low impressions with high CTR.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why per-product matters in a portfolio
&lt;/h2&gt;

&lt;p&gt;A blended view hides the thing you want to know. If one product earns most of your impressions, the totals look healthy while the other products are invisible. Reading per product means you ask the same questions of each site and compare like with like.&lt;/p&gt;

&lt;p&gt;This is the reason LaunchReach lets you connect several sites and Google accounts to one workspace, with each site mapped to a product. The mapping is the important part: a landing page belongs to a product, and a query belongs to a landing page.&lt;/p&gt;

&lt;h2&gt;
  
  
  A routine you can repeat in 20 minutes per product
&lt;/h2&gt;

&lt;p&gt;Use the same four steps for every product, in the same order.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Start with the trend, not the table
&lt;/h3&gt;

&lt;p&gt;Look at clicks and impressions over time for the product. Is it rising, flat or falling? Note the direction and any sudden change. A flat line and a falling line call for different follow-ups. Trend analysis is where a report earns its keep, because a single week's number says little.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Group queries by landing page
&lt;/h3&gt;

&lt;p&gt;Queries on their own are a long list. Queries grouped under the landing page that received the click are a story: this page is being found for these phrases. For each product, list the top landing pages and, under each, its top queries.&lt;/p&gt;

&lt;p&gt;Then check one thing: does the query match what the page is about? If a pricing page is receiving informational queries, the page and the intent are mismatched, and that is a concrete thing to fix.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Find the gap between impressions and CTR
&lt;/h3&gt;

&lt;p&gt;Sort a product's queries by impressions and look for ones where CTR is low. These are searches where you are already visible but not chosen. Common causes are a title that does not say what the page offers, or a description that repeats the title. This is usually cheaper to fix than earning new rankings.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Check position for the queries that matter
&lt;/h3&gt;

&lt;p&gt;For the handful of queries that match your product's real buyer phrases, note the average position. If a query sits just off the first page, a page with a clearer match is worth more effort than a new page. Keep your own short list of buyer phrases per product. Note that average position can shift as you gain impressions on new queries, so compare the same query over time.&lt;/p&gt;

&lt;h2&gt;
  
  
  A small template per product
&lt;/h2&gt;

&lt;p&gt;Keep one note per product with these fields, updated on a schedule:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Product and property&lt;/li&gt;
&lt;li&gt;Trend direction (clicks, impressions)&lt;/li&gt;
&lt;li&gt;Top 3 landing pages and their top queries&lt;/li&gt;
&lt;li&gt;One query with high impressions and low CTR, and the change you will try&lt;/li&gt;
&lt;li&gt;One query close to a better position, and the page you will improve&lt;/li&gt;
&lt;li&gt;What you changed last time, and what happened&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The last line matters most. Without it, you are reading numbers without learning from them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where AI recommendations fit, and where they do not
&lt;/h2&gt;

&lt;p&gt;LaunchReach's website intelligence includes AI recommendations for search opportunities and weak landing pages, each citing the metrics behind it. The product also states that it does not claim attribution the data cannot support, and that AI recommendations are labelled as interpretations. I think that is the right stance. Treat any recommendation as a prompt to check the numbers, not a verdict. If a suggestion cites a metric, open that metric and see whether you agree.&lt;/p&gt;

&lt;h2&gt;
  
  
  Connecting search to what happens after the click
&lt;/h2&gt;

&lt;p&gt;Search Console stops at the click. To see what people do afterwards, you need analytics. LaunchReach connects GA4 and Search Console read-only, and GA4 reporting covers sessions, users, new versus returning, engagement, events, conversions and revenue when configured, across multiple properties. Reading both for the same product gives you the full line: which queries lead to which pages, and which pages hold attention.&lt;/p&gt;

&lt;p&gt;The read-only part is worth noting if you are cautious about connecting accounts: the tool reads the data and does not change your properties.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this will not tell you
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;It will not guarantee rankings. Search Console reports what happened, not what will.&lt;/li&gt;
&lt;li&gt;Average position is an average, not a fixed rank.&lt;/li&gt;
&lt;li&gt;Small sites have small numbers. A few clicks can swing CTR a lot, so avoid reacting to tiny samples.&lt;/li&gt;
&lt;li&gt;Search is one channel. Directory listings, communities and email have their own data.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A weekly rhythm for studios
&lt;/h2&gt;

&lt;p&gt;For a portfolio, I would keep it short and regular:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;One slot per week, one product at a time, same order.&lt;/li&gt;
&lt;li&gt;Fill in the template and write down a single change per product.&lt;/li&gt;
&lt;li&gt;Revisit the change after a few weeks and record the result.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The point of per-product reporting is not more dashboards. It is that each product gets the same honest look, so a quiet product does not hide behind a busy one.&lt;/p&gt;

&lt;p&gt;If you want to see this with your own sites, LaunchReach has a 7-day Growth trial for $1 (card or mobile money, nothing renews automatically). Connect a couple of properties, map each to a product, and run the routine above on real data. You can run the same routine in the raw Search Console UI if you prefer; the tool mostly saves the tab-switching.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mambatxhub.com/r/jnv5hcjx" rel="noopener noreferrer"&gt;Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>seo</category>
      <category>startup</category>
    </item>
    <item>
      <title>Product Hunt feels unreliable. Here is what to measure instead of the leaderboard</title>
      <dc:creator>Mohammad Shazam</dc:creator>
      <pubDate>Sun, 22 Nov 2026 09:53:45 +0000</pubDate>
      <link>https://dev.to/mohammad_shazam_c8450b289/product-hunt-feels-unreliable-here-is-what-to-measure-instead-of-the-leaderboard-2907</link>
      <guid>https://dev.to/mohammad_shazam_c8450b289/product-hunt-feels-unreliable-here-is-what-to-measure-instead-of-the-leaderboard-2907</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I work on LaunchReach, which is mentioned near the end. The first part of this article stands without it.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If you read founder discussions about launching on Product Hunt, a pattern shows up. People say the rankings are opaque, that vote counts shift without explanation, and that some placements seem tied to payment. One person in the research I read put it as having lost trust in the fairness of the competition. Another said upvotes don't correlate to anything.&lt;/p&gt;

&lt;p&gt;I can't verify any of those claims, and I don't know how the ranking works. Product Hunt's own ranking details are not something I have a record on. But I don't need to settle the fairness debate to say something useful: &lt;strong&gt;if you can't trust the leaderboard, don't use it as your scoreboard.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The trust problem, stated plainly
&lt;/h2&gt;

&lt;p&gt;Three complaints keep coming up in the discussions:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Opaque rankings.&lt;/strong&gt; Founders can't see why one launch sits above another, so a result can't be read as a signal of real interest.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Payment-linked placement.&lt;/strong&gt; Some founders describe it as pay-to-play. Whether or not that is accurate in a given case, the perception alone makes the number hard to rely on.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An audience of other founders.&lt;/strong&gt; One source describes the audience as mainly founders and makers. That is a fine crowd for feedback, but it is not automatically your buyer.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;There is also a quieter complaint: results depend on having supporters or an audience beforehand. Some founders report launches with very little to show, such as a single upvote, or around 150 visits and no signups. Those are individual reports, not a rate, so treat them as anecdotes. They do point at the real issue: a rank and a result are different things.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the rank is the wrong thing to track
&lt;/h2&gt;

&lt;p&gt;An upvote count answers one question: how many accounts clicked. It doesn't tell you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;whether the visitors were people who could buy your product&lt;/li&gt;
&lt;li&gt;whether they stayed on the site&lt;/li&gt;
&lt;li&gt;whether anyone signed up, and what happened next&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can finish high and get no customers, or finish low and get a handful of the right ones. Only your own data separates those cases.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to measure instead
&lt;/h2&gt;

&lt;p&gt;Here is a short list that works regardless of which directory or community you launch on.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Visits by source, not in total
&lt;/h3&gt;

&lt;p&gt;Total traffic on launch day blends everything. Give every destination its own tagged link, so each one has its own row in your analytics. A convention like &lt;code&gt;utm_source=producthunt&amp;amp;utm_medium=directory&amp;amp;utm_campaign=launch&lt;/code&gt; is enough. Keep it consistent, because messy tags are the usual reason rollups fall apart.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Engagement, not just sessions
&lt;/h3&gt;

&lt;p&gt;In GA4, look at engagement alongside sessions, and split new from returning users. A source that sends 300 sessions that bounce is worth less than one that sends 30 who read your pricing page.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Signups and conversions per source
&lt;/h3&gt;

&lt;p&gt;This is the number that matters. Mark signup as a conversion event in GA4, then read it by source. If a destination produced visits but zero signups, that is a finding, not a failure to hide.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Search Console, a few weeks later
&lt;/h3&gt;

&lt;p&gt;Launches sometimes change what people search for. Check clicks, impressions, queries and landing pages for movement after the launch. Keep the claim modest: a change in queries might be related to the launch, but you can't always prove it was.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. A dated note per destination
&lt;/h3&gt;

&lt;p&gt;Write down what you submitted, when, whether there was a fee, and what happened. Memory favours the loud day and forgets the quiet destination that sent your best signups.&lt;/p&gt;

&lt;h2&gt;
  
  
  A simple readout
&lt;/h2&gt;

&lt;p&gt;After two to four weeks, build one table:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Destination&lt;/th&gt;
&lt;th&gt;Visits&lt;/th&gt;
&lt;th&gt;Engaged sessions&lt;/th&gt;
&lt;th&gt;Signups&lt;/th&gt;
&lt;th&gt;Cost (fees + time)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Directory A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Community B&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Launch platform C&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Then decide what to repeat, what to drop, and what you simply can't tell yet. Being honest about "can't tell yet" matters. Small numbers are noisy, and attribution has limits: people see you in one place and sign up later through another.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where a tool can help (and where it can't)
&lt;/h2&gt;

&lt;p&gt;You can do all of this with a spreadsheet and careful UTM tags. If you're submitting to many destinations, the bookkeeping gets tedious, and that is the part LaunchReach handles. According to its website, it generates a separate UTM link for each submission, connects GA4 and Search Console read-only, and shows which directories, campaigns and queries drive visitors and signups. It also states that it doesn't claim attribution the data can't support, and that its AI recommendations are labelled as interpretations.&lt;/p&gt;

&lt;p&gt;Two limits worth stating. LaunchReach doesn't guarantee outcomes, because third-party destinations decide whether to accept or publish a listing. And its acceptable-use rules prohibit vote manipulation, so it is not a way to buy a leaderboard position.&lt;/p&gt;

&lt;h2&gt;
  
  
  The takeaway
&lt;/h2&gt;

&lt;p&gt;You may never learn whether a ranking was fair. You can learn whether a launch produced visitors who engaged and signed up, if you set up measurement before you submit. Tag every link, read conversions by source, and let your own numbers decide where you launch next.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mambatxhub.com/r/m7gu8yty" rel="noopener noreferrer"&gt;Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>marketing</category>
      <category>saas</category>
      <category>startup</category>
    </item>
    <item>
      <title>A UTM naming convention for launch week: one link per directory, clean GA4 rollups</title>
      <dc:creator>Mohammad Shazam</dc:creator>
      <pubDate>Sun, 22 Nov 2026 09:52:09 +0000</pubDate>
      <link>https://dev.to/mohammad_shazam_c8450b289/a-utm-naming-convention-for-launch-week-one-link-per-directory-clean-ga4-rollups-4a79</link>
      <guid>https://dev.to/mohammad_shazam_c8450b289/a-utm-naming-convention-for-launch-week-one-link-per-directory-clean-ga4-rollups-4a79</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I work on LaunchReach, which generates a tagged link per submission. The convention below works with any spreadsheet and any analytics setup, and I note where the product fits at the end.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If you submit a product to a handful of launch directories and communities, you will probably look at GA4 a week later and see traffic split across &lt;code&gt;producthunt&lt;/code&gt;, &lt;code&gt;ProductHunt&lt;/code&gt;, &lt;code&gt;product_hunt&lt;/code&gt; and &lt;code&gt;ph&lt;/code&gt;. Each one is a separate row. Nothing is broken; the tags were just never agreed on.&lt;/p&gt;

&lt;p&gt;This tutorial sets up a small naming convention you can write down before launch week, so the reports roll up by destination without cleanup afterwards.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the three parameters do
&lt;/h2&gt;

&lt;p&gt;GA4 reads these UTM parameters from your landing URL:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;utm_source&lt;/code&gt;: where the visitor came from (the specific destination)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;utm_medium&lt;/code&gt;: the type of channel&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;utm_campaign&lt;/code&gt;: the effort this link belongs to&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;GA4 is case-sensitive about values. &lt;code&gt;Directory&lt;/code&gt; and &lt;code&gt;directory&lt;/code&gt; are two different mediums. That is the main reason a convention matters.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Fix the rules before you write any link
&lt;/h2&gt;

&lt;p&gt;Four rules cover most of it:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Lowercase only.&lt;/strong&gt; No exceptions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hyphens for spaces, no other punctuation.&lt;/strong&gt; &lt;code&gt;show-hn&lt;/code&gt;, not &lt;code&gt;Show HN&lt;/code&gt; or &lt;code&gt;show_hn&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One name per destination, forever.&lt;/strong&gt; Decide it once and put it in a sheet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No personal or sensitive data in any value.&lt;/strong&gt; UTM values show up in URLs, reports and sometimes shared screenshots.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Step 2: Choose source = the destination
&lt;/h2&gt;

&lt;p&gt;Source is the one you will filter by most, so make it the destination's name in its simplest form:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;utm_source=producthunt
utm_source=show-hn
utm_source=indie-hackers
utm_source=devto
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Do not put the campaign or date in the source. If you do, the same destination ends up with several sources and you lose the rollup you wanted.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Choose a small, closed list for medium
&lt;/h2&gt;

&lt;p&gt;Medium should come from a short list you never extend casually. For a launch, three or four values are enough:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;directory&lt;/code&gt;: listing sites where you submit a product page&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;community&lt;/code&gt;: forums and discussion sites where you post&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;email&lt;/code&gt;: messages you send to your own list&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;social&lt;/code&gt;: posts on social networks&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The point of a closed list is that you can group by medium and compare types of channel. If you invent a new medium for every launch, that comparison disappears.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Make campaign describe the launch, not the place
&lt;/h2&gt;

&lt;p&gt;Campaign is the effort, so every link in the same launch shares it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;utm_campaign=launch-v1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you ship a second launch later, use &lt;code&gt;launch-v2&lt;/code&gt; or something like &lt;code&gt;pricing-relaunch&lt;/code&gt;. Keep a pattern: &lt;code&gt;&amp;lt;what&amp;gt;-&amp;lt;version or month&amp;gt;&lt;/code&gt;. Then you can compare launches by campaign, and destinations within a launch by source.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Build a sheet with one row per destination
&lt;/h2&gt;

&lt;p&gt;A plain spreadsheet is enough:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;destination&lt;/th&gt;
&lt;th&gt;source&lt;/th&gt;
&lt;th&gt;medium&lt;/th&gt;
&lt;th&gt;campaign&lt;/th&gt;
&lt;th&gt;final URL&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Product Hunt&lt;/td&gt;
&lt;td&gt;producthunt&lt;/td&gt;
&lt;td&gt;directory&lt;/td&gt;
&lt;td&gt;launch-v1&lt;/td&gt;
&lt;td&gt;&lt;code&gt;https://example.com/?utm_source=producthunt&amp;amp;utm_medium=directory&amp;amp;utm_campaign=launch-v1&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Show HN&lt;/td&gt;
&lt;td&gt;show-hn&lt;/td&gt;
&lt;td&gt;community&lt;/td&gt;
&lt;td&gt;launch-v1&lt;/td&gt;
&lt;td&gt;&lt;code&gt;https://example.com/?utm_source=show-hn&amp;amp;utm_medium=community&amp;amp;utm_campaign=launch-v1&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dev.to&lt;/td&gt;
&lt;td&gt;devto&lt;/td&gt;
&lt;td&gt;community&lt;/td&gt;
&lt;td&gt;launch-v1&lt;/td&gt;
&lt;td&gt;&lt;code&gt;https://example.com/?utm_source=devto&amp;amp;utm_medium=community&amp;amp;utm_campaign=launch-v1&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;(&lt;code&gt;example.com&lt;/code&gt; is a placeholder. Use your own landing page.)&lt;/p&gt;

&lt;p&gt;Two habits keep this sheet useful:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Fill it &lt;strong&gt;before&lt;/strong&gt; you submit anywhere, so nobody is typing tags from memory at the last minute.&lt;/li&gt;
&lt;li&gt;Add a column for the date you submitted and the outcome. Later you can match it against what GA4 shows.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 6: Point each link at a page that can convert
&lt;/h2&gt;

&lt;p&gt;A tagged link only tells you where someone came from. Decide where they land. Sending every destination to the same homepage is fine for a first launch, but think about whether a community audience would be better served by a page that matches what you wrote in the post. If you change landing pages per destination, record that in the sheet too, because it changes how you read the numbers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 7: Check the tags before launch day
&lt;/h2&gt;

&lt;p&gt;Before you submit, open each link yourself once. Then in GA4, look at the real-time report and confirm your visit shows the source and medium you expect. It takes a few minutes and catches typos while they are cheap to fix.&lt;/p&gt;

&lt;p&gt;Also check that your signup or key event is configured as a conversion in GA4. Without that you will see sessions per source but not which source produced signups.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 8: Read the report by source first, then by medium
&lt;/h2&gt;

&lt;p&gt;After launch week, in GA4's traffic acquisition view, look at session source / medium. Because you stuck to the convention you should see one clean row per destination, such as &lt;code&gt;show-hn / community&lt;/code&gt;. Group by medium to compare directories against communities, and filter by campaign to isolate this launch.&lt;/p&gt;

&lt;p&gt;One caveat: UTM tags only measure visits that came through the tagged link. Someone who sees your product on a directory and later types your URL will show up as direct. Treat the numbers as a floor for a destination, not an exact total.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Mixed case.&lt;/strong&gt; Fixed by rule 1.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tagging internal links.&lt;/strong&gt; Do not add UTMs to links on your own site; they overwrite the original source.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reusing a tagged link everywhere.&lt;/strong&gt; One link shared across destinations gives you one row and no comparison.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Changing names mid-launch.&lt;/strong&gt; If you rename a source after the first posts, the old and new names will sit side by side in reports.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where LaunchReach fits
&lt;/h2&gt;

&lt;p&gt;If you would rather not maintain the sheet by hand: according to its website, LaunchReach gives every submission and campaign its own tagged link and connects GA4 and Search Console read-only, so traffic and signups can be attributed per destination. It also states that it does not claim attribution the data cannot support, which matches the caveat in step 8. You can use the convention above either way; it just makes the by-hand version predictable.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Lowercase, hyphens, no sensitive data.&lt;/li&gt;
&lt;li&gt;Source = destination, medium = a short closed list, campaign = the launch.&lt;/li&gt;
&lt;li&gt;One row per destination in a sheet, filled in before you submit.&lt;/li&gt;
&lt;li&gt;Test each link, then read GA4 by source, then by medium.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What naming rules do you use that I missed? I would like to hear how others handle sources for destinations that appear under several names.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mambatxhub.com/r/4t7ntnax" rel="noopener noreferrer"&gt;Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>marketing</category>
      <category>startup</category>
    </item>
    <item>
      <title>How to work through a 400-directory list without losing track</title>
      <dc:creator>Mohammad Shazam</dc:creator>
      <pubDate>Sun, 22 Nov 2026 09:51:23 +0000</pubDate>
      <link>https://dev.to/mohammad_shazam_c8450b289/how-to-work-through-a-400-directory-list-without-losing-track-1k1j</link>
      <guid>https://dev.to/mohammad_shazam_c8450b289/how-to-work-through-a-400-directory-list-without-losing-track-1k1j</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I write for LaunchReach, which has features for parts of this workflow. The method below works with any spreadsheet.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A founder on r/SaaS recently described having a list of 400+ directories and launch platforms before a launch. They asked whether people submit by hand, pay a service or hire a freelancer, and what the most annoying part is. Their own list of pain points: Google logins, CAPTCHAs, retyping descriptions, and tracking which listings are live.&lt;/p&gt;

&lt;p&gt;That list is a good outline for a process. Founders in other discussions describe the same routine every launch: search for directories, find outdated lists, track submissions in a spreadsheet. Here is a way to make a long list manageable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Don't submit to 400. Triage first.
&lt;/h2&gt;

&lt;p&gt;A long list is mostly noise. Before you touch a form, add one column called &lt;code&gt;fit&lt;/code&gt; and score each row quickly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A&lt;/strong&gt;: your buyers plausibly browse it (right category, right audience, accepts SaaS)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;B&lt;/strong&gt;: generic, might help with a backlink or discovery, low effort&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;C&lt;/strong&gt;: wrong category, dead, or asks for something you can't give&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Spend about ten seconds per row. Don't research deeply yet. Then sort and work only on the A rows. Revisit B later if you have time. Delete or archive C so it stops costing attention.&lt;/p&gt;

&lt;p&gt;The point is that effort goes to the directories where a listing could plausibly matter, instead of to whatever is first alphabetically.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Record friction before you start
&lt;/h2&gt;

&lt;p&gt;The annoying parts the founder listed are predictable, so note them up front rather than discovering them mid-form. Add these columns:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;login&lt;/code&gt;: none / email / Google / other&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;captcha&lt;/code&gt;: yes / no / unknown&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;fee&lt;/code&gt;: free / paid (and the amount)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;manual_only&lt;/code&gt;: yes if a person must post it themselves (community-style posts, for example)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Now you can batch by friction. Do all the Google-login directories in one sitting while you are signed in to the right account. Do the CAPTCHA ones when you can give them your attention. Leave the paid ones for a deliberate yes or no decision instead of buying out of momentum.&lt;/p&gt;

&lt;p&gt;Batching alone removes much of the context-switching that makes this work feel endless.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Write copy once, then adapt per directory
&lt;/h2&gt;

&lt;p&gt;Retyping descriptions is the other complaint. Keep a single source doc with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a one-line description&lt;/li&gt;
&lt;li&gt;a 50-word description&lt;/li&gt;
&lt;li&gt;a 150-word description&lt;/li&gt;
&lt;li&gt;the category and tags you'd pick&lt;/li&gt;
&lt;li&gt;logo and screenshot filenames&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Directories differ on length limits and rules, so paste from the nearest size and adjust, rather than rewriting from nothing. Add a &lt;code&gt;copy_version&lt;/code&gt; column so you can see which version went where.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Give each submission its own tagged link
&lt;/h2&gt;

&lt;p&gt;If you want to know later whether any directory brought users (the founder asked this too), the link you submit has to be distinguishable. Put a UTM-tagged URL in each row, with the directory name as the &lt;code&gt;utm_source&lt;/code&gt;. Then your analytics can separate one directory from the next. Be modest about conclusions, though: a tagged link only captures people who click through it, and small numbers prove little.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Track live status per row, not just "submitted"
&lt;/h2&gt;

&lt;p&gt;This is the column most sheets lack. "Submitted" is not an outcome. Directories decide whether to accept, publish or remove a listing, so use a status that reflects reality:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;not_started&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;blocked&lt;/code&gt; (needs login, CAPTCHA, payment or a human step)&lt;/li&gt;
&lt;li&gt;&lt;code&gt;submitted&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;pending_review&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;live&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;rejected&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;removed&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Also add &lt;code&gt;submitted_on&lt;/code&gt;, &lt;code&gt;last_checked&lt;/code&gt; and &lt;code&gt;listing_url&lt;/code&gt;. When a listing goes live, paste the URL. A week or two later, check that it is still there and update &lt;code&gt;last_checked&lt;/code&gt;. Without this, you end up with a spreadsheet full of "done" that you can't trust.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Respect the rules
&lt;/h2&gt;

&lt;p&gt;Don't try to get around CAPTCHAs, 2FA or a directory's terms, and don't resubmit the same product repeatedly against a site's rules. If a step needs a human, mark it &lt;code&gt;blocked&lt;/code&gt; and do it yourself. That is also what makes the sheet honest: each row shows what a person still has to do.&lt;/p&gt;

&lt;h2&gt;
  
  
  A weekly rhythm
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Sort by &lt;code&gt;fit = A&lt;/code&gt; and &lt;code&gt;status = not_started&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Pick a batch with the same friction type.&lt;/li&gt;
&lt;li&gt;Submit, record the status and the tagged link.&lt;/li&gt;
&lt;li&gt;Once a week, update &lt;code&gt;pending_review&lt;/code&gt; rows and check live ones.&lt;/li&gt;
&lt;li&gt;Once a month, look at which tagged links got visits and which rows are worth repeating for your next product.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Where a tool fits
&lt;/h2&gt;

&lt;p&gt;You can run all of this in a spreadsheet, and for a first launch that may be enough. If you'd rather not maintain it by hand, LaunchReach covers the same ground: you add a product once and it ranks 45 destinations by fit, with copy written to each destination's rules. Where a destination has an official API it submits through that. Where a form is the only option it can fill it using your authorised session, only where the platform's terms allow. It pauses when a human is needed rather than bypassing CAPTCHA or 2FA, and for communities like Show HN you post yourself while it prepares the copy and records the outcome. Each submission gets its own UTM link. Listing fees are shown before approval and passed through at cost, and it doesn't guarantee that any directory will accept or keep a listing.&lt;/p&gt;

&lt;p&gt;It is a narrower list than 400, so it is a different tradeoff: fewer destinations, ranked and tracked, rather than a giant list you triage yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  Takeaway
&lt;/h2&gt;

&lt;p&gt;With a long list, the bottleneck is attention, not typing. Score for fit, log friction up front, reuse your copy, tag every link, and track live status per row. That turns 400 rows into a short queue you can actually finish.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mambatxhub.com/r/gaf843rc" rel="noopener noreferrer"&gt;Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>marketing</category>
      <category>productivity</category>
      <category>saas</category>
      <category>startup</category>
    </item>
    <item>
      <title>Why a blank field in a launch directory is more honest than a guess</title>
      <dc:creator>Mohammad Shazam</dc:creator>
      <pubDate>Sun, 22 Nov 2026 09:43:23 +0000</pubDate>
      <link>https://dev.to/mohammad_shazam_c8450b289/why-a-blank-field-in-a-launch-directory-is-more-honest-than-a-guess-29co</link>
      <guid>https://dev.to/mohammad_shazam_c8450b289/why-a-blank-field-in-a-launch-directory-is-more-honest-than-a-guess-29co</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I work on LaunchReach, which publishes the directory discussed below. This is a draft for human review, and the product is mentioned where it is relevant.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If you have ever built a spreadsheet of places to launch your SaaS, you know how it goes. You list the sites, then fill in the columns: does it accept free listings, is there an API, how long does review take, what is the character limit on the description. Halfway down, you start filling cells with what seems likely. Then a month later you trust the spreadsheet as if you had checked it.&lt;/p&gt;

&lt;p&gt;This article is about that habit, and about why we think a directory should leave a cell empty when nobody has confirmed the answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem with plausible guesses
&lt;/h2&gt;

&lt;p&gt;A guess in a directory looks identical to a fact. There is no visual difference between "accepts submissions via form" that someone verified and one that someone assumed because similar sites do. The reader cannot tell, so the reader plans around both equally.&lt;/p&gt;

&lt;p&gt;For a founder, the cost shows up in specific places:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You prepare copy for a field that does not exist, or miss one that does.&lt;/li&gt;
&lt;li&gt;You assume a listing is free and find a fee at the last step.&lt;/li&gt;
&lt;li&gt;You assume a site has an official submission route and build around it, when it is actually a manual form.&lt;/li&gt;
&lt;li&gt;You schedule your week around a review time that was never stated.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of these is catastrophic alone. Together they eat the few days you set aside for launch, and they erode trust in the whole list. After the first wrong cell, you recheck everything, which defeats the point of having a directory.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the public platforms page says
&lt;/h2&gt;

&lt;p&gt;LaunchReach has a public page listing the launch platforms it works with: 45 destinations in total. The rule the page follows is simple: items that have not been confirmed are left blank rather than guessed.&lt;/p&gt;

&lt;p&gt;I want to be careful about what that does and does not mean. It does not mean every field for every platform is filled in. It means that when you see a value, someone has confirmed it, and when you see nothing, the honest reading is "unknown", not "probably yes" and not "probably no".&lt;/p&gt;

&lt;p&gt;I will not list per-platform details here, because this article should not claim more than the page itself supports. Go and read the page; the blanks are part of the content.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to read a blank
&lt;/h2&gt;

&lt;p&gt;A blank is a prompt to do a small amount of work before you commit. Here is how I would treat one:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Check the destination's own page.&lt;/strong&gt; The platform's submission page or terms are the primary source. If you find the answer, you have more than the directory had.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Treat the blank as a risk, not a no.&lt;/strong&gt; An unknown fee or rule is something to verify before you prepare assets, not a reason to drop the platform.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write down what you found and when.&lt;/strong&gt; Rules on third-party sites change. A dated note beats a memory.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Order your list by what is known.&lt;/strong&gt; Do the destinations where you can verify the requirements first. Leave the uncertain ones for when you have time to check.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This is slower than trusting a full table. It is also the only way I know to avoid the failure where a confident-looking cell turns out to be wrong at submission time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this matters more for a portfolio
&lt;/h2&gt;

&lt;p&gt;If you run one product, a wrong assumption costs you an afternoon. If you run a studio with several products, the same wrong assumption gets copied across every product, because you reuse the checklist. A single unverified cell becomes several wasted submissions.&lt;/p&gt;

&lt;p&gt;That is an argument for keeping a clear record of the difference between confirmed and assumed, whatever tool you use. Even a plain spreadsheet can do it with a "confirmed on" column that stays empty until you have actually looked.&lt;/p&gt;

&lt;h2&gt;
  
  
  The same principle applies to outcomes
&lt;/h2&gt;

&lt;p&gt;The blank-over-guess rule is not only about directory fields. It is about outcomes as well. On LaunchReach's side, the terms state that third-party destinations decide whether to accept, publish or remove a listing, and that LaunchReach does not guarantee outcomes. The product also states that it does not claim attribution the data cannot support, and that AI recommendations are labelled as interpretations.&lt;/p&gt;

&lt;p&gt;That is the same idea in a different place: say what is known, mark what is interpretation, and leave out what cannot be supported. If a tool tells you which directory drove your signups, you want to know whether that came from a tagged link or from a hunch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the directory fits in the product
&lt;/h2&gt;

&lt;p&gt;For context, here is what LaunchReach does with the directory, based on what the product site states. You add a product once and it reaches 45 destinations, ranked by fit, with copy written per destination's rules. Where a destination has an official API, submission goes through a dedicated adapter. Where it does not, browser automation fills web forms using your authorised session, only where platform terms allow. For communities such as Show HN, you post yourself and LaunchReach prepares the copy and records the outcome. It never bypasses CAPTCHA, 2FA or platform rules, and it pauses when a human is needed.&lt;/p&gt;

&lt;p&gt;Each submission also gets its own UTM link, so traffic and signups roll up to the right destination.&lt;/p&gt;

&lt;p&gt;That is the practical reason the blanks matter to us. If the product is going to prepare copy per destination's rules, it needs to know which rules are confirmed. Guessing would produce confident, wrong copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  A practical checklist you can use without any tool
&lt;/h2&gt;

&lt;p&gt;If you maintain your own list, try this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Add a "source" column: link to the page where you confirmed each fact.&lt;/li&gt;
&lt;li&gt;Add a "confirmed on" date.&lt;/li&gt;
&lt;li&gt;Leave a cell empty rather than writing "probably".&lt;/li&gt;
&lt;li&gt;Mark fees separately, and check them before you write any copy.&lt;/li&gt;
&lt;li&gt;Re-verify anything older than your launch window.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It takes more discipline than filling in a table from memory, but you end up with a list you can rely on at 11pm the night before launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I would take from this
&lt;/h2&gt;

&lt;p&gt;A directory is a tool for saving time, and it only saves time if you can trust it. The way to earn that trust is to be explicit about the edges of what you know. A blank cell tells you where to look. A guess tells you nothing and hides the gap.&lt;/p&gt;

&lt;p&gt;If you want to see how this looks in practice, the platforms page is public. LaunchReach also has a 7-day Growth trial for $1, paid by card or mobile money, and nothing renews automatically. Growth includes 60 submissions per month and attribution by destination. Directory listing fees are shown before approval and passed through at cost.&lt;/p&gt;

&lt;p&gt;Whatever you use, keep the habit: confirmed means confirmed, and unknown stays unknown.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mambatxhub.com/r/upcnjpda" rel="noopener noreferrer"&gt;Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>product</category>
      <category>saas</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
