# Ameblo Email Scraper (`email_scraper/ameblo-email-scraper`) Actor

Ameblo Email Scraper extracts blogger contact emails from Ameba Blog (Ameblo) by keyword, helping brands find Japanese bloggers and influencers for outreach and collaborations.

- **URL**: https://apify.com/email_scraper/ameblo-email-scraper.md
- **Developed by:** [Email Scraper](https://apify.com/email_scraper) (community)
- **Stats:** 32 total users, 31 monthly users, 96.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### 🔍 Ameblo Email Scraper

**Ameblo Email Scraper** is an Apify actor built for one job: turning plain keywords into a clean list of public email addresses published on Ameblo (ameblo.jp). Instead of manually searching Google for "blogger site:ameblo.jp" over and over, the ameblo email scraper automates the entire search-and-extract workflow for you, page after page, keyword after keyword.

This ameblo email scraper is built for marketers, recruiters, sales teams, and growth hackers who need real, publicly available Ameblo contact emails for outreach — without touching Ameblo's own interface or breaking any login walls. Every email the ameblo email scraper returns comes from an indexed, publicly visible page that Google itself has already crawled.

If you've ever wondered how to find Ameblo email addresses at scale, this ameblo email scraper is the easiest way: give it a few keywords, pick the email domains you care about (Gmail, Yahoo, Outlook, or your own company domain), and let the ameblo email scraper do the searching.

### 🔹 Ameblo Email Scraper – Overview

At its core, the ameblo email scraper runs Google searches scoped to ameblo.jp using the `site:` search operator, combined with your chosen keywords and email domain suffixes. It then scans each search result snippet for a matching email pattern and keeps only unique, newly discovered addresses.

Every result the ameblo email scraper pushes to your dataset is tied back to the exact Ameblo page (or the closest resolvable link) where the email was found, along with the keyword that surfaced it and the snippet text surrounding it — so you always know the context behind every Ameblo lead.

Because the ameblo email scraper is keyword-driven rather than crawling the whole site, you stay in control of scope: narrow ameblo email scraper runs to a specific niche, job title, or product category, or run broad ameblo email scraper searches across many keyword and domain combinations in a single job.

### 🔹 Key Features

> **Key Features of this Ameblo Email Scraper**
>
> - 🔎 Keyword-driven search scoped to ameblo.jp using Google's `site:` operator
> - 📧 Automatic email-pattern extraction from search result snippets
> - 🌍 Optional location/region filter to localize ameblo email scraper results
> - 📬 Custom email domain suffix filtering (Gmail, Yahoo, Outlook, or your own domain)
> - 🚫 Exclude-words filter to automatically skip unwanted snippets (e.g. competitor names)
> - 🔁 Automatic de-duplication so the same email is never pushed twice in one run
> - ⏸️ Resumable runs — the ameblo email scraper remembers progress and continues where it left off
> - 📊 Incremental dataset pushes, so results are visible while the run is still in progress
> - ⚙️ Per keyword + domain result cap to control run size and cost precisely

### 🔍 Ameblo Email Scraper – What Data You Can Extract

The ameblo email scraper is purpose-built for one data type: public email addresses connected to Ameblo pages, plus the context needed to qualify each lead. This keeps the ameblo email scraper focused, fast, and genuinely useful for outreach rather than returning noisy, unrelated data.

> **Output / Data Fields**
> | Field | Description |
> |---|---|
> | `keyword` | The search keyword that produced this Ameblo result |
> | `title` | The page title of the matching search result |
> | `description` | The snippet text in which the email address was found |
> | `url` | The resolved link to the Ameblo-related result page |
> | `email` | The extracted, deduplicated email address |

Every row pushed by the ameblo email scraper includes the keyword and snippet alongside the Ameblo email, so you can immediately judge relevance before adding a contact to your outreach list — no separate lookup required.

### 🔹 Ameblo Email Scraper – How to Use It

Running the ameblo email scraper does not require any coding. Set a few input fields on the Apify Store page, start the run, and the ameblo email scraper handles pagination, retries, and deduplication automatically in the background.

#### 🔹 How It Works / Step-by-Step

1. **Enter keywords** — add one or more search terms relevant to the Ameblo contacts you want (for example, "blogger" or "influencer").
2. **Choose email domains** — pick the domain suffixes to match, such as `@gmail.com`, `@yahoo.com`, or a company domain.
3. **(Optional) Set a location** — narrow the ameblo email scraper search to a country or city.
4. **(Optional) Add exclude words** — skip snippets containing specific words or phrases.
5. **Set a max emails value** — cap how many addresses each keyword + domain pair should collect.
6. **Start the run** — the ameblo email scraper searches Google, extracts emails from Ameblo-related results, and pushes each new, unique lead straight to your dataset.

Because results are pushed incrementally, you can open the dataset while the ameblo email scraper run is still active and start working with the Ameblo leads that have already been found.

#### 🔍 How to Scrape Ameblo Emails by Keyword

To scrape Ameblo emails for a specific niche, enter one or more targeted keywords instead of a single broad term. The ameblo email scraper treats every keyword and domain suffix as its own search pair, so three keywords and two domains will run six independent ameblo email scraper searches in one job.

Narrower keywords tend to return more relevant Ameblo contacts, while broader keywords return more total volume at the cost of some noise. Most ameblo email scraper users mix a few broad and a few specific keywords in the same run to balance coverage and relevance.

#### 🔍 Can You Filter Ameblo Emails by Domain or Location?

Yes. The ameblo email scraper supports both an email-domain filter and an optional location filter. The domain filter restricts results to the suffixes you list (for example only `@gmail.com` addresses), while the location filter narrows the underlying Google search to a specific country or city.

Both filters are optional. Leaving the location field empty makes the ameblo email scraper search without any geographic restriction, which is useful when you want the widest possible pool of Ameblo leads.

### 🔹 Ameblo Email Scraper – Automation and Integration

Because the ameblo email scraper is a standard Apify actor, it fits directly into existing automation stacks. You can start a run from the Apify API, trigger it from a webhook, or schedule it to repeat automatically, feeding fresh Ameblo leads into a CRM, spreadsheet, or email tool over time.

> **Automation Highlights**
>
> - 🔗 Full Apify API support for starting and monitoring ameblo email scraper runs programmatically
> - ⏰ Native Apify scheduling for recurring ameblo email scraper jobs
> - 🔔 Apify webhooks to notify downstream systems the moment a run finishes
> - 📦 JSON, CSV, and Excel export for direct use in CRMs, spreadsheets, or mail-merge tools

### 🔍 Is the Ameblo Email Scraper Legal and Accurate?

The ameblo email scraper only collects email addresses that are already publicly visible in Google's search index for ameblo.jp — it does not log in to Ameblo, bypass any paywall, or access private account data. It simply automates a search that anyone could already run manually.

That said, as with any public email scraper, you remain responsible for using the Ameblo contacts you collect in compliance with applicable email marketing laws (such as CAN-SPAM or GDPR) in your own jurisdiction and the recipient's. The ameblo email scraper surfaces public data; how you use it is up to you.

### 🔹 Ameblo Email Scraper – Use Cases

> **Why Use This Actor**
>
> - 📈 **Sales prospecting** — build a list of Ameblo contacts to pitch a product or service
> - 🧑‍💼 **Recruiting outreach** — find Ameblo-connected professionals matching a role or skill
> - 🤝 **Partnership & influencer outreach** — identify Ameblo accounts worth contacting for collaborations
> - 📣 **Marketing & PR campaigns** — reach Ameblo-related audiences directly by email
> - 🧪 **Market research** — sample publicly listed Ameblo contacts for a given niche or region

Any workflow that starts with "I need real email addresses connected to Ameblo" is a good fit for this ameblo email scraper. Because every result is grounded in a real, indexed search snippet, the leads it returns are usable for genuine outreach rather than guesswork.

### 🔹 Input

> **Input Fields**
> | Field | Type | Description |
> |---|---|---|
> | `keywords` | array | One or more search keywords or queries to run the search for |
> | `location` | string | Optional country or city to narrow the search geographically |
> | `customDomains` | array | Email domain suffixes to match, e.g. `@gmail.com`, `@yahoo.com` |
> | `maxEmails` | integer | Maximum emails to collect **per keyword + domain combination** |
> | `excludeWords` | array | Words/phrases that, if found in a snippet, cause it to be skipped |

The `maxEmails` field is a per-combination cap, not a single run-wide total. With 3 keywords and 2 domains, a `maxEmails` value of 20 lets the ameblo email scraper collect up to 20 emails for *each* of the 6 keyword + domain pairs — up to 120 Ameblo emails in total for that run.

### 🔹 Output

Results from the ameblo email scraper are written to the Apify dataset as structured JSON rows, and can be exported directly from the Apify Store UI or API as JSON, CSV, or Excel. A sample row looks like this:

```json
{
  "keyword": "blogger",
  "title": "Example Ameblo result title",
  "description": "...snippet text containing the email...",
  "url": "https://ameblo.jp/example-page",
  "email": "example@gmail.com"
}
```

Because every ameblo email scraper row is deduplicated against previously seen emails in the same run, your dataset never contains the same Ameblo email twice, even across resumed runs.

### 🔹 Pricing

> **Pricing Notes**
>
> - Free-tier usage of this actor is capped at **100 emails per keyword + domain combination**.
> - Paid/upgraded usage removes this cap, limited only by the `maxEmails` value you set.
> - Results are billed per result pushed to your dataset, consistent with Apify's actor pricing model.

If a ameblo email scraper run on the free tier stops at 100 results for a keyword + domain pair, this is the free-tier limit, not an error — upgrading removes the ceiling so the ameblo email scraper can continue collecting up to your configured `maxEmails` value.

### 🔹 Tips and Best Practices

> **Tips / Important Notes**
>
> - Use 3–5 specific keywords rather than one generic term for better Ameblo coverage.
> - Add multiple email domain suffixes (`@gmail.com`, `@yahoo.com`, `@outlook.com`) to widen results.
> - Leave the location field empty for maximum reach, or set it for geo-targeted leads.
> - Use the exclude-words filter to automatically skip irrelevant or unwanted snippets.
> - Sparse results usually mean the ameblo email scraper search is too narrow — broaden keywords or domains.

The ameblo email scraper naturally slows down and stops once Google stops returning new, relevant Ameblo results for a given keyword and domain pair — this is expected behavior, not a bug. Broadening keywords or adding more domain suffixes is the most effective way to get more Ameblo leads from the ameblo email scraper.

### 🔹 Frequently Asked Questions

#### 🔍 What is the Ameblo Email Scraper?

The Ameblo Email Scraper is an Apify actor that searches Google for public email addresses connected to Ameblo (ameblo.jp) pages, based on the keywords and email domains you provide, then returns them as a structured, de-duplicated dataset.

#### 🔍 How do I use the Ameblo Email Scraper?

Enter one or more keywords, choose your target email domains, optionally set a location and exclude words, then start the run. The ameblo email scraper pushes new Ameblo leads to your dataset as it finds them.

#### 🔍 What data does the Ameblo Email Scraper return?

Each result includes the keyword used, the result's title and description snippet, the resolved Ameblo-related URL, and the extracted email address — giving you context for every lead the ameblo email scraper finds.

#### 🔍 Is there a limit on how many Ameblo emails I can collect?

Free-tier runs of the ameblo email scraper are capped at 100 emails per keyword + domain combination. Paid usage follows the `maxEmails` value you configure, with no additional platform-side cap.

#### 🔍 Can I run the Ameblo Email Scraper on a schedule?

Yes. Like any Apify actor, the ameblo email scraper can be triggered manually, via the Apify API, or on a recurring schedule using Apify's built-in scheduler, so you can keep your Ameblo lead list growing automatically over time.

#### 🔍 Does the Ameblo Email Scraper work without coding knowledge?

Yes. The ameblo email scraper is fully no-code: all configuration happens through simple input fields on the Apify Store page, and results are ready to download as JSON, CSV, or Excel once the run finishes.

### 🔹 Support

Questions about this ameblo email scraper, feature requests, or a bespoke build for a different site? Reach out any time.

- contact me by email : alphascraper69@gmail.com

# Actor input Schema

## `keywords` (type: `array`):

A list of keywords or queries to search for.

## `location` (type: `string`):

Optional country, state or city used to narrow the search. Leave it empty to search without a geographic filter.

## `customDomains` (type: `array`):

List of custom email domains

## `maxEmails` (type: `integer`):

How many addresses each search keyword + domain suffix combination may collect before the finder moves on to the next one. This is a per-combination target, not a run-wide total: with 3 keyword and 2 Domains and a limit of 20, the run works through all 6 combinations and aims for up to 20 addresses in each, so up to 120 overall. Lower values finish sooner and cost less; higher values dig deeper but never guarantee a fuller result, since the run can only find what is publicly listed.

## `excludeWords` (type: `array`):

Words or phrases you do not want to see.

## Actor input object example

```json
{
  "keywords": [
    "blogger",
    "influencer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ],
  "maxEmails": 5,
  "excludeWords": []
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "blogger",
        "influencer"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ],
    "excludeWords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("email_scraper/ameblo-email-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "blogger",
        "influencer",
    ],
    "location": "",
    "customDomains": ["@gmail.com"],
    "excludeWords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("email_scraper/ameblo-email-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "blogger",
    "influencer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ],
  "excludeWords": []
}' |
apify call email_scraper/ameblo-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,email_scraper/ameblo-email-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/XDPPtw4jrOvvWpQ7A/builds/U4VhP5Fn7CMzmYhND/openapi.json