Experience the power of Serpstat's Website Data API, offering comprehensive insights into key SEO metrics, organic traffic estimation, and semantical structure analysis. With our API, unlock valuable data to identify top-performing industry players, analyze competitor strategies, and optimize content for maximum impact.

Unveil essential SEO metrics such as website visibility, organic traffic estimation, and keywords that websites rank for organically. Additionally, gain insights into keywords that websites are shown in Google Ads, providing valuable intelligence for ad targeting and optimization.

Utilize our API to uncover top-performing content in any industry, enabling you to identify trends, understand user intent, and refine your content strategy accordingly.

Benefit from the most cost-effective API solution, starting at just $120 per million rows. Tailor your queries to extract the most relevant data for your specific use-cases, ensuring that you're equipped with the insights necessary to thrive in today's competitive digital landscape.

DataForSEO Labs API offers three powerful keyword research algorithms and historical keyword data:

• Related Keywords from the “searches related to” element of Google SERP. • Keyword Suggestions that match the specified seed keyword with additional words before, after, or within the seed key phrase. • Keyword Ideas that fall into the same category as specified seed keywords. • Historical Search Volume with current cost-per-click, and competition values.

Based on in-market categories of Google Ads, you can get keyword ideas from the relevant Categories For Domain and discover relevant Keywords For Categories. You can also obtain Top Google Searches with AdWords and Bing Ads metrics, product categories, and Google SERP data.

You will find well-rounded ways to scout the competitors:

• Domain Whois Overview with ranking and traffic info from organic and paid search. • Ranked Keywords that any domain or URL has positions for in SERP. • SERP Competitors and the rankings they hold for the keywords you specify. • Competitors Domain with a full overview of its rankings and traffic from organic and paid search. • Domain Intersection keywords for which both specified domains rank within the same SERPs. • Subdomains for the target domain you specify along with the ranking distribution across organic and paid search. • Relevant Pages of the specified domain with rankings and traffic data. • Domain Rank Overview with ranking and traffic data from organic and paid search. • Historical Rank Overview with historical data on rankings and traffic of the specified domain from organic and paid search. • Page Intersection keywords for which the specified pages rank within the same SERP.

All DataForSEO Labs API endpoints function in the Live mode. This means you will be provided with the results in response right after sending the necessary parameters with a POST request.

The limit is 2000 API calls per minute, however, you can contact our support team if your project requires higher rates.

We offer well-rounded API documentation, GUI for API usage control, comprehensive client libraries for different programming languages, free sandbox API testing, ad hoc integration, and deployment support.

We have a pay-as-you-go pricing model. You simply add funds to your account and use them to get data. The account balance doesn't expire.

This dataset contains 145063 time series representing the number of hits or web traffic for a set of Wikipedia pages from 2015-07-01 to 2022-06-30. This is an extended version of the dataset that was used in the Kaggle Wikipedia Web Traffic forecasting competition. For consistency, the same Wikipedia pages that were used in the competition have been used in this dataset as well. The colons (:) in article names have been replaced by dashes (-) to make the .tsf file readable using our data loaders.

The data were downloaded from the Wikimedia REST API. According to the conditions of the API, this dataset is licensed under CC-BY-SA 3.0 and GFDL licenses.

This dataset contains 145063 time series representing the number of hits or web traffic for a set of Wikipedia pages from 2015-07-01 to 2022-06-30. This is an extended version of the dataset that was used in the Kaggle Wikipedia Web Traffic forecasting competition. For consistency, the same Wikipedia pages that were used in the competition have been used in this dataset as well. The colons (:) in article names have been replaced by dashes (-) to make the .tsf file readable using our data loaders.

The original dataset contains missing values. They have been simply replaced by zeros.

The data were downloaded from the Wikimedia REST API. According to the conditions of the API, this dataset is licensed under CC-BY-SA 3.0 and GFDL licenses.

Traffic and road condition information captured in the QLDTraffic system is available for use by external developers via GeoJSON feeds.

These feeds cover Hazards, Crashes, Congestion, Flooding, Roadworks and Special Events and Web Cameras details.

The information provided in these feeds is on an 'as is' basis. Additional details about the available information on the QLDTraffic site can be viewed on our disclaimer page .

Transport and Main Roads (TMR) is constantly striving to ensure that they provide accurate, reliable and timely traffic and road condition information.

Given this, the previously available API has undergone changes in August 2016 with the creation of the QLDTraffic public website.

Details on accessing QLDTraffic’s traffic and road condition information via GeoJSON can be found in the QLDTraffic website application programming interface (API) specification.

This API has been developed to allow improved integration of QLDTraffic traffic and road condition information with external systems.

Please be aware that this specification may be subject to change.

