Substack Posts Not Showing Up in Google? Here's Why, and How to Fix It

Try this: take the headline of a post you published a month ago, put it in quotes, and google it. If your post comes up, good — you're indexed. If Google returns nothing, or returns other people's pages that mention similar words but not yours, you've just discovered what a lot of Substack writers eventually discover: publishing a post and having it exist in Google are two separate events, and the second one doesn't happen automatically.

This matters more than it seems. Your subscribers get every post by email regardless. But search is where strangers find you — the person googling a question you answered brilliantly in March. If your archive isn't indexed, that entire discovery channel is switched off, and your growth depends entirely on social media and Substack's internal recommendations.

Here's how indexing actually works, why Substack publications often lag, and what you can do about it.

How a post gets into Google (the actual mechanics)

Google indexes a page in three stages:

1. Discovery. Google learns the URL exists — via a link from an already-indexed page, or via a sitemap.
2. Crawling. Googlebot fetches the page. When it does this depends on "crawl budget," which is heavily influenced by how important Google thinks your site is.
3. Indexing. Google decides whether the page goes into the index at all. This is a real decision, not a formality — Search Console has two statuses, "Discovered – currently not crawled" and "Crawled – currently not indexed," that exist precisely because Google routinely declines to crawl or index pages it considers low-priority.

For a major news site, all three stages happen in minutes. For a new publication on a yourname.substack.com subdomain with few external links, each stage can take days or weeks — or stall indefinitely at stage 3.

Why Substack publications lag

Your subdomain starts with no authority. Every *.substack.com publication is treated essentially as its own site. Substack the company has enormous authority; your subdomain inherits very little of it. A new publication is, in Google's eyes, a brand-new website with zero backlinks — and brand-new websites get crawled slowly and indexed reluctantly.

Few external links. Newsletters live in inboxes. Emails don't create backlinks, and backlinks are the main way Google discovers pages and assigns them priority. A blog accumulates links naturally; a newsletter often doesn't.

Substack gates some SEO features. This surprises people: Substack's own support documentation states that features like Google Search Console indexing and sitemaps are granted after a publication meets a minimum quality standard set internally by their team, and that enabling paid subscriptions, growing your list, and publishing regularly increase the likelihood of access. In other words, on a small publication, some of the machinery below may not be fully available yet. That's Substack's call to make on their platform — but it's worth knowing, because it explains cases where the standard advice doesn't seem to work.

Newsletter titles aren't search titles. "Some thoughts on Tuesday" is a fine email subject and an unfindable search result. Even indexed, a post only ranks for queries its title and content actually match.

Step 1: Find out what's actually indexed

Before fixing anything, measure. Two ways:

• The quick way: search site:yourname.substack.com (or site:yourdomain.com if you have a custom domain). Google returns every page it has indexed from your site. Count them against your published posts. Writers with 80 posts are often startled to find 12 indexed.
• The accurate way: Google Search Console (free). Verify your site as a property, then open the Page indexing report. It lists exactly which URLs are indexed and, for the rest, why not — including those "Discovered" and "Crawled – currently not indexed" statuses.

Verification is straightforward with a custom domain: you add a DNS record and you own the property outright. On a bare Substack subdomain, verification options are more limited — one more argument for the custom domain, below.

Step 2: Submit your sitemap

Substack generates a sitemap for every publication at yourname.substack.com/sitemap.xml (or yourdomain.com/sitemap.xml). In Search Console, go to Sitemaps, enter sitemap.xml, submit. This solves discovery: Google now has a machine-readable list of every post URL, refreshed as you publish. It does not guarantee crawling or indexing — it moves posts from "Google doesn't know this exists" to "Google knows and will get to it according to its own priorities."

Step 3: Request indexing for individual posts

Search Console's URL Inspection tool lets you paste a specific post URL, see its current status, and click Request Indexing. This puts the URL in a priority crawl queue and is the most direct lever you have. In practice it often gets a post crawled within hours to days instead of weeks.

The catch: it's one URL at a time, by hand, with a small daily quota, and Google explicitly treats it as a request rather than a command. For a weekly newsletter that's a manageable chore — paste, click, done — if you remember to do it every time. Most people remember for about three weeks.

Step 4: Improve your odds of being indexed at all

Requesting a crawl doesn't help if Google crawls the page and declines to index it. What raises the odds:

• Use a custom domain. Your authority accrues to a domain you own, verification is clean, and if you ever leave Substack, your indexed pages and rankings move with you. This is the single best structural decision for Substack SEO.
• Get real links. A mention in another newsletter's link roundup, a guest post, a cited chart — each external link is both a discovery path and an authority signal. This is slow and it is also the entire game.
• Link between your own posts. When a new post links to three older ones, a crawl of the new post refreshes Google's interest in the old ones. Substack archives don't interlink automatically; do it in the body text.
• Write at least some titles for searchers. You don't have to abandon voice. But if a post answers a question people google, put the question's words in the title. "What I learned shipping a product with no audience" beats "Some notes, vol. 12" in search forever.
• Be patient with the timeline. Indexing lag for a small site is normal, not a penalty. Weeks, for a new publication, is typical.

The maintenance problem

Everything above works. The failure mode isn't knowledge — it's that steps 1 and 3 are recurring chores. Indexing coverage drifts: new posts wait in the crawl queue, old posts occasionally drop out of the index, and nothing notifies you either way. The writers who stay indexed are the ones who check Search Console weekly and request indexing for every new post, indefinitely.

That's the loop we're automating. Newsletter Health Check watches your Substack's RSS feed, submits each new post through Search Console as it's published, and sends you a weekly report of your indexed coverage — how many posts are in Google's index, which ones aren't, and what changed. $49/year, built for Substack writers. If you'd rather write than babysit a crawl queue, join the waitlist.