Substack SEO: A Practical Checklist to Get Your Newsletter Found on Google

Public Substack posts can appear in Google Search. Start by answering a specific reader question, checking the page's public accessibility, and making its title and content clear. Then use Google Search Console to distinguish an indexing problem from a page that is indexed but receives little search traffic. Neither a custom domain nor a completed SEO checklist guarantees rankings. Sources: Substack's SEO guide; Google's technical requirements.

This guide focuses on the public website version of your newsletter. Sending an email and publishing a web post are separate delivery choices in Substack, so email performance is not a substitute for checking the web page. Source: publishing a Substack post.

By Subshack. Sources checked September 8, 2026. Procedures below are based on official documentation, not a live test inside every account. Examples and priority judgments are our editorial suggestions, not customer results.

The Substack SEO checklist, in priority order

Use this as a work order, not a prediction of traffic. Fix access problems before polishing a description, and improve an existing useful article before creating another page for the same question.

These effort estimates assume a small publication and are not measured benchmarks. The settings, technical checks, and limitations behind the checklist follow below.

Does Substack rank on Google automatically?

Being public makes a page available for consideration, not entitled to a search result. Google's minimum requirements include an accessible page, a successful HTTP response, and indexable content. Google still does not promise to index or serve every eligible page. Source: Google Search technical requirements.

Search Console is a diagnostic tool, not an activation switch for Google. Google can discover pages without it. Verification gives you access to information about your site's search performance and problems. Source: getting started with Search Console.

Do not use a missing search result as proof that you need more subscribers, a paid plan, or a new domain. Inspect the URL before choosing a remedy.

Where are the SEO settings in Substack?

In post settings, the documented SEO controls are title, description, post URL, and social preview image. Defaults come from your post. The SEO title is separate from your email headline. Source: Substack's post SEO controls.

Sources: post settings, image alt text, Analytics settings, and custom domains.

The dedicated SEO guide dates from February 2023. Check your current interface; the newer help pages above cover other controls, not a replacement post-SEO workflow.

The documented post controls do not amount to a general HTML-head editor, redirect manager, or robots.txt editor. Do not apply a WordPress tutorial that assumes those controls exist. Inspect the generated page and ask Substack support about platform-controlled problems instead of pasting technical markup into the article body.

Turn an email headline into a useful search result

You can keep a personal voice without making the subject a guessing game.

Here is a fictional example for a newsletter about freelance design. It illustrates a proposed article package, not a tested SEO result.

The important change is not adding more keywords. It is making a promise the article can fulfill. The proposed description belongs only on an article that actually includes the agenda and brief.

Try this test before editing: What could a reader do after reading the article that they could not do from the headline alone?

For the fictional example, the answer might be: prepare the next client kickoff using a completed sample and a blank template. That is a stronger editorial brief than “write 1,500 words about onboarding.”

Google creates title links using several signals, including the title element and visible headings. It may choose wording different from your SEO title. Keep those elements consistent in meaning rather than trying to optimize them for unrelated subjects. Source: Google's title-link guidance.

Google also generates snippets dynamically and may use page text instead of your meta description. Write a useful summary, but do not assume it will always be displayed verbatim. Source: Google's snippet guidance.

Substack warns that changing a published URL can break existing links. Improve the article without changing its address unless you have verified what happens to the old URL. Source: Substack's URL guidance.

Make the answer usable on the public page

Our editorial recommendation is to start with the answer, then add the reasoning, examples, and exceptions that make it useful. A search visitor should not need last week's newsletter to understand this one.

Give sections descriptive headings. For the fictional onboarding guide, “What to collect before the kickoff” is more useful than “The second thing.” Keep the template in readable text rather than putting the only usable version inside an image.

Add contextual links from older articles when the new resource answers a natural next question. “Use this client onboarding checklist” describes the destination better than “click here.” Google recommends crawlable links and meaningful anchor text so readers and its systems can understand the destination. Source: Google's link guidance.

For an original image, open its menu and choose Edit alt text. Describe what it contributes. For a fictional sample brief, useful text might be: “Example project brief with fields for scope, approval owner, deadline, and required assets.” Do not describe an image that is not actually present. Source: adding alt text on Substack.

What about paid posts and personalized sections?

A paywall is not a universal ban on Google indexing. Google documents requirements for subscription content, but that does not establish which text a particular Substack post exposes to a crawler. Do not assume a crawler receives your paid-reader view. Source: Google's paywalled-content guidance.

