Website Tech Stack Detector - Evidence & Change Tracking

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Documentation captured from build 1.0.6. Example outputs retain their original sample context; they are not live results.

Technology signals with evidence

For website-portfolio reviews and company-list segmentation, identify supported visible technology signals and keep the evidence behind each match.

Coverage: Public HTML and response headers from up to three supplied pages per website. No automatic crawl or browser execution.

Open this Actor in Console · First run · Results · Cost · Full guide

Try this Actor

1. Use the existing WordPress and Next.js two-site example below, with comparison off, to inspect the evidence returned for each site.
2. Open the dataset's overview and evidence views; check the key-value store's SUMMARY for incomplete or failed website scopes.

Read the results correctly: A signal does not verify a subscription or actual usage. A completed zero-signal check is still a result and does not prove a technology is absent.

Copyable input — use the JSON editor in Console.

{
  "websites": [
    { "url": "https://wordpress.org/", "externalId": "wordpress-demo" },
    { "url": "https://nextjs.org/", "externalId": "nextjs-demo" }
  ]
}

Result preview

The first dataset view highlights these columns; the guide below explains additional views and row types:

• Website · url
• Your reference ID · externalId
• Inspection result · status
• Observed technology count · technologyCount
• Observed technologies · technologyNames
• Supplied pages inspected · pageCount

Use the original source links and the field definitions below when interpreting the results. CSV works well for flat columns; JSON preserves nested values.

Usage and pricing

Base result rate on the FREE tier: $5 per 1,000 website observations. The Pricing tab shows your plan's result rate and any Actor Start charge. Set a small result limit for the first run; the requested limit is not a guarantee of that many results.

Full guide

Give this Actor a list of public websites. It reads their HTML and response headers, then returns supported technology signals with the exact asset, header or HTML attribute behind each finding. Use the results to segment supplied company lists, review a website portfolio, or compare the same pages on a schedule.

It supports CMS and ecommerce systems, frameworks, analytics, advertising, customer support, payments and hosting signals. Your own externalId travels with each result so you can join the output to existing records. No external API key is required.

Start with two public examples

Use the copyable first-run input above.

An omitted or empty websites array runs this two-site demo. No automatic site crawl occurs. You can supply up to 100 websites and at most two additional pages on each website's original origin:

{
  "websites": [
    {
      "url": "https://wordpress.org/",
      "externalId": "site-123",
      "additionalUrls": ["https://wordpress.org/about/", "https://wordpress.org/news/"]
    }
  ],
  "maxRunSeconds": 240
}

Reading supplied inner pages helps find tools not visible on the homepage. Every supplied page must be inspected successfully for that website to enter the result dataset. A failed page is recorded in SUMMARY; the incomplete website is not billed as a result or used to update history.

Output

Each successful website check produces one record. A simplified illustrative result:

{
  "url": "https://nextjs.org/",
  "externalId": "nextjs-demo",
  "finalUrl": "https://nextjs.org/",
  "status": "ok",
  "httpStatus": 200,
  "pageCount": 1,
  "technologyCount": 2,
  "technologyNames": ["Next.js", "Vercel"],
  "technologiesByCategory": {
    "framework": ["Next.js"],
    "hosting": ["Vercel"]
  },
  "findings": [
    {
      "name": "Next.js",
      "category": "framework",
      "certainty": "direct",
      "evidence": [
        {
          "type": "header",
          "value": "x-powered-by: Next.js",
          "sourcePage": "https://nextjs.org/"
        }
      ]
    }
  ],
  "detectionMethod": "public_html_and_response_headers",
  "rulesVersion": "1.0.0",
  "changeStatus": "not_compared"
}

Actual records include checkedAt, pageUrls, scopeKey, previousCheckedAt, addedTechnologies and noLongerObservedTechnologies. Findings are alphabetized; evidence is capped at three examples per technology per page, up to nine per website. Asset evidence omits query strings and fragment identifiers. certainty: direct means an identifying artifact was observed, not that we verified a vendor subscription, executed its code, or measured how the site uses it.

status is ok when a supported signal was found, or no_supported_signal when the HTML was successfully inspected without a match. Both are completed, billable checks. A zero-signal result does not prove software is absent.

