Branded Search Reputation Snapshot

Convert captured branded search results into a structured inventory of owned assets, known profiles, review pages, news, social properties, neutral results, and visible reputation-risk terms. Every classification retains the result URL and human-readable evidence that produced it.

What you get

Each visible result becomes a dataset row with:

• brand query and result position;
• result URL and normalized domain;
• asset type: owned, known_profile, review, news, social, or organic;
• owned-asset flag;
• reputation signal classification;
• transparent positive, negative, mixed, or neutral keyword hint;
• visible-rating flag;
• reputation-risk flag and recommended action;
• source URL, issue code, evidence excerpt, scan time, and severity.

With includeReport enabled, the actor writes a Markdown summary, CSV export, issue JSON, evidence JSON, and run metadata to the default key-value store.

Input choices

Use serpHtmlInputs or htmlInputs for captured branded-result HTML. Each object should include query, sourceUrl, and html. The parser recognizes explicitly marked result cards and extracts their linked title, snippet, domain, result type, position, and visible rating.

You can also provide explicit public startUrls. Requests are restricted to the URLs you submit and may be constrained with allowedDomains. The actor does not expand the run by following links found in result cards.

Classification controls:

• brandQueries: query context associated with supplied snapshots.
• ownedDomains: domains classified as controlled assets.
• knownProfileDomains: expected third-party profile hosts.
• sentimentTerms.negative and .positive: visible keyword lists used as transparent hints.
• includeSerpFeatures: include or exclude cards explicitly marked as non-organic features.
• maxResultsPerQuery, maxBrands, maxQueries, maxSnapshots: bound accepted evidence and output.
• includeEvidence: include or suppress excerpts.
• includeRawSnapshots: opt in to capped source HTML storage.
• maxChargeUsd: stop before a paid event would exceed your ceiling.

Example input

{
  "brandQueries": ["junipr"],
  "serpHtmlInputs": [
    {
      "query": "junipr",
      "sourceUrl": "https://example.com/serp/junipr",
      "html": "<article class=\"serp-result\" data-rank=\"1\"><a href=\"https://junipr.io/\">junipr official SEO tools</a><p>Official evidence-backed automation.</p></article><article class=\"serp-result\" data-rank=\"2\"><a href=\"https://ratings.example/junipr\">junipr reviews</a><p>Trusted customer reviews rating 4.7</p></article><article class=\"serp-result\" data-rank=\"3\"><a href=\"https://complaints.example/junipr\">junipr complaint report</a><p>Customer complaint discussion.</p></article>"
    }
  ],
  "ownedDomains": ["junipr.io"],
  "knownProfileDomains": ["linkedin.com", "crunchbase.com"],
  "sentimentTerms": {
    "negative": ["complaint", "fraud", "lawsuit"],
    "positive": ["official", "trusted", "award"]
  },
  "includeSerpFeatures": true,
  "maxResultsPerQuery": 10,
  "maxBrands": 1,
  "maxQueries": 5,
  "maxSnapshots": 5,
  "includeReport": true,
  "maxChargeUsd": 35
}

Example output

{
  "recordType": "branded_search_reputation_snapshot",
  "recordName": "junipr official SEO tools",
  "issueCode": "branded_search_reputation_snapshot_ok",
  "severity": "low",
  "brandQuery": "junipr",
  "resultPosition": 1,
  "resultUrl": "https://junipr.io/",
  "resultDomain": "junipr.io",
  "assetType": "owned",
  "ownedAsset": true,
  "reputationSignal": "owned_result",
  "sentimentHint": "positive_keyword_hint",
  "reviewRatingVisible": false,
  "riskFlag": false,
  "recommendedAction": "Maintain this owned asset and monitor its position.",
  "sourceUrl": "https://example.com/serp/junipr",
  "scannedAt": "2026-07-10T12:00:00.000Z"
}

Classification semantics

Owned and known-profile classification is based on normalized hostnames you provide. Review classification uses visible review or rating language and common result patterns. News and social classification relies on visible text, explicit result type, or recognized social hosts. All remaining linked cards are retained as organic results.

Sentiment is intentionally described as a keyword hint. A negative-term match creates a risk flag because an analyst may need to inspect it, but the actor does not assert that the underlying claim is true. A positive-term match is likewise not an endorsement. Mixed positive and negative terms remain mixed. The result URL and excerpt are retained so decisions can be based on source evidence.

Empty HTML, unsupported layouts, and access-denied or challenge content produce diagnostics instead of reputation conclusions. Sponsored cards are excluded when they are explicitly marked in the supplied HTML.

Pay-per-event pricing

Platform usage pass-through is off. The actor charges before writing associated paid output.

Event	Price
actor-start	$0.0350
branded-query-snapshot-analyzed	$0.0115
reputation-signal-classified	$0.0115
reputation-risk-emitted	$0.0115
executive-report-generated	$0.4000

The default maximum charge is $35. Setting the ceiling to zero prevents paid processing and output.

Practical uses

• inventory owned assets visible for brand queries;
• track review, profile, news, and social-result coverage;
• flag result titles or snippets containing stated risk terms;
• compare branded-result composition across locations or dates;
• export a source-linked action list for reputation and communications teams.

Limits

The actor analyzes provided observations; it does not validate third-party claims, calculate a general sentiment score, or infer the reputation of a person or business. HTML support depends on visible linked result cards. Use consistent query, locale, device, and collection method for comparisons over time.