There is a specific rule for Substack's audience-specific content blocks: search crawlers and RSS feeds see the Not subscribed version. In the editor, these blocks are under More → Audience-specific content, with a Preview option for checking reader tiers. Source: Substack's audience-specific content documentation, updated July 20, 2026.

For an article intended to attract search visitors, our recommendation is to make the core answer useful in that public experience. Reserve genuinely additional value for paying readers rather than promising a free checklist and exposing only a subscription pitch.

Connect Substack to Google Search Console without assuming an old tutorial still works

With a custom domain you control

Add a Domain property for your domain in Search Console. Follow its DNS verification instructions at your DNS provider, then return to verify. Keep the verification record in place. This verifies ownership without depending on a tracking script appearing in Substack's page template. Source: Google's ownership verification instructions.

A Domain property covers its subdomains. For example, a fictional example.com property can include both www.example.com and newsletter.example.com. Filter to the publication or add a narrower URL-prefix property when reviewing it separately. Source: Search Console property types.

With a publication at yourpublication.substack.com

Use the publication's full HTTPS address as a URL-prefix property. You do not control Substack's DNS. Google's Analytics and Tag Manager verification methods are possible only when their placement and account-permission requirements are met. Sources: property types; verification requirements.

Substack currently documents native fields for a GA4 Measurement ID and a Google Tag Manager ID in Settings → Analytics. Its August 19, 2026 help screenshot does not show the Google Site Verification box used in some older tutorials. Do not assume your account has it. Source: current Analytics documentation and screenshot.

If you already use GA4, try Google's Analytics verification method with the same Google account and the required edit access. A tracking setup that records visits is not, by itself, proof that it meets Search Console's verification requirements. Source: Google's verification requirements.

If verification fails, record the exact error, check Google's prerequisites, and ask Substack support about the generated page. This guide does not claim a guaranteed workaround for every account. Do not buy a domain solely because a tutorial's field is missing.

Find a working sitemap, or use the RSS feed

Check the publication's /robots.txt for a declared sitemap and test the sitemap address you find. You can also check /sitemap.xml, but submit it only if it actually returns a sitemap. Do not assume a particular post count makes one appear.

If there is no working sitemap, Substack documents its public RSS feed at https://yourpublication.substack.com/feed. Replace the publication name and check the resulting address, including any custom-domain redirect. Source: Substack's RSS documentation.

Google accepts RSS and Atom feed URLs as sitemap submissions. A feed generally contains recent URLs, so it is not necessarily a complete inventory of your older posts. Submit the working URL in Search Console's Sitemaps report and check its processing status. Submission helps with discovery; it does not guarantee crawling or indexing. Source: Google's sitemap documentation.

If neither endpoint works, keep useful internal links to your archive and report the endpoint problem to Substack. Publishing filler to reach an alleged sitemap threshold is not a fix.

Diagnose a Substack post that is not showing on Google

In the correct Search Console property, paste the complete post URL into URL Inspection. Review Page indexing, the crawl information, and the Google-selected canonical. The indexed report describes Google's recorded version; Test live URL checks current accessibility. A passing live test does not mean the page is already indexed. Source: URL Inspection documentation.

Use the reported status to choose an investigation:

Status meanings come from Google's Page indexing documentation. The suggested investigations are ours; none of these statuses alone diagnoses the quality of a publication.

After a meaningful fix, you can request indexing. Google says repeated requests do not make a URL crawl faster, and a request does not guarantee inclusion. There is no reliable universal deadline for a Substack article to rank. Source: asking Google to recrawl.

Will a custom domain improve Substack SEO?

Do not treat a custom domain as a ranking upgrade. Our recommendation is to choose one for a durable publication identity and control of the domain, not as a promised cure for low traffic.

Substack's documented setup starts at Settings → Domain and provides the DNS target to use. As checked September 8, 2026, Substack lists a one-time US$50 connection fee. Domain registration is separate. Follow the current setup instructions rather than copying an old CNAME value from a blog. Source: Substack's custom-domain documentation.

If a publication already has indexed posts, treat the change as a URL migration. Inventory important addresses, check the old-to-new redirects, inspect canonicals, and monitor the relevant properties. Google warns that rankings may fluctuate while a site move is processed. Source: Google's site-move guidance.

A custom domain also does not answer where every piece of content should live. If you run a separate website, choose a primary home for each substantial guide. Our recommendation is a complete guide at that address, plus a genuinely complementary newsletter or excerpt linking to it, rather than an identical full copy on both.

