Tabelog Scraper

Extract restaurant data from Tabelog (食べログ), Japan's largest restaurant review platform. Get names, ratings, review counts, genres, budgets, and images with advanced filtering options.

Features

• Comprehensive Restaurant Data - Scrape names, URLs, addresses, ratings, review counts, genres, dinner/lunch budgets, and images
• Advanced Filtering - Search by keyword (cuisine type, restaurant name) and area with full Japanese support
• Flexible Sorting - Sort results by highest rating or most reviews
• Pagination Support - Handle up to 500 results across multiple pages
• robots.txt Compliant - Respects Tabelog's crawling guidelines with 2+ second request intervals
• Lazy Loading Support - Automatically detects and extracts lazy-loaded images
• Reliable Data Extraction - Multiple CSS selector fallbacks ensure high extraction accuracy
• Structured Output - Clean JSON dataset with ISO 8601 timestamps

Use Cases

• Market Research: Analyze restaurant trends, ratings distribution, and popularity metrics across Japanese markets
• Restaurant Database: Build a comprehensive catalog of Japanese restaurants with ratings and reviews for discovery platforms
• Competitive Analysis: Monitor competitor restaurants in specific areas and compare ratings, pricing, and customer engagement
• Food Tourism: Create guides and recommendations based on Tabelog's verified ratings and reviews
• Business Intelligence: Track restaurant performance metrics, identify trending cuisines, and analyze regional preferences
• Data Journalism: Source restaurant market data for articles about Japan's dining scene
• Integration with CRM/Analytics: Feed restaurant data into Zapier, Google Sheets, or custom APIs for further analysis

Input

{
  "keyword": "ラーメン",
  "area": "東京",
  "maxResults": 50,
  "sortBy": "rating"
}

Input Parameters

Parameter	Type	Required	Default	Description
keyword	String	No	-	Search keyword (e.g., restaurant name or cuisine type like 'ラーメン', '寿司', 'イタリアン')
area	String	No	-	Area name in Japanese (e.g., '東京', '大阪', '渋谷'). Used to narrow search results by location.
maxResults	Integer	No	20	Maximum number of restaurants to fetch. Min: 1, Max: 500. Results are paginated (20 per page).
sortBy	String	No	rating	Sort order for results: rating (highest first) or review_count (most reviews first)

Output

Each restaurant record contains:

{
  "name": "ラーメン横丁 渋谷店",
  "url": "https://tabelog.com/tokyo/A1303/A130301/13012345/",
  "address": "東京都渋谷区渋谷1-2-3",
  "phoneNumber": null,
  "genre": "ラーメン",
  "rating": 3.58,
  "reviewCount": 247,
  "budgetDinner": "～1000円",
  "budgetLunch": "～800円",
  "imageUrl": "https://image.tabelog.com/...jpg",
  "scrapedAt": "2025-02-12T10:30:45.123Z"
}

Output Fields

Field	Type	Description
name	String	Restaurant name
url	String	Direct link to Tabelog restaurant page
address	String	Full address in Japanese
phoneNumber	String/Null	Phone number (typically null on search results pages)
genre	String	Cuisine type or restaurant category
rating	Number	Tabelog rating (typically 0-5 scale)
reviewCount	Number	Total number of customer reviews
budgetDinner	String	Typical dinner budget (e.g., '～2000円', '2000～3000円')
budgetLunch	String	Typical lunch budget (e.g., '～1000円')
imageUrl	String/Null	URL to restaurant photo/image
scrapedAt	String	ISO 8601 timestamp of when data was extracted

Pricing

$3 per 1,000 restaurants

Cost Examples

Results	Cost
50 restaurants	$0.15
100 restaurants	$0.30
500 restaurants	$1.50
1,000 restaurants	$3.00
5,000 restaurants	$15.00

Tips

1. Narrow Your Search - Combine keyword and area for more targeted results and lower costs. For example, searching for "ラーメン" (ramen) in "渋谷" returns only relevant results.

2. Start with Small Batches - Begin with maxResults: 50 to preview data before scaling to larger datasets.

3. Sort by Rating for Quality - Use sortBy: "rating" to get the most highly-rated restaurants first, useful for quality-focused research.

4. Sort by Reviews for Popularity - Use sortBy: "review_count" to identify the most popular/established restaurants with more customer feedback.

5. Use Area Codes Correctly - Area names should match Tabelog's area system (prefectures like '東京', '大阪' or specific districts like '渋谷', '新宿').

6. Plan for Pagination - Results are 20 per page. If you set maxResults: 100, the actor automatically crawls 5 pages. Plan execution time accordingly.

7. Image Handling - The actor detects lazy-loaded images. Some images may be null if not available on the search results page.

8. Extract URLs for Details - Use returned url fields to make follow-up API calls or manual visits to get additional details like full menus, opening hours, or full reviews.

Integrations

Export your restaurant data to multiple platforms:

• Google Sheets - Automatically sync results with Zapier
• Excel/CSV - Download dataset and import into spreadsheets
• Webhooks - Send data to custom APIs for real-time processing
• Direct API Access - Use Apify API to fetch results programmatically
• Zapier/Make - Build automation workflows with restaurant data
• Email - Receive results directly in your inbox
• Cloud Storage - Export to Google Drive, Dropbox, or AWS S3

Support

For issues, feature requests, or questions:

• Check the Apify Documentation
• Review Tabelog's Terms of Service before using at scale
• Open an issue on GitHub or contact Apify Support

Legal Note: This actor is provided for educational and research purposes. When using at scale, ensure compliance with Tabelog's Terms of Service and robots.txt guidelines. The actor respects these guidelines with built-in 2+ second request intervals.

License

Apache-2.0 License