beehiiv
How do I get my beehiiv newsletter on Google?
beehiiv publishes a web archive of every post and generates a sitemap for it automatically. Connect a custom domain, verify it in Google Search Console, submit yourdomain.com/sitemap.xml, and write post titles that match what people search rather than issue numbers.
https://yourdomain.com/sitemap.xml
Where the beehiiv sitemap lives
beehiiv generates a sitemap for your web archive automatically.
Why beehiiv posts don't get indexed
- Only the web version of a post is indexable. Email-only sends never reach Google.
- Premium posts are indexed on their preview text alone.
- Newsletter titles are the biggest lever and the most neglected — "Issue 12" ranks for nothing.
- The default beehiiv subdomain works but builds beehiiv's authority instead of yours.
- Per-post SEO fields sit on paid tiers; on the free plan Google builds titles and descriptions itself.
Step by step: getting your beehiiv newsletter into Google
- Connect a custom domain in beehiiv's settings and publish.
- Verify the domain in Google Search Console.
- Submit https://yourdomain.com/sitemap.xml under Sitemaps.
- Fill in the per-post SEO title and description on your evergreen posts.
- Make sure the posts you want found are public rather than premium-gated.
- Push new post URLs through the Indexing API at publish time instead of waiting for a sitemap recrawl.
beehiiv indexing controls at a glance
- Sitemap — https://yourdomain.com/sitemap.xml — beehiiv generates a sitemap for your web archive automatically.
- robots.txt — Limited control. beehiiv manages robots.txt. Higher tiers give custom code injection but not per-crawler robots rules.
- Rendering — The web version of each post is server-rendered HTML that crawlers read in full.
- Hiding a page — Per-post SEO settings on paid tiers include indexing control; the web archive is otherwise public by default.
- Custom head code — Custom HTML/head injection is available on higher tiers, which is where JSON-LD goes.
- llms.txt — No root file hosting. Your archive page plus a clean sitemap is the practical substitute.
Connect your own Search Console, point IndexerNow at your sitemap, and push new and updated URLs straight to Google's Indexing API and IndexNow — on your account, your quota, no plugin.
Get your pages indexedFrequently asked
Does beehiiv have a sitemap?
Yes — beehiiv generates one for your web archive automatically, at yourdomain.com/sitemap.xml once a custom domain is connected.
Why aren't my beehiiv posts on Google?
Usually because the posts are premium-gated, the site is still on a beehiiv subdomain that you haven't verified, or Google simply hasn't crawled the new URLs yet.
Should newsletter posts have their own SEO titles?
Yes. The subject line that works in an inbox almost never matches a search query. beehiiv's per-post SEO title field exists precisely so the two can differ.
Why isn't my beehiiv newsletter showing up in AI answers?
Being in Google's index doesn't put you in ChatGPT's answers — those run on Bing plus their own crawlers, and they quote pages built to be quoted. The companion guide covers what beehiiv lets you control.
beehiiv AI visibility guide →Other platforms
Substack
Public Substack posts are indexable by default and Substack maintains the sitemap for you — the work is connecting a custom domain, making sure the posts you want found are public, and giving each post a title that matches what people search rather than a clever newsletter subject line.
Ghost
Ghost ships clean SEO defaults and a sitemap — the work is getting new posts crawled the day you publish.
WordPress
WordPress has a sitemap built in — the classic blocker is one checkbox.