I’m planning an Airtable base for tracking search result data over time and would like to sanity-check the structure.
The use case is keyword and competitor monitoring. An external API would return search results on a schedule, and I want to store each result with fields like query, search engine, date checked, position, title, URL, domain, and snippet.
My first thought is to have one table for keywords and another table for SERP results, with each result linked back to the keyword record.
For context, I work on TalorData, a Search API for SERP data, so I’m trying to understand the cleanest way people store recurring search result data in Airtable.
For people who have built similar recurring data workflows, would you store each search result as a separate record, or store one full search result page as JSON in a single record?
I’m leaning toward separate records because it seems easier to filter by domain, position, and date, but I’m not sure if that becomes messy as the data grows.
