DEV Community: Amrita Labs

How to Tell If Your Pinterest Pin Will Perform (Before You Post)

Amrita Labs — Wed, 29 Jul 2026 00:00:00 +0000

Some Pinterest pins feel dead on arrival.

You post them, maybe give them a day, and it is obvious they are not going anywhere. Then another pin — sometimes one you spent less time on — keeps getting impressions, saves, and clicks for weeks. That used to feel random to me. The more pins I watched, the less random it looked.

A lot of the difference shows up before the pin is even published. Pinterest gets an immediate set of signals from the image, the board, the title, the description, and then the first wave of engagement. If those signals are weak, the pin rarely gets much room to recover.

Pinello is a free Chrome extension that scores Pinterest pins across 5 dimensions — image, board fit, title, description, and keywords — in real time, directly on pinterest.com.

This is the pre-publish check I use when I want a pin to have a better shot.

The first 24 hours matter more than people think

Pinterest is not purely chronological, but early signals still matter.

If a pin gets a decent first impression — people stop, save, or click — Pinterest has a reason to keep showing it. If the pin looks confusing, mismatched, or under-optimized, it often stalls before it gets that chance.

That is why I care so much about the stuff that is fixable before I post.

The 5 signals I look at before posting a pin

1. Will the image stop the scroll?

Before I think about keywords, I do the thumbnail test.

Pinterest is visual, and the image gets judged fast. I usually stick to 2:3 vertical format (1000×1500px) because it fills the feed cleanly without weird cropping. Then I ask a few blunt questions:

Is the pin readable on a phone?
Is there one clear focal point?
Does the text overlay help, or is it fighting the image?
Does the topic make sense in a second or less?

If the thumbnail looks muddy or crowded, the rest of the pin has to work too hard.

2. Does the board make the topic obvious?

The board is not just a folder. It is context.

A pin about weeknight recipes belongs on a board that sounds like weeknight recipes, not a vague catch-all board with a cute name. The stronger the board context, the easier it is for Pinterest to understand what audience the pin belongs with.

I want the board to do three things:

use a searchable topic phrase
already contain enough related pins to feel coherent
make the new pin feel obviously on-theme

When I save a great pin to a lazy board, I usually regret it later.

3. Does the title carry the keyword early enough?

A good Pinterest title does not need to be fancy. It needs to be legible, specific, and front-loaded.

Only part of the title gets real attention in the feed, especially on mobile, so I try to get the key phrase near the front. Titles like these do a clearer job:

"Minimalist Bedroom Ideas for Small Spaces"
"25 Modern Bathroom Ideas Under $500"
"2026 Wedding Color Trends"

What I avoid are titles that waste the opening on filler: "Check this out," "I love this," "Great tips," and so on. They may sound friendly, but they do not help Pinterest or the reader understand the pin.

4. Does the description give Pinterest enough context?

This is where a lot of pins quietly underperform.

If the description is blank, Pinterest has less text to work with. If the description is robotic, it feels stuffed. I want something in the middle: enough context to reinforce the topic, but still readable.

Usually that means 100-300 characters and 2-3 natural sentences.

I also do not waste space on hashtag stuffing here. On Pinterest, that space is better spent on plain-language keywords that actually describe the pin.

For example:

"Easy 30-minute chicken stir fry recipe with vegetables. A simple weeknight dinner idea for busy families who still want something healthy. Save this for your next meal prep day."

That does not try too hard. It just tells Pinterest, and the reader, what the pin is for.

5. Am I giving the pin a decent first-day chance?

This is the signal people skip because it feels less tangible.

The first 24 hours still matter. Saves are strong. Clicks help. Even just stopping the scroll matters more than a pin getting tossed into the void at a random time.

So before I post, I try to think about distribution too:

Am I posting when my audience is actually around?
Is this going to the most relevant board first?
Do I have a reason to expect early saves or clicks?

I do not obsess over timing hacks, but I do not pretend timing is irrelevant either.

My pre-publish Pinterest pin checklist

Before every pin, I run through this:

Dimension	✅ Ready to post	❌ Fix first
Image	2:3 ratio, bright, readable at thumbnail	Square/landscape, dark, tiny text
Board	Keyword title, 10+ pins, topically matched	Creative name, empty, random mix
Title	Keyword in first 40 chars, specific	Vague, starts with filler words
Description	100-300 chars, 2-3 keywords, CTA	Empty, one sentence, hashtag spam
Timing	Peak hours for your audience	Random time, no thought to scheduling

If even one row feels weak, I usually fix it. That is much easier than trying to diagnose a flop afterward.

What I automate now

You can absolutely do this checklist manually. I still do, sometimes.

But if you are publishing a lot of pins, the easy mistakes pile up. Wrong board. Weak title. Empty description. Image resized badly in a rush. That is why we built Pinello to score those dimensions directly on pinterest.com while the pin is still in front of you.

The main benefit is not that it predicts the future perfectly. It is that it catches the obvious misses before they become performance problems.

The few changes that fix most weak pins

If I had to simplify all of this down to the handful of fixes that matter most, it would be these:

Use vertical 2:3 images. This is still the easiest win.
Put the keyword early in the title. Do not bury the topic.
Write a real description. Empty descriptions are usually wasted upside.
Choose the board on purpose. Context matters more than a lot of creators assume.

That will not guarantee a viral pin. It will give the pin a fairer chance, which is usually the more useful goal.

Score your next pin before posting

Before you hit publish, give the pin one last check. Install Pinello from the Chrome Web Store — it's free, works directly on pinterest.com, and scores your pins across all 5 dimensions before you post. No signup needed.

Written by the team at Amrita Labs. We build browser tools that help creators optimize before publishing.

How I Set Up PostHog in a Chrome Extension (MV3, Content Script + Background Worker)

Amrita Labs — Tue, 28 Jul 2026 10:00:00 +0000

Every analytics tutorial I found assumed I was building a normal web app. One runtime. One page lifecycle. One obvious place to initialize the SDK.

A Chrome extension in V3 is not that polite.

In Manifest V3, you have a background service worker that goes to sleep, content scripts living inside tabs, and little UI surfaces like the popup that vanish the second someone clicks away. The first time I tried to add PostHog to that setup, I realized the usual advice was not going to help much.

So this is the setup I ended up with for a Chrome extension: simple enough to maintain, anonymous by default, and good enough to answer the only questions I actually care about.

The first decision: where PostHog should live

This is the part that matters most.

You can initialize PostHog in the background service worker. You get one shared place, which is nice. But the background worker cannot see the DOM, and most of the interesting product moments in my extensions happen where the user is typing or looking at something inside the page.

You can initialize it in the popup or options page too. That is easy, but it only works while that UI is open. For actual product usage, that felt too narrow.

I ended up initializing PostHog in the content script. That puts it closest to the real user action. In MV3, content scripts run in an isolated world, so PostHog's CDN setup is workable there as long as the project API key is available at build time.

I still use the background worker for extension plumbing. I just do not make it the main analytics home.

The small build-time trick that makes this workable

The PostHog project API key is public anyway, so I stopped overthinking it and baked it into the build:

// wxt.config.ts — bake the key at build time
// Set VITE_POSTHOG_PROJECT_API_KEY in your CI secrets

// telemetry.ts
const POSTHOG_KEY = import.meta.env.VITE_POSTHOG_PROJECT_API_KEY;

That avoided adding another config fetch or permission dance. For a Chrome extension, fewer moving parts is usually the right answer.

I use an anonymous device ID, not a user ID

I did not want email addresses, names, or anything else that would make the privacy story messy. Privacy of my users as important to me as my own privacy while using products.

So on install, I generate a random UUID and keep it in chrome.storage.local:

async function getOrCreateDeviceId(): Promise<string> {
  const stored = await chrome.storage.local.get("deviceId");
  if (stored.deviceId) return stored.deviceId;
  const id = crypto.randomUUID();
  await chrome.storage.local.set({ deviceId: id });
  return id;
}

That becomes PostHog's distinct_id.

It is enough to answer questions like "Did this person install and come back?" without turning the extension into a surveillance project.

I track fewer events than I thought I would

My first instinct was to track everything. That would have been a mistake.

In practice, four events told me almost everything I needed to know:

// Install (once)
posthog.capture("install", { version: chrome.runtime.getManifest().version });

// Core value action (the moment they get value)
posthog.capture("subject_scored", { dimension: "title" });

// Monetization trigger
posthog.capture("paywall_shown", { tier: "free", scores_used: 50 });

// Expansion action
posthog.capture("rewrite_requested", { dimension: "description" });

That is it.

Those four events tell me whether people are installing, reaching the value moment, hitting the limit, and asking for the "do it for me" feature. I can always add more later, but starting small kept the data readable.

Debugging got easier once I stopped putting it in the UI

For development, I auto-enable debug mode:

const debugEnabled = import.meta.env.MODE === "development";

And if I need to turn on extra logging manually, I can do it from DevTools:

chrome.storage.local.set({ debugLogging: true });

I briefly considered a user-facing debug toggle. Then I imagined normal users seeing it and wondering whether something was broken. That was enough to kill the idea.

The dashboard I actually check

This part is refreshingly unglamorous.

I set up one funnel insight:

Install
Core action
Paywall shown

Then I filter by app and look at daily trends.

That is basically the whole analytics system. I do not need 19 dashboards. I need a quick answer to: are people using the thing, and where do they stop?

The privacy part I did not want to get wrong

A few rules I kept from day one:

✅ Anonymous UUID only — no PII
✅ No page content in events, only counts and categories
✅ Privacy policy discloses anonymous usage events
✅ Chrome Web Store data disclosure does not claim personally identifiable information
✅ Even if a UUID is often treated differently from direct personal data, I still disclose it plainly

That gave me a setup I could defend without squirming.

If I were helping a friend do this tomorrow

I would not start with "How do I instrument everything?"

