탐색으로 건너뛰기

How should I use a Douyin keyword-index report before deciding on a campaign?

Douyin’s search index is a platform-calculated score, not a number of searches. To read a change, compare the same keyword and the same index across two equal-length windows of an existing daily series. For example, if the daily average rises from 200 to 300, report an increase of 100 index points, and keep the daily values and the source.

For a specific keyword’s history, use index data you can access yourself. BeatAPI can retrieve trending terms, but BeatAPI’s daily keyword-history and audience-profile actions still have no public input and output contracts. For a campaign review, report the index trend, the campaign dates and the observed conversions separately.

What can each index tell you?

Read the search index when your question is about active interest in a topic. When you study broader content attention, keep any source-reported composite index in a separate column. Both indices are platform-calculated indicators, so keep the original metric name, platform and dates. If the search index rises while the composite index stays flat, record stronger search interest as a lead, then check the works and search phrases from the same period. For recent topic discovery, see topic leads and history.

Decide which question the report must answer

QuestionRequired starting evidenceFurther checks
Has this keyword changed recently?Consecutive dates from the same source and indexComplete dates, equal windows and events behind unusual days.
Which of two terms merits content research?Same measure and date window, with context for eachReported values are leads; verify relevance to actual content and audience questions.
Did attention change after the campaign?Campaign dates retained separately from a comparable curveConcurrent promotions, content and events; measured conversions and sales require separate evidence.

Keep a field named search index as an index. Do not rename a value of 10,000 as 10,000 searches or 10,000 people unless the source gives an explicit absolute-count definition and field. Trending-list heat, composite index and search-result counts are three different measures.

The old official index entry now shows a migration notice and redirects to a creator-center login page; without login, the page shows no updated metric definition. Keep the source, the definitions and the version of the export you actually used, instead of applying the old page’s definitions or another platform’s definitions.

What should a weekly keyword report actually say?

Use two equal-length, complete windows for the same keyword, platform, index type and source definition. Record the source, the collection time, the date boundaries and source time zone, the valid daily observations and any missing dates. Keep the original daily values so a reviewer can reproduce the aggregation.

Hypothetical example: all seven daily values are present in each window, and the weekly mean search index changes from 200 to 300. Report: “The mean Douyin search index rose from 200 to 300, an increase of 100 index points or 50%.” Do not write “searches grew by 100” or “50% more people searched.”

Calculate relative change as (new_mean - old_mean) / old_mean * 100. If the old mean is zero, report both values and the point difference without a percentage. Missing, null, suppressed and not-yet-published observations are not zero. If only six days are present, do not divide the six-day sum by seven or present the result as a complete-week comparison. Show the incomplete coverage, then wait for the missing day or compare an explicitly matched subset of dates.

A two-keyword comparison must use the same metric and the same date window. Even then, describe the difference as a difference in reported index values, not as a ratio of audiences, unique searchers or demand. Do not add Douyin, Xiaohongshu and Google scores into a “total searches” column.

A cross-platform brief can put “Douyin search index rose from the previous week” beside “Xiaohongshu search index held steady,” with the dates and source of each. Use the comparison to choose which platform’s posts to read next and which terms to keep tracking.

Can I attribute a rise to a campaign?

Not from the index alone. An index rise is a signal to investigate, not proof that a campaign caused the rise. Put the campaign dates next to the daily series, and check the content, promotions and unrelated events of the same period. Report the index trend separately from measured conversions or sales. A report can say the increase coincided with the campaign; the index alone cannot give conversions, revenue or incremental searchers.

What is verified for automated BeatAPI history collection?

douyin.index.fetch_multi_keyword_hot_trend and douyin.index.fetch_keyword_valid_date are listed with readiness: listed, no public input_schema and next.action: none. A listed action is not a runnable public history workflow.

This page therefore gives no execution template, daily output mapping or batch-collection quote for the two listed actions. Do not infer keyword, date or grouping inputs from the action names. Automated collection needs a published and verified history contract first.

The separate data:douyin.index.fetch_hot_words action is runnable and documents only app_name: aweme for Douyin or toutiao for Toutiao. data:douyin.index.fetch_hot_words documents no keyword or date-window input, so the hot-word action cannot replace a specified keyword’s daily history. Do not add invented keyword/since/until fields.

From existing evidence, hand over a manual report with the keyword, index name, platform and source, both date windows with their valid days, both means, the point difference, a percentage where valid, missing observations and events to verify. Keep the original daily values for reproduction. Without a series, report insufficient evidence instead of building a curve from a hot-word list.

Sources: free Inspect results for the three douyin.index actions above, rechecked on 2026-11-17. This page delivers interpretation and a reporting method; automated history collection is not available.

What can an existing keyword audience report show?

With an existing keyword audience report, first establish whether the report describes search, content viewing or another activity. Save the group definitions, shares, observation windows and comparison populations. If the report contains TGI, keep the TGI reference population and definition. Compare cold-brew and pour-over audiences under the same scope. BeatAPI’s listed keyword-portrait action has no public input and output contract, so keep existing audience reports and content examples as separate evidence.