Skip to content

use-cases.md

Latest commit

 

History

History
29 lines (17 loc) · 1.44 KB

use-cases.md

File metadata and controls

29 lines (17 loc) · 1.44 KB
Raw

Use cases

These workflows use the public input and Dataset contract of the Website Technology Lookup Actor.

Competitor technology profiles

Submit a list of competitor domains:

{
  "domains": ["competitor-one.com", "competitor-two.com"]
}

Inspect technologies, category, name, version and detectionStatus to compare published technology adoption. Treat recently_used records as historical evidence, not current confirmation.

CMS and hosting research

Use the same domain list to research published CMS, hosting, web server and frontend categories. Filter the nested technologies array by category after reading the Dataset as JSON.

SEO and lead-list enrichment

Process a normalized domain list and join the returned status, title, technologies and error fields to an existing SEO or sales dataset. Keep non-ok rows so failed or unavailable lookups remain auditable.

Large batches and recurring snapshots

The Actor accepts up to 10,000 values per run and removes equivalent domains before processing. For recurring research, save the input as an Apify Task and attach a Schedule, then compare Dataset exports over time.

Use examples/python/batch_website_technology_lookup.py for a multi-domain request and examples/python/export_website_technology_csv.py to create a spreadsheet-friendly export.