Baidu is unusual among search engines in naming its algorithms, publishing what each one targets, and maintaining a single consolidated standards document. Knowing the names is not trivia — a penalty notice references them, and each has its own published specification.
How the standards document is organised
Baidu groups the algorithms by what they protect, which is the most useful way to read them:
- Page content quality — Hurricane (飓风) against scraping, cross-field publishing and site networks; Jinfeng (劲风) against abusive aggregation pages; Xiyu (细雨) against B2B low quality.
- Meeting user need — the Title Specification enforced by Qingfeng 1.0; Qingfeng 3.0 with the Download Site Quality Specification.
- User experience — Bingtong 5.0, enforcing the Mobile Landing Page Experience White Paper.
- Fair competition — Jinglei (惊雷) against click manipulation, Lvluo (绿萝) against link trading, Fenghuo (烽火) against hijacking.
The pattern behind them
Each algorithm enforces a published specification rather than a general principle. Qingfeng enforces the title specification and the download-site specification; Bingtong enforces the landing-page white paper. That makes Baidu compliance unusually concrete: there are documents with numbers in them, and the algorithm is the enforcement mechanism.
The versioning matters
Algorithms are upgraded and their scope widens. Qingfeng began as a title algorithm in September 2017 and by 3.0 covered download deception. Hurricane began with scraping in July 2017, added stitching and cross-field collection in 2.0, and added site networks in 3.0 (August 2019). Knowing a name is not enough; the version decides what is covered.
The recovery structure
Restrictions are proportional to severity, and Hurricane’s published terms are the clearest statement of how Baidu handles repetition: three months to lift after a first offence is corrected; a second offence is not released. Compliance here is not a campaign that ends.
How to use this section
Identify which algorithm covers the behaviour in question, read its own specification for the numbers, and check the version history for what was added last. Every page in this section follows that structure.
So setzen wir das um
We work Baidu compliance from the consolidated standards document rather than from individual announcements, because the announcements are point-in-time and the algorithms keep widening. The structural fact worth telling any client early is that Baidu enforces published specifications with numbers in them — which makes an audit against them possible in a way it is not for engines that publish only principles.
Verwandte Leistungen