Bright Data to Google Sheets, rankings logged daily
Manual rank checks are the worst kind of “important.” They’re repetitive, easy to mess up, and they quietly steal time from work that actually moves traffic.
SEO managers feel it on reporting days. Agency owners feel it when clients ask, “Any updates?” Marketing leads dealing with five priorities at once feel it too. This rank tracking automation keeps a daily log in Google Sheets so you stop doing the same Google searches over and over.
You’ll set up an n8n workflow that pulls your keywords from a sheet, checks Google via Bright Data’s SERP API, writes results back to a “Results” tab, then emails a clean HTML summary.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Bright Data to Google Sheets, rankings logged daily
flowchart LR
subgraph sg0["When clicking ‘Test workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Test workflow’", pos: "b", h: 48 }
n1@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n2["<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/code.svg' width='40' height='40' /></div><br/>Making Email Template"]
n3@{ icon: "mdi:database", form: "rounded", label: "Reading Keywords", pos: "b", h: 48 }
n4["<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/code.svg' width='40' height='40' /></div><br/>Transforming Keywords"]
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop over Keywords", pos: "b", h: 48 }
n6["<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/>Getting Ranks"]
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/code.svg' width='40' height='40' /></div><br/>Rank Finder"]
n8@{ icon: "mdi:database", form: "rounded", label: "Post Rank Results", pos: "b", h: 48 }
n9@{ icon: "mdi:message-outline", form: "rounded", label: "Sending Email Message", pos: "b", h: 48 }
n7 --> n8
n6 --> n7
n3 --> n4
n1 --> n3
n8 --> n5
n5 --> n2
n5 --> n6
n2 --> n9
n4 --> n5
n0 --> n3
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,n1 trigger
class n3,n8 database
class n6 api
class n2,n4,n7 code
classDef customIcon fill:none,stroke:none
class n2,n4,n6,n7 customIcon
Why This Matters: Daily rank checks waste real time
If you track rankings manually, you already know the routine. Open an incognito window, search a keyword, scroll, squint, click around, then paste the “rank” into a spreadsheet (and hope you didn’t accidentally copy yesterday’s row). Do that for 20 keywords and it’s suddenly most of your morning. Worse, manual checks aren’t consistent: location, personalization, and “did I search the exact phrase?” all creep in. Then, when someone asks for a trend line, you realize you never logged history reliably, so you can’t explain what changed.
It adds up fast. Here’s where it usually breaks down in real teams.
- Rank checks happen “when someone remembers,” so you end up with gaps that ruin trend analysis.
- Copy-paste logging introduces small mistakes that turn into embarrassing client updates.
- Multiple domains or locations make the process feel endless, which means you track fewer keywords than you should.
- Stakeholders want a tidy email summary, but you’re stuck screenshotting SERPs or sending messy spreadsheets.
What You’ll Build: Bright Data SERP checks logged to Sheets
This workflow turns rank tracking into a repeatable daily system. It starts on a schedule trigger (every 24 hours) or whenever you click “Test workflow” in n8n. First, it reads a Google Sheets tab that lists the keywords you care about alongside the target domain for each one. Next, it formats each keyword into a URL-friendly query (spaces become +), then processes the list in batches so each keyword gets its own SERP request. For every keyword, n8n calls Bright Data’s SERP API, receives the raw HTML, and parses out the non-Google links to find where your target domain appears. Finally, it appends a timestamped record to a “Results” sheet and emails an HTML table summary through Gmail.
The workflow starts from Google Sheets, which becomes your simple control panel. Bright Data handles the Google SERP retrieval, and n8n extracts rank, URL, and a “how many results were checked” context. Then Gmail delivers the report so you can forward it to a client or drop it into an internal update.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you track 30 keywords for one domain and you check rankings five days a week. Manually, even “quick” checks take about 2 minutes each once you search, scan, and log, which is about 1 hour a day. With this workflow, adding the keywords to Google Sheets takes maybe 10 minutes once, then your daily effort is basically zero while n8n runs and emails you the table. You get about 5 hours back every week, plus a real history you can chart.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Bright Data for SERP API access to Google results
- Google Sheets to store keywords and save rank history
- Bright Data API token (get it from your Bright Data dashboard)
Skill level: Intermediate. You’ll paste an API token, connect Google, and confirm your Sheets columns match what the workflow expects.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A daily schedule (or a manual run) kicks things off. You can run it on demand to test changes, then let the 24-hour schedule handle ongoing checks.
Your keyword list is pulled from Google Sheets. The workflow reads rows that contain a Keyword and a Domain, then reformats each keyword so it’s safe to use in a SERP request.
Bright Data is called once per keyword, in batches. n8n loops through your list, requests the Google results HTML via Bright Data’s SERP API (with a default US location), then parses links to find your target domain and rank position.
Results are stored and reported automatically. Every run appends a new line to your “Results” tab for history, then builds an HTML email table and sends it through Gmail to the recipients you choose.
You can easily modify the location parameter (gl=) to run checks for another country based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Set up the workflow entry points so you can run it on demand or on a schedule.
- Add the Manual Execution Start node to allow manual runs for testing.
- Add the Timed Schedule Trigger node for automated daily runs.
- In Timed Schedule Trigger, keep the interval set to
hoursand24to run once per day. - Connect both Manual Execution Start and Timed Schedule Trigger to Fetch Keyword Sheet so either trigger starts the same data flow.
Step 2: Connect Google Sheets
Configure the Google Sheets nodes that read keywords and write rank results.
- Open Fetch Keyword Sheet and set Document ID to
={{ $credentials.googleSheetDocId }}. - Set Sheet Name in Fetch Keyword Sheet to
Keyword. - Credential Required: Connect your googleSheetsOAuth2Api credentials in Fetch Keyword Sheet.
- Open Append Rank Records and set Operation to
append. - Set Document ID to
={{ $credentials.googleSheetDocId }}and Sheet Name toResults. - Map columns in Append Rank Records with expressions like
={{ $json.rank }},={{ $json.url }}, and={{ $('Fetch Keyword Sheet').item.json.Domain }}. - Credential Required: Connect your googleSheetsOAuth2Api credentials in Append Rank Records.
Step 3: Set Up Keyword Processing
Transform keyword data and prepare it for batching and downstream rank checks.
- In Format Keyword Terms, keep the JavaScript that creates
transformedKeywordby replacing spaces with+. - Connect Fetch Keyword Sheet → Format Keyword Terms → Iterate Keyword Batches to pass the transformed keywords into batching.
- Configure Iterate Keyword Batches to control batch size if needed (defaults are acceptable for small lists).
- Iterate Keyword Batches outputs to both Build Email Layout and Retrieve Search Ranks in parallel.
Keyword and Domain to avoid missing data in downstream nodes.Step 4: Configure Rank Retrieval and Parsing
Request SERP data and extract rank positions for the target domain.
- In Retrieve Search Ranks, set URL to
https://api.brightdata.com/requestand Method toPOST. - Set JSON Body to
={"zone": "serp_n8n","url": "https://www.google.com/search?q={{ $json.transformedKeyword }}&gl=US", "format": "raw"}. - Enable Send Headers and add Authorization with value
Bearer {{$credentials.brightDataApiKey}}. - In Determine Rank Position, keep the code that reads
$('Fetch Keyword Sheet').first().json.Domainand outputsrank,url, andcheckedAt. - Connect Retrieve Search Ranks → Determine Rank Position → Append Rank Records.
{{$credentials.brightDataApiKey}} used in Retrieve Search Ranks.Step 5: Configure Output Actions
Generate the email summary and send it after batch processing.
- In Build Email Layout, keep the JavaScript that builds the HTML table and outputs
emailBody. - Connect Build Email Layout → Dispatch Email Update to send the summary email.
- In Dispatch Email Update, set Send To to
={{ $credentials.recipientEmail }}. - Set Message to
={{ $json.emailBody }}and Subject toRanked. - Credential Required: Connect your gmailOAuth2 credentials in Dispatch Email Update.
Step 6: Test and Activate Your Workflow
Validate the data flow and enable scheduled execution.
- Click Execute Workflow on Manual Execution Start to run a full test.
- Confirm that Append Rank Records adds new rows in the
Resultssheet with rank data. - Verify that Dispatch Email Update sends an email containing a table of keywords and ranks.
- Once verified, toggle the workflow to Active to enable the Timed Schedule Trigger for daily tracking.
Troubleshooting Tips
- Google Sheets access can fail if the connected Google account loses permission to the file. If it errors, open the Google Sheets node in n8n and re-select the spreadsheet 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.
- Bright Data requests can return unexpected HTML when rate limits or location settings change. Check the HTTP Request node’s response in n8n execution logs, then confirm your Authorization token and the gl= country parameter.
Quick Answers
About 30 minutes if your Sheets and Bright Data account are ready.
No. You’ll connect accounts, paste a token, and point the workflow at the right Google Sheet.
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 Bright Data SERP API usage costs based on how many keywords you check per day.
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 common. You can change the country by editing the Bright Data request URL in the “Retrieve Search Ranks” HTTP Request node (the gl= parameter), and you can tweak what gets logged by updating the “Determine Rank Position” code step. Many teams add extra columns like “device,” “notes,” or “campaign,” or route alerts to Slack when a keyword drops out of the top 10.
Usually it’s an invalid or expired API token in the HTTP Request node’s Authorization header. Check the execution output for 401/403 errors, regenerate the token in Bright Data, then update it in n8n. If the response is “successful” but the HTML looks odd, confirm your SERP parameters (including gl=) and make sure you’re not hitting usage limits. Occasionally, the issue is simply that your workspace firewall blocks outbound requests, which shows up as timeouts in the run logs.
On n8n Cloud, the practical limit depends on your execution quota and how many keywords you check daily. If you self-host, there’s no hard execution cap, but your server and Bright Data usage limits still matter. For most small teams, a few hundred keywords per day is realistic as long as you keep batching enabled and don’t email a massive table to 20 recipients every run.
Often, yes. This workflow relies on looping, HTML parsing, and custom logic, and that gets awkward (or pricey) in tools built around simple “trigger → action” zaps. n8n handles batching cleanly, and you can self-host to avoid per-task fees when you scale keyword volume. Zapier or Make can still be fine if you only need a tiny report and you never expect to grow past a handful of keywords. If you’re unsure, Talk to an automation expert and you’ll get a straight recommendation based on your reporting needs.
Once this is running, rankings become background data instead of a recurring chore. Open the sheet, skim the email, and get back to work that actually improves the numbers.
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.
