Tripadvisor Reviews Scraper & API: All Languages, from $0.50/1K avatar

Tripadvisor Reviews Scraper & API: All Languages, from $0.50/1K

Pricing

from $0.50 / 1,000 reviews

Go to Apify Store
Tripadvisor Reviews Scraper & API: All Languages, from $0.50/1K

Tripadvisor Reviews Scraper & API: All Languages, from $0.50/1K

Scrape Tripadvisor reviews of hotels, restaurants, attractions and tours: rating, full text, all languages with machine translations flagged, trip type, stay date, sub-ratings, photos, owner response. Plain HTTP, no browser. New-reviews-only monitoring and webhook.

Pricing

from $0.50 / 1,000 reviews

Rating

0.0

(0)

Developer

Alexis Morain

Alexis Morain

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Features

Limited permissions

Share

Tripadvisor Reviews Scraper

This Actor exports the reviews of Tripadvisor hotels, restaurants, attractions and tours. Paste a Tripadvisor page URL (or just the location id), and you get one row per review: rating, title, full text, language, trip type, month of the stay, sub-ratings (value, rooms, location, cleanliness, service, sleep quality), photos, the reviewer's profile data and the owner's response. A summary row per page comes with it.

It works as a Tripadvisor reviews API. The Actor reads the same data endpoint that Tripadvisor's own review pages call, over plain HTTP. No browser, no Tripadvisor login, no residential proxy. That is why a hotel with 16,000 reviews takes under two minutes, and why the price can stay low: $1.00 per 1,000 reviews on the Apify Free plan, down to $0.50 per 1,000 on the Gold plan, plus $0.005 when a run starts.

What makes it different: it reads every language by default and flags the reviews Tripadvisor machine-translated; it filters by star rating on its own side because Tripadvisor's rating filter drops reviews; and it has a New reviews only mode that remembers what it already delivered, so a scheduled run returns (and charges) only new reviews.


What does Tripadvisor Reviews Scraper do?

You give it Tripadvisor pages. For each page it:

  1. Reads the location id from the URL (the number after -d, for example d91703).
  2. Opens a session with Tripadvisor's data endpoint and reads reviews newest first, 20 per request, four requests at a time.
  3. Pushes the reviews to the dataset in batches of 100, and charges one review event per row.
  4. Adds one summary row for the page (name, type, city, how many reviews match, how many the run delivered), unless you turn it off.

Supported pages: hotels (Hotel_Review), restaurants (Restaurant_Review), attractions (Attraction_Review) and tours (AttractionProductReview), on any Tripadvisor domain (.com, .fr, .co.uk and so on). A bare location id such as d228694 also works.

Why scrape Tripadvisor reviews?

  • Reputation monitoring for hotels, restaurants and tour operators. Schedule a daily run in New reviews only mode and send the result to Slack, Make, Zapier or n8n.
  • Competitor research. Pull the 1 and 2 star reviews of the places around yours and read what guests complain about, in their own words.
  • Sentiment analysis and LLM pipelines. Rating, text, language code and trip type are separate columns, ready for a model or a BI tool.
  • Market studies. Compare the sub-ratings (value, rooms, location, cleanliness, service, sleep quality) of every hotel in a city.
  • Review datasets. Build a dataset of hotel or restaurant reviews for training or benchmarking, with the reviewer's home town and the month of the stay.

Apify adds scheduling, an API for every run, integrations with Google Sheets, Slack, Zapier, Make and n8n, and exports to JSON, CSV and Excel.

How to scrape Tripadvisor reviews

From the Apify console

  1. Click Try for free and open the Actor.
  2. Go to Tripadvisor, search for the hotel, restaurant or attraction, open its page and copy the URL from the address bar. It looks like https://www.tripadvisor.com/Hotel_Review-g187147-d228694-Reviews-Hotel_Malte_Astotel-Paris_Ile_de_France.html.
  3. Paste it in Page URLs (one URL per line).
  4. Set Max reviews per page URL. The default is 100, and 0 means every review.
  5. Optionally narrow the run with languages, star ratings, traveller types or a date window.
  6. Click Start. When the run ends, open the Output tab or export the dataset as JSON, CSV or Excel.

From the API