The default key-value store's SUMMARY record contains processed counts, skipped inputs, failures, per-page reasons and time-budget coverage. Failure classes include blocked pages, robots restrictions, HTTP errors, non-HTML responses, request errors and timeouts. If no website can be completely inspected, the run fails with a diagnostic instead of silently succeeding empty.

If your run charge limit prevents a result from being saved, the Actor stops with a clear warning and SUMMARY.stoppedOnChargeLimit: true. Unsaved results do not advance history. A charge limit reached before the first result is a normal empty budget stop, reported as outcome: stopped_on_charge_limit.

Supported signal catalog

These are the explicitly implemented names; coverage is limited to their visible signals:

Signatures inspect script and stylesheet references, selected preload assets, generator tags, explicit HTML attributes, narrow inline JavaScript assignments and response headers. A vendor mentioned in ordinary page prose or a normal hyperlink does not count. Shopify CDN assets alone do not label a site as a Shopify store. A generic Google tag is distinguished from a GA4 tag identifier. No inferred backend or framework dependencies are added.

Compare repeat runs

{
  "websites": ["https://wordpress.org/", "https://nextjs.org/"],
  "comparePrevious": true,
  "snapshotName": "my-website-portfolio"
}

The first successful run returns all successful checks and establishes a baseline. Reuse the same store name and exact supplied page set on later runs. Results still include every successful website, with changeStatus of baseline, baseline_reset, unchanged or changed. Unchanged results are billable because the site was inspected again.

Snapshots contain URLs and technology names and are saved in the named key-value store in your Apify account. A changed supplied page scope creates a separate baseline. A rules version or final redirect destination change resets the baseline, avoiding a misleading comparison. Incomplete or failed website checks never overwrite a baseline. Avoid concurrent runs that share a snapshot store: the last completing run saves the latest snapshot.

noLongerObservedTechnologies means the current complete check did not observe those signals. A site may have changed consent settings, hidden assets or delivered different markup; this is not proof that a tool was uninstalled. There is no webhook or notification sending in this Actor. You can use the exported result with your own automation.

Inputs and limits

At most three supplied pages per website, five redirects per page, 2 MB HTML per page and 20 seconds per request are allowed within the overall budget. Respectful public HTTP requests check robots.txt, including redirect destinations. Requests blocked by access controls are reported. Sites requiring login or JavaScript execution cannot be fully inspected by this Actor. HTML consent gates and geography can change visible signals. This is an observed technology inventory, not a security or compliance audit, traffic estimate, revenue estimate, or complete Wappalyzer/BuiltWith replacement.

Exact repeated page scopes with the same externalId are deduplicated. Different IDs or different supplied page scopes produce separate checks. The Actor preserves the input record's first URL as url; the fetched final location is finalUrl.

Pricing

The launch price is $0.005 per successful website check ($5 per 1,000) on Free/Bronze. Each check includes its supplied scope of up to three pages. A successful zero-signal check and an unchanged comparison are charged. Failed, robots-disallowed, incomplete or unprocessed websites are not charged as results. An Actor Start event of $0.00005 also applies. Silver is 20% lower and Gold/Platinum/Diamond 40% lower. The live Pricing tab is authoritative.

Normal Apify account credits and limits apply. No feature requires a separate API subscription. Do not run the same monitored scope concurrently if you need an ordered comparison history.

Examples

The tasks/ directory contains three proposed example inputs: WordPress CMS/header signals, Next.js framework/hosting signals, and WordPress evidence across three supplied pages. They are local proposals until separately validated on the platform and published.

Help with your run

Open the Issues tab on this Actor with the run URL, the input field that caused trouble and what you expected to receive. Remove API keys and private information before posting.

Explore more Mayd-It Actors

Understand your run

Open Run report in the run’s Output tab for saved-record counts, reported source issues and limits, and suggested next steps. Use CSV export to take the saved results into a spreadsheet. The existing JSON results and detailed machine-readable summary remain available.

The report reflects this run’s recorded coverage. A successful run or a saved result does not establish that every possible source record was collected.