I would start with:

one place to initialize PostHog
one anonymous identifier
four or five events that map to the funnel
one dashboard you will actually open

That gets you useful telemetry in a Chrome extension without letting analytics become its own side project.

Written by the team at Amrita Labs. We build Chrome extensions with privacy-first analytics.

Azure Functions ESM Imports: The Silent Bug That Deploys Fine and Registers 0 Endpoints

Amrita Labs — Tue, 28 Jul 2026 00:00:00 +0000

I had one of those deploys that makes you question your own eyesight. func azure functionapp publish said everything was fine. Azure Portal showed a healthy Function App. My local tests passed. The build passed. Then I ran az functionapp function list and got... nothing.

Not broken endpoints. Not one broken endpoint. Zero endpoints registered.

I lost about four hours to this before the fix turned out to be one boring, insulting detail: I was missing .js on a relative import.

The setup looked healthy

This was the stack:

Azure Functions v4
Node.js 22
TypeScript
"type": "module" in package.json
Clean local runs

Which is exactly why this bug is so annoying. Everything around the app looks healthy. Azure uploads the code just fine. The runtime is what falls over.

The actual ESM import problem in Azure Functions

In Node ESM, relative imports need file extensions. Every time. TypeScript does not magically exempt you from that.

// ❌ Looks fine in dev, fails in production Node ESM
import { logLlmCall } from "../telemetry";

// ✅ What the runtime actually needs
import { logLlmCall } from "../telemetry.js";

That mismatch was the whole issue.

TypeScript compiled happily. Vitest ran happily. My editor did not complain. But once Azure tried to load the compiled JavaScript, Node followed ESM rules strictly, hit ERR_MODULE_NOT_FOUND, and the Functions host never finished registering the app.

Why Azure Functions feels silent when this breaks

This is the part that made the whole thing feel cursed.

The deploy command can still succeed because the package upload is fine. The Function App can still start. The failure happens during cold start, when the runtime walks your module graph. If one import is wrong, the app crashes before Azure registers any functions.

So from the outside, it looks like a successful deployment with a mysteriously empty Function App. The real error usually lives in Application Insights, not in the publish output.

How I finally diagnosed it

The first useful command was this:

az functionapp function list --name your-func-app --resource-group your-rg

If that returns an empty array right after a "successful" deploy, I would assume cold-start failure until proven otherwise.

From there, Application Insights told the truth. In Traces, filtering for ERR_MODULE_NOT_FOUND made the problem obvious.

The fix was annoyingly simple

I went through every relative import in my TypeScript source and added .js:

import { coherenceScore } from "./scoring.js";
import { logLlmCall } from "../telemetry.js";
import { CACHE_TTL } from "../../shared/constants.js";

Yes, importing .js from a .ts file feels wrong the first time you do it.

Yes, it is still the right thing to do for Node ESM.

After that, the exact same deployment registered endpoints normally.

What I would check before every Azure Functions ESM deploy now

If I were doing this from scratch again, I would add a quick pre-deploy check for imports missing .js in the built output:

grep -rn "from \"\.\." dist/ | grep -v "\.js\"" | grep -v "node_modules"

If that returns anything, I would stop there and fix it before touching Azure.

Two other Azure Functions + ESM gotchas I hit

While I was in this rabbit hole, two more sharp edges showed up:

func azure functionapp publish needs FUNCTIONS_WORKER_RUNTIME either in local.settings.json or via the --javascript flag. Without it, you get "Can't determine project language."
The npm-installed func CLI can break on newer Node versions. On Node 26+, I had better luck with winget install Microsoft.Azure.FunctionsCoreTools.

If you are deploying a Chrome extension backend or any small Node service to Azure Functions, this is worth checking early. When ESM imports are wrong, Azure does not always scream. Sometimes it just smiles, deploys, and gives you an app with no functions.

Written by the team at Amrita Labs. We build Chrome extensions powered by serverless backends on Azure.

I Built a Chrome Extension That Scores Your Gmail Subject Lines — Here's What I Learned

Amrita Labs — Tue, 28 Jul 2026 00:00:00 +0000

A few months ago I was sending cold emails for a side project. Personalized openers, clear asks, short paragraphs — I thought the emails were good. But my reply rate was garbage. Like, 1-2% garbage.

I started digging into why. Turns out most of my emails weren't even being opened. They were landing in spam or getting ignored at the subject line.

The frustrating part? I'd spend 20 minutes writing a thoughtful email body, then slap on a subject line in 5 seconds. "Quick question." "Following up." "Hey!" Basically handing Gmail's spam filter a reason to bury me.

So I did what any engineer would do when annoyed enough — I built something.

What I actually built

EmailSubjectScore Pro is a Chrome extension that sits inside Gmail's compose window. As you type a subject line, it scores it on three things:

Spam risk — are you triggering filters without realizing it?
Clarity — does the recipient know what this email is about?
Urgency — is there a reason to open it now vs. never?

If your subject scores poorly, you hit "Suggest rewrite" and the AI proposes alternatives. You pick one, it drops into the subject field. Done.

No external tabs. No copy-pasting. It just... sits there in Gmail and tells you when your subject line sucks.

The three things I learned about subject lines

Building the scoring engine forced me to study what actually works. Most subject line advice online is recycled fluff. But three patterns kept showing up in the data:

Spam triggers are sneakier than you think. Everyone knows to avoid "FREE" and "ACT NOW." But "just checking in" and "quick question" are also flagged now — they've been so overused by sales automation that Gmail treats them as spam signals. The extension catches these in real time, which is something I didn't expect to be so useful for myself.

Specific beats clever, every time. "Thought you'd find this interesting" tells the recipient nothing. "Your onboarding flow has a 60% drop-off at step 3" tells them exactly why they should care. The best subject lines make a promise so specific that the person can decide in 2 seconds whether it's worth opening. No mystery, no games.

Front-load or die. On a phone lock screen, you see maybe 30-35 characters of a subject line. If your important words come after "Hey [Name], I just wanted to reach out because..." — nobody will ever see them. The extension penalizes subjects where the keywords are buried past character 40. Sounds obvious, but I was doing it constantly before I had a score staring me in the face.

Before and after

Some real examples from my own emails:

Before	After
"Quick question"	"Can you review these 3 vendor proposals by Friday?"
"Following up"	"The pricing expires June 30 — here's the breakdown"
"Hey!"	"Your AWS bill is 3x higher than similar companies"

The befores aren't terrible emails written by terrible people. They're what happens when you're in a rush and don't think about it. The afters are what happens when something nudges you for 5 seconds.

Where it's at

100 + installs within a month so far, organic CWS traffic. It's early but also tells me that it is a common problem.

The free tier gives you 50 AI scores per month and 10 per day. Enough to cover a normal person's important emails without hitting a wall.

If you try it and something feels off — a score that doesn't make sense, a rewrite that sounds weird, a bug where it doesn't show up in compose — genuinely tell us. We're building this for people who send emails that matter, and the best feedback comes from people actually using it.

→ Install EmailSubjectScore Pro (free)

Written by the team at Amrita Labs. We build browser tools for people who send important emails.

How to Write Subject Lines That Actually Get Opened

Amrita Labs — Mon, 27 Jul 2026 00:00:00 +0000

I have ruined plenty of decent emails with lazy subject lines.

Not because the email body was bad. Usually the opposite. I would spend 20 minutes writing a careful message, tweaking the ask, trimming the paragraphs, making sure it sounded human — and then I would type something like "Quick question" in five seconds and call it done.

That is such a bad trade.

The subject line is the first decision point. Before someone reads your opener, before they notice your CTA, before they appreciate how thoughtful your email is, they make a snap call about whether this message deserves attention at all.

If you write outreach from Gmail, EmailSubjectScore Pro is a free Chrome extension that scores your subject lines for spam risk, clarity, and urgency in real time — right inside the compose window.

When I look back at the subject lines that consistently work better, they are rarely "clever." They usually just do three jobs well.

The 3 things every great subject line does

1. It creates urgency from context, not from hype

A lot of bad subject lines try to manufacture urgency with volume: caps, exclamation marks, pressure words, fake scarcity.

That is not the kind of urgency people trust.

The versions that work better usually point to something real:

"Your trial expires Friday — here is what changes"
"Before your board meeting Thursday"
"Quick thought before your launch next week"

Those feel urgent because there is an actual reason to pay attention now. "URGENT!!!" feels urgent because the sender is yelling.

2. It is specific enough to feel like it belongs to one person

Generic subject lines used to get away with more. Not anymore.

"Quick question," "Checking in," and "Thought you would find this interesting" all blur together now. They do not give the recipient a reason to believe the email is about them.

Specificity is what changes that.

Compare these:

Bad: "Quick question"
Better: "Question about your Q3 hiring plan"
Bad: "Thought you would find this interesting"
Better: "Your competitor just launched a free tier — one thing stood out"

I like one simple test here: could you send this exact subject line to 100 people without changing anything? If yes, it is probably too generic.

3. It survives the phone screen test

A lot of emails are first seen on mobile, which means your subject line is fighting for maybe 30-40 visible characters.

That is why front-loading matters so much.

Bad: "I wanted to reach out because your team is hiring..."
Better: "Your dev team is hiring — one candidate idea"
Bad: "Following up on our conversation from the conference..."
Better: "SaaStr follow-up: the pricing tool I mentioned"

If the valuable part of the subject only shows up after character 45, a lot of people will never see it.

Subject line formulas I keep coming back to

I do not believe in one magic template, but there are a few patterns I reach for repeatedly because they sound natural and give the recipient a reason to open.

[Their thing] + question

Example: "Your podcast episode on pricing — quick follow-up"

This works when there is a genuine trigger. It shows you are replying to something specific, not spraying a template.

Specific number + benefit

Example: "Cut your support tickets by 40%?"

This can work well when the number is real and the benefit is understandable in one glance. If the number feels made up, it backfires fast.