Send the same input as JSON to the Actor's run endpoint. Python, JavaScript and cURL examples are further down.

Which fields should I fill?

I want to...FillNotes
Try it oncePage URLsThe prefilled URL with 20 reviews costs about three cents on the Free plan.
Get the whole history of a listingMax reviews per page URL = 0One charged result per review, so this is also your cost cap.
Get only recent reviewsOnly reviews from the last N daysRolling window, 1 to 3650 days. Reads newest first and stops when a whole page is older than the date.
Get reviews since a fixed dateOnly reviews published afterYYYY-MM-DD. If you also set the window, the later date wins.
Keep one languageReview languagesCodes such as en, fr, de, es, it, ja, zhCN. Empty means all languages.
Keep the bad reviewsStar ratingsThe Actor reads everything and keeps the ratings you pick. You pay only for kept reviews.
Keep business travellers, families...Traveller typesFAMILY, COUPLES, SOLO, BUSINESS, FRIENDS. Filtered by Tripadvisor itself.
Monitor a listingReview mode = New reviews onlyAdd a Monitoring key if you want several independent watches on the same URL.
Be told when a run endsWebhook URLReceives a JSON summary.
Get a clean reviews-only CSVAdd one summary row per URL = offOtherwise the dataset also holds one place row per URL.
Change the proxyProxyLeave the default (Apify datacenter proxy).

Input examples

One hotel, the 200 newest reviews:

{
"startUrls": ["https://www.tripadvisor.com/Hotel_Review-g45963-d91703-Reviews-Bellagio_Las_Vegas-Las_Vegas_Nevada.html"],
"maxReviewsPerPlace": 200
}

The complaints: 1 and 2 star reviews in English:

{
"startUrls": ["https://www.tripadvisor.com/Hotel_Review-g45963-d91703-Reviews-Bellagio_Las_Vegas-Las_Vegas_Nevada.html"],
"maxReviewsPerPlace": 0,
"ratings": ["1", "2"],
"languages": ["en"]
}

Several places, last 30 days, business travellers:

{
"startUrls": [
"https://www.tripadvisor.com/Hotel_Review-g187147-d228694-Reviews-Hotel_Malte_Astotel-Paris_Ile_de_France.html",
"https://www.tripadvisor.fr/Restaurant_Review-g187147-d15343325-Reviews-99_Haussmann-Paris_Ile_de_France.html",
"d91703"
],
"maxReviewsPerPlace": 0,
"lastDays": 30,
"travelerTypes": ["BUSINESS"]
}

Daily monitoring, with a webhook:

{
"startUrls": ["https://www.tripadvisor.com/Hotel_Review-g187147-d228694-Reviews-Hotel_Malte_Astotel-Paris_Ile_de_France.html"],
"maxReviewsPerPlace": 0,
"reviewMode": "new-only",
"webhookUrl": "https://hooks.example.com/tripadvisor"
}

Details that need a word

  • A failing URL does not stop the others. Each URL is read in turn. If one cannot be read, the log says why and the run moves on. The run is marked failed only when every URL failed.
  • The same listing twice is read once. If two entries point to the same location id, the second is skipped.
  • Languages are read one at a time. Tripadvisor accepts one language per request, so with several languages the Actor reads each in turn. Reviews therefore come newest first within a language, not across languages.
  • Names come from the URL. placeName and city in the output are taken from the URL slug (Bellagio_Las_Vegas-Las_Vegas_Nevada becomes Bellagio Las Vegas and Las Vegas Nevada). If you paste a bare location id such as d228694, both are null. Reviews are not affected.
  • A listing with no reviews is reported, not charged. Tripadvisor answers 0 for a deleted listing and for one without reviews, so the Actor reports it as not found rather than charging for an empty summary row.

What data can it extract? Every output field

Each review is one dataset row with "type": "review".

