dataforseo-domain-analytics-api_skill

Overview

This skill integrates DataForSEO Domain Analytics to enrich and analyze domains for technology detection, domain research, and lead enrichment. It surfaces CMS, frameworks, analytics, hosting, and WHOIS signals to support prospecting, competitive analysis, and risk scoring. Use it for live lookups or task-based batch processing depending on volume and latency needs.

How this skill works

The skill calls DataForSEO Domain Analytics endpoints using HTTP Basic auth and either live (single-request) or task-based flows. For live endpoints it returns immediate technology and WHOIS summaries; for task flows it posts tasks, polls tasks_ready, then fetches task_get results or consumes pingback notifications. Responses are validated by status_code and tasks[].status; the skill normalizes summaries and preserves raw payloads for debugging.

When to use it

• Detect the tech stack of a single site or small list interactively (live endpoints).
• Enrich large lead lists with CMS, analytics, hosting, and WHOIS data (task-based).
• Build targeted prospect lists by technology, location, or language filters.
• Monitor competitor or customer stack changes and replatforming events.
• Add WHOIS and domain registration signals into fraud, risk, or compliance scoring.

Best practices

• Choose live mode for low-latency, single-domain queries and task mode for bulk or scheduled jobs.
• Always validate top-level status_code == 20000 and check each tasks[].status before trusting data.
• Store tasks[].id and use tasks_ready + task_get or webhook postback for reliable retrieval in task flows.
• Include location and language filters when regional accuracy matters (technologies locations/languages endpoints).
• Return both a concise normalized summary and the raw response payload to aid debugging and audits.

Example use cases

• Find US domains running Shopify and produce a ranked prospect list with contact enrichment.
• Run a WHOIS overview for a batch of domains to flag risky registration patterns and registrar anomalies.
• Enrich an inbound lead list with CMS, analytics, and hosting signals for SDR prioritization.
• Compare technology footprints between our domain and competitors and summarize differences by category.