This tutorial shows how to scrape Google Hotels data from Google Travel search results into CSV with the Google Hotels Scraper template for UScraper. You will edit the destination URL, run the result loop, set the export path, and validate hotel names, prices, ratings, amenities, deal tags, and image URLs.
Before you start
Prerequisites for scraping Google Hotels
You need UScraper installed as a local desktop app, the current Google Hotels template JSON, a destination search you are allowed to inspect, and a folder where CSV exports can be written. Start with one destination, not a long market list, because the first run is for selector validation.
The stock workflow starts from a Barcelona hotels URL: https://www.google.com/travel/hotels/Barcelona?hl=es&gl=US&curr=USD. Replace the city, language, country, and currency parameters before you run your own search. Keep those parameters consistent if you plan to compare markets or repeat the export next week.
Treat this as a browser automation workflow for accessible pages. Do not use it to bypass CAPTCHA, paid access, account walls, or technical restrictions.
Workflow anatomy
What the Google Hotels scraper template does
The JSON workflow is the authoritative definition. It follows this browser path: Navigate -> Wait for Page Load -> consent helper -> Wait for hotel images -> scroll result panels -> load-more loop -> normalize rows -> Structured Export -> End. The parser looks for amenity markers such as "Servicios de" or "Amenities for", then attaches nearby price, rating, property label, offer tags, services, and image URLs to one synthetic row per hotel.
This is different from a Google Hotels API integration. Google's hotel developer documentation focuses on partner systems such as Hotel Prices and Hotel Content, while third-party providers expose Google Hotels-style JSON endpoints. UScraper sits in the middle: it gives analysts a no-code, visible-browser export, but still depends on the rendered page.
| Workflow block | What it does | What to verify |
|---|---|---|
| Navigate | Opens the Google Travel hotels search URL | Destination and locale are correct. |
| Consent helper | Clicks common Accept or Agree buttons when visible | The page is not stuck behind a prompt. |
| Scroll and load more | Scrolls the page and nested result panels, then clicks More hotels style buttons | Row count increases before export. |
| Normalize rows | Creates hidden .uscraper-hotel-row elements | Each row has a hotel name. |
| Structured Export | Writes headers and rows to google-hotel-scraper.csv | Save folder and file mode match the project. |
Runbook
How to scrape Google Hotels to CSV
Download and import
Open Google Hotels Scraper, download the JSON workflow, and import it into UScraper.
Edit the destination URL
Replace the sample Barcelona URL in Navigate with your approved Google Travel hotels search. Keep hl, gl, and curr deliberate for consistent exports.
Run one visible search
Start with one destination. If Google shows consent or verification UI, handle it in the browser and rerun after the hotel result cards are visible.
Confirm the export path
In Structured Export, set the project folder and keep the filename google-hotel-scraper.csv unless a downstream spreadsheet expects another name.
Validate before scaling
Open the CSV, compare several rows with the browser, then duplicate the workflow or change the URL for additional markets.
The load-more loop checks button text in English and Spanish. If your browser locale uses another phrase, add it to the XPath before running more searches.
Output
CSV columns from the Google hotel data export
The bundled export writes eight columns. Some headers are Spanish because the default workflow targets a Spanish-language Google Travel URL. Keep the names stable if downstream files depend on them.
| CSV column | Meaning | Validation check |
|---|---|---|
hotel | Hotel or property name parsed from a visible card | Not empty; no navigation labels or policy text. |
precio | Visible price text in the selected currency | May be blank when price is hidden or inventory is unavailable. |
calificacion | Rating and optional review count near the card | Spot-check decimal separators for the selected locale. |
etiqueta | Property label, hotel class, or type text | Useful for filtering hotels, hostels, and apartments. |
oferta | Deal or location signals such as Great deal or Excellent location | Treat as display text, not a guaranteed discount calculation. |
servicios | Amenities joined into a pipe-separated list | Scan for truncation when cards change layout. |
imagen | Primary Google-hosted image URL | Confirm URLs start with a normal image host, not a data URI. |
imagen2 | Secondary image URL when available | Optional enrichment field. |
Quality control
Validate the Google Hotels export
Treat validation as part of the tutorial. Keep the browser open beside the CSV and check rows from the top, middle, and bottom. A good row has a recognizable hotel name and amenities that look like property services.
| Symptom | Likely cause | Fix |
|---|---|---|
| Zero rows | Consent, CAPTCHA, slow load, or no hotel image matched | Resolve the prompt, extend the wait, and rerun one destination. |
| Hotel names look wrong | The amenity marker pattern matched page chrome | Inspect the hidden rows and tighten the parser around result cards. |
| Prices are blank | Price was not visible for the market, date, or currency | Verify the same URL manually and keep search parameters stable. |
| Amenities are truncated | The card loaded below the fold or changed copy | Add another scroll step or adjust the extraction split rules. |
| Duplicate image URLs | The image pool was reused across several cards | Deduplicate later if images are only supporting enrichment. |
Alternatives
Google Hotels API vs scraper vs Python
If you search for "google hotels api alternative" or "scrape google hotels python", you will find three practical paths. Pick based on custody, maintenance, and scale.
| Approach | Best for | Trade-off |
|---|---|---|
| UScraper template | No-code CSV exports, visible QA, local custody, small research batches | Depends on rendered page structure and manual validation. |
| Python scraper | Custom logic, notebooks, internal engineering workflows | Requires code, selectors, retry logic, and maintenance. |
| Hosted Google Hotels API | JSON responses, managed infrastructure, scheduling, higher volume | Usually usage-based and routes requests through a vendor. |
| Official hotel partner docs | Hotel partners managing prices, inventory, landing pages, or Hotel Center data | Not the same as a public search-results scraping endpoint. |
For many research tasks, the local desktop app is enough: import the workflow, run a controlled destination, and inspect the CSV. For a production travel product, a licensed feed or hosted API may be more durable.
FAQ
Google Hotels scraper FAQ
Google Travel hotel listings can be visible in a browser and still be governed by Google terms, hotel partner rules, robots guidance, copyright, privacy law, and local regulations. Use conservative pacing, do not bypass CAPTCHA or access controls, and get legal review before commercial reuse.
Next step
Download the Google Hotels scraper template
When you are ready to run the workflow, download the JSON from Google Hotels Scraper and keep this tutorial open for validation. For neighboring travel workflows, browse all UScraper templates or read more CSV export guides on the UScraper blog.