FieldTypeDescription
typestringreview for a review, place for the summary row
sourcestringAlways tripadvisor
reviewIdstringTripadvisor review id, stable across runs
reviewUrlstringPermalink of the review on Tripadvisor
ratingnumberOverall rating, 1 to 5
ratingScaleintegerAlways 5
titlestringReview title
textstringFull review text
languagestringLanguage code of text
originalLanguagestringLanguage the review was written in
isMachineTranslatedbooleantrue when Tripadvisor shows a machine translation
publishedAtstringPublication date and time, ISO 8601 UTC
stayDatestringMonth of the stay or visit, YYYY-MM
travelerTypestringTrip type as Tripadvisor gives it, for example FAMILY, COUPLES, SOLO, BUSINESS, FRIENDS
subRatingsobjectRatings by aspect, such as Value, Rooms, Location, Cleanliness, Service, Sleep Quality. null when the reviewer gave none
helpfulVotesintegerHelpful votes on the review
photosarrayFull-size URLs of the photos the reviewer attached
reviewerNamestringReviewer display name
reviewerProfileUrlstringReviewer profile page
reviewerLocationstringReviewer home town, as the reviewer wrote it on the profile
reviewerContributionsintegerNumber of contributions of the reviewer
ownerResponsestringPublic reply from the owner
ownerResponseDatestringDate of the reply, ISO 8601
ownerResponderRolestringWho replied (for example a role)
placeIdstringTripadvisor location id
placeNamestringName of the place, from the URL
placeTypestringhotel, restaurant, attraction or attraction_product
placeUrlstringTripadvisor page of the place
providerstringAlways Tripadvisor
scrapedAtstringWhen the row was collected, ISO 8601 UTC

The dataset schema also lists columns that other sources fill (positiveText, negativeText, roomType, nights, reviewerCountryCode). They are present and null on Tripadvisor rows to keep the column names of the Booking.com and Agoda Actors.

The summary row

One row per URL, with "type": "place":

FieldDescription
placeId, placeName, placeType, placeUrlThe place, as above
cityCity, from the URL
reviewsCountReviews Tripadvisor reports for the run's language filter (all reviews when there is none)
reviewsDeliveredReviews this run delivered for the place
inputThe URL or id you gave
scrapedAtCollection time

rating, address and countryCode are null on a Tripadvisor summary row.

Example output

A review row (text shortened), read from the Bellagio Las Vegas listing:

{
"type": "review",
"source": "tripadvisor",
"placeId": "91703",
"placeName": "Bellagio Las Vegas",
"placeType": "hotel",
"placeUrl": "https://www.tripadvisor.com/Hotel_Review-g45963-d91703-Reviews-Bellagio_Las_Vegas-Las_Vegas_Nevada.html",
"reviewId": "1082686111",
"reviewUrl": "https://www.tripadvisor.com/ShowUserReviews-g45963-d91703-r1082686111-Bellagio-Las_Vegas_Nevada.html",
"rating": 5,
"ratingScale": 5,
"title": "Bellagio",
"text": "We stayed for a week in the Bellagio with family/friends to celebrate my brother in law's marriage...",
"language": "en",
"originalLanguage": "en",
"isMachineTranslated": false,
"publishedAt": "2026-10-21T16:37:39.512Z",
"stayDate": "2026-10",
"travelerType": "FAMILY",
"subRatings": {"Value": 4, "Rooms": 5, "Location": 5, "Cleanliness": 5, "Service": 5, "Sleep Quality": 5},
"helpfulVotes": 0,
"photos": [],
"reviewerName": "Freedom60470529778",
"reviewerProfileUrl": "https://www.tripadvisor.com/Profile/Freedom60470529778",
"reviewerLocation": "Bristol, United Kingdom",
"reviewerContributions": 6,
"ownerResponse": null,
"ownerResponseDate": null,
"ownerResponderRole": null,
"provider": "Tripadvisor"
}

A summary row:

{
"type": "place",
"source": "tripadvisor",
"placeId": "91703",
"placeName": "Bellagio Las Vegas",
"placeType": "hotel",
"placeUrl": "https://www.tripadvisor.com/Hotel_Review-g45963-d91703-Reviews-Bellagio_Las_Vegas-Las_Vegas_Nevada.html",
"city": "Las Vegas Nevada",
"reviewsCount": 16004,
"reviewsDelivered": 16003,
"input": "https://www.tripadvisor.com/Hotel_Review-g45963-d91703-Reviews-Bellagio_Las_Vegas-Las_Vegas_Nevada.html"
}

Scrape Tripadvisor reviews in every language

