Tabelog Japan Restaurant Scraper
Pricing
from $2.10 / 1,000 results
Tabelog Japan Restaurant Scraper
Scrape Tabelog (食べログ) restaurants by prefecture or all of Japan, keyword, search link or restaurant link: ratings, cuisine, budgets, station, awards, photos. Add address, phone, hours, coordinates and info rows, or reviews with category scores, spend and full text (Tabelog's English translation).
Pricing
from $2.10 / 1,000 results
Rating
0.0
(0)
Developer
Piquno
Maintained by CommunityActor stats
2
Bookmarked
29
Total users
3
Monthly active users
4 days ago
Last modified
Categories
Features
Share
Scrape restaurants and reviews from Tabelog (食べログ), the Japanese restaurant guide and review site, through its English site. Search by prefecture or all of Japan and keyword, paste Tabelog search links, or paste restaurant links from the English or the Japanese site.
Every restaurant row has the rating, review count, cuisine, nearest station, dinner and lunch budget, award badges and photos. Turn on detail pages to add the address, phone, opening hours, seats, payment methods, coordinates, postal code, Japanese name, full award history and the restaurant's information rows (service charge, private rooms, smoking, parking, website and more). Turn on reviews to get one row per review: reviewer, score, visit month, a review ID and a text preview, plus the five category scores, spend per person and photos when the reviewer gave them, or the full review text with one more switch. Review text is Tabelog's English machine translation of the Japanese original.
No API key, Tabelog account or proxy needed. For scale: Tabelog's English site lists 139,551 restaurants in Tokyo and 72,876 in Osaka (searches of 12 November 2026).
How to use it
- Open the Actor in Apify Console.
- Pick an Area (one of the 47 prefectures, or All Japan) and, if you like, a Keyword (寿司, ramen, a restaurant name) and Sort By. Or paste links into Start URLs instead (see the examples below).
- Set Max Results, the number of restaurants (up to 1,200 per run).
- Tick Include Detail Pages for the restaurant-page fields, and Include individual reviews for review rows. Then set Max reviews per restaurant and, if you want them, the review filters.
- Press Start. The run's status message shows progress while it works and, at the end, what was saved and anything that went wrong.
- Open the Output tab. The Overview, Restaurants and Reviews views show the rows as tables; export them as JSON, CSV, Excel and other formats, or read them through the Apify API.
Start with a Max Results of 10 or 20 to check the fields you need, then scale up. To repeat a run, schedule it in Apify Console or start it through the API.
Input examples
Search by area and keyword
{"area": "tokyo","keyword": "寿司","sort": "highest_rated","maxResults": 100,"includeDetails": true}
The 100 highest-rated sushi restaurants in Tokyo, each with its detail page: 100 rows in about 6 minutes. Use "area": "all" to search all of Japan.
A Tabelog search link
{"startUrls": [{ "url": "https://tabelog.com/en/kyoto/rstLst/?SrtT=rt" }],"maxResults": 40}
Set up a search on tabelog.com/en (area, station, genre, filters), copy the address from the first page of results and paste it here. The Actor turns the pages itself. Area, Keyword and Sort By are ignored when Start URLs are given.
Restaurant links
{"startUrls": [{ "url": "https://tabelog.com/en/tokyo/A1308/A130802/13015251/" },{ "url": "https://tabelog.com/tokyo/A1301/A130101/13300481/dtlrvwlst/" }],"includeDetails": true}
Each restaurant link gives one row. Any page of a restaurant works (its review list here), and so does a link from Tabelog's Japanese site: the second link is read as https://tabelog.com/en/tokyo/A1301/A130101/13300481/. With details on, the details come from the same page, so they add no time. This exact input took 5.7 s on 12 November 2026.
Reviews with filters
{"startUrls": [{ "url": "https://tabelog.com/en/tokyo/A1306/A130602/13042979/" }],"includeReviews": true,"maxReviewsPerRestaurant": 100,"reviewOrder": "newest_visit","reviewVisitedSince": "2026-11","minReviewRating": 4,"includeFullReviewText": true}
Reviews of visits in November 2026 or later, rated 4 or more, newest visit first, with their full text. In a run with the same filters on 12 November 2026, the first page of 20 reviews held 5 that matched; the Actor stopped there because the rest were older visits, saved 6 rows (the restaurant and 5 reviews) and did not save or bill the 15 that did not match.
Input options
| Option | API name | Default | What it does |
|---|---|---|---|
| Start URLs | startUrls | none | Tabelog search links and/or restaurant links (details below). Overrides Area, Keyword and Sort By. |
| Area (Prefecture) | area | tokyo | One of the 47 prefectures, or all for all of Japan |
| Keyword | keyword | empty | Cuisine, dish or restaurant name, in Japanese or English |
| Sort By | sort | highest_rated | highest_rated, most_reserved_travelers, most_reserved_locals, most_viewed. most_reviews is kept for old inputs: Tabelog's English site no longer sorts by review count, so it returns the Most Reserved (Travelers) order. |
| Max Results | maxResults | 100 | 1-1,200 restaurants per run, in total across all Start URLs. Review rows come on top. |
| Include Detail Pages | includeDetails | off | Opens each restaurant's own page for the detail fields |
| Include individual reviews | includeReviews | off | One row per review |
| Max reviews per restaurant | maxReviewsPerRestaurant | 20 | 1-1,200 |
| Include full review text | includeFullReviewText | off | Opens each review's own page and adds reviewTextFull. Adds time, not rows. |
| Dinner or lunch reviews | reviewMealTime | all | all, dinner or lunch, using Tabelog's own Dinner reviews and Lunch reviews lists |
| Review order | reviewOrder | default | default (Tabelog's order) or newest_visit (Tabelog's Sort by visit month). Tabelog's English site cannot sort reviews by rating. |
| Visited since (YYYY-MM) | reviewVisitedSince | empty | Only visits in this month or later. Reviews that show no visit month are left out when this is set. |
| Minimum review rating | minReviewRating | empty | Only reviews rated at least this, for example 4 or 3.5. Unrated reviews are left out when this is set. |
| Only reviews with photos | onlyReviewsWithPhotos | off | Only reviews that show at least one photo |
| Max review pages per restaurant (with filters) | maxReviewPagesPerRestaurant | 10 | With Visited since, Minimum review rating or Only reviews with photos set, at most this many review pages (20 reviews each) are read per restaurant, 1-60 |
| Proxy | proxyConfiguration | off | Turn on Apify Proxy only if the status message or the log shows blocked or empty pages |
Start URLs in more detail:
- Search pages on tabelog.com/en keep the filters you set on the site. The Actor reads them 20 restaurants per page, up to Tabelog's 60 pages. Copy the link from the first page of results: a link to a later page (
.../rstLst/2/...) gives only that page's 20 restaurants. - Restaurant pages: any page of a restaurant (its top page, review list or a single review) counts as that restaurant. Each gives one row and counts towards Max Results; details and reviews follow your settings. A restaurant pasted twice is saved once.
- Links from Tabelog's Japanese site (
tabelog.com/tokyo/...) are read on the English site. Restaurant links always work. Search links work when they are an area, station or genre-code search without a keyword or other search options (the ranking orderSrtT=rtis fine); they are read from their first page. Japanese keyword searches and genre names such as/rstLst/sushi/are skipped with a note: use Area and Keyword instead, or open the search on tabelog.com/en and paste that link. - Paste each link whole, with its
https://: Apify refuses a link without it before the run starts. - Links that are skipped or refused are reported at the end: the first three by name in the status message, the rest counted there and all of them in the log.
Review filters: Dinner or lunch reviews and Review order use Tabelog's own lists. Tabelog's Dinner or Lunch list can still include reviews with another meal time. The Actor leaves those out (not saved, not billed) and reads on, so it can need more pages. Visited since, Minimum review rating and Only reviews with photos are checked by the Actor on each review it reads. A review that does not match is never saved and never billed, and its full text is never fetched; Max reviews per restaurant counts matching reviews only. With Review order newest_visit and Visited since together, the Actor stops reading a restaurant's reviews at the first older visit. With every review option at its default, the Actor requests exactly the same pages as earlier versions.
Output
Restaurants and reviews go into one dataset. recordType says which is which, and restaurantId joins a review to its restaurant. The Restaurants and Reviews views in the Output tab show each kind with its own columns.
Restaurant rows
On every restaurant row (read from the search results):
| Field | What it holds |
|---|---|
| recordType | restaurant |
| name, url, restaurantId | Restaurant name (English), its page on tabelog.com/en and Tabelog's ID |
| rating | Tabelog score, 0-5 |
| reviewCount | Number of reviews Tabelog shows |
| nearestStation | Station and walking distance, for example "Tottori Sta. 446m" |
| genre | Cuisine, for example "Sushi, Fugu (Pufferfish), Crab" |
| dinnerBudget, lunchBudget | Average spend per person; null when not listed |
| closedDays | Regular closing days ("-" means not listed) |
| features | Tags such as "Credit card accepted", "Non smoking", "Children welcome" |
| awards | Current Tabelog Award and "Tabelog 100" badges |
| images | Up to 5 photo links |
| scrapedAt | When the row was saved (UTC) |
| searchArea, searchKeyword | Your Area (null with Start URLs) and Keyword |
| detailsScraped | true when the detail page was read, false when details were on but the page failed, null when details are off |
| prefecture | The prefecture in the restaurant's link, written like the Area input ("tokyo"), in every mode |
For a restaurant link in Start URLs these come from the restaurant's own page: nearestStation is the station's name without the distance, closedDays is null when the page lists none, features is null (only search results show those tags) and images are the photos at the top of the page.
With Include Detail Pages on. Measured fill is the number of restaurants that had the field, out of 42 read in November 2026 (top-rated restaurants in Osaka, Kyoto and Fukuoka plus two Tokyo restaurant links; ordinary restaurants may show less):
| Field | What it holds | Filled |
|---|---|---|
| addressClean | Address in Japanese, for example "大阪府大阪市中央区内久宝寺町2-7-14" | 42 |
| address | The same address followed by the page's map-button text ("Show larger mapFind nearby restaurants"), kept as earlier versions wrote it | 42 |
| phone | Phone number; empty when the restaurant does not publish one | 39 |
| businessHours | Opening hours and notes | 42 |
| transportation | Directions from the nearest station | 42 |
| detailGenre | Full category list | 42 |
| paymentMethods | Cards, electronic money and QR payments | 42 |
| reservationInfo | Reservation rules | 42 |
| seats | Number of seats as shown, for example "8 seats ( counter only)" | 42 |
| description | The restaurant's own description | 0 (rare) |
| latitude, longitude | Coordinates from the page's structured data | 42 |
| postalCode | 7 digits, no hyphen, for example "5400013" | 42 |
| nameJapanese | Japanese name, for example "鮨 三心" | 42 |
| mainPhotoUrl | Main photo (640 x 640 on 32 of the 42, 320 x 320 on the rest) | 42 |
| awardHistory | Every Tabelog Award and "Tabelog 100" selection, newest Tabelog Award first; [] when none | 34 |
| dinnerAveragePrice, lunchAveragePrice | Price per person as given by the restaurant | 37, 22 |
| dinnerAveragePriceFromReviews, lunchAveragePriceFromReviews | Spend per person reported by reviewers | 42, 27 |
| serviceCharge | Service charge and fees | 23 |
| maximumPartySize | Largest group the restaurant takes | 8 |
| privateRooms, privateUse | Private rooms, and whether the whole restaurant can be booked | 42, 41 |
| smokingPolicy | Smoking rules (Tabelog's general note on the 2020 smoking law is left out) | 42 |
| parking | Parking | 41 |
| spaceAndFacilities | For example "Stylish space, Relaxing space, Spacious seating, Counter seating" | 35 |
| drinks | For example "Particular about Sake (Nihonshu)" | 36 |
| foodFeatures | For example "Particular about fish" | 22 |
| occasions | For example "Family friendly, Business" | 26 |
| locationFeatures | For example "Hideout, A house restaurant" | 28 |
| website | The restaurant's website, when the page lists one | 14 |
| openingDate | Opening date as written, for example "2016.11.1" | 25 |
| remarks | The restaurant's remarks | 19 |
The fields from addressClean to description are left out of the row when the page does not show them; the fields from latitude on are always there in detail mode, null (or []) when the page does not show them. Where Tabelog machine-translated an information row, the restaurant's own Japanese wording follows in brackets, because the translation can be wrong: "Service charge 10% (Original: サービス料10%)". This was on 11 of the 23 service charges.
Review rows
With Include individual reviews on, each review is its own row (recordType: "review"). Measured fill is on 640 reviews of two Tottori sushi restaurants (12 November 2026):
| Field | What it holds | Filled |
|---|---|---|
| restaurantId, restaurantName, restaurantUrl | The restaurant the review belongs to | 100% |
| reviewerName, reviewerUrl | Reviewer and their Tabelog profile. The name can have the reviewer's home area glued on, for example "トモサクTokyo" | 100% |
| reviewerArea | That home area on its own, for example "Tokyo" | 37% |
| reviewerPostCount, reviewerFollowers | How many reviews the reviewer has posted, and their followers | 100%, 98% |
| reviewRating | The reviewer's overall score; null when unrated | 95% |
| reviewMealTime | What the score is for: dinner or lunch on almost every review, sometimes takeout or Etc; null on some unrated reviews | 98% |
| reviewVisitPeriod, reviewVisitCount | Visit month, for example "December 2025", and how many times they have visited | 97%, 100% |
| reviewTitle | Title; null when the review has none | 49% |
| reviewUrl | Link to the review; null when it has no title (use reviewPageUrl) | 49% |
| reviewText | Preview of the text, about the first 100 characters; null for reviews without text | 84% |
| scrapedAt | When the row was saved (UTC) | 100% |
| reviewTextFull | Only with Include full review text on: the complete text, line breaks kept; null if its page could not be read | |
| reviewId | Tabelog's ID of this review, unique per row: use it to remove duplicates across runs | every review checked (124) |
| reviewPageId, reviewPageUrl | The review's own page, on every review. It holds all of one reviewer's visits to the restaurant, so a regular's rows share it | 100% |
| reviewSpendPerPerson | Spend per person as a price band, for example "JPY 10,000~JPY 14,999" | 60% |
| reviewScoreFood, reviewScoreService, reviewScoreAtmosphere, reviewScoreCostPerformance, reviewScoreDrinks | The five category scores, 1-5, when the reviewer gave them | about 39% (drinks 20%) |
| reviewPhotos | Links to the review's photos shown in the review list (640 x 640, usually up to 3); [] when none | 91% |
| reviewUpdatePeriod | Month an older review was updated ("ー Visited on (June, 2023 Update)"); those reviews show no visit month | 3% |
Fill varies by restaurant: on 60 reviews of a popular Tokyo yakiniku restaurant, the category scores were on 13 and the spend on 33.
Column order
In each JSON row, fields added in later versions come after the older ones: on restaurant rows detailsScraped, addressClean, seats, the detail fields from latitude to remarks, and prefecture; on review rows reviewerArea, reviewTextFull and the fields from reviewId to reviewUpdatePeriod. In CSV and Excel exports, read columns by their name, not their position: Apify's CSV export orders columns alphabetically, or by the view's column list when you export a view, so a new field can move columns there.
Example output
A restaurant row from a search (Tottori, keyword "sushi"; images shortened to one link):
{"name": "Sasa Sushi","url": "https://tabelog.com/en/tottori/A3101/A310101/31000904/","restaurantId": "31000904","rating": 3.69,"reviewCount": 103,"nearestStation": "Tottori Sta. 446m","genre": "Sushi, Fugu (Pufferfish), Crab","dinnerBudget": "JPY 10,000 - JPY 14,999","lunchBudget": null,"closedDays": "Sunday","features": ["Credit card accepted", "Non smoking", "Wi-Fi available", "Children welcome", "Vegetarian options"],"awards": [],"images": ["https://tblg.k-img.com/restaurant/images/Rvw/4009/320x320_square_4009982.jpg"],"recordType": "restaurant","scrapedAt": "2026-11-12T15:30:53.584994+00:00","searchArea": "tottori","searchKeyword": "sushi","detailsScraped": null,"prefecture": "tottori"}
Some of the fields Include Detail Pages adds, from another restaurant's row (Sushi Sanshin, Osaka; a selection, with the award history cut to three of its nine entries):
{"phone": "06-6767-0677","addressClean": "大阪府大阪市中央区内久宝寺町2-7-14","seats": "8 seats ( counter only)","detailsScraped": true,"latitude": 34.6781569580002,"longitude": 135.51829250723029,"postalCode": "5400013","nameJapanese": "鮨 三心","awardHistory": ["The Tabelog Award 2026 Gold winner","The Tabelog Award 2025 Gold winner","The Tabelog Award 2024 Gold winner"],"lunchAveragePrice": "JPY 30,000 - JPY 39,999","dinnerAveragePriceFromReviews": "JPY 40,000 - JPY 49,999","privateRooms": "Unavailable","smokingPolicy": "Non smoking","parking": "Unavailable Coin parking available nearby","website": "https://sushisanshin.com/","openingDate": "2016.11.1"}
A review row (reviewPhotos shortened to one of its three links):
{"recordType": "review","restaurantId": "31000904","restaurantName": "Sasa Sushi","restaurantUrl": "https://tabelog.com/en/tottori/A3101/A310101/31000904/","reviewerName": "ごはん太郎丸","reviewerUrl": "https://tabelog.com/rvwr/014142560/","reviewerPostCount": 911,"reviewerFollowers": 1895,"reviewRating": 3.8,"reviewMealTime": "dinner","reviewVisitPeriod": "December 2025","reviewVisitCount": 1,"reviewTitle": "A locally-focused sushi restaurant","reviewUrl": "https://tabelog.com/en/tottori/A3101/A310101/31000904/dtlrvwlst/B519610170/?smp=0&use_type=0","reviewText": "Since I came to Tottori, I wanted to eat sushi. So, I made a reservation at this local gem that seem...","scrapedAt": "2026-11-12T15:30:58.240592+00:00","reviewerArea": null,"reviewId": "223869066","reviewPageId": "B519610170","reviewPageUrl": "https://tabelog.com/en/tottori/A3101/A310101/31000904/dtlrvwlst/B519610170/","reviewSpendPerPerson": "JPY 10,000~JPY 14,999","reviewScoreFood": 4,"reviewScoreService": 3.6,"reviewScoreAtmosphere": 3.6,"reviewScoreCostPerformance": 3.6,"reviewScoreDrinks": 3.6,"reviewPhotos": ["https://tblg.k-img.com/restaurant/images/Rvw/335666/640x640_rect_0dcd835e354d27dd88e6ad33b02d2b4d.jpg"],"reviewUpdatePeriod": null}
With Include full review text on, reviewTextFull comes right after reviewerArea.
What it costs
You pay per row saved, and restaurant rows and review rows cost the same. Prices depend on your Apify plan:
| Apify plan | Per row | 1,000 rows |
|---|---|---|
| Free | $0.0025 | $2.50 |
| Bronze | $0.0024 | $2.40 |
| Silver | $0.00225 | $2.25 |
| Gold and above | $0.0021 | $2.10 |
Plus Apify's start fee of $0.00005 per GB of run memory, once per run. On the Free plan:
| Run | Rows | Cost |
|---|---|---|
| 100 restaurants, search results only | 100 | $0.25 |
| 100 restaurants with detail pages | 100 | $0.25 |
| 100 restaurant links | 100 | $0.25 |
| 100 restaurants with up to 20 reviews each | up to 2,100 | up to $5.25 |
| 1,000 reviews (50 restaurants x 20) | 1,050 | $2.63 |
| Full review text | no extra rows | no extra cost |
Detail pages and full review text take longer but add no rows. Reviews your filters leave out are not saved and not billed. A restaurant that appears twice in one run is saved once.
How long it takes
Measured on Apify runs at 1024 MB of memory in November 2026. The Actor sends one request at a time with 2.5 s pauses, so time grows with the number of pages:
| Run | Per restaurant | 100 restaurants |
|---|---|---|
| Search results only | about 0.2 s | about 25 seconds (54-57 s in 3 of 11 runs) |
| With detail pages | about 3.4 s | about 6 minutes |
| With detail pages + 20 reviews | about 8 s | about 13-14 minutes |
| With detail pages + 20 reviews + full review text | about 70-100 s | about 2-3 hours |
The first two rows are measured (100-restaurant and 10-restaurant runs); the last two add up the measured parts: each page of 20 reviews took 4.3-4.8 s and each full review text 3.2-4.6 s. A restaurant link takes about 3.4 s, with or without details.
The default run timeout is 1 hour. That fits roughly 1,000 restaurants with detail pages; for more, or for big review runs, raise the timeout in the run options. If the timeout comes near, the Actor stops about a minute before it, keeps everything saved, and says so in the status message.
FAQ
What does a run cost? The number of rows times the price for your plan, plus the start fee (see the tables above). Rows are saved as the run goes, so you can see the count growing in the status message.
How many restaurants can I get from one search? At most 1,200: Tabelog's English site serves 60 pages of 20 restaurants per search, so a Tokyo search without a keyword gives the first 1,200 of its 139,551 restaurants in the order you chose. Max Results is also capped at 1,200 per run, across all Start URLs. For more, run several narrower searches (a keyword, a smaller area, or search links for single areas or stations). Reviews have the same limit: up to 1,200 per restaurant (60 pages of 20).
Why do I get more review rows than the restaurant's review count? The Actor saves one row per visit, and a regular's visits are separate reviews on Tabelog (each with its own reviewId, sharing one reviewPageId). Sasa Sushi showed 103 reviews and gave 132 review rows; another Tottori restaurant showed 440 and gave 508. Max reviews per restaurant counts rows.
How do I get only recent reviews? Set Review order to newest_visit and Visited since to a month, for example 2026-06. The Actor reads newest visits first and stops at the first older one, so you pay only for the matching reviews. Add Minimum review rating or Dinner or lunch reviews to narrow it further.
Does it remember what an earlier run returned? No. Each run starts fresh. For scheduled runs, remove reviews you already have with reviewId and restaurants with restaurantId.
What happens when my maximum cost per run is reached? The Actor stops as soon as no more rows fit, instead of loading pages it could not deliver. Everything saved so far is kept, and the status message says how many restaurants and reviews were saved and that the maximum cost was reached. It also never reads more reviews than the remaining cost allows.
Can I paste links from Tabelog's Japanese site? Restaurant links, yes. Search links only without a keyword or other search options; the others are skipped with a note (see Start URLs above). Either way the Actor reads the page on tabelog.com/en: Tabelog's Japanese site refused requests from Apify's servers when we tested it in November 2026, and the Actor does not try to get past that.
Is the data in English or Japanese? Restaurant names, labels, hours, budgets and categories are in English, the address is in Japanese, and nameJapanese gives the Japanese name in detail mode. Review titles and text come from Tabelog's English pages, so most review text is Tabelog's machine translation; the original Japanese review text is not on those pages. Where Tabelog machine-translated a restaurant's information row, the restaurant's own Japanese wording follows in brackets. It is worth reading: one Osaka restaurant's English service-charge row said a service charge would be added, while its Japanese original said 無し (none).
Why is a field empty?
- Detail fields need Include Detail Pages, and many exist only when the restaurant filled them in (see the fill counts above).
phoneis empty when the restaurant does not publish its number. detailsScraped: falsemeans the detail page could not be read during the run. The row keeps its other fields, is still saved and billed, and the status message counts these rows.featuresisnullfor restaurant links: only search results show those tags.reviewUrlisnullfor reviews without a title;reviewPageUrlis always there.reviewTextisnullfor reviews without text;reviewRatingisnullfor unrated ones.reviewVisitPeriodisnullon older reviews that show only an update month (reviewUpdatePeriod).- The category scores and
reviewSpendPerPersonare there only when the reviewer gave them.
Why did my run fail? A run that saves nothing ends FAILED with the reason in its status message: for example every Start URL was skipped, an input value is not valid, or Tabelog refused 8 pages in a row (then try turning on Apify Proxy). A search that Tabelog itself says has no results ends SUCCEEDED with no rows and a message saying so. Busy answers and network errors are retried twice, after 2 and 5 seconds.
Known limitations
- Data comes from Tabelog's English site: names and labels in English, addresses in Japanese, review text mostly machine-translated. Original Japanese review text is not available.
- At most 1,200 restaurants per search and per run, and 1,200 reviews per restaurant.
- Rows from restaurant links have no
features, and theirnearestStationhas no walking distance. - Japanese-site search links with a keyword or other search options are skipped, and an English search link copied from a later page (
.../rstLst/2/...) gives only that page. - When a search-result card has no station line,
nearestStationholds the cuisine andgenreis empty (11 of 268 restaurants in our November 2026 runs). addressends with the map buttons' text; useaddressCleanfor the address alone.searchKeywordshows the Keyword box even when Start URLs are used (the keyword is then ignored).- Tabelog's English site no longer sorts restaurants by review count, and it does not sort reviews by rating.
Use cases
- Market research: restaurant density, ratings and price levels by area and cuisine
- Travel apps: restaurant databases for Japan trip planning, with English names, coordinates and opening hours
- Food analytics: top-rated cuisines, pricing patterns, regional specialties, award history
- Review analysis: overall and category scores, spend per person and visit months over time
- Location intelligence: map restaurants by coordinates (detail mode), station and prefecture
- Competitive analysis: compare restaurants by rating, review volume and budget range
Compliance
This Actor follows Tabelog's robots.txt: search pages, restaurant pages and review pages are open to crawlers. It sends one request at a time and pauses 2.5 seconds between most requests. A restaurant's first request (its detail or review page) can follow a search page, or a restaurant with no reviews, without that pause. A request that fails on a network error or gets a busy answer (HTTP 429 or 5xx) is retried after a 2 and then a 5 second pause; a refusal (such as HTTP 403) is not retried, and 8 refused or failed pages in a row stop the run.
Legal
This is an unofficial tool, not affiliated with Tabelog or Kakaku.com, Inc. It reads public pages of Tabelog's English site without logging in. You are responsible for using the data in line with Tabelog's terms of use and applicable law, including Japan's Act on the Protection of Personal Information and, where it applies, the GDPR. Review rows hold reviewer names, profile links and home areas, which can be personal data. Review text is written by Tabelog's users, and Tabelog's terms forbid reproducing or reusing posted reviews without permission, so check them before you publish or resell review text.
Related scrapers
- HotPepper Gourmet Japan Restaurant Scraper: restaurants, phone numbers and coupons from HotPepper Gourmet
- Gurunavi Japan Restaurant Scraper: restaurants from Gurunavi (ぐるなび)