Google uses canonicalization signals to choose among duplicate or similar URLs; your preferred canonical is not an absolute command. Do not assume Substack offers a cross-domain canonical field without verifying the current controls. Source: Google's canonicalization guidance.

Measure search progress without confusing clicks and subscribers

In Search Console's Performance → Search results, select Web, choose a date range, and filter to the article under Pages. Then inspect Queries. Keep impressions, clicks, CTR, and average position in context: average position is an aggregate, not a promise of one fixed ranking for every reader. Source: Search Console's Performance report.

Our suggested first comparison is two complete 28-day periods. This is a review interval, not a deadline for success. With sparse data, use a longer observation period instead of declaring a winning title after two clicks.

Separate people searching your publication's name from people finding a topic. Use the branded-query filter where available, or a query exclusion for your publication and author names. Check the exclusions manually. Google notes that automatic brand classification can be imperfect and some queries are withheld, so the result is not a complete census of non-brand demand. Sources: query dimensions and limitations; filtering instructions.

Read the pattern before choosing the next edit. For example, new impressions for an irrelevant query suggest a different investigation from more relevant impressions with few clicks. Look at what the searcher wanted and whether your result honestly promises it. A title is a hypothesis to test, not the default explanation for every change.

A search click is not a subscription. Use a confirmed signup event or the attribution actually exposed by your measurement tools. Do not divide all new subscribers by Google clicks and call it an organic-search conversion rate: the subscribers may have arrived through other routes.

To interpret the subscriber side of that journey, start with the distinction between Substack followers and subscribers. For channel planning, see our Substack growth strategy guide.

What changes for AI search and citations?

Do not rewrite the guide into a collection of disconnected paragraphs just for AI. Google says there is no required “chunking” format, special AI markup, or ideal page length. It also says llms.txt does not improve visibility in Google Search. Original, useful work and accessible pages remain the priorities. Source: Google's generative AI optimization guide.

Our editorial test is simple: does the page provide something worth consulting directly, such as a worked example, a useful comparison, or a reusable template? Put sources near consequential claims and make clear which recommendations are yours. These choices serve readers; they do not guarantee a citation.

Google's current documentation includes Settings → Search generative AI in Search Console. Check the effective choice, including any inherited setting, if visibility in those features is your goal. This control is distinct from AI training controls. Source: Search generative AI control.

For measurement, the Generative AI performance report documents impressions from supported Google AI features. Those impressions are not visits or subscriptions, and the report is not a list of every assistant that cited you. Do not add its impressions to the Web total as though they were a separate audience. Source: Google's generative AI report.

OpenAI separately documents OAI-SearchBot for search and GPTBot for potential training use, with independent controls. A webmaster can allow search while disallowing training. On a hosted publication, verify what you can actually control rather than assuming access to robots.txt or the platform's firewall. Source: OpenAI's crawler documentation.

For citations you observe directly, record the assistant, question, date, and linked page. Keep that log separate from referral visits and confirmed conversions. It is an observation sample, not your total AI visibility.

Copy this one-page SEO review sheet

Use one sheet per important article. It is a working document, not a score or an automated diagnosis.

ARTICLE AND PURPOSE
Public URL:
Reader's main question:
Useful answer or resource the page provides:
Why this deserves a page rather than an update to an existing one:

PUBLIC EXPERIENCE
What a signed-out reader can actually access:
SEO title and description reviewed:
Existing pages that link here:
Image descriptions and mobile readability checked:

GOOGLE CHECK
Search Console property:
Inspection date and reported indexing status:
Google-selected canonical, if available:
Sitemap or feed processing status, if submitted:
Access problem to fix or refer to Substack support:

EVIDENCE AND NEXT ACTION
Date range and filters:
Relevant queries, impressions, and clicks:
Observed AI citations, recorded separately:
Confirmed signups and their actual attribution source:
One change to test:
Reason for that change:
Review date and what the available data cannot prove:

Start with one article you would confidently recommend to a reader, not your entire archive at once. Once the review process is useful, reuse the sheet and automate exports or reminders before considering automated content changes.

For the public-facing profile, Subshack's free profile audit reviews signals across positioning, conversion, trust, activity, and discovery. It is our own tool. It does not have private subscriber data, and a good audit score is not a Google ranking, an indexing confirmation, or a growth guarantee. Use Search Console for the search checks in this guide. Source: the audit's published scope.

Make the page worth finding, verify that it can be found, and use the evidence to decide what to improve next.