How Substack SEO Works: What Google Can Index, What It Can't, and the Custom Domain Decision That Changes Everything

Every newsletter creator eventually hits the same wall: you publish something good, Google never shows it, and the advice online splits between "Substack is terrible for SEO" and "just switch to WordPress." Both answers are lazy. Understanding how Substack SEO works comes down to three things: what Google can see, what it can't, and the one decision, subdomain or custom domain, that sets your ceiling before you write a word.

Yes, Substack ranks on Google, with a ceiling most creators never diagnose

Substack posts are crawlable, indexable, and fully capable of ranking. The platform renders pages server-side, which means Google sees your full text without needing to run JavaScript. Posts on yourname.substack.com get picked up regularly, and Substack's own guide to SEO on Substack confirms the platform treats search visibility as a real concern, even if that guide hasn't been updated since February 2023.

The ceiling is not about whether Google can find you. It is about whose site Google thinks it found.

When your post lives on a Substack subdomain, Google attributes that content to a property it already knows: substack.com. Your post benefits from Substack's existing domain authority, which is why new publications sometimes rank quickly for low-competition phrases. But the authority your post earns flows uphill to Substack's root domain, not to anything you own.

This matters more for some goals than others. If you write essays targeting long-tail, question-shaped queries, a Substack subdomain can perform well. If you want to rank for anything competitive in your niche, you are fighting with one hand tied.

What Google can actually see: the indexing mechanics

Substack handles the technical basics better than its reputation suggests. Every publication gets an auto-generated sitemap.xml file, accessible at yourpublication.substack.com/sitemap.xml whether you are on a subdomain or a custom domain. Google's own documentation on sitemaps explains that this file is how crawlers discover your pages efficiently, and Substack generates it without you touching anything.

The platform also serves a robots.txt file, the plain-text file that tells crawlers which parts of a site they may visit. Substack's version allows crawling of your posts and archive page. You cannot edit it, but you do not need to for standard SEO work.

Canonical tags are handled automatically too. A canonical tag is a line of code that tells Google which version of a page is the "real" one when duplicates exist. Google recommends canonicalization as the primary way to avoid diluting ranking signals across similar URLs. Substack applies canonicals to each post, so if someone reads your article through the app or a shared link with tracking parameters, Google still credits the original URL.

What Substack does not do, according to IndexerNow's detailed walkthrough, is ping Google when you publish a new post. Your sitemap updates, but Google discovers the change on its own schedule. For a new publication with few external links, that schedule can stretch to weeks.

The subdomain problem: why yourname.substack.com caps your ceiling

This is the structural issue that matters most, and it is the one most advice glosses over. When you publish on yourname.substack.com, you are a tenant on Substack's property. Google treats subdomains as semi-independent entities, but they inherit signals from the root domain and pass authority back to it.

In practice, this means two things.

Your posts get a head start. Substack.com has enormous domain authority built from millions of publications, and Google extends some of that trust to new subdomains. This is why a brand-new Substack can sometimes outrank a brand-new WordPress site on a fresh domain within the first few weeks.

You also hit a wall. You share a root domain with every other Substack publication, including low-quality ones. You cannot control site-level technical settings, and you cannot build domain authority, the cumulative trust Google assigns to your site based on its history and links, on a property you do not own. Every external link pointing to your Substack post strengthens substack.com's position in search, not yours.

For low-competition, long-tail queries, this trade-off works fine. "Best morning routine for night-shift nurses" is winnable from a Substack subdomain. "Best project management software" is not.

Custom domain on Substack: the setup and the real trade-offs

Moving to a Substack custom domain means your posts live at yourdomain.com or blog.yourdomain.com instead of under Substack's subdomain. Substack's own setup guide walks through the process, and it is simpler than most people expect.

You buy a domain from any registrar, then add a CNAME record in your DNS settings. A CNAME record is a pointer that tells browsers "when someone visits this address, show them the content hosted at this other address." Substack's documentation specifies the exact values. You paste them into your DNS provider's dashboard, then enter the domain in your Substack publication settings.

DNS propagation, the time it takes for the new record to spread across the internet, can take anywhere from a few minutes to 48 hours depending on your provider. During that window your site may load intermittently.

Substack handles SSL certificates automatically, so your custom domain serves over HTTPS without extra configuration. The platform also redirects your old yourname.substack.com URLs to the new domain, which preserves most of the link equity from anything already indexed.

The trade-off is real though. A fresh custom domain starts with zero domain authority. Your first few months on it may rank worse than they did on the subdomain, because you have lost Substack's borrowed trust. This is the cost of ownership: you are building equity in your own property instead of renting someone else's.

The on-page controls Substack gives you (and the ones it withholds)

Substack gives you more control than most hosted platforms, and less than any self-hosted one. Knowing exactly which levers exist saves you from hunting for settings that are not there.

You control these directly:

• Post titles, which become your title tags, the blue clickable text in search results
• Meta descriptions, the short summary shown under the title, editable per post in the publish settings
• URL slugs, the end of the post's web address, customizable before publishing
• Image alt text, headings within posts, and internal links between your own articles

You do not control site speed, schema markup (the structured data that helps Google understand what a page is about), redirect rules, tag page architecture, or robots.txt contents. You cannot install plugins, edit the archive page layout, or modify how Substack structures its URLs.

Whether the missing controls matter depends on your goals. If you are writing essays and want them to surface for relevant searches, the controls you have are enough. If you are trying to build a content site with rich snippets, breadcrumb navigation, and programmatic page types, they are not.

How to actually get your Substack indexed and ranking

Getting indexed is the bottleneck for most Substack creators, not ranking. A post Google has not indexed cannot rank for anything. The workflow below reflects what actually moves the needle, based on current practitioner guides and Substack's own behavior.

Start by verifying your publication in Google Search Console, Google's free tool for monitoring how your site appears in search. Several current guides recommend using the URL prefix property type for Substack subdomains. If you are on a custom domain, you can use either URL prefix or the broader domain property. Substack supports the HTML tag verification method in its settings, which is the simplest path for subdomain users.

Once verified, submit your sitemap. Paste yourpublication.substack.com/sitemap.xml (or yourdomain.com/sitemap.xml on a custom domain) into the Sitemaps section. This tells Google where to find all your posts and speeds up discovery for new ones.

For individual posts that matter, use the URL Inspection tool to request indexing. This is a manual nudge, and it works. IndexerNow's integration guide notes that some operators go further with automated indexing workflows, but manual requests through Search Console are sufficient for most publications.

Beyond the technical setup, three things drive ranking more than any on-page tweak. Internal links between your own posts help Google understand your topical focus. External links from other sites pointing to your Substack carry the most ranking weight of anything you can do. And Substack Notes, the platform's built-in short-form feed, drives engagement signals that correlate with faster indexing for linked posts.

On content format, the pattern across 2026-era guides is consistent: write evergreen, query-shaped posts rather than issue-numbered dispatches. "How to price a freelance project" will match search intent for years. "Issue #47: This week's thoughts" will not. Keep timely or community posts behind the paywall if you want, but make your evergreen content public, because public crawlable pages are the only ones with search potential.

If you want to track where your newsletter traffic actually comes from, that pairs well with Search Console data. Search Console shows you which queries bring impressions and clicks; UTM parameters show you which links your subscribers actually used.

Substack SEO vs WordPress SEO: when each one wins

The honest comparison is not about which platform is "better." It is about which job each one does well.

WordPress gives you complete control. You can install SEO plugins, add schema markup, manage redirects, optimize page speed, and structure your site however you want. The cost is maintenance: hosting bills, plugin updates, security patches, and the time to learn the system. For a creator whose newsletter is the product and who wants compounding organic traffic, that control pays for itself.

Substack gives you distribution infrastructure WordPress cannot match. Recommendations from other Substacks, the Notes feed, the app, and the network effect of being on the platform where readers already are. The cost is the technical ceiling described throughout this piece.

The practical verdict: if search traffic is a primary growth channel, use WordPress or a custom-domain Substack. If search is a bonus on top of your email-driven growth, a Substack subdomain is fine and you should spend your energy on writing instead of DNS records.

What happens to your SEO if you leave Substack

This is the question nobody asks until they are already moving, and by then the answer is already locked in.

If you are on a Substack subdomain and migrate to another platform, you cannot set up redirects. Your old URLs stay live on Substack's servers, keep whatever rankings they earned, and point to a platform you no longer use. Readers who find those posts through Google land on a ghost town. You have no way to forward that traffic to your new home.

If you are on a custom domain, you take the domain with you. You set up proper 301 redirects on your new platform, Google follows them, and most of your accumulated authority transfers. The transition is not painless, but it is possible.

This is why the custom domain decision matters even if you never plan to leave. It is insurance. The cost is a $12 domain and thirty minutes of DNS configuration. The alternative is discovering, two years from now, that your entire search presence belongs to a platform you want to exit.

Once your posts are indexed and ranking, the next question worth asking is whether AI engines like ChatGPT and Perplexity cite them when people ask about your topic. Google rankings alone no longer guarantee visibility the way they did two years ago, and you can use Google Search Console to track AI-driven traffic to see if that shift is already affecting you. At AnswerRank, we measure exactly that: whether AI assistants recommend a brand when real buyers ask, the same way Search Console measures your Google clicks. The pattern that keeps surprising us is how often a page ranks on page one of Google and is completely absent from AI answers.

Understanding how Substack SEO works comes down to this: the platform indexes fine, ranks for the right queries, and gives you enough on-page control to compete on long-tail searches. The one decision that changes your trajectory is whether you build on Substack's subdomain or your own domain, and that decision is cheapest to make today, before you have an archive worth protecting. Set up your custom domain, verify in Search Console, submit your sitemap, and write something worth finding.