Mutual context

Example: "Sarah suggested I reach out"

Warm context still beats cold context. The trick is to use it naturally, not like borrowed credibility.

Observation + curiosity

Example: "Noticed your pricing page skips enterprise"

I like this one because it feels grounded. You saw something. You have a reason for the email. That is enough.

Time-anchored

Example: "Before your Series B announcement"

This works best when the timing is real. If the deadline is fake, the whole email starts to smell fake too.

Subject lines I have mostly stopped using

There are a few subject lines I almost never use now, even though they used to feel harmless.

"Quick question" — too generic, too overused, and too closely associated with automation.

"Following up" — fine inside a real ongoing thread, weak as a standalone subject because it gives the recipient nothing new to care about.

"Hope you are doing well" — better as a sentence in the body than as the headline for the entire email.

Fake RE: or FW: — not worth it. Even if a filter misses it, the recipient notices.

[Their company] x [Your company] — unless the relationship is obvious already, it usually reads like partnership-template filler.

How I test subject lines before sending

I do not have a dramatic process for this. I just try not to trust my first draft too much.

Real-time scoring. If I am writing in Gmail, I want feedback while the email is still open in front of me. That is why EmailSubjectScore Pro shows spam risk, clarity, and urgency beneath the subject field as I type.

A/B testing in small batches. If two subject lines seem equally good, I split the send and see which one gets better replies. Not forever. Just enough to stop pretending I can always guess right.

The phone test. I look at the subject the way a recipient probably will: as a tiny line on a crowded phone screen. If the important words are buried, I rewrite.

Ask one other human. This sounds almost too simple, but it works. Show someone two or three options and ask which one they would open first.

Common mistakes by email type

A few patterns show up over and over.

Cold outreach

People try to be mysterious. Usually it is better to be clear.

Follow-ups

People reuse "Following up" when they should be adding a new reason to care.

Networking emails

People force the connection too hard instead of sounding like a normal person.

Internal emails

People go vague on the emails that actually need clarity most. If there is a deadline or decision, put it in the subject.

The 60-second subject line audit

Before I send an important email, I try to give the subject line one quick pass:

Character count — does the important part show up early?
Spam phrases — anything that sounds like automation?
Specificity — could this only belong to this person or company?
Urgency — is there a real reason to open now?
Gut check — if a stranger sent this to me, would I open it?

That one minute is usually worth more than another ten minutes polishing the body.

Score your next subject line

Before your next important email, give the subject line a quick score. Install EmailSubjectScore Pro — it's free, works inside Gmail, and shows you exactly what feels weak before you hit send. No signup, no copy-pasting to external tools.

Written by the team at Amrita Labs. We build tools for people who send emails that matter.

Why Your Cold Emails Go to Spam (And How to Fix It)

Amrita Labs — Mon, 27 Jul 2026 00:00:00 +0000

The hardest part about cold email is not rejection. Rejection is information. Silence is the part that messes with your head.

You send 50 emails, maybe 100 if you are feeling ambitious. You refresh your inbox. Nothing. At first you start rewriting the offer in your head. Then you blame the list. Then you wonder whether your CTA was too soft. Eventually you have to admit the more annoying possibility: maybe the emails never really made it to the inbox in the first place.

That is a big part of cold outreach. Even when everything is going well, reply rates usually live in the low single digits. So if your deliverability is off, the whole campaign can look dead before a human ever sees it.

If you write outreach from Gmail, EmailSubjectScore Pro is a free Chrome extension that scores your subject lines for spam risk, clarity, and urgency in real time — right inside the compose window.

A lot of "my cold email is not working" turns out to be "my email setup and subject line are quietly working against me." These are the five problems I keep seeing.

Why cold emails go to spam

1. Your subject line sounds like automation

This one has gotten worse over the last few years.

Everyone already knows to avoid obvious spam language like "Free," "Guaranteed," or "Act now." But the modern trap is subtler: subject lines that sound like they came from a sales sequence.

"Quick question."
"Following up."
"Just checking in."

None of those are outrageous on their own. They are just exhausted. Spam filters have seen them millions of times, and so have recipients. Even if your email body is thoughtful, the subject line can frame the whole thing as low-effort automation before the message is opened.

The fix is not to become clever. It is to become specific. A subject like "Question about your Q3 hiring plan" feels more human because it clearly belongs to someone, somewhere, for a reason.

2. Your domain has no reputation yet

I see founders do this all the time: buy a domain on Monday, start sending cold email on Tuesday, and then act shocked when Gmail treats them like a stranger.

A new domain has no trust history. To mailbox providers, that can look a lot like spam.

If you are starting fresh, you need a warm-up period. Send low-volume emails first. Have real back-and-forth conversations. Get replies. Let the domain build a normal-looking history before you turn it into an outreach engine.

It is annoying because it feels slow. It is still faster than getting flagged and spending a month trying to recover deliverability.

3. The body looks promotional instead of personal

Cold email works best when it still feels like email.

The moment you stuff the message with links, tracking URLs, images, and extra formatting, you start drifting toward newsletter territory. Spam filters notice that, and recipients do too.

The link count matters more than people think. One link is usually fine. Two can be okay. Three or more, especially with tracking wrappers, starts to feel like marketing automation.

For a first-touch email, I like to keep it boring on purpose: plain text, one link max, no tracking pixel, no image, no fancy signature circus.

4. Your sending volume jumps too fast

Mailbox providers care about patterns. Humans are messy but consistent. Spammers spike.

If your account usually sends 8 emails a day and suddenly sends 200, that is not subtle. It looks like either a compromised account or a brand-new campaign from a domain that has not earned the right to do that yet.

A gradual ramp is painfully unsexy, but it works better. Increase volume slowly. Let the domain prove it can send outreach without triggering alarms.

This is one of those things that feels conservative until you have to dig yourself out of a deliverability hole. Then it feels obvious.

5. You skipped SPF, DKIM, and DMARC

These are not glamorous settings, but skipping them is one of the easiest ways to sabotage yourself.

SPF tells receiving servers which systems are allowed to send on behalf of your domain.
DKIM signs the email so it can be verified in transit.
DMARC tells receiving servers what to do when those checks fail.

If you skip them, you are asking inbox providers to trust a message that is harder to verify. Some will. Many will not.

Setting them up is not complicated, but forgetting them is expensive.

How I check a subject line before sending

Once the technical setup is decent, the subject line is the part I want feedback on before I launch anything.

A few ways I do that:

Real-time scoring. If I am drafting inside Gmail, I would rather see spam-risk feedback while I am typing than after a campaign underperforms. That is why we built EmailSubjectScore Pro in the first place.
Small-batch testing. If two subject lines both seem reasonable, I send small batches and let replies break the tie.
The phone screen test. Most people first see your email on a phone. If the important words are buried after character 40, they may never be seen.

None of these are complicated. They just catch problems early, which is most of the battle.

Subject line patterns that feel safer and more human

I trust these more than the usual "quick question" template language:

Specific + relevant — "Saw your talk at SaaStr — question about pricing"
Observation + curiosity — "Noticed something on your onboarding page"
Direct value — "Cut your onboarding time by 30%"
Time-anchored context — "Before your Q4 planning next week"

What they have in common is simple: they read like a person had a reason to send them.

A quick deliverability checklist before a campaign

Before sending a batch of cold emails, this is the boring checklist I would rather run than regret:

[ ] Domain is warmed up and has some reply history
[ ] SPF, DKIM, and DMARC are configured
[ ] Subject line has been checked for spammy phrasing
[ ] Body uses one link max on first touch
[ ] No tracking pixel unless there is a very good reason
[ ] Sending volume is consistent with recent history
[ ] Important words appear early enough to make sense on mobile

If that list is clean and the campaign still flops, then I will start questioning the offer. But I try not to blame the copy before I have ruled out deliverability.

Start scoring before sending

Most cold email mistakes are preventable. You do not need a giant deliverability stack to catch the obvious ones. You just need a way to notice the problems before you hit send.

Install EmailSubjectScore Pro from the Chrome Web Store — it's free, works inside Gmail, and takes about 5 seconds to install. Score your next subject line before you send it.

This article is by the team at Amrita Labs. We build tools for people who send important emails.

Pinterest SEO Checklist: Score Your Pins Before Posting

Amrita Labs — Mon, 27 Jul 2026 00:00:00 +0000

The easiest way to get disappointed on Pinterest is to treat it like Instagram.

You make a pretty graphic, post it, wait for engagement, and then wonder why the pin dies with 12 impressions. I did that too at first. The annoying part is that the pin itself may be fine. It is just not packaged in a way Pinterest understands.

Pinterest is much closer to a search engine than a traditional social platform. A pin is a search result. A board is context. The title and description are metadata. Once that clicks, the whole platform makes more sense.

And the payoff is different too. A decent Instagram post disappears quickly. A well-optimized Pinterest pin can keep surfacing for months. Some of the pins we have posted keep getting impressions long after we stopped thinking about them.

Pinello is a free Chrome extension that scores Pinterest pins across 5 dimensions — image, board fit, title, description, and keywords — in real time.

This is the checklist I keep coming back to before I post anything important.

Why Pinterest SEO matters more than followers

One thing I like about Pinterest is that it gives smaller creators a better shot than most platforms do.

A lot of Pinterest searches are unbranded. People search for things like "minimalist living room ideas" or "easy meal prep recipes," not specific creator handles. That means a small account can still win if the pin lines up with what people are actually searching for.

That is also why SEO matters so much here. If the board, title, description, and image all reinforce the same topic, Pinterest has a much easier time deciding where your pin belongs.

The 5 parts of a Pinterest SEO checklist

1. Start with the image, because Pinterest does

Pinterest is visual first. If the image does not stop the scroll, the rest of the optimization does not get much of a chance.

I stick to the boring best practice here: 2:3 ratio, usually 1000×1500px. It gives you good feed presence without awkward cropping.

A few image habits that help:

keep text overlay short enough to read on a phone
use contrast that survives thumbnail size
avoid clutter when one focal point will do
make sure the image actually signals the topic fast

If I have to squint at the thumbnail to understand the pin, I assume everyone else will keep scrolling too.

2. The board tells Pinterest what kind of pin this is

This one gets missed constantly.

A strong board name gives Pinterest topic context. "Healthy Dinner Recipes" is useful context. "Yum Yum" is not. Same pin, different board, very different signal.

I try to keep boards boring in the best possible way:

board title uses a searchable phrase
board description includes a few related keyword variations
board already has enough on-topic pins to feel coherent
the new pin genuinely belongs there

If I would be embarrassed to explain why a pin lives on a certain board, I take that as a sign the board choice is wrong.

3. The title needs to front-load the keyword

Pinterest gives you room for a long title, but users do not see all of it. On mobile, the useful part is often whatever appears in the first 30-40 characters.

So I try to get the main phrase in early.

Good titles tend to be specific:

"Minimalist Bedroom Ideas for Small Spaces"
"15 Easy Meal Prep Recipes for Beginners"
"2026 Wedding Color Trends"

Weak titles tend to sound like placeholders:

"Check This Out!"
"Bathroom Inspo"
"Cute Ideas"

The difference is not subtle. One helps Pinterest categorize the pin. The other just fills space.

4. The description is where a lot of pins quietly lose

A lot of people leave the description blank or write one lazy sentence. That is usually wasted opportunity.

I do not try to turn pin descriptions into essays. I just want 2-3 natural sentences that give Pinterest more context and give the reader one reason to care.

The sweet spot for me is usually 100-300 characters.

A useful rhythm is:

first sentence: primary keyword + what the pin gives them
second sentence: related keyword variation + who it helps
third sentence: light CTA if it fits

Example:

"Easy 30-minute chicken stir fry recipe with vegetables. Great for busy weeknights when you want something healthier than takeout. Save this for your next meal prep day."

That reads like a person wrote it, but it still gives Pinterest plenty of relevant context.

5. Keywords still matter, but they need to sound natural

The best Pinterest SEO advice is usually less glamorous than people want.

Hashtags are not doing the job they used to on Pinterest. I do not treat them as meaningful SEO anymore. What matters more is whether your title, board, and description all reinforce the same search intent without sounding stuffed.

When I need ideas, I usually look in three places:

Pinterest search suggestions
Pinterest Trends for seasonality
the titles and descriptions of pins already ranking for the term

If the keyword strategy makes the description sound robotic, I back off. Pinterest still needs text signals, but readers do too.

My quick Pinterest SEO checklist before posting

Before posting any pin, I run through this table:

Dimension	✅ Good (post it)	❌ Bad (fix first)
Image	2:3 ratio, bright, text readable on mobile	Square/landscape, dark, tiny text
Board	Keyword title, 10+ pins, topically matched	Creative name, empty, random mix
Title	Keyword in first 40 chars, specific	Vague, too short, clickbait
Description	100-300 chars, 2-3 keywords, CTA	Empty, one sentence, hashtag spam
Keywords	Natural phrases in description + title	Hashtags only, or none

If one row looks weak, I usually fix it before posting. That five-minute cleanup is cheaper than guessing later why the pin stalled.

When manual scoring stops being fun

If you only post occasionally, this checklist is manageable.

If you are batch-creating pins for a business, it gets tedious fast. That is where automation helps. Pinello scores those same five dimensions directly on pinterest.com, which is mostly useful because it catches the boring mistakes I miss when I am rushing.

The practical benefit is not "AI magic." It is just fewer avoidable misses: wrong board, weak title, empty description, off-ratio image.

The 80/20 changes that move the needle fastest

If this all feels like a lot, these are the three adjustments I would make first:

Use 2:3 images consistently. Feed presence matters more than people think.
Write real descriptions. Two thoughtful sentences beats an empty field every time.
Rename vague boards. Searchable board titles help every future pin on that board.

Those three changes are not flashy, but they do more for Pinterest SEO than most hacks people chase.

Start scoring before posting

Your next pin might quietly compound traffic for months, or it might disappear before anyone really sees it. The difference is often a few minutes of optimization before you hit publish.

Install Pinello from the Chrome Web Store — it's free, works directly on pinterest.com, and scores your pins across all 5 dimensions before you post. No signup needed.

Written by the team at Amrita Labs. We build browser tools that help creators optimize before publishing.

Chaty Alternative for Shopify: Free Forever, No Tracking, No Visitor Cap (2026)

Amrita Labs — Mon, 27 Jul 2026 00:00:00 +0000

Amrita Chat Widget is a free Shopify chat button that competes directly with Chaty. This is a technical comparison of both apps, published by the team that ships Amrita Chat Widget — bias disclosed up front. Each claim is a fair comparison and where Chaty is stronger, or Amrita Chat Widget we say so.

Amrita Chat Widget on a Shopify storefront — one button opens 9 channels: WhatsApp, Facebook Messenger, Instagram, SMS, Email, LINE, Viber, Telegram, phone.

TL;DR

	Amrita Chat Widget	Chaty Free	Chaty Paid
Price	Free forever	Free up to 500 visitors/mo	$15 / $39 / $79 per month
Visitor cap	None	500/mo	10K / 50K / 150K per month
Cookies set on storefront	0	5 (including a persistent visitor ID)	5
External scripts loaded	0	1 (`cdn.chaty.app/pixel.js`)	1
Shadow DOM isolation (prevents theme CSS collisions)	Yes	No	No
Channels supported	9 (WhatsApp, Messenger, Instagram, SMS, Email, LINE, Viber, Telegram, phone)	20+	20+
App Store listing languages	8 (EN, ES, FR, PT-BR, DE, IT, NL, JA)	1 (EN)	1 (EN)
Admin features (agent avatars, business hours, country targeting, merge tags, live chat + AI via Chatway integration)	No	No	Yes

Short version: Amrita Chat Widget is the right pick for stores that want a lightweight, private-by-default chat button that stays free at any traffic level. Chaty is the right pick for stores that need agent avatars, business hours scheduling, 20+ channels including WeChat/Skype/TikTok, or live chat plus AI. Chaty is more mature and has been shipping longer.

Where Chaty Free is stronger today: page targeting, click triggers, an attention-pulse animation, and a contact-form channel are all in Chaty's free plan. Amrita Chat Widget does not ship these YET. Stores that need any of them today are better served by Chaty Free up to the 500 visitor/month cap.

When to pick which

Choose Amrita Chat Widget if the store has exceeded Chaty's 500 visitor/month free cap and paid tiers are not justified, if the storefront's theme has previously been affected by widget CSS bleed, or if the store sells internationally — Amrita Chat Widget App Store listing and widget both localize into 8 languages, Chaty's listing is English only.

Stay on Chaty if the store needs agent-side workflows (avatars, business hours scheduling, country targeting, merge tags), if it specifically requires WeChat, Skype (which Microsoft retired in 2025), TikTok, or Poptin, or if it needs live chat plus AI via the Chatway integration.

Both apps solve the same top-level problem: a chat button on a Shopify storefront. The differences are in the engineering trade-offs behind that button.

Amrita Chat Widget at a glance

Amrita Chat Widget installs from the Shopify App Store in under 5 minutes. Setup happens entirely inside the theme editor — no external dashboard, no separate account.

Setup: enable the App Embed in the theme editor, enter the messaging channels in use for the store, save. No code required.

9 channels supported: WhatsApp, Facebook Messenger, Instagram, SMS, Email, LINE, Viber, Telegram, phone. Merchants enable the channels their team actively replies on and hide the rest.

Preset greeting for WhatsApp: a customer taps the chat button, WhatsApp opens with the merchant's pre-written message already in the compose box. The same pre-fill behavior is supported for SMS and Email.

Amrita Chat Widget in six bullets:

Free at any traffic level. No visitor cap, no upgrade prompts, no gated features.
9 messaging channels in a single button: WhatsApp, Facebook Messenger, Instagram DM, SMS, Email, LINE, Viber, Telegram, and click-to-call phone.
Zero cookies set on the storefront. Zero third-party scripts. No data leaves the browser.
Shadow DOM isolated. The theme's CSS cannot affect the widget, and the widget's CSS cannot affect the theme.
8-language admin. English, Spanish, French, Portuguese (BR), German, Italian, Dutch, Japanese. The widget itself auto-localizes to the storefront language.
Under 5 minutes to install from the Shopify App Store. No account signup, no billing screen.

What Chaty does to the storefront (as of 2026-07)

The findings below were captured by loading Chaty's demo store inspection.

1. No Shadow DOM isolation

document.querySelectorAll('*').filter(el => el.shadowRoot).length
// → 0

Every element the Chaty widget renders lives in the main document. Chaty's stylesheet loads into the customer theme <head> HTML. This is why some merchants report Chaty rendering incorrectly on specific themes. If you don't want to break your themes use Amrita Chat Widget

Amrita Chat Widget mounts inside a #shadow-root. The theme's CSS cannot reach the widget, and the widget's CSS cannot affect the theme — an isolation model designed to avoid theme CSS collisions.

2. External tracking script loads on every page

https://cdn.chaty.app/pixel.js?id=ebjpftyjrx&shop=chaty-demo.myshopify.com

Third-party origin. The filename is pixel.js.

Amrita Chat Widget's JavaScript ships from Shopify's own CDN as an app embed. No third-party origin, no additional entries required in a Content Security Policy allowlist. This matters for stores that maintain a strict CSP for security and privacy.

3. Six global functions leak into `window`

window.launch_chaty
window.close_chaty
window.open_chaty_whatsapp_popup
window.close_chaty_whatsapp_popup
window.open_chaty_contact_form
window.close_chaty_contact_form