For detailed information regarding the Traffic API, see the Interactive Traffic Map website from the Traffic and Parking website.Traffic WebCam APIProvides images for the City of Ottawa’s traffic web cams. These images are available at sixty second intervals and are approximately 30-50KB in size. To access the images users will be required to have an access key. The application form for access keys can be found on this page: http://trafficopendata.ottawa.ca/ts/rsadmin/certificate.jsp

After completing the registration form and receiving a confirmation email with a certificate number you will be able to access the camera images. To access a camera image you can access the URL http://traffic.ottawa.ca/opendata/camera with the following parameters:

Camera number Certificate: The certificate string as supplied in the confirmation email. Id: User Id (optional).

Note: City of Ottawa cameras have camera numbers less than 2000, and MTO cameras have camera numbers greater than 2000.

Note: The Id is a string value assigned by your user to each user or instance of your application accessing the images. The Id must be alphanumeric characters [a-z, A-Z, 0-9]. A given user id for a given certificate may only access the cameras at intervals of at least 60 seconds.

e.g. To access City Camera 16 (Bank and Hunt Club) -- http://traffic.ottawa.ca/opendata/camera?c=16&certificate=CERT123&id=2

e.g. To access MTO Camera 2002 (St Laurent) -- http://traffic.ottawa.ca/opendata/camera?c=2002&certificate=CERT123&id=1

The images Getting Camera Numbers

To obtain a list of camera numbers you can access a JSON list of the available cameras: http://traffic.ottawa.ca/map/camera_list

More information about the format of the list can be found in the following document: http://traffic.ottawa.ca/map/opendata_info

Accuracy: There are no known errors associated with these images. Update Frequency: N/A - API delivers most up to date information available.Contact: Motaz Aladas

Due to unforeseen circumstances, this service is temporarily out of order. We are sorry for the trouble this may cause you. We are working hard to restore the service as soon as possible, but we cannot provide an estimated time of resolution at the moment.Network operations traffic data from Main Roads Western Australia from 01 January 2013. The data from this API includes data collected on the Perth Metropolitan State Road Network (PMSRN) at 15 minute intervals. The network operations traffic data provided here is of variable quality and has not been checked, quality assured or manually corrected. An automated process is used to patch over missing or suspect data with the most representative data available within the database. Patches may be reapplied as new data becomes available and patched data may change over time. Note that you are accessing this data pursuant to a Creative Commons (Attribution) Licence which has a disclaimer of warranties and limitation of liability. You accept that the data provided pursuant to the Licence is subject to changes. Pursuant to section 3 of the Licence you are provided with the following notice to be included when you Share the Licenced Material: “The Commissioner of Main Roads is the creator and owner of the data and Licenced Material, which is accessed pursuant to a Creative Commons (Attribution) Licence, which has a disclaimer of warranties and limitation of liability.” Instructions and documentation for using this API: Links Reporting Links: publicirisservices.mainroads.wa.gov.au/RoadNetworkPerformanceService/api/ReportingLinks Link Data: publicirisservices.mainroads.wa.gov.au/RoadNetworkPerformanceService/api/LinkData?linkdatadate=2017-9-1

TomTom's Safety Related Traffic Information (SRTI) API is a webservice that delivers anonymized non-personal raw data on hazardous situations directly collected by TomTom's own applications. The content of the API includes anonymized, non-personal, crowd-sourced data from drivers using TomTom's AmiGO application that reports 'hazards' and 'broken down car' incidents on the road. In accordance with EU Regulation 886/2013 this data is accessible to other users and can be integrated in other applications to improve road safety conditions. The access and use of this data are laid out in our terms and conditions. The service delivers safety messages for the area of the European Union in the form of a RESTful web service. The content contains information based on sensor or end-user feedback.

The Traffic and Travel Data System API lets you access real time data on events / incidents that affect traffic conditions across the network of national highways in New Zealand. An example of an event/incident could include road works, an accident, or weather related problems such as ice or snow.Traffic and Travel Data System API services currently include:· Real time data on traffic conditions and congestion on national highways.· Estimates of the time required for vehicles to travel along sections of the state highway and arterial network.· Real time data on events and incidents, including weather and general warnings, that affect traffic conditions across the network of national state highways.· Static images from over 100 cameras across various parts of New Zealand.· Messaging displayed on Variable Message Signs (VMS) across various parts of New Zealand.Available RESTful API services· Endpoint address: https://trafficnz.info/service/traffic/rest/4· WADL: https://trafficnz.info/service/traffic/rest/4?_wadlWe have several SOAP API services available as well. Details are described at this site: https://www.nzta.govt.nz/traffic-and-travel-information/use-our-data/about-the-apis/Usage CaveatsThis information is ONLY for notable events and/or incidents that may cause delays to road users or require caution, and only where the details have been verified by the Waka Kotahi or another official source.Data QualityAs of 3 October 2024, previous known quality issues have been repaired where there were null or missing values. These fields are now showing valid values: - Event Comment - Alternative Route - Event ModifiedResourcesThis data service is intended for data architects and developers that must integrate their applications with the Traffic and Travel Data web services API.Data elements included in each API Service are listed on the NZTA information page: https://www.nzta.govt.nz/traffic-and-travel-information/use-our-data/about-the-apis/ We are happy to have your feedback on this NZTA Open Data product. Please contact us at opendata@nzta.govt.nz.

