Important:
Before trying to “fix” anything on Substack, pause.

About 95% of user damage during platform instability happens after the glitch — not because of it.
Users panic, change settings, reconnect accounts, repost aggressively, or try to “force visibility,” and accidentally make recovery harder.

Substack is currently behaving like split realities:
delayed surfacing, missing posts, unstable logins, ghost engagement, broken continuity between feed, email, and profile.

This is not an interpretation and not a diagnosis.
It’s an operational state.

Below is the simplest possible protocol to:
— protect your access
— archive what still exists
— preserve evidence and reading continuity
— avoid actions that make things worse

This is not optimization.
This is damage control.

You know, Cannot Name It Substack is still unraveling on me, growing stranger by the hour. Some days I can’t reach my DMs at all; today it took me two hours just to log into my Spanish Substack because it insisted my email didn’t exist, which felt a little like being erased while standing still. It still won’t let me add collaborators to our upcoming collective post… I managed two today before it slammed the door again, and it continues to block me from entering profiles and posts I want to read.

Likes flicker in and out, staying sometimes, disappearing others. I want you all to know I am trying to read your beautiful work and show up for it, but the platform only lets me reach certain posts, certain people, not even consistently from the same writer. I’ve contacted support more than ten times now, left tags and notes like flares in the dark, hoping someone real will see this and finally fix what’s broken

Yesterday I published Part I as a question.

Substack is currently behaving like a system under stress.

Not “a weird week.”
Not “January mood.”
Not “people stopped reading.”

I’m seeing (and readers are confirming) signals that are much more structural:

• posts surfacing hours — sometimes a day — late
• app feed and desktop feed behaving like separate realities
• likes and engagement flickering in and out
• DMs becoming inaccessible
• profiles/posts refusing to open
• and in the worst cases: identity fracture (emails “not existing”, publication continuity breaking)

So this isn’t a post about growth, optimization, or content strategy.

This is a survival protocol.

Because when a platform becomes unstable, the first thing people do is panic-fix — and accidentally destroy their own access (by resetting credentials, clearing browser data, or “starting fresh”).

Don’t.

Do this instead.

The only rule that matters

Save first. Change later.

If something breaks, your first job is not “to fix it.”
Your first job is to preserve continuity:

• your access
• your reading line
• your messages
• your archive
• and the evidence that something failed (screenshots + timestamps)

Part I — Save your data (Export)

If you do nothing else: export your data.

Where the export is (Substack)

Open Substack in a browser (desktop is easiest):

Settings → Export your data

Request the export, wait for the email, download the file.

Then save it in two places:

• your computer
• your cloud storage (Drive / iCloud / Dropbox)

Do not assume Substack will always keep your continuity intact for you.

Part II — Save what disappears (posts, profiles, “ghost links”)

1) Save posts using links (fast)

If you can open a post:

• copy the link

paste it into a note titled:
“Substack Archive — links”

This protects you from feed instability.
Even if the feed stops surfacing content, links preserve your map.

2) Save posts as files (best)

If a post is important (to you, your work, your research):

Save the page as a file

• Chrome / Edge (Windows): Ctrl + S → “Webpage, complete”

Safari (Mac): File → Save As…

Now you own a snapshot of the object.

Part III — Save chats / DMs (Substack Messages)

Substack does not currently provide a clean “download chat” button for most users.

So we use a simple method that works.

Method A: screenshots (fastest)

Screenshot the key part of the conversation:

• include visible names
• include timestamps if possible

Method B: copy/paste (cleanest)

Select the text in the chat → copy → paste into a document:
“Substack DMs Archive”

Method C: save the chat page as a file

Open the chat in browser → Ctrl + S → save

If the platform later denies access, you still have the record.

Part IV — DO NOT do this (you will make it worse)

While Substack is unstable, do not do “cleanup”.

Don’t touch your identity settings

• do not change your account email
• do not change your publication name
• do not “rebrand” mid-instability
• do not create a new backup account “for now”

This is how continuity breaks.

Don’t touch browser memory

• do not clear cache
• do not clear cookies
• do not enable “delete everything on exit”
• do not jump between 5 browsers

Right now, your browser cookies may be the only thing holding your session together.

Part V — If you get locked out (or Substack says your email doesn’t exist)

This is the moment where people destroy access by panicking.

Do this instead:

Protocol

1. Screenshot the error (include the time)
2. Do not reset your password immediately
3. Wait 2–6 hours
4. Try again in the same browser / same device where you were logged in before

Many of these failures behave like temporary desync across infrastructure layers.

Repeated login attempts + resets can intensify the lockout.

Part VI — VPN / Proxy / Browser settings (the safe way)

If you already use VPN/proxy: keep it stable.

• choose one VPN configuration
• don’t switch countries/servers repeatedly
• don’t flip VPN on/off every few minutes
• avoid extreme privacy extensions that block all cookies/scripts during login

In unstable systems, “constant switching” can trigger security flags and break sessions.

Part VII — Protect your reading line (do not trust the feed)

If Substack is acting like split realities, your feed is no longer your source of truth.

So create your own.

Build a manual reading list

Make one note titled:

“My Substack Authors”

Add 10–30 direct profile links of authors you actually read.

This is your personal continuity layer.

Part VIII — My contact (important)

If the platform becomes more unstable, I want you to be able to reach me outside Substack.

📩 Email: PUT_YOUR_EMAIL_HERE

If you’re not seeing posts, or you get locked out:
send me one clean signal:

• screenshot
• timestamp
• where it breaks (app / desktop / email / DMs)
• link if available