Programmatic access is useful for triggering the chat from a custom button. It also creates a namespace-collision risk if another app or the store's theme defines a launch_* global.

Amrita Chat Widget exposes no globals on window by default. When programmatic control is needed, a single scoped API can be enabled instead of six top-level functions.

None of the findings above indicate Chaty is doing anything wrong. These are engineering choices — perfectly valid for a chat widget. But they are choices, and merchants selecting a chat widget should evaluate them against their own storefront requirements.

Pricing model

Chaty's four tiers:

Plan	Price	Visitor cap	New features unlocked
Free	$0	500/mo	—
Basic	$15/mo	10,000/mo	Agents Pop Up, page targeting, scheduling, country targeting, merge tags
Pro	$39/mo	50,000/mo	—
Growth	$79/mo	150,000/mo	—

Chaty's Pro and Growth tiers ship identical feature sets to Basic. The only variable across the three paid tiers is the visitor cap. At $79/month, the additional cost purchases traffic allowance, not additional widget capability. A store doing 200,000 pageviews pays $79/month for the same widget a store doing 12,000 pageviews pays $15/month for.

This model is a rational fit for businesses with per-visitor serving costs. Amrita Chat Widget has none — the widget is a static asset served from Shopify's own CDN. Pricing reflects that architecture: Amrita Chat Widget is free at any traffic level.

Language coverage

Chaty's App Store listing is available only in English. Merchants browsing the German, Japanese, or Brazilian Shopify App Store see "This app is not translated into your language" at the top of the Chaty listing — a friction point during evaluation from non-English markets.

Amrita Chat Widget App Store listing ships in 8 languages: English, Spanish, French, Portuguese (Brazil), German, Italian, Dutch, and Japanese.

Migrating from Chaty in five minutes

Migration completes in five steps:

Uninstall Chaty from Shopify Admin → Apps. The storefront reloads without the widget on the next request.
Clear the residual cookies in a test browser (Chrome → F12 → Application → Cookies → right-click the five chaty_* entries → Delete). Real visitors' cookies expire on their own schedule.
Install Amrita Chat Widget from the Shopify App Store.
Enable the App Embed in the theme editor (Theme customize → App embeds → toggle "Amrita Chat Widget" on).
Enter the channels in use — WhatsApp number, Messenger page, Instagram handle, and any others the team replies on. Save.

Amrita Chat Widget does not present a billing screen, a visitor-cap warning, or an upgrade prompt at any point during setup.

FAQ

Is Amrita Chat Widget really free?

Yes, at any traffic level — no visitor cap, no gated features. The widget is served from Shopify's CDN, so Amrita Chat Widget has no per-visitor infrastructure cost. A free tier will remain part of the product; any change to the pricing model would be disclosed on the App Store listing before it took effect.

Does it work with every theme?

The widget renders inside a Shadow DOM, a browser-native isolation mechanism. The theme's CSS cannot reach into the widget, and the widget's CSS cannot affect the theme. Amrita Chat Widget renders identically on Dawn, Prestige, Impulse, Warehouse, and every custom theme it has been tested against.

What happens above 500 visitors per month?

Nothing. Amrita Chat Widget does not implement a visitor cap.

What is the performance cost?

Amrita Chat Widget's JavaScript ships from Shopify's CDN as an app embed. It loads no third-party scripts, sets no cookies, and runs no analytics. The performance cost is a single same-origin script tag.

Are WeChat, Skype, TikTok, or Poptin supported?

Not currently. Amrita Chat Widget supports 9 channels: WhatsApp, Facebook Messenger, Instagram, SMS, Email, LINE, Viber, Telegram, and phone. Channel additions are prioritized by merchant demand — three or more merchant requests for a specific channel typically trigger implementation. Requests can be sent via Reddit DM (/u/sukhmeet2390) or as a GitHub issue.

Can the widget language differ from the storefront language?

The widget reads <html lang>, the attribute Shopify sets when a language is assigned to a domain or path. A Japanese storefront served at /ja/ renders the widget in Japanese automatically — no merchant configuration required.

The bottom line

Chaty is great if the store needs agent-side workflows (avatars, business hours scheduling, country targeting, merge tags), and if it needs live chat plus AI via the Chatway integration.

Amrita Chat Widget ships a different product: 9 channels, zero cookies, zero third-party scripts, Shadow DOM isolation, an 8-language admin, and a permanent free tier at any traffic level. Stores that prioritize a lighter storefront footprint and predictable pricing over channel breadth and agent workflows should use Amrita Chat Widget.

Both apps solve the same top-level problem through different engineering trade-offs. The right choice depends on the store's requirements.

Amrita Chat Widget is built and maintained by Amrita Labs, an independent studio building focused Shopify apps. Install Amrita Chat Widget on the Shopify App Store — free forever, under five minutes to set up.

5 Best Chrome Extensions for Screen Sharing Privacy (2026)

Amrita Labs — Mon, 20 Jul 2026 00:00:00 +0000

Accidentally sharing the wrong thing on a call is one of those mistakes that feels small for one second and huge the next. Maybe it is a Slack DM, a private channel name, a salary note, a customer account balance, or an internal tab you forgot was still open. The more remote work becomes normal, the more this happens to managers, sales teams, recruiters, customer success reps, founders, and anyone else who lives in browser tabs all day.

That is why screen-sharing privacy extensions are so useful. They let you hide sensitive information before the meeting starts instead of relying on last-second tab juggling. Some are built for a specific app. Others work on almost any website. The best one for you depends on where your privacy risk actually shows up.

In this guide, I compared the best Chrome extensions for screen sharing privacy for everyday work use, not technical edge cases. If you mostly share Slack, one tool clearly stands out. If you jump between lots of sites, a generic blur tool may fit better.

What to Look for in a Screen-Sharing Privacy Extension

Before you install the first blur tool you see, focus on five practical criteria:

App-specific vs. generic: A Slack-specific tool can feel much faster inside Slack, while a generic tool is better if you present from many different sites.
Ease of use: In a real meeting, you want one click or one shortcut, not a complicated setup flow.
Hover-to-reveal: This is underrated. It lets you keep information hidden from your audience while still quickly checking something yourself.
Persistence: If you share the same tools repeatedly, saved blur rules can save a lot of time.
Price: Free is great, but paid can still be worth it if you screen share constantly and need repeatable protection.

A good rule of thumb: choose the most specific tool that matches your daily workflow. If most of your screen-sharing mistakes happen in Slack, a generic extension can feel slower than something built exactly for Slack. But if you move between dashboards, spreadsheets, admin panels, and web apps all week, flexibility matters more.

1. Privacy Blur for Slack

Install from Chrome Web Store — Free forever, with Pro at $3/month

Privacy Blur for Slack is the best choice if Slack is where your risky screen-sharing moments usually happen. It is built around the parts of Slack people expose by accident: messages, names, channels, media, shortcuts, and persistence rules. That app-specific focus makes it faster than a generic blur tool when you are moving quickly in a meeting.

Its biggest strength is control without making Slack unusable. You get six independent blur zones, so you can hide exactly what matters and leave the rest of Slack readable. Hover-to-reveal is especially helpful during live calls because you can briefly inspect hidden content without turning privacy off for everyone watching. There is also an Alt+Shift+B shortcut for fast toggling and a floating draggable panel for changing settings on the fly.

Another important plus: it runs 100% client-side, which is exactly what you want when the content includes internal conversations, customer data, or sensitive team discussions.

The free version covers the core workflow. Pro adds persistence, keyword rules, and sender rules for people who want the same protections to re-apply automatically.

The real limitation is scope. This is a Slack Web-only tool. If your privacy problem happens across Gmail, dashboards, and random websites as often as it happens in Slack, one of the generic options below may be a better fit.

Best for: Teams and individuals who spend a large part of the workday screen sharing Slack.

Price: Free forever. Pro: $3/month.

2. Page Blur — Hide Sensitive Info for Screen Sharing

Chrome Web Store — Free

Page Blur is the best generic option on this list because it covers the core privacy jobs most people need without overcomplicating the experience. You can blur any element on a page, hide tab names, keep blur states persistent, adjust blur intensity, and use keyboard shortcuts. Because it works on any website, it fits people who jump between CRMs, email tools, internal dashboards, and browser tabs all day.

Its flexibility is the main reason to choose it over an app-specific product. If you need to hide a customer name on one page, a balance figure on another, and the tab title itself while sharing your whole screen, Page Blur can handle that.

The trade-off is that it stays manual. It is not optimized around one app, so it does not automatically know what is sensitive. You usually need to select the elements yourself every time, which is fine for planned presentations but adds friction when a meeting starts unexpectedly or you need to share your screen quickly without preparation time.

Best for: Remote workers who need one free privacy extension across many websites.

Price: Free.

3. Privacy Blur: Screen Privacy Tool

Chrome Web Store — Free download, optional premium

Privacy Blur: Screen Privacy Tool is the most feature-rich option in this roundup. Instead of focusing on one way to hide content, it gives you Focus Mode, Full Blur, Word Masking, Area Blur, Decoy Mode, and Smart Financial Mode. If you present lots of different kinds of content and want more than click-to-blur, that variety is a real advantage.

The biggest appeal here is range. Full Blur and Focus Mode are useful when you want to keep attention on one safe part of the screen. Word Masking helps when the same names or terms appear repeatedly. Area Blur is good for quick temporary protection, and Decoy Mode is useful for demos where you want something safer than your live page visible.

It also emphasizes local processing. But it is still a generic tool, not something tailored to one app or one workflow. The six different modes can feel overwhelming when you just want to jump on a call — you may spend more time choosing which mode to use than actually protecting content. Some advanced features are also premium-only.

Best for: People who want the broadest set of privacy modes in one extension.

Price: Free download with optional premium features.

4. BlurWeb

blurweb.app — Paid premium after trial/refund window