You can also access an API version of this dataset.

TMS

(traffic monitoring system) daily-updated traffic counts API

Important note: due to the size of this dataset, you won't be able to open it fully in Excel. Use notepad / R / any software package which can open more than a million rows.

Data reuse caveats: as per license.

Data quality

statement: please read the accompanying user manual, explaining:

how

 this data is collected identification 

 of count stations traffic 

 monitoring technology monitoring 

 hierarchy and conventions typical 

 survey specification data 

 calculation TMS 

 operation. 

Traffic

monitoring for state highways: user manual

[PDF 465 KB]

The data is at daily granularity. However, the actual update

frequency of the data depends on the contract the site falls within. For telemetry

sites it's once a week on a Wednesday. Some regional sites are fortnightly, and

some monthly or quarterly. Some are only 4 weeks a year, with timing depending

on contractors’ programme of work.

Data quality caveats: you must use this data in

conjunction with the user manual and the following caveats.

The

 road sensors used in data collection are subject to both technical errors and 

 environmental interference.Data 

 is compiled from a variety of sources. Accuracy may vary and the data 

 should only be used as a guide.As 

 not all road sections are monitored, a direct calculation of Vehicle 

 Kilometres Travelled (VKT) for a region is not possible.Data 

 is sourced from Waka Kotahi New Zealand Transport Agency TMS data.For 

 sites that use dual loops classification is by length. Vehicles with a length of less than 5.5m are 

 classed as light vehicles. Vehicles over 11m long are classed as heavy 

 vehicles. Vehicles between 5.5 and 11m are split 50:50 into light and 

 heavy.In September 2022, the National Telemetry contract was handed to a new contractor. During the handover process, due to some missing documents and aged technology, 40 of the 96 national telemetry traffic count sites went offline. Current contractor has continued to upload data from all active sites and have gradually worked to bring most offline sites back online. Please note and account for possible gaps in data from National Telemetry Sites. 

The NZTA Vehicle

Classification Relationships diagram below shows the length classification (typically dual loops) and axle classification (typically pneumatic tube counts),

and how these map to the Monetised benefits and costs manual, table A37,

page 254.

Monetised benefits and costs manual [PDF 9 MB]

For the full TMS

classification schema see Appendix A of the traffic counting manual vehicle

classification scheme (NZTA 2011), below.

Traffic monitoring for state highways: user manual [PDF 465 KB]

State highway traffic monitoring (map)

State highway traffic monitoring sites

Explore Serpstat's Backlinks API Insights, providing real-time access to comprehensive backlink data at the lowest possible cost. With pricing starting at just $120 for 1M API Data rows, our API offers unparalleled value for businesses of all sizes.

With seamless integration and no separation between fresh and historical records, our API provides a holistic view of backlink profiles, encompassing 1.7 trillion links and 170 million domains. Plus, with no API credits burnout at the end of the month, you can use the API without constraints.

Preliminary research efforts regarding Social Media Platforms and their contribution to website traffic in LAMs. Through the Similar Web API, the leading social networks (Facebook, Twitter, Youtube, Instagram, Reddit, Pinterest, LinkedIn) that drove traffic to each one of the 220 cases in our dataset were identified and analyzed in the first sheet. Aggregated results proved that Facebook platform was responsible for 46.1% of social traffic (second sheet).

Current status of the Live Traffic NSW website in JSON format

TRIMARC (Traffic Response and Incident Management Assisting the River City) camera locations in Louisville Metro Kentucky. This feature layer was created from a TRIMARC JSON files of camera locations. This item includes description, direction, and videos links and is used in the Louisville Metro Snow Map. The cameras are used to monitor the roadways and verify incidents to assist in freeway and incident management This feature is a static extract and will be reviewed before each snow season for updates. For more information on this feature layer and it's use please contact Louisville Metro GIS or LOJIC. To learn more about TRIMARC please visit the following website http://www.trimarc.org.

