Outway documentation
Search and SEO data
Understand source availability, imported observations and live search collection in Outway.
Understand the source
Outway separates stored search observations from live source collection. Imported SERP snapshots preserve supplied evidence; they do not establish current Google rankings.
A source adapter must be configured and enabled before live collection can run. Native Google collection targets an initial US, English, desktop workflow, but requires suitable worker and egress configuration. A parsed result alone does not prove its location or freshness.
Work with observations
Use the app’s Search Data and Intelligence areas to inspect available observations, compare domains and review supporting evidence. Preserve the source, market, device and observation time in reports.
API entry points
SERP imports use POST /v1/projects/{projectId}/serp-snapshots. Configured search collection uses POST /v1/projects/{projectId}/search-tasks. These are different operations: follow the published schemas and availability responses in the API reference.
Avoid misleading conclusions
Google Ads metrics, search volume and other licensed datasets are not produced by ordinary page scraping. Each requires its own configured source and access. An optional DataForSEO adapter is replaceable; it is not required for native web collection. Do not present unavailable datasets as live features.
Authorized Google account reports
Optional Search Console and Google Ads connections provide saved account-backed performance and historical estimates. They are separate from live SERP collection and require operator activation and appropriate Google access. Administrators can explicitly share selected saved reports with project AI readers.