Substack: get your custom-domain newsletter pages indexed
To get custom-domain Substack posts indexed, push each new post's URL through Google's Indexing API on publish — Substack adds a sitemap entry but never pings Google, and its crawl cadence for mid-traffic newsletters is unpredictable. The indexed archive is the real SEO asset, so submit every post to close the gap.
Substack's editorial flow is great. The SEO flow is not. New posts get a sitemap entry, but Substack doesn't ping the Indexing API, and Google's crawl cadence for medium-traffic newsletters is unpredictable. Pushing each post through IndexerNow closes the gap.
Custom-domain setup matters
- Set up your custom domain in Substack settings (e.g., posts.yourname.com).
- Verify the custom domain in Search Console.
- Sign into IndexerNow with the Google account that owns the verification.
- Your post URLs are now eligible for the Indexing API.
Per-post push workflow
- Publish the post. Substack sends the email.
- Grab the public web URL (posts.yourname.com/p/post-slug).
- Push to IndexerNow. Free quota covers 15 posts/day, which is far more than any newsletter ships.
- After 24h, check Status to confirm indexed.
If you've been writing for a year and only the recent posts are indexed, use the Sitemap picker to pull every URL from your Substack and bulk-push the old ones. The archive is your evergreen SEO asset.
Substack-specific gotchas
- Posts behind the paywall return a partial-content page to Google. They can still rank, but the indexed content is limited to the preview.
- Substack's sitemap.xml lives at /sitemap.xml on your custom domain.
- Avoid changing post slugs after publish — Substack does NOT 301 the old slug.
Sign in with Google, paste your URLs, ship them through Google's Indexing API. Free daily quota, $9.99 for a 50-URL pack.
Try IndexerNow free