NOTE: The Historic Traffic Data Dashboard & Feature Hosted Service have been retired.Network operations traffic data from Main Roads Western Australia for 2015 to 2019. The data provided includes data collected on the Perth Metropolitan State Road Network (PMSRN) at 15 minute intervals.

The Historic Traffic Data is provided in CSV format per year. Each table has over 34 million rows and can be linked to the M-Links Road Network using the M-Links ID. A data dictionary for M-Links Road Network and the Historic Traffic Data is at the following link:https://bit.ly/2S86uSnNetwork Operations traffic data can also be accessed via the Daily Traffic Data API at the following link: https://bit.ly/34ZsyAK

The network operations traffic data provided here is of variable quality and has not been checked, quality assured or manually corrected. An automated process is used to patch over missing or suspect data with the most representative data available within the database. Patches may be reapplied as new data becomes available and patched data may change over time.

Note that you are accessing this data pursuant to a Creative Commons (Attribution) Licence which has a disclaimer of warranties and limitation of liability. You accept that the data provided pursuant to the Licence is subject to changes.

Pursuant to section 3 of the Licence you are provided with the following notice to be included when you Share the Licenced Material:- “The Commissioner of Main Roads is the creator and owner of the data and Licenced Material, which is accessed pursuant to a Creative Commons (Attribution) Licence, which has a disclaimer of warranties and limitation of liability.”

This dataset consists of 24-hour traffic volumes which are collected by the City of Tempe high (arterial) and low (collector) volume streets. Data located in the tabular section shares with its users total volume of vehicles passing through the intersection selected along with the direction of flow.Historical data from this feature layer extends from 2016 to present day.Contact: Sue TaaffeContact E-Mail: sue_taaffe@tempe.govContact Phone: 480-350-8663Link to embedded web map:http://www.tempe.gov/city-hall/public-works/transportation/traffic-countsLink to site containing historical traffic counts by node: https://gis.tempe.gov/trafficcounts/Folders/Data Source: SQL Server/ArcGIS ServerData Source Type: GeospatialPreparation Method: N/APublish Frequency: As information changesPublish Method: AutomaticData Dictionary

This web feature service transports data from the Digital Basic Landscape Model (ATKIS Base DLM) of the state of Rhineland-Palatinate according to the alternative data format Shape. The focus is on uncomplicated usability without the requirement to map the full range of performance of the original data in NAS format. The landscape is divided into meshes in the basic DLM by the network of roads, roads, rail-bound traffic routes and water bodies. These are filled seamlessly and without redundancy by surface-shaped objects from the real use area (settlement, traffic, vegetation and water bodies).

This dataset provides detail on how all assets on a domain are being used (e.g. views, downloads, API reads).

User activity is provided by date, asset uid, asset type, asset name, access type and user segment. Please see Site Analytics: Asset Access for more detail about these fields.

The dataset will reflect new Asset Access records within a day of when they occur.

Content

Web traffic statistics for the top 2000 most visited pages on nyc.gov by month.

Context

This is a dataset hosted by the City of New York. The city has an open data platform found here and they update their information according the amount of data that is brought in. Explore New York City using Kaggle and all of the data sources available through the City of New York organization page!

• Update Frequency: This dataset is updated quarterly.

Acknowledgements

This dataset is maintained using Socrata's API and Kaggle's API. Socrata has assisted countless organizations with hosting their open data and has been an integral part of the process of bringing more data to the public.

NOTE: The Historic Traffic Data Dashboard & Feature Hosted Service have been retired.Network operations traffic data from Main Roads Western Australia for 2015 to 2019. The data provided includes data collected on the Perth Metropolitan State Road Network (PMSRN) at 15 minute intervals. The Historic Traffic Data is provided in CSV format per year. Each table has over 34 million rows and can be linked to the M-Links Road Network using the M-Links ID. A data dictionary for M-Links Road Network and the Historic Traffic Data is at the following link:https://bit.ly/2S86uSnNetwork Operations traffic data can also be accessed via the Daily Traffic Data API at the following link: https://bit.ly/34ZsyAK The network operations traffic data provided here is of variable quality and has not been checked, quality assured or manually corrected. An automated process is used to patch over missing or suspect data with the most representative data available within the database. Patches may be reapplied as new data becomes available and patched data may change over time. Note that you are accessing this data pursuant to a Creative Commons (Attribution) Licence which has a disclaimer of warranties and limitation of liability. You accept that the data provided pursuant to the Licence is subject to changes. Pursuant to section 3 of the Licence you are provided with the following notice to be included when you Share the Licenced Material:- “The Commissioner of Main Roads is the creator and owner of the data and Licenced Material, which is accessed pursuant to a Creative Commons (Attribution) Licence, which has a disclaimer of warranties and limitation of liability.”