serp-extract

SERP evidence capture saves organic results and observed SERP features for requested keywords while preserving keyword order and provider facts. It stores immutable raw provider payloads and writes normalized YAML artifacts to support reporting, auditing, and downstream content workflows.

Extracting organic results for offline auditing uses an offline fixture mode to capture and normalize SERP evidence without live provider calls. It writes normalized YAML artifacts with complete provider metadata, returning empty evidence and explicit limitations when fixture data is missing.

DataForSEO standard flow is used by default for SERP feature tracking, and live or async modes are supported when explicitly requested. This controlled approach ensures raw provider responses are stored immutably as raw JSON alongside normalized YAML extraction outputs.

SERP evidence extraction deliberately does not perform intent inference, focusing solely on capturing organic result snapshots and observed features. It blocks execution or returns empty evidence when required inputs like location, language, or device cannot be determined.

SERP extraction returns empty evidence with explicit limitations when results are missing or required inputs like location, language, and device cannot be determined. This guardrail against invention prevents fabricating data when inputs or fixture data are absent.