PAL | Third-Party Script Inventory avatar

PAL | Third-Party Script Inventory

Pricing

from $5.00 / 1,000 completed third party script audits

Go to Apify Store
PAL | Third-Party Script Inventory

PAL | Third-Party Script Inventory

Inventory first-party and external script hosts in public static HTML. Export script-host findings for website migration and vendor QA. Try a ready-to-run Example task. No JavaScript execution.

Pricing

from $5.00 / 1,000 completed third party script audits

Rating

0.0

(0)

Developer

Practical AI Lab

Practical AI Lab

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

19 hours ago

Last modified

Categories

Share

PAL Third Party Script Audit

Demo transparency: the prefilled public Apify-hosted HTML is a synthetic PAL test fixture. It contains no real product reviews, stock assertions, marketing campaign performance or customer data. Replace the sample with your own public HTTPS URLs for production checks.

Start here: understand which script hosts a public page references

For website owners and technical operations teams: get an exportable inventory of JavaScript source hosts before a CMS migration, tag-manager cleanup, vendor change or privacy review. This is a static script inventory, not a vulnerability scan.

Paste public page URLs in the Input tab:

{"urls":["https://api.apify.com/v2/key-value-stores/DHMHtotPcN9CAKXYj/records/complete.html"]}

Each audited page returns details.scriptCount, details.hostCounts and details.thirdPartyHostCount. Export the Dataset to CSV/JSON to compare counts after changes. The synthetic sample includes one third-party hostname and one same-origin script reference. Substitute your actual public page to inventory real vendor references.

Useful interpretation: a third-party host is a hostname different from the page origin. It is not necessarily malicious. This tool cannot see JavaScript-injected network traffic, browser requests, cookies, consent compliance or real-world security risk.

Related PAL workflow: review website link security separately; for product pages, use ecommerce listing QA.

Count first- and third-party script hosts embedded in static HTML.

Ideal users and practical workflow

Best for: web administrators and technical QA teams.

What it checks: Count first- and third-party script hosts embedded in static HTML. Upload a short list of public HTTPS URLs to receive an individual evidence-based record and issue flags per page. Review the flagged URLs first, then export the Dataset as JSON or CSV for your team's workflow.

When it is useful: Before deploying front-end changes or when reviewing public security-related markup. This is not a penetration test.

What it does not do: It does not crawl an entire website automatically, render JavaScript, guarantee a search ranking, or change the target site. Check the exact limitations below before purchasing runs.

Why use this PAL Actor?

Get a structured, repeatable report for this specific issue without opening dozens of webpages by hand. Each input URL is analyzed independently. The output identifies data found on the page and flags likely omissions for manual review. Save output in Apify Dataset and export to JSON, CSV or Excel.

Practical use cases

Built for: web operations teams, website auditors and engineering teams.

  • Spot the issue: Count first- and third-party script hosts embedded in static HTML. See machine-readable results for each submitted public URL.
  • Prioritize corrections: use issues, issueCount and details to decide which pages merit human review.
  • Repeat as needed: rerun the same URL list after editing page markup to compare findings.

What makes this tool useful?

Focused on Third Party Script Audit, rather than requiring a full-site crawling subscription. Export results to a spreadsheet, CSV or a data pipeline; connect via Apify API where appropriate. The tool processes static HTML and embedded metadata, with no client-side browser, API keys or private-page logins.

Important: each URL is a separate charged successful audit event at the rate visible in Apify Store. A missing signal is an observation, not a legal or search-engine verdict. If your site renders important data only with JavaScript, that data may not appear in the result.

How this fits with other Practical AI Lab (PAL) tools

For ecommerce projects, start with PAL Product Price & Stock Snapshot and follow with PAL Product GTIN & SKU SEO Auditor to inspect identifiers. For storefront trust information, use PAL Store Policy Link Mapper before reviewing return or shipping schema. These are independent PAL tools; there is no bundle requirement.

Example input

{"urls": ["https://api.apify.com/v2/key-value-stores/DHMHtotPcN9CAKXYj/records/complete.html"]}

Results

Each successful fetch produces a Dataset row with sourceUrl, finalUrl, mode, issueCount, issues and details. Issue flags indicate markup detected in static HTML; they are not a guarantee of legal compliance, accessibility certification, search rank, or a live inventory position. Missing data can be published through JavaScript or other channels not read here.

Billing

Pay per event: pal-scripts is triggered for each successfully fetched and audited page at the price displayed by Apify Store. URL errors generate a free error row. Maximum 18 URLs per run. No paid API keys, logins, or third-party services required.

Technical limits

Public HTTPS only; no JavaScript rendering, captcha bypass or private pages. Each response is at most 1.5 MB, 11-second network timeout. The site may block bots. Output reflects visible HTML at retrieval time, not a complete website audit. Running the Actor does not itself fix issues.

More Practical AI Lab (PAL) tools

Use independent PAL tools in a natural sequence: first capture price and stock, then audit the corresponding product markup; or locate policy links and inspect returns/shipping markup. Each Actor is separately usable, with no mandatory bundle.

Browse the PAL developer profile for additional focused audit tools.


Practical AI Lab | Catalog product 48 | SECURITY