A reader emails: “I know you wrote about WordPress caching last month—where is it?” You know you sent it. You can see it in your sent folder. But when they search your archive page, nothing turns up.
Archive search is one of those features newsletter platforms advertise but rarely explain. Some index subject lines only. Others index the first 200 characters. A few index the full body—but only if you’re on a paid tier. And almost none tell you which approach they use until you test it yourself.
Here’s what actually gets indexed on the platforms solo operators use most, and what to do when search fails.
What gets indexed on each platform
Beehiiv indexes the full email body on all tiers, including free. Search works across subject lines, body text, and author names if you’ve enabled bylines. The index updates within a few minutes of sending. One caveat: if you use custom HTML blocks, only plain text inside those blocks gets indexed—images, buttons, and styled div containers are ignored.
Substack indexes subject lines and body text, but search results prioritize exact matches in titles first. If your subject line was vague (“Issue #47”) and the meat of the topic is buried in paragraph three, it won’t surface until a reader scrolls past a dozen other posts. Substack’s archive search also doesn’t support Boolean operators—no “AND,” “OR,” or quoted phrases.
ConvertKit offers archive search only if you’ve enabled the public archive feature, which is off by default. When enabled, it indexes subject lines and the first 500 characters of body text. Anything below the fold in your email—your detailed how-to, your step-by-step breakdown—doesn’t get indexed. If you bury the lede, readers won’t find it.
MailerLite doesn’t offer built-in archive search at all. The public archive page displays a reverse-chronological list with subject lines and send dates. Readers have to use browser find (Cmd+F) and hope the subject line matches what they remember. For a catalog of 50+ emails, that’s borderline unusable.
When to use tags and categories instead
If your archive grows past 30 posts, search alone won’t save readers. They need filters—by topic, by format, by content type. Beehiiv lets you tag posts and surface those tags as filters on your archive page. Substack offers Sections, which let you split your newsletter into topic-based streams (each with its own archive and RSS feed).
ConvertKit doesn’t support tags or categories in the public archive view. If you need taxonomy, you’ll need to maintain a separate landing page with manual links—or migrate to a platform that supports it natively.
The non-obvious move: if you publish consistently on a topic (say, WordPress hosting or AI prompts), create a dedicated landing page that lists all related posts with short descriptions. Link to it from your welcome email and your site nav. That page becomes your real archive. The platform’s built-in search becomes a backup.
What breaks when readers search from mobile
Most newsletter platforms serve the same archive page to mobile and desktop, but mobile browsers handle search differently. Safari on iOS doesn’t support in-page search widgets that rely on JavaScript—if your platform uses a custom search bar (instead of a plain HTML form), iOS readers get a broken experience. They tap the search icon, nothing happens, and they leave.
Beehiiv and Substack use standard HTML forms, so mobile search works. ConvertKit’s archive search widget relies on JavaScript and fails silently on older mobile browsers. MailerLite, again, offers no search at all.
Test your archive page on an actual phone, not just a resized browser window. Open it in Safari, Chrome, and Firefox mobile. Try searching for a post you know exists. If the search bar doesn’t respond or returns zero results for a term you know is there, your readers are hitting the same wall.
When to embed a third-party search tool
If your archive has 100+ posts and your platform’s search isn’t cutting it, you can embed a third-party site search tool. Algolia offers a free tier for up to 10,000 searches per month. You’ll need to generate a JSON feed of your archive (most platforms support RSS; convert it to JSON with a script or a tool like Feed43), push it to Algolia’s index, and embed their search widget on a custom landing page.
This works if you host a separate website alongside your newsletter (common for operators who publish on Substack but maintain a WordPress site for SEO). It doesn’t work if you rely solely on the platform’s hosted archive—Substack and Beehiiv don’t let you inject third-party JavaScript into their archive pages.
The simpler fix: write better subject lines. If every email is titled “Weekly Update” or “Issue #23,” no search tool will help. Use the subject line to signal the topic clearly. “WordPress object caching: Redis vs. memcached” beats “Performance tips” every time.
Want more tool breakdowns like this? Subscribe to One Two Three Send and get one operator-focused deep-dive every day—no fluff, just what actually works and what breaks.
Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.