Website Status, SEO, Tech & Contact Checker

Check any list of URLs for status, SEO metadata, technology and public contact details, in one run.

Paste in a list of websites and get one clean row of data for each: whether the site is live, its HTTP status and redirects, page title, meta description, canonical URL, robots directives, Open Graph tags, Schema.org types, CMS, analytics IDs, and any public email addresses, phone numbers and social profiles.

No browser, no proxies to configure and no HTML parsing on your side. Most URLs come back in well under a second.

What you can use it for

• Cleaning lead and company lists. Find out which websites in a CRM export are dead, redirected or parked, and pick up public contact details from the ones that are live.
• SEO audits at scale. Check titles, meta descriptions, canonicals, robots tags and structured data across hundreds of pages or competitor sites.
• Technology research. See which sites run WordPress, Shopify, Webflow and other platforms, and which use GA4, Google Tag Manager, Meta Pixel, Hotjar and similar tools.
• Monitoring. Run it on a schedule to spot sites that go down, change their title or start redirecting.
• AI agents and automations. Every result has the same predictable JSON shape, which makes it easy to use from Make, Zapier, n8n, LangChain or any agent through the Apify API and MCP server.

Input

Field	Description
Website URLs	The sites to check, one per line. Each must be a public http or https URL. Duplicates are checked once.
Parallel checks	How many URLs to check at the same time (1 to 20, default 5).

Output

One dataset item per URL. A live site looks like this (shortened):

{
  "requested_url": "https://example.com/",
  "reachable": true,
  "fetch_error": null,
  "bot_protection": null,
  "final_url": "https://www.example.com/",
  "redirects": ["https://example.com/"],
  "http_status": 200,
  "response_time_ms": 142,
  "title": "Example Domain",
  "meta_description": "An example site.",
  "canonical_url": "https://www.example.com/",
  "schema_types": ["Organization", "WebSite"],
  "cms": { "name": "WordPress", "version": "6.6.2", "evidence": ["meta generator: WordPress 6.6.2"] },
  "analytics": [{ "platform": "Google Analytics 4", "id": "G-ABC123XYZ9" }],
  "emails": ["info@example.com"],
  "phone_numbers": ["+44 1772 123456"],
  "social_profiles": [{ "platform": "LinkedIn", "url": "https://www.linkedin.com/company/example/" }]
}

Dead and unreachable sites

A site that does not exist, times out, refuses the connection or redirects in a loop is still a result, not a failure. reachable is false and fetch_error says why, for example host_not_found, dns_error, too_many_redirects, upstream_fetch_failed or upstream_timeout. One bad URL never stops a run.

Bot protection

Some sites answer automated requests with a block or challenge page. When that happens, bot_protection names the provider (such as Cloudflare or DataDome) so you know the page fields describe the block page rather than the real site. This Actor does not try to get around these protections.

Invalid input

A malformed or private URL is recorded with an error field and is not charged.

Pricing

You pay per URL analysed, including dead sites, because "this site is unreachable" is a useful answer. Invalid URLs are free. Set a maximum cost per run in the run options and the Actor stops as soon as it is reached.

How it works

Each URL is fetched once, following at most five redirects, and only the first 2 MiB of HTML is read. No cookies or credentials are sent, and private or internal addresses are refused. The fetcher identifies itself as meter-api, with an information page for site owners at https://meter-api.quarterredwing.workers.dev/bot.

Also available as an API

The same data is available as a REST API on RapidAPI under the name meter-api, with a free plan of 100 calls a month.