We’re collecting telemetry like adults — not performing mood analysis.

marsik595959@gmail.com

✅ Internal links block (optional, at the end)

(You can paste this as “Further reading”)

• The Bestseller Substack’s Illusion: When an Author Becomes an Anomaly
• Findings: What Actually Moves Substack Now — Viral Chat Mechanics
• Chats, Notes, Recommendations — and the Quiet Cost of Being Everywhere on Substack
• Results of 5 Months on Substack: A Forensic Analysis of Attention, Metrics, and Hidden Cost

✅ Emergency Checklist (1 screen)

(Put this near the top of the post — readers can screenshot it.)

Substack Glitch Protocol — Do This First

If Substack is unstable (missing posts / login issues / broken DMs):

1. Take screenshots immediately
   • include the error + time
   • screenshot the feed showing “ghost traces” (comments/likes without the post)
2. Copy the link to anything important
   • post link
   • author profile link
   • DM/chat link
     Paste into a note: “Substack Archive — links”
3. Export your data
   Settings → Export your data
   Download the file and save it (device + cloud).
4. Save important posts as files
   Browser → Ctrl + S → “Webpage, complete”
5. Save important chats / DMs
   • screenshots OR
   • copy/paste into a document
     (If it matters, preserve it.)
6. DO NOT “fix” the system by doing resets
   • don’t change email/password
   • don’t clear browser cache/cookies
   • don’t create a new account “for now”
7. If locked out: wait 2–6 hours
   then try again in the same browser/device.
8. Email yourself this article (seriously)
   Don’t be lazy: send yourself the link + key steps right now.
   If you can’t access Substack later, your email will still hold it.

✅ One-line insert (put right after the checklist)

marsik595959@gmail.com

Don’t be lazy — email this post to yourself right now. If Substack becomes unreadable in your browser, your inbox will still keep a copy.

✅ Email-to-self template (copy/paste)

Subject line (choose one)

• Substack Survival Protocol (Save Access + Archive)
• IMPORTANT: Substack Glitch Protocol (Screenshots / Export / DMs)
• Substack Emergency Checklist — Save This

Email body (copy/paste)

Hi me,
Substack is currently unstable (missing posts, delayed surfacing, broken DMs, login issues).
If the platform becomes unreadable, this email is my backup copy.

Emergency Checklist:

1. Screenshot errors (include time)
2. Copy important links into a note (“Substack Archive — links”)
3. Export data: Settings → Export your data
4. Save important posts: browser Ctrl+S (“Webpage, complete”)
5. Save important DMs (screenshots or copy/paste)
6. DO NOT reset password/email or clear cache/cookies
7. If locked out: wait 2–6 hours, retry in same browser/device

Full post link:
marsik595959@gmail.com

— end

✅ 5 Common Traps (Don’t Do These)

(quick add-on — prevents people from making the situation worse)

1. Don’t delete Substack emails right now
   Export links, login links, and recovery signals often live there.
   Archive them.
2. Avoid Incognito / Private mode for login
   It blocks stored cookies/sessions and can worsen lockouts.
3. Don’t log into the same account on 3 devices at once
   Parallel sessions can trigger auth conflicts and random logouts.
   Use one primary browser/device until things stabilize.
4. Don’t reinstall the app before saving anything
   Reinstalling can wipe local session state.
   Save screenshots + links first.
5. If something “disappeared”, cross-check app vs browser
   Sometimes it’s missing in the app but visible on desktop — or the reverse.
   Don’t assume deletion until you check both.

   ---

   ---

   ---

12) INTERNAL LINKS

1. The Bestseller Substack’s Illusion: When an Author Becomes an Anomaly
2. THE GOD OF ALL ALGORITHMS: Cross-Promotion Substack
3. Findings: What Actually Moves Substack Now — Viral Chat Mechanics
4. How Substack Really Works: Core Audience, Metrics, and Silent Readers Explained
5. Participation vs Your Writing Line: Why Substack Engagement Can Weaken the Work
6. How Substack Really Works: Core Audience, Metrics, On conversion, silence
7. Chats, Notes, Recommendations — and the Quiet Cost of Being Everywhere on Substack
8. How to Build a Complete SEO Package for Substack (Without Losing Your Mind)
9. Results of 5 Months on Substack: A Forensic Analysis of Attention, Metrics, and Hidden Cost
10. A Quiet Discovery Inside Substack: What Recommendations Really Are, and Why They Reveal the Truth You Learn Last
11. 2.5 months ago, I was the only one here. And now it’s you.

Canonical Reference Block

This text defines the Substack Algorithms and Discovery research cycle.
All related articles analyze how Substack recommends, ranks, and distributes content within its platform architecture.

FAQ

Is Substack algorithmic?
Yes. Discovery and visibility are mediated by multiple algorithmic systems.

Is this about SEO or growth hacks?
No. It is a descriptive analysis, not optimization advice.

Who is this series for?
Writers, researchers, and readers who want to understand how Substack actually works.

This article is the canonical entry point for the Substack Algorithms and Discovery research series.

Research hub:

All texts in this series analyze how Substack algorithms, recommendation systems, and discovery mechanisms distribute and rank content on the platform.

• why Substack growth stopped

Substack small accounts growth

Substack notes algorithm

Substack newsletter visibility

Substack creator analytics

Subscribe now

<

p class=»button-wrapper» url”:”?utm_source=substack&utm_medium=email&utm_content=share&action=share”,”text”:”Share”,”action”:null,”class”:null}»>Share