The blog posts. The feed is dead.

Several “blog / SEO” bugs look alike. They do not share a fix. This page is only when the blog Atom / RSS feed URL 404s, returns empty XML, stays stale, or never mounts in the theme head. Blog comments not posting is shopify-blog-comments-not-posting. Blog tag /blog/tagged thin SEO is shopify-blog-tag-pages-thin.

Soft-check shopify-sitemap-not-updating when sitemap.xml is stuck, and soft-link shopify-robots-txt-blocking when Disallow rules — not the feed itself — are the leftover gap.

On Current theme (not a draft), open the blog feed in incognito: typically /blogs/{handle}.atom. Confirm HTTP status and whether XML contains recent published entries. Soft-check Online Store password / Markets / customer-accounts gates that 401 or blank the feed for guests. Soft-check theme layout / blog template for a stripped alternate Atom link. Soft-check robots.txt and SEO apps that Disallow /blogs/*.atom or feed paths. Soft-check feed / syndication apps that replace native Atom. Soft-check that the blog handle has at least one published article (draft-only looks like an empty feed).

Capture: feed URL + status code, first ~40 lines of XML, password / Markets toggles, theme head / alternate link, robots.txt snippet, SEO / feed app list on Current, and desktop + mobile hard-refresh results.

Confirm the correct blog handle and .atom URL. Turn off store password (or allow the feed path) if the store is live. Restore the theme alternate feed link from default if liquid was emptied. Soften robots / SEO app rules that block /blogs/*.atom. Disable conflicting feed apps one at a time. Publish at least one test article on that blog. Publish Current, hard-refresh the feed URL on desktop and phone.

Honest retest: feed returns 200 with valid Atom/XML and the new entry — not 404, empty, or stale. Soft-link shopify-blog-comments-not-posting when comments are the leftover gap. Soft-link shopify-blog-tag-pages-thin when tag SEO / crawl is the leftover gap. Soft-link shopify-sitemap-not-updating when sitemap.xml is the leftover gap.

Blog comments not posting is shopify-blog-comments-not-posting. Blog tag /blog/tagged thin SEO is shopify-blog-tag-pages-thin. Sitemap.xml not updating is shopify-sitemap-not-updating. Robots.txt blocking crawl is shopify-robots-txt-blocking.

The only honest test for this page: a blog Atom / RSS feed URL 404s, returns empty XML, stays stale, or never mounts — while related comments / tag SEO / sitemap / robots paths may still work.

Stay DIY if you can spend one afternoon on the list above: prove feed URL vs password vs theme vs robots, soft-check apps / Markets, repair, retest. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: blog comments not posting, blog tag pages thin, sitemap not updating.

Pay for help when the work is not the feed URL itself — it is connecting the stack you already have so storefront / blog / feed / SEO exceptions land in a channel you already check, and the live store is one workflow instead of a spreadsheet plus a Slack bot you forgot. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a theme rebuild retainer, not a conversion guarantee, not a brand or theme job.

Other shops' public ranges, not testimonials: a checkout / ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or conversion-lift claim.

What it does not buy: more orders, recovered revenue, a forever feed-uptime guarantee, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.