Last year someone who publishes home-renovation explainers asked me whether one draft could be pushed across twenty Zhihu accounts.
I said it could, and 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 answers on the remaining four added up to fewer than two thousand views.
This kind of result shows up often. Content distribution on Zhihu is quite far from other platforms. Bringing over the volume playbook from short video is an easy way to do the work for nothing.
Why Zhihu does not reward volume
Most content platforms give you a little traffic first, watch whether the numbers are good, and add more if they are. Zhihu leans more on the content itself, and on the standing an account has accumulated.
Three points in particular.
When the same piece shows up again and again, the platform’s cost of recognizing it is low. Moving a piece around on other platforms can slip through for a while. On Zhihu it is usually visible within one round. Once duplicated content is judged, the whole account is affected. It is more than that one answer being collapsed.
Account standing is accumulated. An account that keeps publishing in one subject gets its answers pushed more readily to people interested in that subject. An account that answers everything, and says nothing in any depth, has a hard time building that.
Zhihu readers have little tolerance for templated wording. On another platform, “first, clarify the goal; second, prepare the resources” is something a reader scrolls past. On Zhihu, that kind of sentence makes people swipe away, and they may downvote it on the way out.
The half that can be automated
Taken apart, Zhihu distribution is two kinds of work.
One kind is fixed actions: open Zhihu, go to a question, tap write answer, paste content that is already written, tap publish, then note which question it went to and when. These actions are almost the same every time, in a fixed place and a fixed order.
The other kind is the content itself: how to open, which case to use, what judgment to give, where to put the data. That changes every time, and it is the part that decides the traffic.
The first kind suits a template that runs again. The second kind stays with a person. If you can close your eyes and still know which button comes next, the computer can have that step. If you have to stop and think, keep it yourself.
| Step | Can it be automated | Note |
|---|---|---|
| Find questions and record the question links | Yes | Collect and log them, so later work can run in batches |
| Open the question and enter the editor | Yes | The actions are fixed |
| Paste content that is already written | Yes | The content is passed in as a parameter |
| Submit | Yes | Keep manual confirmation the first time |
| Record the publish result | Yes | Time, question, and account, for later review |
| Collect views and engagement | Yes | Run a summary on a cycle |
| Choose the topic and write the opening | No | Decides whether the piece takes off |
| Opinion, cases, judgment | No | This is the value you add |
The part that can be automated is about half the workload, and what it saves is the repetition that wears people down. The other half is where your time belongs.
How to split several accounts, and where the line is
If you run several accounts, split them by content direction. Piling them up by count works poorly.
One workable split: one account on industry commentary, one on tools and hands-on work, one on career development. The three directions are related and do not overlap, and each has a clear readership. Each account can accumulate its own standing, and it is hard for an outsider to see that the same people run all of them.
Pushing the same batch of content onto every account under a different title is a narrow road on Zhihu. The chance of being recognized is high. Even when it is not recognized, the numbers and the standing still fail to build.
Once there are many accounts, device management is real work. Bind one phone to one account, and set the alias to the account name. The habit pays off when you are looking through a dozen devices for which account just posted.
Zhihu polices off-platform promotion firmly. Leaving a WeChat ID, a QR code, or an external link directly in an answer, or dodging that with an obvious homophone or split characters, carries real risk. The light outcome is that the answer gets collapsed. The heavy one pulls the account in with it.
The steadier approach is to put the effort into answer quality, let interested people find their way to you, or use a compliant route the platform allows. That is slower, and the account is less likely to be restricted.
Having several accounts upvote and promote each other under the same question is also easy to recognize. Keep that pattern rare.
How to set it up
If you are going to do it, follow this order:
Install the workstation and the phone-side program from the install selection page, then register the phones you will use, set aliases, and group them. Details are in Devices. One account per device, with the alias set to the account name.
Then go back to the Devices page and confirm the target phone is online. An offline phone can be viewed and cannot run. Keep this check in the sequence.
Next, on the Conversation page, pick the phone and switch to refine mode to talk the publish flow through: open Zhihu, go to the specified question, tap write answer, paste the content, tap publish. On the first run, leave publish for a person to confirm. Remove that limit after it runs cleanly.
Once the flow is stable, save it as a workflow, and leave the parts that change, such as the answer content and the question link, as parameters. One template covers an account’s day-to-day publishing.
Finally, on the Schedule page, give each account its own time. Spread the times. Keep every account off the same minute. A schedule only fires at the set time. Whether the piece should go out stays your decision.
After the run, check Execution History line by line. If one account fails often, look past that single run and read the history, to see whether it has been failing all along.
The renovation explainer later changed the approach. Twenty accounts came down to three: one on choosing materials, one on construction, one on budgeting. He writes the content himself. Publishing and logging go to the computer. Three months later he said the three accounts together were getting far more traffic than the twenty had. He also said that on Zhihu, the effort you save by pushing volume has to be paid back double.
With one or two accounts, doing it by hand is faster. With many accounts, and with other platforms on the same kind of flow, get one account through the steps above first, then add the rest. Installation is in the install documentation.
Frequently asked questions
- Can I push content to Zhihu in bulk like other platforms?
- You can, but you will get almost no traffic. Distribution on Zhihu leans on answer quality and account standing. When the same piece appears on dozens of accounts, the platform detects duplicated content cheaply, and the usual outcome is a few answers with no data and a batch of restricted accounts. Automate the process, not the content.
- Is running several Zhihu accounts by myself realistic?
- It depends what you are doing. If each account has its own subject and direction, one person handling topics and writing while the computer handles posting and logging is workable. If the plan is to spread the same material across accounts, more accounts means more risk.
- Which steps suit handing to a computer?
- Finding questions, opening them, entering the answer editor, pasting prepared content, submitting, recording the result and collecting data on a cycle. These are fixed actions in a fixed order, which makes them good candidates for a reusable template.
- Which steps must a person write?
- The opinion, the case, the cited data, the professional judgement, and the opening two or three sentences. Zhihu readers have very little tolerance for templated openings. A paragraph that runs first, second, finally is filed as low quality almost immediately.
- How should multiple accounts be split?
- By content direction, not by count. One account on career development, one on industry commentary, one on hands-on tools, for example. Clear directions let each account accumulate standing, and it is not obvious to outsiders that the same people run all of them.
- What happens if I put contact details in an answer?
- High risk. Zhihu polices off-platform promotion firmly. Leaving a messaging handle, QR code or external link gets the answer collapsed at best and the account restricted at worst. The steadier approach is to put the effort into answer quality and let interested readers find you, or use whatever compliant route the platform allows.
- Does posting time matter?
- It matters, but less than content. Follow when your readers are active, such as the lunch break and the evening on weekdays. With several accounts, spread the times rather than stacking them on the same minute. It looks more natural, and when something breaks you can tell a single device from the whole flow.
- Where is the safest place to start?
- One full loop: one account, one question, one answer you wrote yourself. Get the posting action working and visible in Execution History before adding a second account. Starting with a dozen accounts means you will not even know where to look when something breaks.
Move the repetitive actions out
Give the computer the finding, posting and logging
Software is completely free and runs on your own computer.