Website Tech Signal Detector avatar

Website Tech Signal Detector

Pricing

from $1.05 / 1,000 tech signal pages

Go to Apify Store
Website Tech Signal Detector

Website Tech Signal Detector

Detect public website tech stack signals, metadata QA issues, CRM-ready lead tags, and optional stack-change snapshots.

Pricing

from $1.05 / 1,000 tech signal pages

Rating

0.0

(0)

Developer

replexa

replexa

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Website Tech Signal Detector is a lightweight website technology lookup and lead enrichment Actor. It detects public tech stack signals, compact metadata QA issues, CTA/pricing intent signals, and optional change snapshots from website HTML, script URLs, generator metadata, and HTTP headers.

Paste website URLs, run the Actor, and get one dataset item per website. The output is designed for CRM enrichment, lead scoring, competitor research, website technology audits, technical inventories, and scheduled monitoring where users need clear evidence instead of opaque scoring.

What It Does

  • Detects common public signals for CMS, website builders, ecommerce, analytics, tag managers, CDNs, frameworks, hosting, payments, consent, advertising, marketing automation, monitoring, security, documentation, AI support widgets, and server headers
  • Returns evidence explaining why each signal was detected
  • Adds confidence values so weak and strong signals can be reviewed differently
  • Separates confirmed public technology signals from weaker site hints
  • Produces lead-use-case tags such as wordpress_site, shopify_store, analytics_installed, and cdn_detected
  • Lists unknown script hosts that may be useful for follow-up research
  • Adds compact unknown-host summary fields for quick triage
  • Adds compact metadata QA for title, description, canonical, Open Graph, Twitter/X card, and JSON-LD signals
  • Optionally compares detected technologies, metadata, CTA texts, pricing mentions, and intent tags with a previous snapshot
  • Adds changeSeverity, changeSummary, and changedFields for faster competitor or client-portfolio monitoring
  • Adds an action-first SEO metadata report with primaryUseCase, topFixPriority, nextBestAction, and seoActionReport
  • Keeps failed URL rows in the dataset with request_failed tags and request error details
  • Uses public pages only and avoids browser automation by default for low-cost runs

Common Use Cases

  • Run bulk website technology lookup for prospect lists
  • Enrich prospect website lists before CRM import or outbound qualification
  • Segment leads by CMS, website builder, ecommerce platform, analytics, CDN, framework, hosting, marketing, payment, consent, or server signals
  • Run quick competitor tech stack checks
  • Build a lightweight technical inventory for a client portfolio
  • Flag websites that need manual follow-up because unknown script hosts were found
  • Monitor prospect, customer, or competitor websites for visible stack changes
  • Monitor pricing-page, CTA, and metadata changes without configuring selectors
  • Turn metadata issues into prioritized fixes instead of reviewing raw fields one by one
  • Check whether a website profile has basic SEO and social metadata needed for previews and enrichment

Input

The only required input is Website URLs.

{
"urls": [
{ "url": "https://example.com" }
]
}

Advanced settings such as website limit, metadata QA, stack comparison, parallel requests, timeout, and retries are optional. The defaults are intended for a quick first run.

Output

Each checked website produces one dataset item.

{
"url": "https://example.com",
"finalUrl": "https://example.com/",
"statusCode": 200,
"title": "Example website",
"technologies": ["WordPress", "Google Analytics"],
"categories": ["CMS", "Analytics"],
"technologyCount": 2,
"leadUseCaseTags": ["wordpress_site", "analytics_installed"],
"evidence": [
{
"name": "WordPress",
"categories": ["CMS"],
"confidence": 0.9,
"signalStrength": "strong",
"reason": "wp-content or generator meta"
}
],
"unknownSignals": [
{
"type": "script_host",
"value": "cdn.example-cdn.com",
"example": "https://cdn.example-cdn.com/app.js"
}
],
"unknownSignalCount": 1,
"topUnknownHosts": ["cdn.example-cdn.com"],
"siteHints": [],
"strongSignalCount": 1,
"mediumSignalCount": 1,
"weakHintCount": 0,
"metaTitle": "Example website",
"metaDescription": "Example website description",
"canonicalUrl": "https://example.com/",
"openGraphSummary": {
"title": "Example website",
"description": "Example Open Graph description",
"image": "https://example.com/preview.png",
"url": "https://example.com/",
"type": "website"
},
"twitterCardSummary": {
"card": "summary_large_image",
"title": "Example website",
"description": "Example Twitter/X card description",
"image": "https://example.com/preview.png"
},
"jsonLdTypes": ["Organization"],
"jsonLdParseErrors": [],
"metadataIssues": [],
"profileCompletenessScore": 100,
"monitoringProfile": {
"ctaTexts": ["Start free trial"],
"pricingMentions": ["$29", "monthly"],
"intentTags": ["cta_detected", "pricing_signal_detected"]
},
"primaryUseCase": "seo_metadata_action_report",
"topFixPriority": "high",
"nextBestAction": "Add a meta description that explains the page value in one sentence.",
"seoActionReport": [
{
"fixPriority": "high",
"issueType": "description",
"recommendedFix": "Add a meta description that explains the page value in one sentence."
}
],
"changeStatus": "not_compared",
"changeSeverity": "none",
"changeSummary": "Snapshot comparison was not enabled.",
"changedFields": [],
"addedTechnologies": [],
"removedTechnologies": [],
"previousCheckedAt": "",
"snapshotKey": "",
"server": "nginx",
"poweredBy": "",
"requestError": "",
"checkedAt": "2026-08-13T00:00:00.000Z"
}

Pricing Plan

  • Pricing model: Pay per event
  • Event: apify-default-dataset-item
  • Event title: Tech signal page
  • Price: $0.00105 per website
  • Equivalent display: $1.05 / 1,000 websites
  • Platform usage: included in the event price
  • Baseline rule: 30% below the lowest directly comparable paid website technology detector found during pricing research.

Notes And Limits

Detection is based on public page signals and heuristics. It is useful for enrichment and triage, but it should not be treated as a complete security inventory or guaranteed technology fingerprint. Some technologies leave no public signal, and some websites hide or bundle scripts.

Responsible Use

Use this Actor only on public pages that you are authorized to inspect. Keep request limits reasonable. Do not use the output for spam, deceptive outreach, unauthorized security testing, or high-impact decisions without manual verification.