# Website Status, SEO, Tech & Contact Checker (`quarterredwing_prog/meter-api`) Actor

Check any list of URLs: live or dead, HTTP status, redirects, title, meta tags, CMS, analytics IDs, emails, phones and social profiles. Clean JSON, $1 per 1,000 URLs, invalid URLs free.

- **URL**: https://apify.com/quarterredwing_prog/meter-api.md
- **Developed by:** [Bryan Donbavand](https://apify.com/quarterredwing_prog) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.70 / 1,000 url analyseds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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):

```json
{
  "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.

# Actor input Schema

## `urls` (type: `array`):

The websites to check, one per line, for example https://example.com. Each must be a public http or https URL. Duplicates are checked once, and invalid URLs are listed in the results without charge.

## `maxConcurrency` (type: `integer`):

How many URLs to check at the same time. The default of 5 suits most lists; raise it for large lists.

## Actor input object example

```json
{
  "urls": [
    "https://example.com",
    "https://www.wikipedia.org"
  ],
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

All results as JSON, one item per input URL. Items with an error field were invalid input and were not charged.

## `overview` (type: `string`):

The key fields per URL: URL, live, status, title, CMS, emails, phones, social profiles, bot protection and errors.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://example.com",
        "https://www.wikipedia.org"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("quarterredwing_prog/meter-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": [
        "https://example.com",
        "https://www.wikipedia.org",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("quarterredwing_prog/meter-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://example.com",
    "https://www.wikipedia.org"
  ]
}' |
apify call quarterredwing_prog/meter-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quarterredwing_prog/meter-api"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/fdFCqMrOti7gFdiRw/builds/5mZ8MnihMaHNmnZCZ/openapi.json