Content Distribution on Zhihu: Where the Line Is for Batch Answers

A person who publishes home renovation explainers came to me last year and asked whether he could push one article across twenty Zhihu accounts.

I said he could, but that it would not do much. He did not believe me and tried anyway. Two weeks later he came back: sixteen of the twenty accounts had been restricted, and the remaining four had collected under two thousand views between them.

This is not a new story. Zhihu is one of the few places where the distribution mechanics differ enough from other platforms that the volume playbook from short video simply does not carry over.

Understand why Zhihu does not work that way

Most content platforms distribute on a give a little, watch the numbers, give more basis. Zhihu leans more on the content itself and on accumulated account standing.

Three things are worth knowing.

First, repeated content is cheap to detect. Reusing the same piece across other platforms might survive for a while. On Zhihu it is usually obvious within one round. And once duplication is flagged, the effect is not limited to one collapsed answer. It drags on the whole account.

Second, standing is accumulated. An account that keeps publishing in one subject area gets its answers pushed to people interested in that subject. An account that answers everything shallowly never builds that.

Third, readers have little tolerance for templated writing. This one gets overlooked the most. On other platforms, a sentence like first we clarify the goal, second we prepare resources, is something readers scroll past. On Zhihu it makes them leave, and possibly downvote.

The half a computer can take

Taken apart, the work splits into two kinds.

One kind is fixed actions: open Zhihu, go to a question, tap write answer, paste prepared content, submit, then note which question and what time. These are near identical every time, in a fixed order.

The other kind is the content itself: how to open, which case to use, what judgement to give, where the data goes. That changes every time, and it is precisely what determines the traffic.

The first kind suits a reusable template. The second cannot be automated. The test is simple: if you can close your eyes and still know which button is next, the computer can have it. If you have to stop and think, keep it.

Step	Automatable	Note
Finding questions and logging links	Yes	Collect and record for batch processing later
Opening the question and editor	Yes	Fixed actions
Pasting prepared content	Yes	Content passed in as a parameter
Submitting	Yes	Keep manual confirmation on the first runs
Recording the result	Yes	Time, question, account, for later review
Collecting views and engagement	Yes	Run a periodic sweep
Choosing topics and writing openings	No	Decides whether the piece takes off
Opinion, cases, judgement	No	This is the value you add

With the table in view, the automatable half is roughly half the workload, but it is the half that wears people down. The other half is where your time actually belongs.

How to split multiple accounts without them stepping on each other

If you do run several accounts, split by content direction rather than by volume.

A workable split: one account on industry commentary, one on tools and hands-on work, one on career development. The three are related but do not overlap, and each has a clear readership. Two benefits follow. Each account accumulates its own standing, and outsiders cannot tell the same people run all of them.

What I would avoid is pushing the same material under different titles across every account. That road is narrow on Zhihu. Detection is likely, and even when it does not trigger, neither the numbers nor the standing develop.

Once accounts multiply, device management becomes a real task. My habit is one phone per account, with the alias set to the account name. It looks trivial until you are hunting through a dozen devices for the one that just posted, at which point you appreciate the habit.

Where the promotion line sits

This needs to be stated plainly, because the downside is real.

Zhihu polices off-platform promotion firmly. Leaving a messaging handle, a QR code or an external link in an answer, or disguising it with homophones or split characters, all carry meaningful risk. The light outcome is a collapsed answer. The heavy one takes the account with it.

The steadier approach is to put the effort into answer quality and let interested readers find you, or use a compliant route the platform permits. It is slower, but it does not get you killed.

One more note: if several accounts upvote and promote each other under the same question, that pattern is also easy to detect. Do not do it.

How to set it up

Once the limits are clear, if you are going ahead, work in this order.

Install the workstation and phone-side program using the install selection page, then scan the phones in, alias them and group them, as covered in Devices. One account per device, alias set to the account name.

Then confirm the target phone is online. An offline phone can be seen but not used, and this step is not worth skipping.

Next, on the Conversation page, pick the phone and use refinement mode to spell out the posting flow: open Zhihu, go to the specified question, tap write answer, paste the content, submit. Keep submission for manual confirmation the first time and drop the restriction once it runs cleanly.

Once the flow is stable, save it to Workflows with answer content and question links left as parameters. One template then covers one account day to day rather than one workflow per post.

Finally, set different times for different accounts on the Schedule page. Two details matter. Spread the times rather than stacking every account on the same minute. And remember that a schedule only triggers on time. It does not judge whether a piece should go out, which stays your call.

After the run, check Execution History line by line. If one account keeps failing, do not look only at that instance. Scroll back and see whether it has been failing all along.

Back to the renovation explainer. He cut twenty accounts down to three, one on materials, one on construction, one on budgeting. He writes the content himself and hands posting and logging to the computer. Three months later he told me the three together were getting far more traffic than the twenty ever did. He added a line I agreed with: on Zhihu, the effort you save by pushing volume comes back to you doubled.

For one or two accounts of your own, honestly, doing it by hand is faster. But if you have several accounts and want them on the same flow as your other platforms, run one account through the steps above first, then add the rest.