Skip to main content
skill CX Codex

finding-industry-event-coverage-google — Claude Code skill

Searches Google for industry conference press and event recaps via Apify. Categorizes articles and extracts key announcement signals into structured tables.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add apidojo-io/apidojo-skills --skill finding-industry-event-coverage-google -a claude-code
Open on GitHub

What finding-industry-event-coverage-google does

This skill queries Google Search through Apify's apidojo/google-search-scraper actor to collect media coverage around conferences and trade shows. It extracts articles based on defined keywords, targeting specific countries like US and languages, while gathering article titles, source outlets, dates, and announcements.

The workflow classifies scraped articles into categories like ANNOUNCEMENT, KEYNOTE_RECAP, AWARDS, TREND_REPORT, or EDITORIAL. It evaluates each entry with an authority score based on publication tier (from 0.3 to 1.0) and recency weight, outputting a ranked markdown table.

Execution halts without a valid APIFY_TOKEN configured in your environment or .env file. You can run the scraper via the included scripts/run_actor.js, through the Apify MCP tool apify:run-actor, or via REST API.

What it helps with

  • track trade show coverage and press recaps on Google
  • identify product announcements made by competitors during summits
  • gather keynote quotes and summaries from industry sessions
  • rank event media mentions by publication tier and recency

Example prompts for the agent

  • Find press coverage and key announcements from CES 2026
  • Gather recap articles and speaker quotes from the latest FinTech Summit
  • Track news coverage for the upcoming cloud conference and classify the results

How to install finding-industry-event-coverage-google

1Skills CLI (Vercel)

npx skills add apidojo-io/apidojo-skills --skill finding-industry-event-coverage-google -a claude-code

2Manually: put the files in place

~/.claude/skills/finding-industry-event-coverage-google/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/finding-industry-event-coverage-google/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about finding-industry-event-coverage-google

How do I install finding-industry-event-coverage-google in Claude Code?

Run npx skills add apidojo-io/apidojo-skills --skill finding-industry-event-coverage-google -a claude-code.

What does finding-industry-event-coverage-google do?

It scrapes Google Search using Apify to locate articles about industry events. The skill groups links by content type and scores them based on publication authority and recency.

What are the prerequisites for this skill?

You must set the APIFY_TOKEN environment variable in your system or .env file. An Apify MCP server can also be connected as an alternative execution method.

Source text

SKILL.md · Apache-2.0
---
name: finding-industry-event-coverage-google
description: >
  Finds industry event and conference coverage on Google using apidojo's Google Search scraper. Triggers when the user asks to: find coverage of an industry conference or event on Google, track press coverage of a trade show or summit, research what was announced at a conference, find news and recaps of an industry event, discover what happened at a recent trade show, find speaker quotes or session summaries from a conference, or compile event coverage for competitive intelligence.
  Returns article list with title, publication, date, coverage type, and key announcement signals.
  Ideal for industry analysts, competitive intelligence teams, PR professionals, and event marketers.
license: Apache-2.0
metadata:
  author: apidojo
  version: "1.0"
  apify-actor: apidojo/google-search-scraper
---

# Finding Industry Event Coverage Google

Executes finding industry event coverage google using apidojo scrapers. Part of the apidojo intelligence skills library.

## Prerequisites

- `APIFY_TOKEN` environment variable set
- Optional: Apify MCP server installed

## Inputs

| Parameter | Type | Required | Default | Notes |
|-----------|------|----------|---------|-------|
| `startUrls` | array | Optional | `[]` | Google search URLs |
| `searchTerms` | array | Optional | `[]` | Keywords to search on Google |
| `countryCode` | string | Optional | `US` | Country for Google search (e.g. `US`, `GB`, `TR`) |
| `languageCode` | string | Optional | — | Language for results (e.g. `en`) |
| `maxItems` | number | Optional | Unlimited | Maximum results to return across all queries |
| `maxPagesPerQuery` | integer | Optional | `1` | Maximum result pages per query |
| `mobileResults` | boolean | Optional | `false` | Fetch mobile SERP layout |
| `customMapFunction` | string | Optional | — | JavaScript function to transform each output object |

## Workflow

```
Progress:
- [ ] Step 1: Define parameters
- [ ] Step 2: Run google-search-scraper
- [ ] Step 3: Filter and classify results
- [ ] Step 4: Score by quality and relevance
- [ ] Step 5: Deliver output
```

### Step 2: Run the Actor