BlurWeb is a strong choice for people who create tutorials, onboarding videos, demos, or livestreams on a repeat basis. It lets you blur any element, draw blur over custom areas, persist blur between sessions, and adjust intensity. That combination makes it useful when you need to clean up the same product walkthrough more than once.

The standout feature is repeatability. If you regularly record the same pages or demo flows, persistent blur saves time because you do not have to rebuild your privacy setup every session. The draw-blur option also helps when what you want to hide is awkwardly placed and does not map neatly to one clickable element.

The main drawback is price and setup complexity. BlurWeb is not the best fit for someone who only occasionally presents in meetings — the manual element selection and configuration take time upfront. It makes more sense when polished recordings or repeat demos are part of your job. Like Page Blur, it is also a general tool, so you still decide manually what to hide before every session.

Best for: Trainers, tutorial creators, sales demo teams, and livestreamers.

Price: Paid premium after the trial/refund window.

5. Obscuro

GitHub — Free and open source (MIT)

Obscuro is the best option for developers and security-focused teams because it is built around rules, not just manual clicking. It can use CSS selectors and regex pattern matching to detect sensitive data such as emails, card numbers, and other text patterns, then either blur or scramble that content. It is also open source under the MIT license, which matters for teams that want transparency and control.

For the right user, Obscuro can be more powerful than a generic blur extension. If your internal dashboards, test environments, or admin tools surface the same types of sensitive values again and again, rule-based hiding can be more reliable than manually selecting elements before every call.

The catch is usability. This is not the easiest tool for non-technical users — configuring CSS selectors and regex patterns requires developer knowledge. The real value comes from setting up rules once and reusing them, but most people who just need quick meeting privacy will find this approach confusing compared to a toggle-based tool.

Best for: Developers, security teams, and technical internal demo environments.

Price: Free and open source.

Comparison Table

Extension	Best for	Price	App-specific?	Hover-reveal?
Privacy Blur for Slack	Slack users who screen share often	Free forever; Pro $3/mo	Yes — Slack Web only	Yes
Page Blur	Free privacy across many websites	Free	No	No
Privacy Blur: Screen Privacy Tool	Users who want many blur modes	Free + optional premium	No	No
BlurWeb	Tutorials, recordings, livestreams	Paid premium	No	No
Obscuro	Developers and security teams	Free	No	No

How to Choose the Right One

Use this simple decision flow:

If most of your screen sharing happens in Slack: choose Privacy Blur for Slack.
If you need one free tool that works across many websites: choose Page Blur.
If you want advanced modes like full-screen blur, word masking, or decoy views: choose Privacy Blur: Screen Privacy Tool.
If you record tutorials or demos repeatedly and want persistent visual cleanup: choose BlurWeb.
If your team wants programmable, open-source privacy rules: choose Obscuro.

The biggest mistake is choosing the tool with the most features instead of the one that matches your actual workday. In practice, the best screen-sharing privacy extension is the one you can turn on in seconds before a meeting starts.

Final Take

If Slack is where your private messages, channel names, and internal chatter usually leak into meetings, Privacy Blur for Slack is the strongest fit because it solves that exact problem without making Slack hard to use.

If your screen-sharing risk is spread across lots of sites, Page Blur is the best free all-purpose choice.

Ready to make Slack safer before your next call? Install Privacy Blur for Slack and keep sensitive Slack content hidden while you share.

Pinterest Pin SEO Checklist Before Publishing: 10 Checks That Get More Saves

Amrita Labs — Mon, 20 Jul 2026 00:00:00 +0000

Most Pinterest creators do not need to publish more pins. They need to publish better ones.

That is the real 80/20 of Pinterest: one optimized pin can outperform 10 rushed ones. On a platform with 500M+ monthly active users, tiny pre-publish details matter because Pinterest is both a visual platform and a search engine. If your image, title, description, board, and link are aligned, your pin has a much better chance of earning saves and clicks over time.

That is exactly why tools like Pinello are useful. Instead of guessing whether your pin is ready, Pinello scores it in real time inside Pinterest's pin creation modal across image quality, board fit, title SEO, description optimization, and keyword density — with AI rewrite suggestions when something is weak.

If you are a food blogger, craft seller, lifestyle creator, or niche publisher, use this Pinterest pin SEO checklist before publishing every time. It takes a few extra minutes, but it can save you from posting pins that look nice and still go nowhere.

The 10-point pre-publish checklist

1. ✅ Use a vertical image in the 2:3 ratio

Pinterest favors vertical visuals, and 1000 x 1500 px remains the safest default size for standard pins. That 2:3 ratio fills space nicely in the feed without getting awkwardly cropped.

Before you publish, check:

Is the image vertical, not square or horizontal?
Does it still look sharp on mobile?
Is the subject clear even at a smaller size?

If you are posting recipes, show the finished dish first. If you sell crafts, show the final product clearly before any close-up details. Lead with the outcome.

2. ✅ Add a clear text overlay that is easy to read on mobile

A beautiful image is not always a clear image. Pinterest users scroll fast, and your pin often gets judged in seconds.

Your text overlay should tell people what they are getting right away:

"5 Easy Fall Charcuterie Board Ideas"
"DIY Budget Closet Makeover"
"Beginner Sourdough Checklist"

Keep fonts large, high-contrast, and uncluttered. If the text disappears into a busy background, simplify it. Mobile readability matters more than desktop perfection.

3. ✅ Write a keyword-rich title with the main keyword first

Your pin title should be specific, natural, and front-loaded with the search term you want to rank for. A good rule of thumb is to stay under 100 characters and place the main keyword near the beginning.

Weak title:

"A Few Ideas I Loved This Week"

Better title:

"Small Balcony Garden Ideas for Apartments"

Notice the difference: the second one instantly tells Pinterest and the reader what the content is about.

If you have to choose between clever and clear, choose clear every time.

4. ✅ Put keywords in the first sentence of the description

This is one of the easiest wins in Pinterest SEO.

Pinterest allows up to 500 characters in a pin description, but longer is not automatically better. Descriptions in the 100-200 character range tend to be the sweet spot for engagement and can drive 25-30% more engagement than max-length descriptions. Only the first 30-60 characters are typically visible in the feed preview, so your opening line does the heavy lifting.

Put the main keyword in the first sentence, naturally.

Weak description:

"This is one of my favorite things I made lately."

Better description:

"These easy meal prep breakfast ideas help busy moms plan quick, high-protein mornings."

Be direct. Be descriptive. Do not waste the first sentence on filler.

5. ✅ Include a simple CTA in the description

Pinterest is not just about getting seen. It is about getting the next action.

A soft call to action tells people what to do next:

"Save for later"
"Click for the full tutorial"
"Read the full step-by-step guide"
"Shop the full collection"

You do not need hypey copy. You just need a clear next step. Pairing keywords with a simple CTA makes the description feel complete instead of unfinished.

6. ✅ Verify the destination URL before publishing

This sounds obvious, but broken links quietly kill pin performance.

Before you publish, click through and check:

Does the URL load correctly?
Does it match the promise of the pin?
Does it work on mobile?
Is the page fast enough to keep visitors from bouncing?

If your pin says "full tutorial," the page should open directly to that tutorial. If your pin promises a printable, recipe, or shopping page, the visitor should land there without confusion.

7. ✅ Choose the most specific relevant board

Board placement is context. A strong pin placed on a vague board can underperform.

If you have a choice between:

"Recipes"
"Healthy Recipes"
"High-Protein Breakfast Recipes"

choose the most specific relevant board.

That specificity helps Pinterest better understand where your content belongs. It also helps your ideal audience find it in the right environment. Broad boards feel safe, but specific boards usually send a stronger signal.

8. ✅ Fill in alt text

Alt text is easy to skip, but it is worth filling out. It improves clarity, supports accessibility, and gives you one more place to describe the image accurately.

Keep it simple and literal. Describe what is actually in the pin image, not a list of random keywords.

Example:

"Vertical pin showing a white farmhouse kitchen shelf with labeled pantry jars and neutral decor"

Helpful, readable, and relevant beats robotic every time.

9. ✅ Keep branding consistent

The highest-performing creators often look recognizable before users even read the account name.

Consistency builds that recognition:

Similar colors across pins
Repeating font choices
A small logo or brand mark
A familiar layout style

This does not mean every pin should look identical. It means they should feel like they came from the same creator. Over time, that familiarity can increase trust and make your content more memorable in crowded feeds.

10. ✅ Publish fresh content, not the exact same image + URL again

Pinterest rewards freshness. Republishing the exact same image with the exact same destination URL is usually weaker than creating a fresh variation.

Fresh can mean:

A new pin design for the same blog post
A different headline angle
A new cover image
A different crop or text overlay

For example, one recipe post could become multiple fresh pins:

"Easy Weeknight Pasta Dinner"
"20-Minute Creamy Pasta Recipe"
"Budget-Friendly Family Pasta Meal"

Same destination, new creative angle.

Why hashtags no longer work on Pinterest

If you learned Pinterest marketing a few years ago, you were probably told to stuff a few hashtags at the end of every description.

That advice is outdated.

Pinterest deprecated hashtags in 2023, which means they no longer function as a meaningful discovery tool on the platform. So if you are still adding hashtag bundles to your descriptions, you are using space that could be doing better work.

What to do instead:

Put your primary keyword in the first sentence
Add 1-2 closely related phrases naturally in the description
Match the keyword theme across the image, title, description, board, and landing page
Write for humans first, search clarity second

In short: stop thinking in hashtags and start thinking in keyword alignment.

How to automate this checklist with Pinello

The problem with checklists is not knowing what to do. It is remembering to do it every single time.

That is where Pinello — Live Pin Score & SEO for Pinterest Creators fits naturally into the workflow. Inside Pinterest's own pin creation modal, it scores your draft in real time across five dimensions:

Image quality
Board fit
Title SEO
Description optimization
Keyword density

