Description
n8n-nodes-seranking
n8n community node for SE Ranking‘s unified API — 194 operations across 21 resources: AI Search, Backlinks, Domain Analysis, Keyword Research, SERP Classic, Website Audits, Project Management, Competitors, Backlink Checker, Sub-Accounts, and more.
SE Ranking is a comprehensive SEO platform providing keyword research, competitor analysis, website audits, backlink monitoring, and AI search visibility tracking.
n8n is a workflow automation platform.
—
Table of Contents
- Installation
- Credentials
- Compatibility
- Operations
- Usage Examples
- API Documentation
- Version History
- Node.js 18.x or higher
- n8n 1.0.0 or higher
- SE Ranking API Token (Get it here)
—
Installation
Follow the installation guide in the n8n community nodes documentation.
Prerequisites
npm (Recommended)
npm install @seranking/n8n-nodes-seranking
Quick Installation
1. Navigate to your n8n installation directory
2. Install the package:
npm install @seranking/n8n-nodes-seranking
3. Restart n8n
Manual Install
Step 1: Install n8n
npm install n8n -g
Step 2: Install SE Ranking Node
Option A: From .tgz file
npm install -g seranking-n8n-nodes-seranking-1.3.0.tgz
Option B: From GitHub
npm install -g git+https://github.com/seranking/n8n-nodes-seranking.git
Option C: From source (for developers)
cd ~/.n8n/custom
git clone https://github.com/seranking/n8n-nodes-seranking.git
cd n8n-nodes-seranking
npm install
npm run build
npm link
Step 3: Start n8n
n8n start
Open http://localhost:5678 and add the SE Ranking node to your workflow.
Step 4: Configure Credentials
1. Add SE Ranking node
2. Click “Create New Credential” for SE Ranking API — enter your API token
3. Save
> v2.0.0 note: SE Ranking unified its two APIs (Data API + Project API) onto a single host (api.seranking.com) with a single token in 2026-05. The node now uses one credential type for everything. If you’re upgrading from v1.x, see the Migration section below.
Docker Installation
Create custom directory
mkdir -p ~/.n8n/custom
cd ~/.n8n/customInstall node
npm install @seranking/n8n-nodes-seranking
OR
npm install git+https://github.com/seranking/n8n-nodes-seranking.gitRun n8n
docker run -it --rm
--name n8n
-p 5678:5678
-v ~/.n8n:/home/node/.n8n
docker.n8n.io/n8nio/n8n
Verify Installation
1. Open n8n at http://localhost:5678
2. Search for “SE Ranking” node
3. If it appears, installation successful ✓
Updating
From npm:
npm update @seranking/n8n-nodes-seranking
From .tgz:
npm uninstall -g seranking-n8n-nodes-seranking
npm install -g seranking-n8n-nodes-seranking-NEW-VERSION.tgz
From GitHub:
npm install -g git+https://github.com/seranking/n8n-nodes-seranking.git
From source:
cd ~/.n8n/custom/n8n-nodes-seranking
git pull
npm install
npm run build
Then restart n8n
—
Credentials
To use this node, you need:
1. SE Ranking Account — Sign up at seranking.com
2. API Token — Generate from your SE Ranking API Dashboard
Setting up credentials in n8n
1. Open any workflow and add the SE Ranking node
2. In the SE Ranking API credential slot, click “Create New Credential” and enter your API token
3. Click Save — the credential is tested by hitting GET /v1/account/subscription
Migrating from v1.x
v1.x used two separate credential types (seRankingApi for Data API and seRankingProjectApi for Project API) with two different base URLs and two different tokens. As of v2.0.0:
api4.seranking.com is deprecated; everything now lives under api.seranking.com/v1/v1/project-management/... path prefixIf you’re upgrading and have saved credentials of type seRankingProjectApi, you’ll need to re-save them as seRankingApi on each affected node. The v1.5.13 release is preserved on npm for rollback (npm install @seranking/n8n-nodes-seranking@1.5.13).
—
Compatibility
api.seranking.com/v1Operations
This node provides access to 21 SE Ranking resources with 194 total operations on the unified API:
Data API (6 resources, 65 operations)
AI Search (5 operations)
Backlinks (25 operations)
Domain Analysis (11 operations)
Keyword Research (5 operations)
Website Audit (14 operations)
SERP Classic (5 operations)
—
Project API (14 resources, 107 operations)
Project Management (20 operations)
Project Groups (5 operations)
AI Result Tracker (14 operations)
Keyword Groups (5 operations)
Competitors (7 operations)
URL Tags (4 operations)
Analytics Traffic (2 operations)
Account System (3 operations)
Sub-Account Management (8 operations)
General Data (4 operations)
Marketing Plan (5 operations)
Website Audit (Project) (21 operations)
Backlink Checker (17 operations)
Search Volume (4 operations)
Usage Examples
Ready-to-use workflows demonstrating real-world applications of the SE Ranking node. Each example includes importable n8n workflows, setup instructions, and expected outputs.
—
🤖 Example 1: AI Search Visibility Tracker
Track your brand’s presence and competitive gaps across ChatGPT, Perplexity, and Gemini
Two comprehensive workflows for monitoring AI visibility and identifying content opportunities.
Workflow 1: AI Search Visibility Tracker
Monitor how often your brand appears in AI-powered search engines with automated historical tracking.
Workflow 2: Competitor Topic Gap Analysis
Identify content opportunities by analyzing where competitors outrank you in AI search and traditional SEO.
Best For: Marketing teams tracking AI SEO performance, Content strategists planning editorial calendars, SEO teams doing competitive intelligence
📂 View Full Guide & Download Workflow →
—
🔗 Example 2: Backlinks Monitoring & Analysis
Track new/lost backlinks, monitor domain authority, and analyze anchor text distribution
Automatically monitor backlink portfolio health with daily tracking and alerts for significant changes.
What You’ll Get:
Best For: SEO agencies managing client backlink portfolios, In-house SEO teams tracking link-building campaigns
📂 View Full Guide & Download Workflow →
—
📊 Example 3: Domain Analysis Data Processor
Transform SE Ranking API data into structured Google Sheets reports
Automatically process and organize domain analysis data with intelligent type detection.
What You’ll Get:
Best For: SEO agencies managing multiple clients, Enterprise teams tracking regional performance
📂 View Full Guide & Download Workflow →
—
🔍 Example 4: Keyword Research Automation
Automate comprehensive keyword research with trend analysis
Build an automated keyword intelligence pipeline with historical tracking and SERP features.
What You’ll Get:
Best For: Content strategists planning editorial calendars, SEO specialists doing competitor research
📂 View Full Guide & Download Workflow →
—
🔧 Example 5: Website Audit Automation
Automatically crawl sites, detect issues, and generate reports
Schedule regular technical SEO audits and get alerts when critical issues are detected.
What You’ll Get:
Best For: Development teams doing pre-launch checks, SEO consultants managing multiple client sites
📂 View Full Guide & Download Workflow →
—
📍 Example 6: SERP Classic Tracking
Track keyword rankings and analyze SERP features across search engines
Monitor keyword positions, SERP features, and competitor visibility with automated rank tracking.
What You’ll Get:
Best For: SEO teams tracking keyword performance, Local businesses monitoring location-based rankings, Agencies managing multi-client SERP tracking
📂 View Full Guide & Download Workflow →
—
🔔 Example 7: SERP Pingback Webhooks
Get notified instantly when SERP results are ready — no polling required!
Instead of checking task status repeatedly, SE Ranking calls your webhook when done.
#### Simple Workflow (3 nodes)
[Webhook] → [SE Ranking: Get Results] → [Google Sheets]
↑
└── SE Ranking calls this when task completes
#### Step-by-Step Setup
Step 1: Create Webhook to Receive Notifications
Add a Webhook node:
| Setting | Value |
|———|——-|
| HTTP Method | GET |
| Path | serp-callback |
| Response Mode | Immediately |
Click “Listen for test event” and copy the URL.
Step 2: Create SERP Task with Pingback
In another workflow, add SE Ranking node:
| Setting | Value |
|———|——-|
| Resource | SERP Classic |
| Operation | Add Tasks |
| Search Engine | google |
| Device | desktop |
| Language Code | en |
| Location ID | 2840 (USA) |
| Keywords | seo tools |
| Tag | my-test |
| Pingback URL | https://your-n8n.com/webhook/serp-callback?id=$id&tag=$tag |
> ⚠️ Use $id and $tag exactly as shown — SE Ranking replaces them with real values.
Step 3: Fetch Results When Webhook Fires
Back in your webhook workflow, add SE Ranking node after the Webhook:
| Setting | Value |
|———|——-|
| Resource | SERP Classic |
| Operation | Get Results |
| Task ID | {{ $json.query.id }} |
That’s it! When SE Ranking finishes, it calls your webhook, which fetches the results automatically.
#### Using in Advanced Workflows
Add pingback to any existing SERP workflow:
[Schedule] → [SE Ranking: Add Tasks] ──(async)──→ [Webhook] → [Get Results] → [Process]
│
└── pingback_url triggers webhook when done
—
🏆 Example 8: AI Search Leaderboard
Compare your AI visibility against competitors in one request.
See how your brand performs vs competitors across ChatGPT, Perplexity, Gemini, and Google AI Overview.
#### Simple Workflow (2 nodes)
[Manual Trigger] → [SE Ranking: Get Leaderboard] → [View Results]
#### Step-by-Step Setup
Step 1: Add SE Ranking Node
| Setting | Value |
|———|——-|
| Resource | AI Search |
| Operation | Get Leaderboard |
| Primary Target | yoursite.com |
| Primary Brand | Your Brand |
| Source | us |
| AI Engines | Select: chatgpt, perplexity, ai-overview |
Step 2: Add Competitors
Click “Add Competitor” and enter:
| Target Domain | Brand Name |
|—————|————|
| competitor1.com | Competitor 1 |
| competitor2.com | Competitor 2 |
Step 3: Run and View Results
Execute the workflow. Response includes:
#### Using in Advanced Workflows
Combine with scheduling and reporting:
[Schedule: Weekly] → [Get Leaderboard] → [Code: Calculate Gaps] → [Google Sheets] → [Slack Alert]
Example: Find where competitors beat you
// In Code node after Get Leaderboard
const dominated = $input.all().filter(item =>
item.json.competitorpresence > item.json.primarypresence
);
return dominated;
—
🚀 Quick Start
1. Browse the example that matches your use case
2. Download the workflow.json file from the example folder
3. Import into n8n (Workflows → Import from File)
4. Configure your SE Ranking API credentials
5. Run and customize to your needs
Need help? Each example includes troubleshooting tips and configuration details.
—
API Documentation
This node implements the SE Ranking unified API (api.seranking.com/v1):
Data API resources:
Project API resources (under /v1/project-management/):
For detailed API specifications, visit SE Ranking API Documentation.
—
Version History
v2.0.1 (Current)
keywordsids (plural), not keywordidssite_ids must be a single integer per request; now loops one call per site so multiple IDs workv2.0.0
api.seranking.com). Old seRankingProjectApi credential type removed. Re-save affected nodes with unified SE Ranking API credential.v1.5.13
/api/ prefixv1.5.8
v1.3.6
v1.3.5
v1.3.3
v1.3.0
v1.2.3
v1.0.7
—
Features
✅ 192 Operations – Comprehensive coverage across 21 resources (unified API)
✅ Pingback Webhooks – Event-driven notifications for SERP task completion
✅ AI Competitive Analysis – Leaderboard comparison across LLM engines
✅ Type Safety – Full TypeScript implementation with strict typing
✅ Error Handling – Detailed error messages with troubleshooting hints
✅ Pagination – Efficient handling of large datasets
✅ Advanced Filtering – Volume, position, CPC, difficulty filters
✅ Validation – Input validation for domains, country codes, and parameters
✅ Authentication – Automatic credential management and testing
✅ Rate Limiting – Built-in rate limit handling with retry logic
✅ Batch Operations – Support for multiple keywords/domains
✅ Backlink Monitoring – Complete backlink analysis and tracking
✅ Website Auditing – Technical SEO audits with issue detection
✅ SERP Tracking – Keyword ranking and SERP features analysis
✅ Advanced Filtering – Volume, position, CPC, difficulty, traffic, search intent, SERP features, keyword word count, and include/exclude keyword pattern filters, and the new SERP Feature Link filter (filter[serpfeatures2]) — which lets you filter keywords where your domain is specifically linked within a SERP feature (e.g. AI Overviews, Reviews), distinct from the existing serpFeatures filter which only checks for feature presence on the SERP.
—
Limitations
—
Rate Limiting
This node includes built-in rate limiting (300ms delay between requests) to help prevent hitting SE Ranking API limits.
If you still encounter “429 Too Many Requests” errors when processing large amounts of data, you can use n8n’s built-in solutions:
1. Retry On Fail: Open node Settings → enable “Retry On Fail” → set “Wait Between Tries” to 1000ms or more
2. Split In Batches + Wait: Use the “Loop Over Items” node to process items in smaller batches with a “Wait” node between requests
For more details, see n8n’s rate limiting documentation.
—
Troubleshooting
Pingback Not Received
Problem: SERP task completes but webhook never fires
Solution:
1. Use production webhook URL (not webhook-test)
2. Ensure URL is publicly accessible (not localhost)
3. Use HTTPS
4. Respond within 5 seconds with HTTP 200
5. Use literal $id and $tag placeholders
Valid URL format:
✅ https://your-domain.com/webhook/serp-callback?id=$id&tag=$tag
❌ https://localhost:5678/webhook/...
❌ https://your-domain.com/webhook-test/...
---Authentication Errors
Problem: "401 Unauthorized" or "Invalid API Token"
Solution:
1. Verify API token is correct (copy from SE Ranking dashboard)
2. Ensure your SE Ranking API credential has the correct unified token
3. Check token hasn't expired
4. Regenerate token in SE Ranking dashboard if needed
5. Test credentials using the "Test" button in n8n
---
Invalid Source/Country Code
Problem: "Invalid source" or "400 Bad Request"
Solution:
1. Use correct Alpha-2 country codes: us, uk, de, fr, es, it, ca, au, pl
2. Country code must be lowercase
3. Check if SE Ranking has data for that region
4. Some engines/features may not be available in all regions
---
Domain Format Errors
Problem: "Invalid domain format" or "Domain validation failed"
Solution:
1. Remove http:// or https:// from domain (unless operation specifies full URL)
2. Remove www. prefix
3. Remove trailing slashes
4. Use format: example.com not www.example.com/
5. For subdomains: blog.example.com is valid
Valid formats:
✅ example.com
✅ blog.example.com
✅ example.co.uk
❌ https://example.com
❌ www.example.com
❌ example.com/ ---
Empty Results
Problem: No data returned from API
Solution:
1. Verify domain has data in SE Ranking database
2. Check if domain is indexed/tracked
3. Try different source/region (domain may rank elsewhere)
4. Adjust filters - they may be too restrictive
5. For new domains, wait 24-48 hours for initial data collection
6. Check if keyword has search volume in selected region
---
Timeout Errors
Problem: "Request timeout" or "Operation exceeded time limit"
Solution:
1. Reduce limit parameter (try 100 instead of 1000)
2. Use pagination with offset to fetch data in chunks
3. For keyword export, reduce number of keywords (try 100 instead of 700)
4. Remove history_trend parameter if not needed (adds processing time)
5. Use "Get Worldwide Aggregate" instead of getting all regional databases
---
Too Many Keywords Error
Problem: "Too many keywords" or "Maximum 700 keywords exceeded"
Solution:
1. Split keyword list into batches of 700 or less
2. Use multiple node executions with different batches
3. Consider using keyword suggestion operations first to narrow down list
---
Rate Limit Errors
Problem: "429 Too Many Requests" or "Rate limit exceeded"
Solution:
1. Add delay between requests using n8n Wait node
2. Reduce frequency of scheduled workflows
3. Use batch operations instead of individual requests
4. Upgrade SE Ranking plan for higher rate limits
5. Implement exponential backoff retry logic
---
Best Practices
1. Efficient Data Retrieval
✅ DO:
Use "Get Worldwide Aggregate" for quick domain overview
Use pagination for large datasets (limit: 100-500)
Cache frequently accessed data
Use filters to reduce result size ❌ DON'T:
Request all databases when you only need one region
Fetch 10,000 keywords at once without pagination
Request history_trend unless specifically needed 2. Keyword Research
✅ DO:
Start with similar keywords, then expand to related/questions
Use filters to focus on achievable opportunities (difficulty < 50)
Export metrics in batches of 200-500 keywords
Include multiple keyword types for comprehensive research ❌ DON'T:
Request all keyword types simultaneously without filtering
Ignore difficulty scores (targeting too-hard keywords wastes effort)
Forget to check search intent and relevance 3. Backlink Monitoring
✅ DO:
Schedule daily checks for new/lost backlinks
Use "Get Summary" for quick health checks
Export full data monthly for archival
Track Domain InLink Rank trends over time
Monitor anchor text distribution for natural link profile ❌ DON'T:
Poll "Get All Backlinks" every hour (use history endpoints)
Download exports without checking status first
Ignore referring domain diversity (IP distribution) 4. Competitor Analysis
✅ DO:
Use "Get Competitors" to identify relevant competitors first
Track competitor changes over time (weekly/monthly)
Focus on keywords where competitors rank in top 20
Analyze multiple competitors to find patterns ❌ DON'T:
Compare against irrelevant competitors
Track too many competitors (focus on top 5-10)
Ignore competitor's content strategy and backlink profile 5. AI Search Optimization
✅ DO:
Monitor multiple engines (ChatGPT, Perplexity, Gemini)
Track brand mentions and citation types
Focus on high-volume prompts
Use base_domain scope for brand monitoring ❌ DON'T:
Only track one LLM engine
Ignore prompt context and user intent
Forget to optimize content based on insights 6. Website Auditing
✅ DO:
Use Advanced Audit for JavaScript-heavy sites (React, Vue, Angular)
Set realistic max_pages based on site size
Schedule monthly audits for ongoing monitoring
Compare historical audits to track improvements
Export issues to spreadsheet for team collaboration ❌ DON'T:
Set max_pages too high (start with 1000-5000)
Ignore robots.txt unless intentionally testing blocked areas
Run audits too frequently (daily audits waste credits) 7. Error Handling
✅ DO:
Implement retry logic for transient errors
Log errors for debugging
Use n8n's "Continue on Fail" for batch operations
Validate input before API calls ❌ DON'T:
Ignore error messages (they contain helpful hints)
Retry immediately after rate limit (wait 60s)
Skip input validation ---
Development Setup
bash
Clone the repository
git clone https://github.com/seranking/n8n-nodes-seranking.git
Navigate to directory
cd n8n-nodes-seranking
Install dependencies
npm install
Build the node
npm run build
Watch for changes during development
npm run dev
Project Structure
n8n-nodes-seranking/
│
├── credentials/
│ └── SeRankingApi.credentials.ts # API credentials configuration
│
├── nodes/
│ └── SeRanking/
│ ├── SeRanking.node.ts # Main node definition
│ ├── dataApi/
│ │ ├── operations/
│ │ │ ├── AiSearchOperations.ts # AI Search operations logic
│ │ │ ├── BacklinksOperations.ts # Backlinks operations logic
│ │ │ ├── DomainAnalysisOperations.ts # Domain Analysis operations logic
│ │ │ ├── KeywordResearchOperations.ts # Keyword Research operations logic
│ │ │ ├── WebsiteAuditOperations.ts # Website Audit operations logic
│ │ │ └── SerpClassicOperations.ts # SERP Classic operations logic
│ │ └── descriptions/
│ │ ├── AiSearchDescription.ts # AI Search UI definitions
│ │ ├── BacklinksDescription.ts # Backlinks UI definitions
│ │ ├── DomainAnalysisDescription.ts # Domain Analysis UI definitions
│ │ ├── KeywordResearchDescription.ts # Keyword Research UI definitions
│ │ ├── WebsiteAuditDescription.ts # Website Audit UI definitions
│ │ └── SerpClassicDescription.ts # SERP Classic UI definitions
│ ├── projectApi/
│ │ ├── operations/
│ │ │ ├── ProjectManagementOperations.ts # Project Management operations
│ │ │ ├── ProjectGroupsOperations.ts # Project Groups operations
│ │ │ ├── AiResultTrackerOperations.ts # AI Result Tracker operations
│ │ │ ├── AirtGroupsOperations.ts # AIRT Groups (prompt groups) operations
│ │ │ ├── KeywordGroupsOperations.ts # Keyword Groups operations
│ │ │ ├── CompetitorsOperations.ts # Competitors operations
│ │ │ ├── UrlTagsOperations.ts # URL Tags operations
│ │ │ ├── AnalyticsTrafficOperations.ts # Analytics Traffic operations
│ │ │ ├── AccountSystemOperations.ts # Account System operations
│ │ │ ├── SubAccountOperations.ts # Sub-Account operations
│ │ │ ├── GeneralDataOperations.ts # General Data operations
│ │ │ ├── MarketingPlanOperations.ts # Marketing Plan operations
│ │ │ ├── WebsiteAuditOperations.ts # Website Audit (Project) operations
│ │ │ ├── BacklinkCheckerOperations.ts # Backlink Checker operations
│ │ │ └── SearchVolumeOperations.ts # Search Volume operations
│ │ └── descriptions/
│ │ ├── ProjectManagementDescription.ts # Project Management UI definitions
│ │ ├── ProjectGroupsDescription.ts # Project Groups UI definitions
│ │ ├── AiResultTrackerDescription.ts # AI Result Tracker UI definitions
│ │ ├── AirtGroupsDescription.ts # AIRT Groups UI definitions
│ │ ├── KeywordGroupsDescription.ts # Keyword Groups UI definitions
│ │ ├── CompetitorsDescription.ts # Competitors UI definitions
│ │ ├── UrlTagsDescription.ts # URL Tags UI definitions
│ │ ├── AnalyticsTrafficDescription.ts # Analytics Traffic UI definitions
│ │ ├── AccountSystemDescription.ts # Account System UI definitions
│ │ ├── SubAccountDescription.ts # Sub-Account UI definitions
│ │ ├── GeneralDataDescription.ts # General Data UI definitions
│ │ ├── MarketingPlanDescription.ts # Marketing Plan UI definitions
│ │ ├── WebsiteAuditDescription.ts # Website Audit (Project) UI definitions
│ │ ├── BacklinkCheckerDescription.ts # Backlink Checker UI definitions
│ │ └── SearchVolumeDescription.ts # Search Volume UI definitions
│ └── utils/
│ ├── validators.ts # Input validators
│ └── apiRequest.ts # API request handler
│
├── Usage-Examples/
│ ├── AI-Search/
│ │ ├── AIVisibilityTracker.json # Workflow 1: AI Visibility Tracker
│ │ ├── AIVisibilityTrackerResults.xlsx # Workflow 1 Results
│ │ ├── SERanking-CompetitorTopicGapAnalysis.json # Workflow 2: Competitor Topic Gap Analysis
│ │ ├── SE Ranking – Competitor Topic Gap Analysis.xlsx # Workflow 2 Results
│ │ └── README.md # AI Search workflows documentation
│ │
│ ├── Backlinks/
│ │ ├── Backlinks-Monitoring&Analysis.json # Backlinks monitoring workflow
│ │ └── README.md # Backlinks workflow documentation
│ │
│ ├── Domain-Analysis/
│ │ ├── DomainAnalysisMulti-FormatProcessor.json # Workflow 1: Multi-Format Data Processor
│ │ ├── DomainAnalysisMulti-FormatProcessor.xlsx # Workflow 1 Results
│ │ ├── DomainTraffic&CompetitorAnalysis.json # Workflow 2: Multi-Domain Traffic Analysis
│ │ ├── DomainTraffic&CompetitorAnalysis.xlsx # Workflow 2 Results
│ │ ├── GetRegionalDB_Overview.jpg # Screenshot: Regional Overview
│ │ ├── GetWorldwideAggregate.jpg # Screenshot: Worldwide Aggregate
│ │ ├── GetDomainKeywords.jpg # Screenshot: Keywords Analysis
│ │ ├── Get_Competitors.jpg # Screenshot: Competitors
│ │ ├── Get keywords comparison Organic Common Keywords.jpg # Screenshot: Keywords Comparison
│ │ ├── Get keywords comparison Organic Keyword Gap.jpg # Screenshot: Organic Gap
│ │ ├── Get keywords comparison Paid Keyword Gap.jpg # Screenshot: Paid Gap
│ │ ├── Get keywords comparison Paid.jpg # Screenshot: Paid Comparison
│ │ ├── Get overview history Organic.jpg # Screenshot: Organic History
│ │ ├── Get overview history Paid.jpg # Screenshot: Paid History
│ │ ├── Get paid ads for domain.jpg # Screenshot: Domain Ads
│ │ ├── Get paid ads for keyword.jpg # Screenshot: Keyword Ads
│ │ ├── Get audit links.png # Screenshot: Audit Links
│ │ ├── Get crawled pages.png # Screenshot: Crawled Pages
│ │ ├── Get issues for URL.png # Screenshot: URL Issues
│ │ └── README.md # Domain Analysis workflows documentation
│ │
│ ├── Keyword-Research/
│ │ ├── KeywordResearch→GoogleSheetsPipeline.json # Keyword research workflow
│ │ ├── KeywordResearch→GoogleSheetsPipeline.xlsx # Workflow results
│ │ ├── GetSimilarKeywords.jpg # Screenshot: Similar Keywords
│ │ ├── GetRelatedKeywords.jpg # Screenshot: Related Keywords
│ │ ├── GetQuestionKeywords.jpg # Screenshot: Question Keywords
│ │ ├── GetLongtailKeywords.jpg # Screenshot: Longtail Keywords
│ │ └── README.md # Keyword Research workflow documentation
│ │
│ ├── Website-Audit/
│ │ ├── Website-Audit-Technical-SEO-Monitor.json # Website audit workflow
│ │ └── README.md # Website Audit workflow documentation
│ │
│ └── SERP-Classic/
│ ├── Gelato-Small-Towns-Amsterdam-Area.json # SERP tracking workflow
│ ├── Gelato Small Towns Amsterdam Area.xlsx # Workflow results
│ └── README.md # SERP Classic workflow documentation
│
├── package.json
├── package-lock.json
├── tsconfig.json
└── README.md
“`
—
Acknowledgments
—
Keywords
n8n, n8n-custom-node, seranking, seo, keyword-research, domain-analysis, ai-search, llm-visibility, serp-tracking, competitive-analysis, seo-automation, workflow-automation, project-management, backlink-checker, website-audit, search-volume, marketing-plan, sub-account, ai-result-tracker
—
Made with ❤️ for SEO professionals using n8n
