← Back to stories Wooden letter blocks spelling tariffs, China, and USA representing trade relations.
Photo by Markus Winkler on Pexels
凤凰科技 2026-03-10

Xiaohongshu (小红书) Regulates AI‑Managed Accounts: All AI‑Powered Homepage Posts Will Be Directly Banned

What happened

It has been reported that Xiaohongshu (小红书), the Chinese social‑commerce and lifestyle app popular with young urban users, will bar AI‑managed accounts from publishing posts to users’ homepages. According to coverage on ifeng, the move targets accounts that are primarily or entirely operated by generative AI rather than by human creators; such AI‑powered homepage posts will reportedly be directly banned. The platform’s announced change is part of a wider push to tighten controls over automated content on major Chinese apps.

Why it matters

Xiaohongshu blends user recommendations, short posts and e‑commerce; its homepage feed drives discovery and sales. Banning AI‑managed posts from that prime space changes incentives for creators and companies that package generative models into influencer tools. Who benefits? Human creators gain protection from synthetic competition. Platforms reduce risks from misinformation, fraud and manipulated product endorsements. But AI toolmakers and some content startups could see distribution curtailed overnight.

Wider context and implications

China has been sharpening rules on online content and algorithmic governance even as global debates over AI safety and export controls heat up. It has been reported that domestic platforms face mounting pressure to police deepfakes, unverified synthetic content and commercial fraud. For Western readers: Xiaohongshu sits at the intersection of social media and e‑commerce in China, so platform policy shifts can ripple into marketing strategies, influencer economies and cross‑border brand campaigns. Will rivals such as Douyin or Bilibili follow? That remains to be seen, but this signals a turning point in how Chinese tech platforms balance innovation with content control.

AISpacePolicy
View original source →