# Meta Tag Checker: OG, Canonical, Robots & Deploy QA (`ferrolark/live-deploy-qa`) Actor

Meta tag checker and live deploy QA: check up to 20 deployed URLs over HTTP for status, redirects, title, canonical, noindex, robots.txt, Open Graph image, favicon and changes since the last deploy. Flags client-rendered pages. No scores. $0.003 per URL.

- **URL**: https://apify.com/ferrolark/live-deploy-qa.md
- **Developed by:** [Ferrolark](https://apify.com/ferrolark) (community)
- **Categories:** SEO tools, Developer tools, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 url auditeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Live Deploy QA: Meta Tags, OG, Canonical & Robots Check

Check what your deployed site actually serves, route by route, with plain HTTP requests. For up to 20 URLs per run you get:

- status code and the full redirect chain
- `<title>`, meta description, `<h1>`, `lang` and viewport
- canonical tag (missing, duplicated, or pointing to another host such as a leftover preview domain)
- `noindex` from meta robots or the `X-Robots-Tag` header, and whether `robots.txt` blocks the URL
- Open Graph and Twitter tags, plus a real download of `og:image` to check status, type and size in pixels
- the favicon actually loading
- **what changed since the last run**: title, canonical, robots, OG image, status and more

Each finding has a code, a severity and the exact evidence. There is **no invented "SEO score"**. When a page is client-rendered (an empty `#root` and little server HTML), it gets `needsBrowser: true` with the reasons, instead of a false pass.

Built for the moment after a deploy, from Lovable, Bolt, Replit, v0, Vercel, Netlify or your own CI: did the tags you expect really ship?

### Real example

This input (six public pages, one of them a deliberate 404):

```json
{
  "urls": [
    "https://htmx.org/",
    "https://htmx.org/docs/",
    "https://www.sitemaps.org/",
    "https://excalidraw.com/",
    "https://astro.build/",
    "https://htmx.org/does-not-exist"
  ]
}
```

took **4 s** on Apify (256 MB, $0.0004 of platform usage). Your cost for 6 URLs at $0.003 each is **$0.018**.

| URL | HTTP | Errors | Warnings | Needs browser | Main findings |
|---|---:|---:|---:|---|---|
| htmx.org/ | 200 | 0 | 2 | no | no og:image; description shared with /docs/ |
| htmx.org/docs/ | 200 | 0 | 2 | no | no og:image; description shared with the home page |
| sitemaps.org/ | 200 | 0 | 4 | no | no canonical, no viewport, /favicon.ico returns 404 |
| excalidraw.com/ | 200 | 0 | 1 | **yes** | client-rendered app shell; OG image 1200×675 loads |
| astro.build/ | 200 | 0 | 0 | no | none |
| htmx.org/does-not-exist | 404 | 1 | 2 | no | `http-error` |

The second run with the same input compared each route with the stored snapshot. All six came back `unchanged`.

One dataset row, shortened:

```json
{
  "url": "https://excalidraw.com/",
  "finalUrl": "https://excalidraw.com/",
  "statusCode": 200,
  "responseTimeMs": 59,
  "robotsTxtAllowed": true,
  "title": "Excalidraw Whiteboard",
  "metaDescription": "Excalidraw is a virtual collaborative whiteboard tool that lets you easily sketch diagrams that have a hand-drawn feel to them.",
  "canonical": "https://excalidraw.com",
  "robotsMeta": null,
  "htmlLang": "en",
  "og": {"title": "Excalidraw — Collaborative whiteboarding made easy", "image": "https://excalidraw.com/og-image-3.png", "type": "website"},
  "ogImageCheck": {"statusCode": 200, "contentType": "image/png", "bytes": 74022, "width": 1200, "height": 675},
  "faviconCheck": {"url": "https://excalidraw.com/favicon-32x32.png", "statusCode": 200, "contentType": "image/png", "declared": true},
  "visibleTextChars": 10,
  "needsBrowser": true,
  "needsBrowserReasons": [
    "empty app root (#root) with little server-rendered text",
    "only 10 characters of visible text with 6 script(s)",
    "noscript message asks to enable JavaScript"
  ],
  "issues": [{"code": "needs-browser", "severity": "warning", "message": "The HTML looks client-rendered (...)"}],
  "errorCount": 0,
  "warningCount": 1,
  "snapshotStatus": "unchanged",
  "changes": []
}
```

When something changes between deploys, `snapshotStatus` is `changed` and `changes` lists each field:

```json
[{"field": "canonical", "before": "https://www.example.com/pricing", "after": "https://example-git-main.vercel.app/pricing"},
 {"field": "robotsMeta", "before": null, "after": "noindex"}]
```

### Price and limits

- **$0.003 per URL audited.** You pay for each URL that returned an HTTP response, including 404 and 500, because those are findings too.
  - URLs that cannot be fetched at all (DNS failure, timeout, private address) are not charged.
  - There is no start fee.
- Up to 20 URLs per run, and the first 1 MB of HTML per URL.
- Up to 300 KB is read for `og:image` (enough for its dimensions) and 100 KB for the favicon.
- Per run, there is one `robots.txt` request per host and at most 4 parallel requests.
- It does not crawl: only the URLs you list are fetched.

### Findings reference

| Code | Severity | Meaning |
|---|---|---|
| `http-error` | error | Final status is 4xx or 5xx |
| `fetch-failed` | error | No HTTP response (not charged) |
| `title-missing` | error | No `<title>` in the HTML |
| `noindex` | error | Meta robots, googlebot or `X-Robots-Tag` says noindex or none |
| `robots-blocked` | error | `robots.txt` disallows the URL for `User-agent: *` |
| `canonical-multiple` | error | More than one canonical tag |
| `og-image-broken` / `og-image-not-image` | error | `og:image` does not load, or is not an image |
| `canonical-missing` | warning | No canonical tag |
| `canonical-other-host` | warning | Canonical on another host (preview domain, template leftover) |
| `og-image-missing` / `og-image-small` / `og-image-heavy` / `og-image-http` | warning | Social preview image problems |
| `favicon-broken` | warning | The declared icon, or `/favicon.ico`, does not load |
| `viewport-missing` | warning | No meta viewport |
| `description-missing` | warning | No meta description |
| `redirect-chain` / `not-https` | warning | More than 2 redirects, or the final URL on plain HTTP |
| `duplicate-title` / `duplicate-description` | warning | Same value as another audited route |
| `needs-browser` | warning | Client-rendered HTML; JavaScript-added tags are not visible to this check |
| `title-long`, `description-long`, `canonical-other-url`, `og-title-missing`, `og-description-missing`, `twitter-card-missing`, `lang-missing`, `h1-missing`, `temporary-redirect`, `not-html`, `html-truncated` | info | Worth a look; not necessarily wrong |

The length thresholds are display guidelines, not ranking rules. A finding is evidence about the HTML that was served. It is not a guarantee of indexing, ranking or how a social network will render the preview, because those platforms cache previews and have their own rules.

### Input

| Field | Default | What it does |
|---|---|---|
| `urls` | none | Up to 20 deployed URLs. |
| `baseUrl` + `paths` | none | Alternative input. Run the same routes against production and a preview deploy by changing only `baseUrl`. |
| `snapshotName` | host of the first URL | Which stored snapshot to compare with. Use, for example, `myapp-production` and `myapp-preview`. |
| `compareWithStoredSnapshot` | `true` | Report `changes` against the last run with the same name. |
| `saveSnapshot` | `true` | Store this run's values; routes not in this run are kept. |
| `checkOgImage` / `checkFavicon` / `checkRobotsTxt` | `true` | Turn off the extra requests you don't need. |

Snapshots live in your own Apify account, in the key-value store `live-deploy-qa-snapshots`.

### Call it from code, CI, n8n or an AI agent

**API (synchronous):**

```bash
curl -X POST "https://api.apify.com/v2/acts/ferrolark~live-deploy-qa/run-sync-get-dataset-items?maxTotalChargeUsd=0.06" \
  -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \
  -d '{"baseUrl": "https://www.example.com", "paths": ["/", "/pricing"], "snapshotName": "example-production"}'
```

**CI gate (GitHub Actions or any shell step):** the step fails the build when any route has an error.

```bash
ERRORS=$(curl -s -X POST "https://api.apify.com/v2/acts/ferrolark~live-deploy-qa/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \
  -d '{"baseUrl": "'"$DEPLOY_URL"'", "paths": ["/", "/pricing"]}' | jq '[.[].errorCount] | add')
test "$ERRORS" -eq 0
```

**n8n:** paste this workflow on the canvas (Ctrl+V). Then add a Header Auth credential with the name `Authorization` and the value `Bearer <your Apify token>`.

- Point your host's deploy hook at the webhook node.
- Rows with errors come out of the "true" branch, ready for a Slack or email node.

```json
{
  "name": "Live Deploy QA after each deploy",
  "nodes": [
    {"parameters": {"httpMethod": "POST", "path": "deploy-finished"}, "name": "Deploy webhook", "type": "n8n-nodes-base.webhook", "typeVersion": 2, "position": [0, 0]},
    {"parameters": {"method": "POST", "url": "https://api.apify.com/v2/acts/ferrolark~live-deploy-qa/run-sync-get-dataset-items?maxTotalChargeUsd=0.06", "authentication": "genericCredentialType", "genericAuthType": "httpHeaderAuth", "sendBody": true, "specifyBody": "json", "jsonBody": "{\"baseUrl\": \"https://www.example.com\", \"paths\": [\"/\", \"/pricing\", \"/blog\"], \"snapshotName\": \"example-production\"}", "options": {"timeout": 120000}}, "name": "Run Live Deploy QA", "type": "n8n-nodes-base.httpRequest", "typeVersion": 4.2, "position": [220, 0]},
    {"parameters": {"conditions": {"number": [{"value1": "={{ $json.errorCount }}", "operation": "larger", "value2": 0}]}}, "name": "Has errors?", "type": "n8n-nodes-base.if", "typeVersion": 1, "position": [440, 0]}
  ],
  "connections": {
    "Deploy webhook": {"main": [[{"node": "Run Live Deploy QA", "type": "main", "index": 0}]]},
    "Run Live Deploy QA": {"main": [[{"node": "Has errors?", "type": "main", "index": 0}]]}
  }
}
```

**Make / Zapier:** use the Apify app's "Run Actor" action with `ferrolark/live-deploy-qa`, then "Get dataset items".

**AI agents (MCP):** add `ferrolark/live-deploy-qa` to the Apify MCP server (`https://mcp.apify.com?actors=ferrolark/live-deploy-qa`). A coding agent can verify its own deploy and read the exact evidence back.

### Use cases

- **Right after a deploy:** catch a `noindex` left over from staging, a canonical pointing to the preview domain, or a broken OG image before you share the link.
- **Vibe-coded apps:** check whether Lovable, Bolt, Replit or v0 output serves real HTML tags, or needs a browser or pre-rendering.
- **Migrations and redesigns:** compare the same routes before and after, using `changes` from the snapshot.
- **Launch day:** the Product Hunt, X and LinkedIn previews depend on `og:image`, and this checks it actually loads at a sensible size.

### Troubleshooting

- **`needsBrowser: true` on your own app:** the server sends an empty shell and JavaScript builds the page. If your tags are added at runtime (for example with React Helmet), this check cannot see them, and neither can many link-preview bots. Use server-side rendering or pre-rendering, or set the tags in `index.html`.
- **`http-error` with 403 on a working site:** a firewall or bot protection is blocking automated requests. The check never bypasses protection; allow the user agent `Ferrolark-LiveDeployQA` or test a preview URL.
- **Preview deploys behind login** return 401 or a login page. Only public URLs can be checked.
- **Everything shows `new` again:** the `snapshotName` changed. Set it explicitly in scheduled tasks.

### Limitations

- Plain HTTP only: no JavaScript execution, screenshots, Lighthouse or Core Web Vitals.
- No crawling, form submission or login, and no security scanning.
- Social platforms cache previews: a fixed `og:image` can take time to show on X, LinkedIn or Slack.

### Changelog

- **1.0** (November 2026): first release. Status and redirects, head tags, canonical, robots and `X-Robots-Tag`, `robots.txt`, OG image download, favicon, duplicate titles, `needsBrowser` detection and snapshot diffs.

### More Ferrolark tools

- [Brand Name Availability Checker](https://apify.com/ferrolark/brand-name-checker): domains, GitHub, npm, PyPI and more in one report.
- [Domain Intelligence Report](https://apify.com/ferrolark/domain-intelligence-report): WHOIS, DNS, email security, SSL and hosting for any domain.
- [Launch Asset Pack](https://apify.com/ferrolark/launch-asset-pack): favicons, PWA icons, OG image and head tags from one logo.
- [Sitemap Delta](https://apify.com/ferrolark/sitemap-delta): new, removed and broken URLs in any sitemap since the last run.
- [RSS Delta](https://apify.com/ferrolark/rss-delta): only new RSS, Atom and JSON Feed items, de-duplicated.
- [PDF Merge API](https://apify.com/ferrolark/pdf-merge-api): merge PDFs from URLs or base64 with page ranges and a SHA-256 manifest.
- [PDF Split API](https://apify.com/ferrolark/pdf-split-api): split a PDF by page ranges or every N pages, or extract pages, with a ZIP and manifest.
- [Image Convert](https://apify.com/ferrolark/image-convert): PNG, JPG, WebP, AVIF and HEIC conversion (SVG input too) from URLs or base64.
- [Image Compress & Resize](https://apify.com/ferrolark/image-compress-resize): resize images and compress them to a target size in KB, WebP or AVIF.
- [PDF to Image](https://apify.com/ferrolark/pdf-to-image): PDF pages to PNG, JPG or WebP at the DPI you choose.
- [Image to PDF](https://apify.com/ferrolark/image-to-pdf): JPG, PNG, HEIC and WebP images to one PDF, JPEGs embedded without recompression.
- [PDF Compress](https://apify.com/ferrolark/pdf-compress): smaller PDFs, lossless or with image downsampling; charged only when smaller.
- [HTML to PDF & URL to PDF](https://apify.com/ferrolark/html-to-pdf): web pages or raw HTML to PDF with headless Chrome.
- [Markdown to PDF](https://apify.com/ferrolark/markdown-to-pdf): Markdown with tables, code and footnotes to a clean PDF.
- [DOCX to PDF](https://apify.com/ferrolark/docx-to-pdf): Word, Excel, PowerPoint and ODT to PDF with LibreOffice.
- [Data Convert](https://apify.com/ferrolark/data-convert): CSV, JSON, NDJSON and Excel XLSX in any direction.

***

*Built by Ferrolark.*

# Actor input Schema

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

Up to 20 public URLs of your deployed site (home, pricing, blog post...). Only plain HTTP GET requests are made: no browser, no forms, no crawling.

## `baseUrl` (type: `string`):

Alternative to full URLs: a base such as https://my-app.vercel.app combined with the paths below. Handy for checking a preview deploy with the same routes.

## `paths` (type: `array`):

Paths joined to the base URL, for example /, /pricing, /blog/hello-world.

## `snapshotName` (type: `string`):

Name of the saved snapshot to compare against and update. Defaults to the host of the first URL.

## `compareWithStoredSnapshot` (type: `boolean`):

Report what changed (title, canonical, robots, OG tags, status...) since the last run with the same snapshot name.

## `saveSnapshot` (type: `boolean`):

Store the checked fields for the next comparison (key-value store "live-deploy-qa-snapshots" in your account).

## `checkOgImage` (type: `boolean`):

Download up to 300 KB of the og:image to check status, type and dimensions.

## `checkFavicon` (type: `boolean`):

Check the declared icon, or /favicon.ico when none is declared.

## `checkRobotsTxt` (type: `boolean`):

Read robots.txt once per host and report URLs disallowed for all crawlers.

## Actor input object example

```json
{
  "urls": [
    "https://htmx.org/",
    "https://htmx.org/docs/"
  ],
  "compareWithStoredSnapshot": true,
  "saveSnapshot": true,
  "checkOgImage": true,
  "checkFavicon": true,
  "checkRobotsTxt": true
}
```

# Actor output Schema

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

No description

## `summary` (type: `string`):

No description

# 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://htmx.org/",
        "https://htmx.org/docs/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ferrolark/live-deploy-qa").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://htmx.org/",
        "https://htmx.org/docs/",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("ferrolark/live-deploy-qa").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://htmx.org/",
    "https://htmx.org/docs/"
  ]
}' |
apify call ferrolark/live-deploy-qa --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ferrolark/live-deploy-qa"
        }
    }
}
```

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/HOIkmF4ddwFcypuLw/builds/XSHKOR6qGzTV28uAr/openapi.json