Tripadvisor shows reviews written in many languages, and the English site often hides most of them. By default the Actor does not filter on language, so you get all of them. We measured this on the Hôtel Malte Astotel page in Paris during recon (21 October 2026): about 30% of its reviews were not in English, and 423 of them were machine translations that Tripadvisor flagged.

Two fields tell you what happened to each review:

  • isMachineTranslated is true when Tripadvisor shows a machine translation of the review.
  • originalLanguage is the language the reviewer wrote in.

So you can keep everything, keep only original-language reviews, or drop the translations. When a review is machine-translated, text is the text Tripadvisor shows, which is the translation. This version does not return the original wording of a translated review.

To restrict a run to some languages, fill Review languages (en, fr, de, es, it, ja, zhCN...). The filter is applied by Tripadvisor.

How to scrape all reviews of a big hotel

Measured on the Apify platform on 21 October 2026, all languages, no filter:

ListingReviews on TripadvisorCollectedTime
Bellagio Las Vegas (hotel)16,00416,003104 s
Hôtel Malte Astotel, Paris3,9743,97327 s

Both listings lose one review compared with Tripadvisor's own count. Tripadvisor counts a review it does not send back, and the Actor cannot get it.

Deep pages. Past an offset of about 10,000, Tripadvisor answers some pages with an internal error. We saw it on the Eiffel Tower page (144,135 reviews): the offset 10,020 answered, while 12,000 failed three times out of four. The Actor retries the failed pages at the end of the run, in up to three passes with more attempts on each. If a page still refuses, the log names it. In New reviews only mode such a run is not recorded as complete, so the next run reads again from the top. We did not record a full read of the Eiffel Tower page, so treat very large listings (well above Bellagio's 16,000) as not verified.

Filter by star rating without losing reviews

Tripadvisor has a star filter on its pages, and it loses reviews. For Bellagio, the five star buckets add up to 11,893 reviews while the listing holds 16,004 (measured on 21 October 2026). A scraper that sends the rating filter to Tripadvisor silently skips about a quarter of the reviews.

This Actor never sends the rating filter to Tripadvisor. It reads every review and keeps the ones with the ratings you asked for. Only the reviews it keeps are pushed to the dataset, so only those are charged. The cost is time, not money: a run that keeps 1 and 2 star reviews still reads the whole listing.

Monitor new Tripadvisor reviews: New reviews only mode

Set Review mode to New reviews only and schedule the Actor (daily or weekly).

  • The Actor keeps a registry per place, in a named key-value store of your account called tripadvisor-reviews-registry. It holds the ids of the reviews already delivered.
  • The first run reads the whole history. Set Max reviews per page URL to 0 for this run: a run stopped by the review limit, the spend limit, a timeout or unreadable pages is not recorded as a complete read, and the next run then reads the full history again (reviews already delivered are never returned or charged twice).
  • After a complete read, later runs only read reviews newer than the date of that read minus 30 days. The margin is there because a review can show up on Tripadvisor after more recent ones (moderation).
  • Reviews already in the registry are skipped and not charged. The log and the status message say how many were skipped.
  • A different set of filters (languages, ratings, traveller types) is a different watch with its own registry. With a Monitoring key, the memory is named by you instead, and changing the filters makes the next run read the full history once.
  • If you set Only reviews from the last N days or Only reviews published after, the run is not recorded as a complete read.

Webhook at the end of the run

If you fill Webhook URL, the Actor sends one JSON POST when it has finished reading. It works with Slack incoming webhooks, Make, Zapier and n8n. The body looks like this:

{
"actor": "tripadvisor-reviews-scraper",
"runId": "abc123",
"datasetId": "def456",
"mode": "new-only",
"status": "succeeded",
"places": 1,
"reviews": 3,
"skippedAlreadySeen": 4012,
"targets": 1,
"failedTargets": 0,
"chargeLimitReached": false
}

status is succeeded, partial (some URLs failed) or failed (all of them failed). The URL is a secret field: it is never written to the log. The call is a one-shot POST with a 15 second timeout. A failure is logged and never changes the result of the run. A 307 or 308 redirect is followed once, other redirects are not. The webhook is not sent when the input itself is invalid.

Export Tripadvisor reviews to CSV, Excel or JSON

Open the run, go to Storage (or the Output tab), and pick a format: JSON, CSV, Excel, HTML or XML. From the API, add format=csv to the dataset items URL:

https://api.apify.com/v2/datasets/<DATASET_ID>/items?format=csv&token=<YOUR_API_TOKEN>

Two tips for a clean spreadsheet:

  • The dataset holds place rows next to review rows. For a reviews-only file, turn off Add one summary row per URL, or filter on type after the export.
  • photos is a list and subRatings is an object. They are intact in JSON. In CSV and Excel they become text or extra columns, depending on the export format.

Using the Tripadvisor reviews API from your code

Python

from apify_client import ApifyClient
client = ApifyClient("<YOUR_API_TOKEN>")
run = client.actor("alexmorain/tripadvisor-reviews-scraper").call(run_input={
"startUrls": ["https://www.tripadvisor.com/Restaurant_Review-g187147-d15343325-Reviews-99_Haussmann-Paris_Ile_de_France.html"],
"maxReviewsPerPlace": 0,
"reviewMode": "new-only",
})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
if row["type"] == "review":
print(row["publishedAt"], row["rating"], row["title"])

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_API_TOKEN>' });
const run = await client.actor('alexmorain/tripadvisor-reviews-scraper').call({
startUrls: ['https://www.tripadvisor.com/Hotel_Review-g187147-d228694-Reviews-Hotel_Malte_Astotel-Paris_Ile_de_France.html'],
maxReviewsPerPlace: 500,
ratings: ['1', '2'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.filter((row) => row.type === 'review').length);

cURL

curl -X POST "https://api.apify.com/v2/acts/alexmorain~tripadvisor-reviews-scraper/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"startUrls": ["https://www.tripadvisor.com/Hotel_Review-g187147-d228694-Reviews-Hotel_Malte_Astotel-Paris_Ile_de_France.html"], "maxReviewsPerPlace": 50}'

This call waits for the run and returns the items. For large listings, start the run with POST /v2/acts/alexmorain~tripadvisor-reviews-scraper/runs, then read the dataset when the run has finished.

What people use it for

Hotel reputation monitoring

A hotel group lists its properties' URLs, schedules a daily run in New reviews only mode, and sends the webhook to Slack. A run that finds three new reviews costs about one cent on the Free plan (three reviews, one summary row, the start fee).

Competitor complaint mining

Fill Star ratings with 1 and 2 for the hotels around yours. The output gives you the complaint text, the trip type and the month of the stay, so you can see whether noise, cleanliness or service dominates.

Restaurant and tour operator reviews

Restaurants and tours work like hotels: paste a Restaurant_Review or AttractionProductReview URL. Our recorded platform runs cover hotels and one restaurant.

Training data and benchmarks

Collect reviews across languages with their ratings and trip types. language and isMachineTranslated let you keep only original text.

Tripadvisor Reviews Scraper pricing

You pay per event. There is no monthly rental.

EventFree planBronzeSilverGold and above
Review (per 1,000)$1.00$0.90$0.80$0.50
Summary row (per 1,000)$2.00$1.80$1.60$1.00
Actor start (per run, per GB of memory, minimum one)$0.005$0.005$0.005$0.005

The Actor runs with 512 MB, so the start fee is $0.005 per run. The tier that applies is the one of your Apify plan.

JobFree planGold plan
100 reviews, one place$0.107$0.056
1,000 reviews, one place$1.007$0.506
All 3,973 reviews of Hôtel Malte Astotel$3.98$1.99
All 16,003 reviews of Bellagio Las Vegas$16.01$8.01
Daily monitoring run with 3 new reviews$0.010$0.0075

Each worked example is the reviews, plus one summary row ($0.002 Free, $0.001 Gold), plus the start fee. The $5 of monthly credit in the Apify Free plan covers about 5,000 reviews.

Cost control. Max reviews per page URL caps each URL. You can also set a maximum cost for the run in the Apify run options: the Actor pushes reviews through the platform's charging check, so it stops when the limit is reached instead of going over it. We checked this on the platform before publishing.

Reviews already delivered in New reviews only mode are not charged again.

Limits and what this Actor does not do

  • It reads public reviews only. No Tripadvisor login, no private data.
  • No original text for translated reviews. For a machine-translated review, text is Tripadvisor's translation and originalLanguage tells you the source language.
  • One or two reviews can be missing on a big listing. Bellagio: 16,003 of 16,004. Hôtel Malte: 3,973 of 3,974.
  • Very large listings are not verified. Beyond about 10,000 reviews Tripadvisor's deep pages fail from time to time. The Actor retries and reports what it could not read, but we have recorded no full read above Bellagio's 16,004.
  • Tripadvisor rating filter is not used. Filtering by stars reads the full listing first.
  • Names come from the URL. placeName and city are null when you give a bare id.
  • Attractions and tours are accepted, but our recorded full runs are hotels and one restaurant.
  • Only reviews. Forum posts, Q&A and standalone photos are not covered.
  • The reviewer's name is the display name the reviewer chose, which is often a username.

FAQ

Is there a Tripadvisor reviews API?

This Actor does not use an official Tripadvisor API. It reads the review data that the public Tripadvisor pages load, and returns it as JSON through the Apify API. You call it with an Apify token, not a Tripadvisor key.

How do I scrape Tripadvisor reviews without coding?

Open the Actor in the Apify console, paste the page URL, set the maximum number of reviews, press Start, and download the dataset as CSV or Excel.

How many reviews can I scrape from one Tripadvisor page?

All of them, in our measurements up to 16,003 on one hotel in 104 seconds. Set Max reviews per page URL to 0. Above about 10,000 reviews, Tripadvisor's deep pages sometimes fail; the Actor retries them and says in the log if some stayed out.

Can I scrape only 1 star Tripadvisor reviews?

Yes. Fill Star ratings with 1. The Actor reads the listing and keeps the matching reviews. You are charged for the kept reviews only.

Can I scrape Tripadvisor restaurant reviews?

Yes. Paste a Restaurant_Review URL. The output is the same, with placeType set to restaurant.

Can I get Tripadvisor reviews in one language only?

Yes. Use Review languages, for example ["fr"]. Leave it empty for all languages.

Why does the number of reviews differ from the number on the Tripadvisor page?

Tripadvisor counts some reviews it does not send back. We saw a difference of one review on Bellagio and on Hôtel Malte. If you filter by language, the count in the summary row (reviewsCount) is the count for that language.

Does it need a Tripadvisor account, cookies or a residential proxy?

No account, and you do not supply cookies. The Actor gets the access cookie it needs by itself. The default Apify datacenter proxy is enough. Keep the Proxy field at its default.

Does it get the original text of translated reviews?

Not in this version. You get the text Tripadvisor shows, a flag saying it was machine-translated, and the original language code.

What happens if Tripadvisor blocks a request?

The Actor opens a new session on a new IP and retries, up to six times for a page (ten in the later passes). If a URL cannot be read at all, the log says so and the other URLs carry on. The run fails only if every URL failed.

How do I find the URL of a Tripadvisor page?

Search the place on Tripadvisor, open its page, copy the URL. The id after -d is the location id. You can also paste just that id, for example d228694.

How do I export Tripadvisor reviews to CSV?

Run the Actor, open the dataset, choose CSV. See the export section above for a reviews-only file.

How do I monitor new Tripadvisor reviews?

Use New reviews only with a daily or weekly schedule, and add a webhook. See the monitoring section.

The Actor reads pages that anyone can open without logging in. The output contains personal data that the reviewers made public: a display name, a home town, a profile link, the review itself. Personal data is protected by the GDPR in the European Union and by similar laws elsewhere. Use the data for a legitimate purpose, and check Tripadvisor's terms and your own legal advice for your use. This is not legal advice.

Integrations, exports and support

Connect the dataset to Google Sheets, Slack, Zapier, Make or n8n with Apify's integrations, or call the Actor through the Apify API and client libraries. Runs can be scheduled from the console.

Something not working, or a field you need? Open an issue in the Issues tab. The same developer publishes Booking.com Reviews Scraper, Agoda Reviews Scraper and Airbnb Reviews Scraper, with the same column names.

Guide and use cases

Use cases for outbound and automation, the output fields, pricing and common questions are on the Tripadvisor Reviews Scraper page of my site. The Reviews family page puts it side by side with the other scrapers of the same family.