If something is weak, you see it before you publish. If your copy needs help, Pinello can suggest rewrites. If your image is off-spec or your keyword use is thin, you catch it while the pin is still a draft.

That matters when you are publishing at volume. Food bloggers, Etsy sellers, and lifestyle creators do not want a separate manual audit every time. They want a quick green-light check inside the workflow they already use.

Pinello works on pinterest.com and all country variants, offers 50 AI scores per month for free, and keeps structural scoring unlimited. Its image analysis also runs 100% locally, which is especially useful if you work with original product photography or unpublished content.

Before vs. after: a quick optimization example

Here is what a weak pin draft can look like before optimization.

Before

Title: "Cute idea"
Description: "Love this so much!! #decor #home #farmhouse"
Board: "Home"
Image: Beautiful, but no text overlay
URL: Homepage instead of the actual tutorial

Why it underperforms:

The title says nothing searchable
The description wastes the first sentence
Hashtags do not help discovery anymore
The board is too broad
The destination is not specific

After

Title: "Farmhouse Pantry Organization Ideas for Small Kitchens"
Description: "Farmhouse pantry organization ideas for small kitchens with labeled jars, shelf styling tips, and budget-friendly storage inspiration. Save for later."
Board: "Small Kitchen Organization"
Image: Vertical 1000x1500 design with a bold text overlay
URL: Direct link to the pantry organization blog post

Same creator. Same topic. Much stronger search signal.

That is the goal of this checklist: not making your pins sound robotic, but making them unmistakably clear.

FAQ

Do I need to use all 500 characters in my Pinterest description?

No. Pinterest allows up to 500 characters, but that does not mean you should force it. For most creators, 100-200 characters is the better target because it stays focused and puts the important keywords up front.

Should I put keywords in both the title and description?

Yes. Use the main keyword in the title and again in the first sentence of the description, then support it with a related phrase or two. Think natural repetition, not keyword stuffing.

Can I publish multiple pins to the same blog post or product page?

Yes — and you should, as long as the pins are fresh variations. Change the image, headline angle, or design so each pin gives Pinterest a new creative asset to evaluate.

Final pre-publish rule: score before you post

Most Pinterest underperformance happens before a pin ever goes live. The image is the wrong shape. The title is vague. The first sentence is wasted. The board is too broad. The link is sloppy.

That is fixable.

Before you publish your next pin, run this checklist once — or make it even faster by using a live scoring tool inside Pinterest itself.

Install Pinello and check every pin for image quality, board fit, title SEO, description optimization, and keyword density before you hit publish.

How to Hide Slack Messages During Screen Sharing: 6 Practical Options

Amrita Labs — Mon, 20 Jul 2026 00:00:00 +0000

You've probably had this moment: you're sharing your screen, talking through a project update, and then you notice Slack sitting there with a private message preview, a sensitive channel name, or a thread you definitely didn't mean to show the whole room.

If you need a fix fast, Privacy Blur for Slack is the most practical option because it lets you keep Slack open while hiding the parts you don't want coworkers or clients to see. But it's not the only way to reduce the risk.

This guide walks through the best ways to hide Slack messages during screen sharing, ranked by how well they protect your privacy without slowing down your meeting. Some methods are perfect if Slack needs to stay visible. Others work better if you just want the safest possible setup before you click Share.

Why Slack doesn't have a built-in solution

Slack gives you lots of control over notifications, status, and window layout, but it still doesn't offer a true presenter mode that hides message content while you share your screen. That means there is no native Slack setting that blurs existing chats, masks channel names, or hides media previews in the main interface.

Slack's own Do Not Disturb tools help with new interruptions, not existing content already visible on your screen. So if your sidebar includes confidential channels, your DMs contain employee information, or a thread has customer details in plain view, you need a workaround before the meeting starts.

The good news: you don't need to overhaul your workflow. In most cases, one of the six options below is enough.

1. Privacy Blur for Slack — Best if Slack needs to stay on screen

Install Privacy Blur for Slack

If Slack actually needs to be visible during the meeting, this is the best option because it solves the real problem instead of working around it. Privacy Blur for Slack works on app.slack.com in Chrome and lets you blur the parts of Slack that usually cause embarrassment during screen sharing: messages, names, channels, and media.

The big advantage is control. Instead of blurring the entire page, you can choose from 9 independent blur zones and keep the rest of Slack usable. Need to glance at a message without turning protection off completely? You can hover to reveal specific content when you need it. There's also an Alt+Shift+B shortcut for quick toggling before a call starts.

It runs 100% client-side with no data collection, so your Slack data stays in your browser, and the free plan is enough for most people. The Pro plan ($3/month) adds persistence and rules if you want your preferred blur setup to stick automatically.

How to use it:

Install the extension from the Chrome Web Store.
Open Slack Web in Chrome.
Turn on the blur zones you want before your meeting starts.
Hover to reveal only what you need while sharing.

This is the most complete choice for managers, recruiters, founders, support teams, and anyone who has to keep Slack open during live calls.

2. Share only the specific window or tab you're presenting

If you don't actually need Slack on screen, the safest method is simply not to share it. Zoom, Google Meet, and Microsoft Teams all let you share a specific window instead of your full desktop, and Meet also lets you share a single browser tab.

That means you can present your slide deck, browser tab, design file, or spreadsheet while Slack stays on another part of your computer that viewers never see. For many people, this is the easiest zero-install fix.

How to use it:

Open only the file, browser tab, or app you plan to present.
Click Share or Present in your meeting tool.
Choose Window or Tab instead of Entire Screen.
Double-check the preview before confirming.

This works especially well for status updates, demos, and training sessions where Slack is not part of the presentation. The limitation is obvious: if you need to switch into Slack mid-meeting, you'll either need to stop sharing, reshare a different window, or risk showing it anyway. Great safety, less flexibility.

3. Turn on Slack Do Not Disturb or pause notifications

If your main fear is surprise popups, Slack's built-in Do Not Disturb feature is worth using every time you present. It pauses desktop alerts, mobile notifications, and other interruptions for a set amount of time, which immediately lowers the odds of a private message flashing onto your screen at the worst moment.

How to use it:

In Slack, click your profile picture.
Open Notifications.
Choose a pause length such as 30 minutes, 1 hour, or a custom time.
Start your meeting once the snooze icon appears.

This is quick, official, and free. It also helps if you're presenting in front of clients, leadership, or a large internal meeting where even a harmless DM preview would feel distracting.

The downside: Do Not Disturb does not hide existing conversations already open in Slack. Your channel list, message history, names, and media are still visible if Slack itself is on screen. Think of this as a backup layer, not a complete privacy solution. It's best paired with window-only sharing or a blur tool.

4. Put Slack on a second virtual desktop

Virtual desktops are a simple middle ground between "close Slack completely" and "leave Slack exposed." On Windows, press Win+Tab to create another desktop. On Mac, you can use Mission Control to add a separate desktop space. Then keep Slack on one desktop and your presentation materials on another.

How to use it:

Create a second virtual desktop before the meeting.
Move Slack to that desktop.
Keep your slides, browser, or demo on the desktop you'll share.
Switch carefully only when you need to check messages privately.

This method is helpful if you want Slack available without cluttering the workspace you're showing to everyone else. It can also reduce the mental load of constantly minimizing and reopening apps.

The tradeoff is that it depends on your own discipline. If you accidentally switch desktops while sharing your entire screen, Slack can still appear. It's safer than leaving Slack front and center, but not as foolproof as blurring or sharing a single window. Best for people who multitask heavily and already use multiple desktops every day.

5. Close or minimize Slack before the meeting starts

This is the least fancy option, but it's still one of the most reliable. If Slack does not need to play any role in the meeting, closing it removes the problem completely. No visible messages, no sidebar, no unread threads, no accidental channel-name reveal.

How to use it:

Finish any urgent Slack replies before the call.
Quit the Slack desktop app, close the Slack browser tab, or at least minimize the window.
Start screen sharing only after confirming Slack is gone from view.

This works best for short presentations, interviews, webinars, and client walkthroughs where your attention should already be on the call. It's also a good habit when you're tired or rushed and don't want one more thing to remember.

The downside is convenience. You lose instant access to chats during the meeting, and you may miss something time-sensitive until the presentation ends. Still, for pure risk reduction, "just close Slack" remains surprisingly effective.

6. Use a generic blur extension like Page Blur or BlurWeb

If you want one privacy tool that works across many websites, a generic blur extension can help. Tools like Page Blur and BlurWeb are designed to blur elements or selected areas on web pages, which means you can use them on Slack, dashboards, CRMs, docs, and other browser-based tools.

That flexibility is the main appeal. If your workday jumps between many tabs with sensitive information, a general-purpose blur tool may fit better than a site-specific extension.

How to use it:

Install the extension you prefer.
Open Slack Web or another site with sensitive content.
Blur the visible areas manually before you present.
Test the page once to make sure the blur stays where you expect.

The tradeoff is precision and speed. Generic tools are not built specifically for Slack's layout, so they require manual element selection every single time — there's no "toggle Messages on" shortcut. If Slack's interface changes or you switch channels, you'll need to redo the blur setup from scratch. They also cannot automatically detect new messages that arrive mid-call, so content that loads after your initial blur setup may still appear unblurred. For people who screen share Slack often, a Slack-specific tool is usually faster and less error-prone.

Quick comparison

Method	Hides existing Slack messages?	Stops new popups?	Keeps Slack usable during sharing?	Best for
Privacy Blur for Slack	Yes	No — pair it with DND	Yes	Daily Slack users who still need Slack open
Share specific window/tab	Yes, by keeping Slack off screen	Usually, if Slack stays off the shared surface	No	Presentations where Slack isn't needed
Slack Do Not Disturb	No	Yes	Yes	Preventing surprise notifications
Virtual desktop	Partly	No	Yes, privately	Multitaskers who want Slack nearby
Close or minimize Slack	Yes	Yes	No	Short meetings and lowest-risk setup
Generic blur extensions	Yes	No	Usually	People who need privacy across many websites

FAQ

Does Privacy Blur for Slack work in the Slack desktop app?

No. Privacy Blur for Slack works on app.slack.com in Chrome. If you mainly use the desktop app, you can switch to Slack Web before a meeting or use one of the non-extension methods in this guide.

Is Slack Do Not Disturb enough on its own?

Usually no. Do Not Disturb is great for stopping new notification popups, but it does not hide the Slack content that's already sitting on your screen. If Slack will remain visible during the meeting, pair DND with either Privacy Blur for Slack or a window-sharing strategy.

What's the best setup for people who screen share every day?

If Slack needs to stay open, the most practical setup is Privacy Blur for Slack + Slack Do Not Disturb. That combination protects visible content and reduces the chance of a surprise popup at the same time.

The simplest way to avoid an awkward Slack moment

If you screen share often and still need Slack open, use the tool built for that exact problem. Install Privacy Blur for Slack and blur messages, names, channels, and media before your next call. It's free forever, works entirely client-side, and takes less than a minute to set up.

How to Write Email Subject Lines That Get Replies

Amrita Labs — Mon, 20 Jul 2026 00:00:00 +0000

Your email lives or dies in about 2-3 seconds. Before anyone reads your pitch, proposal, follow-up, or intro, they scan the subject line and make a snap decision: open, ignore, or delete.

That tiny line carries more weight than most people realize. Cleanlist reports that 47% of recipients open an email based on the subject line alone, while 69% report emails as spam based on the subject line alone (Cleanlist 2026). And because average cold email reply rates sit around 3-5% across 53M+ emails analyzed, small subject-line improvements matter a lot more than they look on paper (Saleshandy 2026).

If you write outreach from Gmail, tools like EmailSubjectScore Pro make this easier by scoring your subject line for spam risk, clarity, and urgency in real time — right inside the compose window, with no copy-paste to external tools.

Most people obsess over the email body. Smart senders know the subject line decides whether the body gets a chance.

Why reply rate matters more than open rate

Apple Mail Privacy Protection made open tracking much less reliable in 2021 by preloading email pixels, so opens are no longer the cleanest signal of real interest. Reply rate is harder to fake, which makes it the better metric for judging whether your subject line attracted the right person enough to respond.

7 data-backed tips for subject lines that get replies

1. Keep it short

The best-performing subject lines are usually 3-7 words and under 45 characters. That length works because it is easy to scan on both desktop and mobile, and it forces you to cut filler.

Example: Quick question about onboarding

Why it works: It sounds human, specific, and easy to process in one glance. Compare it to something bloated like Following up regarding a possible opportunity to improve your onboarding experience, which feels heavier before the email is even opened.

Actionable advice:

Cut throat-clearing words like "following up," "touching base," and "wanted to reach out"
Remove anything the recipient can learn in the first sentence of the email instead
Read your subject line out loud; if it feels long, it is long
Aim for a focused idea, not a full summary

A short subject line does not mean vague. It means tight.

2. Personalize with something real

Personalized subject lines can lift open rates by 26-50%, which is still useful directional evidence even if open rate is no longer the main scoreboard. More important: personalization signals that this email is for them, not for a list.

Example: Idea for Acme's demo flow

Why it works: It uses a company name and hints at a relevant topic. That feels more credible than a generic line like Growth idea for your business, which could have been sent to anyone.

Actionable advice:

Personalize with a company name, role, recent launch, or obvious pain point
Keep the personalized detail near the front
Use a strong detail, not several weak ones
Make sure the body matches the promise of the subject line

Good personalization is specific and earned. Bad personalization feels stitched in.

3. Ask a question

Question-based subject lines can generate 10-21% higher opens. They work because they create a small curiosity gap and feel more conversational than a statement.

Example: Still hiring SDRs?

Why it works: A real question invites a mental response. The reader can instantly tell whether it is relevant, and if it is, they are more likely to open because the email feels like a direct conversation rather than a broadcast.

Actionable advice:

Ask simple yes/no or short-answer questions
Keep the question tied to a real business or personal outcome
Avoid vague questions like Can I help?
Use question marks sparingly; one is enough

Question subjects work especially well for sales outreach, freelancer pitches, recruiting emails, and job search follow-ups.

4. Avoid spam triggers

This is the easiest win and the most overlooked. If 69% of people report spam based on the subject line alone, you cannot afford to sound like a promotion even when your offer is legitimate (Cleanlist 2026).

Bad examples:

FREE OFFER INSIDE!!!
Last chance to 10x revenue
Urgent response needed

Better examples:

Question about your Q3 pipeline
Idea for reducing no-shows
Intro from a fellow founder

Actionable advice:

Avoid all caps, excessive punctuation, and hype language
Be careful with words like "free," "guaranteed," and "urgent" unless they are absolutely necessary
Skip clickbait phrasing that overpromises
Write like one person contacting another person

Remember the upside and downside together: 47% open based on subject line alone, but 69% may flag spam based on that same line. The subject line is both your first impression and your first filter.

5. Create urgency without sounding pushy

The goal is not pressure. The goal is relevance now. Since 58% of replies come from the first email, your opening subject line should give the recipient a reason to care today instead of "later," which usually means never.

Example: Before next week's rollout

Why it works: It introduces a timeframe without fake drama. It suggests the email is timely, but it does not scream for attention.

Actionable advice:

Tie urgency to a real event: launch, hiring push, renewal, campaign, deadline
Use calm phrasing like before, for, ahead of, or this week
Avoid manipulative pressure like final notice or act now
Make sure the body quickly explains why the timing matters

Strong urgency feels helpful. Weak urgency feels salesy.

6. A/B test every campaign

Average cold email reply rates are only 3-5%, while the best campaigns break 10%+ reply rate. That gap is your reminder not to fall in love with the first subject line you write.

Example test:

A: Idea for Acme's onboarding
B: Quick question about onboarding

Both are short. Both are clear. But they frame the email differently. One leads with value, the other with conversation. You will not know which angle fits your audience until you test it.

Actionable advice:

Test one variable at a time: personalization, question vs statement, or urgency angle
Keep the email body roughly the same when comparing subject lines
Use reply rate as the main score, not opens alone
Save winners and turn them into reusable patterns

A/B testing does not need to be fancy. It just needs to be consistent.

7. Time it right

Even a strong subject line can flop if it lands at the wrong moment. Tuesday and Wednesday mornings are consistently strong send windows for cold outreach according to Snov.io's 2026 guidance.

Example: Instead of sending Quick question about your hiring funnel late Friday afternoon, schedule it for Tuesday morning when inboxes are active but not yet buried in end-of-week cleanup.

Actionable advice:

Start with Tuesday or Wednesday morning in the recipient's time zone
Avoid late Friday, weekend, and late-night sends for first-touch cold emails
Keep timing notes alongside your subject-line test results
Re-test timing when you change audience segments

Timing will not rescue a bad subject line. But good timing gives a good subject line a fair shot.

How to check your subject lines before sending

If you send important emails from Gmail, the fastest habit upgrade is to check the subject line before you hit send, not after a campaign underperforms.

That is where EmailSubjectScore Pro fits naturally into the workflow. It works directly inside the Gmail compose window and scores your subject line in real time across three practical dimensions:

Spam risk — does this sound promotional, manipulative, or filter-friendly in the wrong way?
Clarity — will the recipient immediately understand what the email is about?
Urgency — is there a believable reason to open now?

If your score is weak, the tool gives AI rewrite suggestions right there in Gmail, so you can improve the line without opening another tab or pasting your text into an external analyzer. That matters because convenience drives usage — web-based tools like CoSchedule or SubjectLine.com require you to leave Gmail, copy-paste your subject, and mentally carry the feedback back. By the time you switch tabs, you've lost momentum. An in-Gmail scorer removes that friction entirely.

Free users get 50 scores per month, which is enough for many freelancers, job seekers, consultants, and light outreach workflows. Pro gives you unlimited scoring, so if you are sending a lot of outbound email, you never have to ration checks.

10 high-performing subject line templates

Use these as starting points, not copy-and-paste magic bullets. Fill in the bracketed part with something real and relevant.

Quick question about [topic]
Idea for [company]
[Company] + [pain point]
Still working on [goal]?
Before [event or deadline]
Question about your [process]
For your [team or role]
Worth trying for [company]?
Regarding [specific initiative]
[Name], quick thought on [topic]

A few notes on using templates well:

Favor plain language over cleverness
Choose the template based on the relationship: cold outreach, follow-up, job search, or client work
Make the body deliver exactly what the template hints at
If a template starts feeling generic, rewrite it in your own natural voice

Templates save time, but relevance gets replies.

FAQ

What is a good reply rate for cold email?

A solid benchmark is 3-5% average reply rate, according to Saleshandy's 2026 analysis of 53M+ cold emails. The strongest campaigns can reach 10%+, which is why improving your subject lines, targeting, and offer is worth the effort.

Should I optimize for opens or replies?

Optimize for replies first. Opens can still help with rough comparisons, but Apple Mail Privacy Protection made them less trustworthy, while a reply is a real signal that your message connected.

How many subject lines should I test?

Start with a small set of clear variations for any meaningful outreach campaign. That gives you enough contrast to learn what works without creating unnecessary complexity.

Final takeaway

If your subject line is too long, too generic, too pushy, or too spammy, the rest of your email never gets a fair chance. A better subject line will not fix a weak offer, but it will help good emails earn more of the replies they deserve.

If you want an easy way to check subject lines as you write them, install EmailSubjectScore Pro. It works directly inside Gmail, scores spam risk, clarity, and urgency in real time, includes AI rewrite suggestions, and gives you 50 free scores per month before you ever need Pro.