Weather.com Scraper
Pricing
from $1.00 / 1,000 results
Weather.com Scraper
Extract current weather, 48-hour hourly forecasts, 10-day forecasts, and active weather alerts for multiple locations into structured datasets.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer
SearchShark Tools
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
๐ฆ๏ธ Weather.com Scraper
Weather.com Scraper lets you extract structured current weather, hourly forecasts, daily forecasts, and active weather alerts for multiple locations.
Collect weather data for travel planning, logistics, agriculture, events, local dashboards, research, monitoring, and automation without manually checking Weather.com.
- ๐ก๏ธ Get current conditions: temperature, feels-like temperature, humidity, wind, pressure, visibility, dew point, and UV index
- ๐ Collect hourly forecasts: retrieve up to 48 upcoming forecast hours
- ๐ Collect daily forecasts: retrieve up to 10 forecast days
- โ ๏ธ Monitor weather alerts: collect active alert information when Weather.com exposes it
- ๐ Use multiple location formats: city names, ZIP codes, coordinates, or Weather.com URLs
- ๐ Get normalized data: every result is stored as a clean Dataset row with a clear
recordType - โก Automate workflows: export structured results to Apify Dataset, API, integrations, dashboards, or downstream applications
๐ฆ What data does Weather.com Scraper extract?
| ๐ Location name | ๐ Latitude & longitude |
| ๐ก๏ธ Temperature | ๐ก๏ธ Feels-like temperature |
| ๐ค๏ธ Weather condition | ๐ง Humidity |
| ๐จ Wind speed | ๐งญ Wind direction |
| ๐งญ Cardinal wind direction | ๐ก๏ธ Dew point |
| ๐ Atmospheric pressure | ๐๏ธ Visibility |
| โ๏ธ UV index | ๐ง๏ธ Precipitation probability |
| ๐ง๏ธ Precipitation amount | โฌ๏ธ Daily high |
| โฌ๏ธ Daily low | ๐ Forecast time |
| ๐ Forecast date | โ ๏ธ Alert headline |
| ๐ Affected alert area | โฐ Alert expiry |
| ๐ Alert description | ๐ก๏ธ Recommended action |
| ๐ข Alert issuing source | ๐ Weather.com source URL |
| ๐งพ Record type | ๐ Scrape timestamp |
Missing fields are returned as
nullwhen Weather.com does not expose them reliably. The Actor does not invent weather or alert data.
๐ Features
Weather.com Scraper is designed for weather monitoring, forecasting workflows, structured data collection, and automation.
- Multiple locations: process several locations in one Actor run
- Current weather conditions
- 48-hour hourly forecast
- 10-day daily forecast
- Active weather alerts
- Metric and imperial units
- City-name input
- U.S. ZIP-code input
- Latitude and longitude input
- Weather.com URL input
- Normalized Dataset rows
- Record-type separation: current, hourly, daily, and alerts are clearly identified
- Partial failure protection: one failed location does not discard successful results from other locations
- HTTP-first architecture: normal page requests are attempted before browser rendering
- Browser fallback: Chromium is used when Weather.com returns client-rendered placeholder values
- API-friendly output: Dataset rows follow a predictable structure
- Schedule-friendly: suitable for repeated Apify Tasks and recurring weather collection
โฌ๏ธ Input
You can configure Weather.com Scraper directly from the Apify Console or send the input programmatically through the Apify API.
๐ Locations
Add one or more locations.
Example:
You can use:
City examples
Coordinate example
ZIP-code example
Each location is processed independently.
If one location fails, successful locations can still remain available in the Dataset.
๐ก๏ธ Units
Choose the measurement system used for returned weather values.
Imperial
Typically uses values such as:
Metric
Typically uses values such as:
๐ฆ๏ธ Weather data
Choose one or more weather record types.
Available options:
๐ก๏ธ Current conditions
Returns the latest current conditions available for the location.
Possible fields include:
๐ Hourly forecast
Returns up to:
for each successfully processed location.
Possible hourly fields include:
๐ Daily forecast
Returns up to:
for each successfully processed location.
Possible daily fields include:
Additional fields may be present when Weather.com exposes them reliably.
โ ๏ธ Weather alerts
Checks the selected location for active weather alerts.
Possible fields include:
A location may return:
No alert record is created when no active alert is detected.
๐ Language / locale
Set the Weather.com locale used during requests.
Default:
Example:
The current public location resolver is primarily optimized around the tested en-US workflow.
๐งช Example input
For a faster current-weather-only run:
โฌ๏ธ Output
Results are stored in the Actor's default Apify Dataset.
You can access the results from:
Every Dataset row contains:
This identifies what kind of weather record the row represents.
Possible values:
๐ Example current result
Optional fields may be
nullwhen they are not exposed reliably by Weather.com for that page or rendering session.
๐งพ Normalized record types
Weather.com Scraper does not return one huge nested object containing every forecast.
Instead, weather observations are stored as individual Dataset rows.
For example:
This makes the output easier to use in:
๐ก๏ธ Current weather records
A current record represents the current conditions collected for one location.
Important fields include:
๐ Hourly records
Each hourly row represents one forecast hour.
For example:
Possible fields include:
The Actor intentionally limits the current hourly mode to:
๐ Daily records
Each daily row represents one forecast day.
Example:
Possible fields include:
The Actor intentionally saves:
even when Weather.com may expose additional forecast entries.
โ ๏ธ Alert records
Each alert row represents one active weather alert discovered for a location.
Possible fields include:
The scraper only returns alert values that are available from Weather.com's visible pages or alert links.
The Actor does not infer severity, certainty, urgency, alert IDs, or timestamps when Weather.com does not explicitly expose them.
๐ Location resolution
Weather.com Scraper supports several ways to identify a location.
๐ City names
Example:
The Actor resolves the city to coordinates and verifies the resulting location with Weather.com.
๐ City + state code
Example:
A city can resolve to Weather.com's preferred locality.
For example:
may resolve to a Weather.com locality such as:
This reflects Weather.com's location mapping.
๐ฎ ZIP codes
Example:
The current public resolver directly supports tested five-digit U.S. ZIP codes.
๐ Coordinates
Example:
Coordinates are useful when you need a specific geographic point instead of a city-level location.
๐ Weather.com URLs
You can also provide a supported Weather.com location URL directly.
โ ๏ธ Ambiguous city names
Some city names exist in many regions.
For example:
can refer to multiple places.
Instead of silently choosing a random match, provide additional location context:
This improves location resolution accuracy.
โก Performance
The scraper uses an HTTP-first architecture.
The Actor first requests the normal Weather.com page.
When Weather.com returns fully usable weather values, the scraper can parse them directly.
When the page contains client-rendered placeholders such as:
the Actor can launch Chromium and wait for the normal public page to render.
This approach reduces unnecessary browser work while still supporting pages that require JavaScript.
๐ก Reliability
Weather.com pages are processed one location at a time in the current version.
If you run:
and one location fails, successful results from the other locations are still preserved.
Temporary page or browser behavior can vary between locations, so the Actor is designed to keep already collected results instead of discarding the complete run.
๐ก Access handling
Weather.com Scraper accesses normal public Weather.com pages.
If the page behaves like an access or verification challenge, the Actor does not attempt to bypass the challenge.
This is intentionally different from stealth or challenge-evasion scraping.
๐ API & integrations
Weather.com Scraper can be used programmatically through the Apify API.
You can connect results to workflows such as:
- Google Sheets
- Make
- Zapier
- n8n
- Internal APIs
- Databases
- Data warehouses
- Logistics systems
- Travel applications
- Agriculture systems
- Weather dashboards
- Event-planning systems
- AI agents
- MCP workflows
Every Actor run stores structured records in the default Dataset, making the output easy to consume from another application.
๐ก Example use cases
โ๏ธ Travel planning
Monitor weather for destinations such as:
Collect:
Use the data in travel dashboards or automated trip-planning systems.
๐ Logistics and delivery operations
Monitor weather around:
Weather information can help operational systems identify:
๐พ Agriculture
Collect scheduled weather observations for farming locations.
Useful fields can include:
Store results over repeated Actor runs for downstream analysis.
๐ช Event planning
Check forecast conditions around an event location.
For example:
This can be integrated into event dashboards or automated notification systems.
๐ Weather dashboards
Run the Actor on a schedule and send Dataset results into:
The normalized Dataset format avoids having to flatten a large nested forecast object.
โ ๏ธ Severe weather monitoring
Enable:
for locations you want to check.
When Weather.com displays active alerts, the Actor can collect information such as:
๐ฌ Research and analysis
Collect weather records across several locations for downstream analysis.
Possible workflows include:
โ ๏ธ Current limitations
The current version focuses on current conditions, 48-hour forecasts, 10-day forecasts, and active alerts.
It does not currently provide:
These are intentionally separate from the current V1 workflow.
๐ Public page variability
Weather.com is a dynamic website.
Different pages can:
Because of this, optional values may sometimes be:
even when other weather fields for the same record are available.
๐ค Why can condition be null?
Weather.com does not always expose the visible condition text in the same DOM structure as the other current-condition metrics.
If the scraper can confidently extract:
but cannot confidently identify the condition text, it returns:
instead of guessing.
โ FAQ
How does Weather.com Scraper work?
The Actor takes each supplied location and resolves it to a usable Weather.com page.
It then:
How many locations can I scrape?
You can supply multiple locations in one run.
Actual practical run size depends on:
Hourly, daily, and alert modes naturally require more processing than a current-only run.
How many hourly records are returned?
The current V1 target is:
How many daily records are returned?
The current V1 target is:
Does every location have weather alerts?
No.
Alerts are returned only when Weather.com exposes an active alert for that location.
A normal run may therefore contain:
This does not mean the Actor failed.
Why are some fields null?
Weather.com does not expose every field consistently for every location or page.
The Actor deliberately returns:
when a value cannot be determined confidently.
It does not fabricate missing weather data.
Can I use city names?
Yes.
For example:
For ambiguous city names, add the state, province, or country.
Can I use ZIP codes?
Yes, for the tested U.S. ZIP-code workflow.
Example:
Can I use coordinates?
Yes.
Example:
Can I use multiple locations in one run?
Yes.
Example:
Each location is processed independently.
Can I choose Fahrenheit or Celsius?
Yes.
Choose:
or:
Can I scrape current weather only?
Yes.
Select:
This is the lightest normal workflow.
Can I request several weather modes at once?
Yes.
For example:
This produces different Dataset row types for the same location.
Can I use Weather.com Scraper through an API?
Yes.
Every Apify Actor can be started through the Apify API, and its Dataset results can be retrieved programmatically.
This makes the Actor suitable for automated weather-data pipelines.
Can I export the results?
Yes.
Apify Dataset results can be exported in supported formats such as:
Is a browser always required?
No.
The Actor uses an HTTP-first approach.
Browser rendering is used when Weather.com's public page returns placeholder weather values that require JavaScript rendering.
Does the Actor bypass Weather.com security challenges?
No.
If a genuine access or verification challenge is detected, the Actor does not attempt to bypass it.
๐งญ Recommended workflow
For routine weather collection, choose only the forecast types you actually need.
For lightweight current monitoring:
For short-term planning:
For multi-day planning:
For weather-sensitive operations:
Avoid selecting every mode for large location lists unless the additional data is actually needed, because browser-rendered weather pages require more processing time.
๐ Scheduling
Weather.com Scraper works well with Apify Tasks and schedules.
Example workflows:
Save your Actor input as an Apify Task and configure the schedule appropriate for your application.
๐ Location data
Named-city resolution uses the locally installed cities.json dataset to match human-readable city inputs to geographic coordinates.
Those coordinates are then used with Weather.com to resolve the actual weather location.
The location dataset is used only for location matching and does not generate or estimate weather conditions.
โ๏ธ Responsible use
Weather.com Scraper is an independent tool and is not affiliated with, endorsed by, or sponsored by Weather.com, The Weather Channel, or The Weather Company.
Users are responsible for ensuring that their use of the Actor and resulting data complies with:
Review the applicable Weather.com / The Weather Company terms and obtain any required permissions or licenses for your intended use.
๐ฌ Feedback & support
Found a bug or have a feature request?
Use the Actor's Issues tab on Apify.
When reporting a weather extraction problem, include:
This makes the issue much easier to reproduce.
Useful future additions may include:
๐ Weather data without the manual checking
Enter your locations, choose the weather data you need, run the Actor, and receive structured Weather.com data ready for dashboards, research, APIs, scheduling, integrations, and automation.