**Recommended — run_actor.js (handles waiting, output, and file saving automatically):**
```bash
# Quick answer (prints table to chat)
node scripts/run_actor.js \
  --actor "apidojo~google-search-scraper" \
  --input '{"param": "value"}'

# Save as CSV
node scripts/run_actor.js \
  --actor "apidojo~google-search-scraper" \
  --input '{"param": "value"}' \
  --output YYYY-MM-DD_results.csv --format csv

# Save as JSON
node scripts/run_actor.js \
  --actor "apidojo~google-search-scraper" \
  --input '{"param": "value"}' \
  --output YYYY-MM-DD_results.json --format json
```
> `APIFY_TOKEN` must be set in environment or `.env` file.

**If Apify MCP is available:**
```
Tool: apify:run-actor
Actor: "apidojo~google-search-scraper"
Input:
{
  "searchTerms": ["[EVENT_NAME] 2026", "[EVENT_NAME] recap", "[EVENT_NAME] announcements", "[EVENT_NAME] highlights"],
  "maxItems": 100
}
```

**REST API fallback:**
```bash
curl -X POST \
  "https://api.apify.com/v2/acts/apidojo~google-search-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchTerms": ["[EVENT_NAME] 2026", "[EVENT_NAME] recap", "[EVENT_NAME] announcements", "[EVENT_NAME] highlights"], "maxItems": 100}'
```

Wait for `SUCCEEDED`. Fetch dataset:
```bash
curl "https://api.apify.com/v2/actor-runs/$RUN_ID/dataset/items?token=$APIFY_TOKEN"
```

### Step 3: Classify Results

```
classification: ANNOUNCEMENT (new product/feature) | KEYNOTE_RECAP (event summary) | AWARDS (industry recognition) | TREND_REPORT (analyst take) | EDITORIAL (opinion)
```

### Step 4: Score Each Result

```
score = coverage_authority = (publication_tier: tier1=1, tier2=0.6, tier3=0.3) * article_recency_weight
```

### Step 5: Edge Cases

- **Event may have a different official name vs. common name — try both; also search the hosting organization name if event name is ambiguous**

Additional fallbacks:
- **< 20 results**: Broaden search terms; remove secondary filters
- **No results**: Verify the search terms are correct; try alternate phrasings
- **Data quality issues**: Remove entries with missing key fields; note count in output

## Output Format

```
# Finding Industry Event Coverage Google
Results: [N] | Date: [DATE]

| # | [Key Field] | [Metric 1] | [Metric 2] | [Classification] | [Score] |
|---|------------|-----------|-----------|-----------------|---------|
| 1 | [value] | [value] | [value] | [type] | [0.XX] |

## Summary
Top result: [description]
Key finding: [insight]
```

## Troubleshooting

**Too few results:** Broaden the primary search term; remove restrictive filters.
**Low quality results:** Apply minimum score threshold (≥ 0.50) to filter noise.
**Actor fails to run:** Verify API key; check actor status at apify.com/apidojo.

© apidojo · Apache-2.0 · apidojo-io/apidojo-skills

Similar skills

All skills for Browser and scraping →

From the same set96

scraping-instagram-location-content Pulls public Instagram posts tagged at one place and returns post URLs, captions, handles, likes and dates. Useful when you want to see what visitors post about a venue. CX Codex +1 810installs scraping-instagram-profile-data Collect Instagram profile stats and recent post metrics through an Apify scraper. Use it to check a set of accounts or export profile details. CX Codex +1 806installs discovering-brand-ambassadors-across-platforms Finds prospective brand ambassadors across Instagram, TikTok, and Twitter using Apify scrapers. Calculates combined reach and groups creators into tiers. CX Codex +1 804installs extracting-google-paa-questions-for-seo Pulls Google People Also Ask questions for SEO planning, then sorts them by intent and turns the findings into a usable content outline. CX Codex +1 804installs scraping-tweets-from-account This skill pulls tweets, replies and media from a public Twitter/X account through apidojo's tweet scraper on Apify. Handy when you need a dataset for someone else's profile. CX Codex +1 802installs analyzing-youtube-competitor-channel-strategy This skill examines a competitor’s YouTube strategy, video mix, publishing rhythm, and engagement. Use it when a channel benchmark needs data behind it. CX Codex +1 800installs scraping-tiktok-user-data Scrapes a TikTok creator's video history and engagement metrics through Apify. Built for auditing competitor feeds and collecting view counts or comments. CX Codex +1 799installs monitoring-instagram-brand-mentions Collects public Instagram posts that mention a brand through hashtags, tags, or product names. Useful for review, complaint, and user-generated content analysis. CX Codex +1 797installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor