Archive search indexes titles—but not the paragraphs readers remember
The coffee’s gone cold while you dig through six months of back issues, hunting the paragraph you swear you published about abandoned-cart timing. Your reader gave up twelve seconds ago.
Most newsletter archive search bars can’t find what you actually wrote
Only a handful of platforms index email body text—the rest search subject lines and maybe metadata.
When a reader lands on your archive page and types “conversion rate” into the search box, they expect to find every issue where you mentioned conversion rates. What they get instead depends entirely on which platform you use—and most newsletter tools only index subject lines, tags, and post titles. The full body text? Never touched.
Substack indexes the entire post body, so search works as expected. Beehiiv indexes titles and descriptions but not body content unless you’re on the Scale plan ($99/month and up). Ghost indexes everything by default if you’ve enabled its built-in search. ConvertKit doesn’t offer archive search at all—your public archive is a reverse-chronological list with no filter. MailerLite’s archive pages are static HTML with no search widget. Mailchimp’s campaign archive has a search bar, but it only queries campaign names, not content.
If your platform doesn’t index body text, your options are limited: add a third-party site search tool like Algolia (starts at $1 per 1,000 searches) or Swiftype (absorbed into Elastic, minimum $79/month), embed a Google Custom Search Engine (free but cluttered with ads on the free tier), or accept that readers will use Ctrl+F on a single long archive page. The last option works surprisingly well if you paginate archives into quarterly or annual views and keep load time under two seconds.
TACTIC
When Notion CRMs collapse under sponsor outreach volume
Notion feels infinitely flexible when you’re tracking twenty sponsor prospects across three columns. At two hundred contacts it starts to break—filtered views slow to a crawl, relation properties don’t cascade reliably, and the mobile app won’t load your database at all. Solo operators hit this ceiling faster than they expect, especially when layering deal stage, contact history, and follow-up reminders into the same table. There’s a predictable threshold where the database model stops working, and a narrow set of tools that actually solve the problem without drowning you in enterprise CRM complexity.
WORTH READING
Google Search Console’s click data doesn’t update in real time
You published a post this morning that’s already pulling traffic from Reddit, but Search Console still shows yesterday’s numbers. The platform’s click and impression data lags by design—most reports settle within forty-eight to seventy-two hours, and early numbers shift as Google reconciles logs across data centres. If you’re checking Performance reports to gauge whether a new post is working, you’re looking at stale data. Some metrics update faster than others, and knowing which ones refresh in near-real time changes what you can trust when you’re trying to make a call today, not next week.
FROM THE ARCHIVE
Referral widgets count signups—but you need to track retention
Referral programmes light up your dashboard with new subscriber counts, and it’s easy to treat every referred signup as pure growth. The problem is that incentive-driven subscribers churn faster than organic ones—especially if the reward is a one-time download or entry into a giveaway. What matters isn’t how many people your top referrers bring in this month; it’s how many of those subscribers are still opening six weeks after the incentive window closes. Most newsletter platforms report gross referral signups but don’t surface cohort retention by acquisition source, so you’re left measuring the wrong number unless you export and segment manually.
Know someone who would like this? Forward today’s email — every operator we reach is one closer to running an online business with a little less friction.