本站有中文版。
切换到中文Every channel does one or two of three things. AI answer engines are where buyers ask and where we check who gets named. Publishing channels are where approved drafts go. Official data channels are the platforms' own consoles, which we read so the numbers come from the source. Some platforms do both: Xiaohongshu takes the note and reports how it did.
Source runs the questions your buyers ask on each of these engines and records every page cited and every brand named.
We ask it your buyers' questions with web search on, so the answer cites live pages, and record which pages it cites and which brands it names. We ask through both the API and ChatGPT Search on the web, because the two can answer differently.
More →We ask it with web search on and record the pages it cites and the brands it names, on your own query set, refreshed on demand.
More →We ask it through the API and through Gemini Search on the web, and record which pages and brands it names in each. Because it leans on Google's index, we also collect the ordinary Google results page for the same queries as a baseline.
More →We ask it in Chinese through its official API with web search on, and record how it expanded the question, which pages it cited, the excerpt it took from each, and who it named.
More →We ask it in Chinese with web search on and record who it names. The Doubao app answers differently from the API and exposes the pool of pages it read before choosing what to cite, so we collect the app surface separately when you want that depth.
More →Nothing is published until you approve it. Once you do, the team puts the page or post where it belongs, under your own accounts.
New pages are submitted to Bing as soon as they are published, so they get indexed sooner. The Indexing Specialist reports how many were submitted, how many accepted, and what is left of the day's quota.
More →New pages are submitted to Baidu Search Resource Platform for indexing as soon as they are published, which matters for any brand selling in mainland China. Connected with a push token. Submission tells Baidu the URL exists; it does not guarantee the page gets indexed, and the report says so.
More →The Rednote Content Creator drafts the note: title, body, tags, image guidance and a pre-publish checklist. After you approve, it is published from a browser that lives inside your workspace, logged in to your own account.
More →The finished post opens in X's composer in your browser, ready to send. Sourso never holds your X account or its token, and nothing is sent until you press the button.
More →Pages go to your site through GitHub Pages or straight to your server over SSH. The team writes the file; the site, the domain and the content stay yours. Once a page is live, it is submitted to Bing and Baidu for indexing if those are connected.
More →You authorize once. The platform's own console reports into your workspace, read-only, and the analysts work from those numbers.
One Google sign-in, read-only. We read clicks, impressions, average position and the queries behind them. The Search Traffic Analyst starts work as soon as it is connected: last 28 days against the 28 before, top queries and pages, brand versus non-brand, which queries sit at positions 4 to 20, and how much traffic the pages the team published are getting.
More →Clicks, impressions and click-through rate for your site in Bing Search, the daily trend, and the top queries and pages by week. Bing does not report a site-wide average position, so neither do we.
More →Visits, sources and search words for your site in Baidu Tongji, with traffic from AI assistants such as Doubao and DeepSeek broken out. The authorization app is being registered.
More →With your authorization we read the creator center of the same account: how each note did and how the account is growing. The account analyst works from that history to find which topics and formats worked and what to try next. It never scrapes and never invents a missing number.
More →