RapidAPI to Google Sheets, SERP ranks logged clean
Keyword rank tracking sounds simple until you actually have to do it. You look up results, copy rows, paste JSON blobs somewhere “for later,” then realize later never comes.
SEO managers feel it first, honestly. But marketing leads building weekly reports and agency folks juggling 10 clients deal with the same SERP rank tracking automation problem: too many checks, too many places to log them, and not enough confidence in the data.
This workflow takes a keyword + country input, pulls real SERP ranking data through RapidAPI, then writes a clean record to Google Sheets every time. You’ll learn what it does, what you need, and how to run it without babysitting.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: RapidAPI to Google Sheets, SERP ranks logged clean
flowchart LR
subgraph sg0["On form submission Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/form.svg' width='40' height='40' /></div><br/>On form submission"]
n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Global Storage", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If", pos: "b", h: 48 }
n3@{ icon: "mdi:database", form: "rounded", label: "Google Sheets", pos: "b", h: 48 }
n4@{ icon: "mdi:cog", form: "rounded", label: "Wait", pos: "b", h: 48 }
n5@{ icon: "mdi:database", form: "rounded", label: "Google Sheets1", pos: "b", h: 48 }
n6@{ icon: "mdi:cog", form: "rounded", label: "Wait1", pos: "b", h: 48 }
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>SERP Keyword Ranking Checker"]
n2 --> n6
n2 --> n4
n4 --> n5
n6 --> n3
n1 --> n7
n0 --> n1
n7 --> n2
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n2 decision
class n3,n5 database
class n7 api
classDef customIcon fill:none,stroke:none
class n0,n7 customIcon
Why This Matters: Clean rank tracking without spreadsheet chaos
Rank checks are sneaky work. One check turns into five, then suddenly you’re tracking 30 keywords across three countries and trying to remember if “us” and “USA” are the same filter in your sheet. Manual lookups also invite messy logging: someone pastes the wrong keyword, forgets the country code, or only records “position 7” with no context of what the API returned. Later, when you need to explain a drop in visibility, you have nothing reliable to point to. That’s the real cost: not the lookup, the uncertainty.
It adds up fast. Here’s where it breaks down in real life.
- You end up doing the same SERP check multiple times because the last result wasn’t recorded clearly.
- Copy-paste logging is fragile, and one wrong row can throw off an entire client report.
- When an API returns “no results,” most people skip logging it, so you lose the audit trail.
- Scaling to more keywords or countries becomes a planning problem instead of a simple process.
What You’ll Build: RapidAPI SERP checks logged to Google Sheets
This n8n workflow turns rank checking into a repeatable, trackable system. It starts with a simple form submission where you enter a keyword (like “labubu”) and a country code (like “us”). n8n stores those inputs, sends them to the SERP Keyword Ranking Checker API on RapidAPI, and waits briefly so downstream steps don’t trip over timing or rate limits. Then it makes a decision: if the API returns real SERP results, it appends a new row to Google Sheets with your keyword, country, and the returned JSON data for full context. If nothing comes back, it still logs the attempt, but with a clear “No result found…” message so your spreadsheet stays honest.
The workflow begins at the form, not in a dashboard you have to remember to open. From there, RapidAPI handles the SERP lookup, and Google Sheets becomes your single place for tracking results over time. One input. One logged record. Every time.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you track 20 keywords across 3 countries each week. Manually, you’ll spend maybe 5 minutes per check between searching, confirming the result, and logging it, which is about 5 hours weekly. With this workflow, you submit each check in roughly 30 seconds, then let n8n wait and log the result to Google Sheets automatically. That’s closer to 10 minutes of actual effort, plus background processing you don’t have to watch.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets for storing rank checks over time.
- RapidAPI to access the SERP Keyword Ranking Checker API.
- RapidAPI key (get it from the RapidAPI API “Security” tab).
Skill level: Beginner. You’ll connect accounts, paste an API key, and choose the target spreadsheet.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A form submission triggers the run. You enter a keyword and a country code in an n8n form, which keeps inputs consistent (and prevents “us/USA/U.S.” style logging errors).
Your inputs get stored for reuse. n8n saves the keyword and country as variables so the API request and the Google Sheets row use the same values, every time.
RapidAPI handles the SERP lookup. The workflow sends a POST request to the SERP Keyword Ranking Checker endpoint with your keyword and country, using your RapidAPI key in the headers.
Results are checked, then logged to Google Sheets. If SERP data exists, it appends the JSON results to your “success” sheet. If nothing comes back, it appends a clear fallback message to your “not found” log instead, after a short 5-second delay on both paths.
You can easily modify the Google Sheets columns to match your reporting format, or swap the form input for a Google Sheet “keyword list” trigger if you want batch checks. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Form Trigger
Set up the intake form so users can submit a keyword and country for SERP lookup.
- Add a Form Intake Trigger node and open its settings.
- Set Form Title to
SERP Keyword Ranking Checker. - Set Form Description to
Enter your keyword for research the market.. - In Form Fields, add two required fields: keyword (placeholder
e.g. labubu) and Country (placeholdere.g. us).
Step 2: Connect Google Sheets
Prepare Google Sheets nodes to log successful results and missing data outcomes.
- Open Append Results Sheet and set Authentication to
serviceAccount. - Credential Required: Connect your googleApi credentials in Append Results Sheet.
- Open Append Not Found Log and set Authentication to
serviceAccount. - Credential Required: Connect your googleApi credentials in Append Not Found Log.
- For both Google Sheets nodes, select the target spreadsheet in Document and confirm Sheet Name is
Sheet1.
Step 3: Set Up Processing and API Request
Normalize input data and call the SERP API, then route based on whether results are returned.
- In Store Input Values, add assignments for keyword and country with values
{{ $json.keyword }}and{{ $json.Country }}. - In SERP API Request, set URL to
https://rapidapi.com/PrineshPatel/api/serp-keyword-ranking-checkerand Method toPOST. - Enable Send Body and set Content Type to
multipart-form-data. - Add body parameters: keyword =
{{ $json.keyword }}and country ={{ $json.country }}. - Enable Send Headers and set x-rapidapi-host to
serp-keyword-ranking-checker.p.rapidapi.comand x-rapidapi-key to your API key (replace[CONFIGURE_YOUR_API_KEY]). - In Result Availability Check, configure the condition to check
{{ $json.data.semrushAPI.serpResults }}with OperationnotEmpty.
[CONFIGURE_YOUR_API_KEY] will cause 401/403 errors.Step 4: Configure Output and Wait Handling
Route successful results and missing data to their respective Google Sheets logs after brief waits.
- Connect Result Availability Check “true” output to Delay for Valid Data, and the “false” output to Delay for Missing Data.
- From Delay for Valid Data, connect to Append Results Sheet.
- In Append Results Sheet, map columns to
{{ $('Store Input Values').item.json.country }},{{ $('Store Input Values').item.json.keyword }}, and{{ $json.data.semrushAPI.serpResults }}. - From Delay for Missing Data, connect to Append Not Found Log.
- In Append Not Found Log, map columns to
{{ $('Store Input Values').item.json.country }},{{ $('Store Input Values').item.json.keyword }}, and set Json data toNo result found. Please try another keyword....
Step 5: Test and Activate Your Workflow
Validate the end-to-end flow and enable it for production use.
- Click Execute Workflow and submit a test entry through Form Intake Trigger (e.g., keyword
labubu, countryus). - Confirm the request reaches SERP API Request and that Result Availability Check routes correctly based on returned data.
- Verify that Append Results Sheet logs results when data exists, or Append Not Found Log logs the fallback message when no results are found.
- Once verified, toggle the workflow Active for continuous form submissions.
Troubleshooting Tips
- RapidAPI credentials can expire or be tied to the wrong app. If things break, check your RapidAPI project and the API “Security” tab for the current key first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Google Sheets writes can fail silently when the sheet name, tab, or header structure changes. Confirm the target spreadsheet and the append range inside the Google Sheets node before you assume the API is the issue.
Quick Answers
About 30 minutes if your Google Sheet and RapidAPI key are ready.
No. You’ll paste an API key, connect Google Sheets, and map a few fields.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in RapidAPI subscription costs for the SERP Keyword Ranking Checker API, which depend on the plan you choose.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s straightforward. You can replace the form trigger with a scheduled trigger to run daily, or swap the input source to a “keyword list” sheet so it checks many rows at once. You can also change what gets stored in Google Sheets by editing the “Store Input Values” Set step and the two “Append…” Google Sheets steps (for example, log the top URL, the rank position, and a timestamp instead of the full JSON). Some teams even route the “no result found” path to an email alert using a Send Email node.
Usually it’s an invalid or expired RapidAPI key, so regenerate it (or copy the correct one) and update the HTTP request headers in n8n. Another common issue is being subscribed to the wrong API or plan inside RapidAPI, which can return auth or quota errors. If you’re testing a lot in a short window, you may also be hitting rate limits, so the 5-second wait may need to be increased.
On self-hosted n8n, volume mainly depends on your server and the RapidAPI plan limits.
Often, yes. n8n makes it easier to keep the “success vs not found” logic clean, and you can self-host for unlimited executions if your volume grows. It also handles storing and passing JSON data between steps more naturally, which matters when you want the full SERP context saved to Google Sheets. Zapier or Make can still work, but complex branching or high task volume can get expensive fast. Talk to an automation expert if you want help choosing the right stack for your reporting workflow.
Once this is running, your “rank tracking” stops being a recurring chore and becomes a dependable dataset. Set it up, run checks when you need them, and let Google Sheets stay clean for reporting.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
