Public Website Metadata Audit

What does Public Website Metadata Audit do?

Public Website Metadata Audit checks the public metadata of up to 10 web pages and returns one structured record per URL. It extracts the page title, meta description, canonical URL, robots directive, H1 headings, Open Graph and Twitter tags, HTTP status, and selected security headers. Try it with https://example.org/ in the Input tab. Results are stored in an Apify dataset and are available through Apify's API, schedules, and integrations.

Why use it?

Use the Actor to inspect landing pages before publication, verify social preview tags, or compare metadata after a site change. The compact JSON is convenient for another automation or agent. The Actor uses direct HTTP requests and Cheerio, with no browser, proxy, AI model, authenticated session, or paid external API.

How to use it

1. Open the Actor's Input tab and enter one to 10 public HTTP or HTTPS URLs.
2. Start a run, then open the dataset linked from the Output tab.
3. Download the dataset as JSON, CSV, HTML, or Excel, or read it through the Apify API.

Start with one URL and set a maximum run cost in Apify Console if you want a small trial. The Actor does not follow page links. It checks robots.txt before each page request, including redirect destinations.

Input

{"startUrls":[{"url":"https://example.org/"}]}

startUrls is required. The Actor rejects URLs containing credentials, local or private network destinations, and custom ports. It reads at most 1 MB of HTML per page and waits at most eight seconds for each HTTP request.

Output

One dataset item is written per input URL. A simplified successful result is:

{"requestedUrl":"https://example.org/","status":"ok","finalUrl":"https://example.org/","httpStatus":200,"title":"Example Domain","h1":["Example Domain"]}

Other statuses include excluded_by_robots, unsupported_content_type, http_error, and error. The Actor stores metadata and diagnostics, never raw page HTML.

Data table

Field	Meaning
requestedUrl, finalUrl	Requested and final page URL
status, httpStatus	Outcome and HTTP response code
title, description, canonical, robots	Search metadata
h1, openGraph, twitter	Heading and social preview metadata
headers, inspectedAt	Header observations and UTC time

Pricing and cost estimation

The Actor is published on Apify Store with Pay per event pricing: $0.01 for each apify-default-dataset-item result and the standard $0.00005 apify-actor-start event. Actor.pushData() triggers the dataset event automatically; the code adds no second charge. Memory is fixed at 256 MB and each run accepts at most 10 pages. Check the actual price and resource cost in Apify Console. Apify calculates developer profit for paying users as 80% of event revenue minus platform usage costs. No customer payment or positive margin has been demonstrated yet.

Tips and limits

Use public pages whose terms allow automated access. The Actor honors robots.txt, does not sign in, and does not render JavaScript. Metadata inserted only after browser execution may be missing. Some sites may block automated HTTP requests. Pages are processed sequentially to avoid unnecessary load.

FAQ and support

Is this a full SEO or security audit? No. It reports observable metadata and selected header presence.

Can it access private URLs? No. It rejects private addresses and checks redirect targets.

Where can I report a problem? Use the Actor's Issues tab after publication and include a public example URL. Do not post credentials or private URLs.

Local development

Use Node.js 22. Run npm ci, npm test, and npm start. This repository is linked to Apify through GitHub and automatically builds on a push to main.