What to watch
Brand monitoring usually covers a few recurring checks:
- Branded search results: which pages rank for your brand name, product names and "brand + review" or "brand + alternative" queries.
- Ads bidding on your brand terms.
- Resellers and partner pages: whether they use your product names, descriptions and prices correctly.
- Mentions on public review, news and comparison pages.
The SERP API covers the search side and the Scraper API covers the pages. Batch and webhooks tie them into a job that runs without supervision.
Start small. A dozen branded queries in your main markets and a list of the reseller pages that matter most will tell you more in the first month than a sprawling setup. Add queries when a check keeps surfacing something new, and drop the ones that never change.
Step 1: check branded search results
Query Google, Bing and DuckDuckGo for your brand terms in each market you sell in. The response separates organic results, ads, featured snippets, related questions and related searches.
curl https://api.siftzo.com/v1/serp \
-H "X-API-Key: $SIFTZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"engine": "google", "q": "examplebrand review", "country": "us", "language": "en"}'From each result page, record:
- The domains in the top organic results, and whether your own pages hold the first positions.
- Every entry in
results.ads, with itsplacement, so you can see who advertises on your name. people_also_askandrelated_searches, which show what people want to know about you.
Check parse_status before comparing runs, so a partly parsed page is not mistaken for a change.
Step 2: fetch the pages behind the results
New URLs in your branded results deserve a closer look. Collect them, along with your list of known reseller and review pages, and send them to POST /v1/batch. A batch takes up to 1,000 scrape requests; with dedupe: true the same URL is fetched once even if several queries found it.
curl https://api.siftzo.com/v1/batch \
-H "X-API-Key: $SIFTZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"requests": [
{"url": "https://reviews.example.net/examplebrand", "format": "markdown"},
{"url": "https://reseller.example.org/p/example-product", "format": "markdown"}
],
"dedupe": true,
"webhook_url": "https://hooks.example.com/siftzo"
}'Markdown output makes it easy to search for your brand and product names and to diff a page against last week's version. For reseller pages, the Data API product record gives you price and availability in a fixed shape.
Checking reseller and partner pages
Resellers and marketplaces often show your products to more people than your own site does, so it is worth knowing how they present them. Keep a list of the product pages you care about and check them on a fixed rhythm. For each page, compare:
- Product name and brand against your catalogue, to spot misspellings and outdated names.
- Price and availability against your price policy, using the product record.
- The description in Markdown against your current copy, to find claims you no longer make.
Many shops show different content to different countries. Set country on each request to see the page as a local visitor sees it, and keep one series per market. For shops that need several requests in a row from the same address, the session parameter keeps a sticky IP for 10 minutes.
Your own sites deserve a check too. Fetching your key landing pages from each market with render: "always" and screenshot: true shows what a visitor actually sees, and is a cheap way to catch a broken regional page before customers do.
Step 3: react when results arrive
When every job in the batch is done, Siftzo posts a batch.finished event to your webhook. Deliveries are signed with HMAC-SHA256 over the timestamp and the raw body, sent in the Siftzo-Signature header as t=…,v1=…. Verify it before you trust the payload, answer with a 2xx quickly, and do the work afterwards.
Delivery is at least once and retried for up to 24 hours, so deduplicate on event_id. Answering 410 Gone stops retries for a delivery. From there, compare with the previous run and alert only on changes that matter: a new domain in the top results, a new advertiser on your brand terms, a reseller price below your policy.
Doing it responsibly
Monitor public pages, at a frequency that matches how fast things change; daily is plenty for most brands. Do not collect personal data about reviewers or commenters; count and read mentions, do not profile people. A feed runs the checks on a schedule for you. See responsible use and pricing.
Try it on your own data
1,000 free credits every month, no card needed. Failed requests are never billed.
Questions
Can I see who is advertising on my brand name?
Yes. SERP responses include an ads array with each ad's position, placement, title and URL, so you can record advertisers for each branded query and market.
How do I know a batch has finished?
Pass webhook_url when you create the batch. Siftzo sends a signed batch.finished event when every job is done. You can also poll GET /v1/batch/{id}.
What if my webhook endpoint is down?
Siftzo retries failed deliveries for up to 24 hours. Each delivery keeps the same event_id, so deduplicate on it. You can also redeliver an event later.