Get Google Search Results (SERPs) for SEO Research
Configured with Filter, HTTP Request, Split Out. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Transform
- Routing
- Code
- Web / API
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| SERP results | Transform | Edit Fields | See node parameters |
| Separate | Transform | Split Out | See node parameters |
| Title <> Empty | Routing | Filter | See node parameters |
| Assign SERP #pos | Code | Code | See node parameters |
| GET SERP | Web / API | HTTP Request | POST |
| Connect to your own database - | Routing | No Op | See node parameters |
| Set Keywords to get SERPs for | Transform | Edit Fields | See node parameters |
| Connect to your own database2 | Routing | No Op | See node parameters |
| Assign SearchQuery | Transform | Edit Fields | See node parameters |
| Split out Keywords | Transform | Split Out | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
httpHeaderAuthhttpQueryAuth
Workflow notes
Separate
Split SERP into rows
Title <> Empty
Title is not empty
Assign SERP #pos
Assign SERP position
GET SERP
SERP results - scrapingRobot
https://dashboard.scrapingrobot.com/dashboard
Sticky Note29
Get data from airtable and check if already done
Sticky Note30
POST to Scraping Robot API
Sticky Note22
REQUIRED
Connect to your database of keywords. Name the column 'Keyword' or alternatively enter keywords in the Set Keywords to get SERPs for array
Set Keywords to get SERPs for
Array of keywords
Sticky Note24
REQUIRED Update the Auth parameter to your own Scraping Robot token
Query Auth parameter name - token value - your-own-api-key
Sticky Note31
Splits out queries for organic search and assigns them a ranking 1-10
Sticky Note27
Update record in own Database
Sticky Note40
REQUIRED Output the data to your own data source e.g. Airtable
Get Google Search Results (SERPs) for SEO Research
Get Google Search Results (SERPs) for SEO Research
Use Case
Research search engine rankings for SEO analysis:
- You need to track keyword rankings for your website
- You want to analyze competitor positions in search results
- You need data for SEO competition analysis
- You want to monitor SERP changes over time
What this Workflow Does
The workflow uses ScrapingRobot API to fetch Google search results:
- Retrieves SERP data for your target keywords
- Captures URL rankings and page titles
- Processes up to 5000 searches with free account
- Organizes results for SEO analysis
Setup
- Create a ScrapingRobot account and get your API key
- Add your ScrapingRobot API key to the HTTP Request node's
GET SERPtoken parameter - Either connect your keyword database (column name "Keyword") or use the "Set Keywords" node
- Configure your preferred output database connection
How to Adjust it to Your Needs
- Modify keyword source to pull from different databases
- Adjust the number of SERP results to capture
- Customize output format for your reporting needs
Made by Simon @ automake.io
Get Google Search Results (SERPs) for SEO Research
Get Google Search Results (SERPs) for SEO Research
Purpose and structure
This folder contains the Get Google Search Results (SERPs) for SEO Research workflow. Its executable nodes use code, filter, httpRequest, manualTrigger, noOp, set, splitOut. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking ‘Test workflow’
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Splitout/0608_Splitout_Code_Import_Webhook.json MIT; preserve source notices.