Site Diagnostics by Acinsoft

Website diagnostics for APIs and automations

Diagnose a public web page or a small website crawl through one configurable API. Use structured evidence to review a website before delivery, investigate broken links or feed recurring technical checks into your automation workflow. Choose one page or a bounded crawl, select the checks you need, and pay for useful pages and new link observations delivered in the report.

If input is omitted, the Actor checks https://acinsoft.com/ with the bounded basic page profile. Replace that default with the public URL you intend to diagnose. The default keeps Console, API, scheduler and Store test runs executable.

Choose your checks

• basic: DNS, TLS and HTTP observations.
• seo: all five modules, including SEO and link checks.
• custom: choose dns, tls, http, seo and links explicitly.

Review one page's SEO and links

{
  "url": "https://example.com/",
  "profile": "custom",
  "modules": ["http", "seo", "links"],
  "mode": "page",
  "maximumLinks": 10
}

Review a small website crawl

{
  "url": "https://example.com/",
  "profile": "seo",
  "mode": "crawl",
  "maximumPages": 5,
  "maximumDepth": 1,
  "maximumLinks": 10
}

Page mode checks one URL. Crawl mode visits up to 10 pages, depth 2, on the final initial page's origin. Query-string links are excluded. DNS/TLS target the initial hostname; TLS probes port 443. Robots rules apply to page/link requests and redirects independently of SEO selection. Blocked pages are marked skipped; unavailable policy stops access. The report explains partial coverage.

SEO inspects server HTML, title, description, headings, canonical and robots signals. It interprets robots.txt, the conventional sitemap XML, HTML hreflang and JSON-LD syntax/selected structure. It reports precise limits: child sitemap indexes, reciprocal hreflang, schema vocabulary and rich-result eligibility require further evaluation. Browser performance and accessibility are planned extensions of this Actor. JavaScript rendering is outside this release.

Results and consumption

The Dataset contains one row with the complete report, including per-page results for crawls. OUTPUT adds integrity metadata, delivery status, observed event counts and the Platform receipt. A finding indicates observed evidence, not guaranteed health or indexability. A provider-recorded event is not a settled payment.

Pay-per-event pricing in USD:

Event	Quantity	Price per event
site-page-diagnosed	Useful page reports delivered	$0.003
site-link-checked	New successful link observations; HTTP error statuses are evidence	$0.0001
apify-actor-start	Starts recorded by Apify, including recovery starts	$0.00005

For configured page price P, link price L and start price S, the event amount is completed pages × P + new observed links × L + starts × S. A page without link checking contributes P; a five-page crawl with 30 new link observations contributes 5P + 30L, plus starts. Work limits are ceilings; the report's completed units determine result-event quantities. One page without links costs $0.00305 including one start. Ten useful pages and 200 new link observations cost $0.05005 including one start.

Reused link responses add zero link units. Transport failures and skipped pages add zero useful units. Technical quotas still count whole reports separately from these commercial units. Selecting additional modules can add link work; basic and SEO page observations share the configured page price in this initial contract.

maximumChargeUsd optionally tightens Apify's run budget. Both ceilings cover result events and starts. Reaching the work budget preserves completed results. The report's resultChargeUsd excludes starts. The private unpriced pilot accepts work limits, with the monetary input reserved for pay-per-event runs.

Delivery and recovery

The Actor validates original response bytes with SHA-256, saves an HMAC-signed checkpoint, verifies the Dataset row, prepares a receipt, then records page/link events with stable idempotency keys and confirms exact counts. Recovery preserves the original run, input, account and price contract. An ambiguous API execution or Dataset append requires reconciliation; an absent row alone does not authorize another append. Each event batch retains its original quantity and key. Partial observed counts remain pending rather than triggering an additional batch.

Keep CHECKPOINT and OUTPUT intact. ERROR records historical failures; successful recovery can subsequently complete OUTPUT. Automatic restart should be disabled. Cross-build recovery requires Platform's explicit compatibility process.

Operator configuration

Use 128 MiB and limited permissions. The Node wrapper calls Platform; Platform performs diagnostics. The timeout is 600 seconds for API work, delivery, two bounded event-observation windows and receipts.

Required secret variables: ACINSOFT_ACCOUNT_KEY and ACINSOFT_APIFY_BROKER_API_KEY. Set ACINSOFT_API_ORIGIN to the approved HTTPS origin and ACINSOFT_BILLING_MODE to private-pilot or pay-per-event. The paid contract additionally requires ACINSOFT_PAGE_PRICE_USD, ACINSOFT_LINK_PRICE_USD, ACINSOFT_START_PRICE_USD and ACINSOFT_PRICE_VERSION. These must match Platform's Tools:SiteDiagnostics:Apify configuration and Apify's three flat-price events; page/link events are repeatable. Prices are explicit, positive for page/link, nonnegative for start, up to eight decimal places.

The input contains job parameters; runtime credentials come from secret settings and Apify's limited run token. Diagnostic results and checkpoint data live in the run's Apify storage and the account-scoped Platform result store. URLs and observed site metadata form part of the report; use public targets appropriate to that storage scope. Secrets are excluded from reports and logs.

Free-plan consumers receive up to 10 useful reports per verified Apify consumer for this Tool over their lifetime, sharing a pool of 50 reports per rolling seven days. A paid Apify plan uses separate counters. Shared trial exhaustion preserves the individual's remaining allowance. Event prices and Apify credits still apply; the trial allowance is an execution quota, not a billing discount. Initial admission allows one concurrent execution shared by the integration account and up to 10 requests per minute per consumer. Each report can contain several billable pages and links. Recovery may add a start event while preserving the original report quantities.