Generate SEO meta tags with Gemini AI & competitor analysis using Google Sheets
This workflow automates the entire process of creating SEO-optimized meta titles and descriptions. It analyzes your webpage, spies on top-ranking competitors for the same keywords, and then uses a multi-step AI process to generate compelling, length-constrained meta tags.
🤖 How It Works This workflow operates in a three-phase process for each URL you provide:
Phase 1: Self-Analysis
When you add a URL to a Google Sheet with the status "New", the workflow scrapes your page's content.
The first AI then performs a deep analysis to identify the page's primary keyword, semantic keyword cluster, search intent, and target audience.
Phase 2: Competitor Intelligence
The workflow takes your primary keyword and performs a live Google search.
A custom code block intelligently filters the search results to identify true competitors.
A second AI analyzes their meta titles and descriptions to find common patterns and successful strategies.
Phase 3: Master Generation & Update
The final AI synthesizes all gathered intelligence—your page's data and the competitor's winning patterns—to generate a new, optimized meta title and description.
It then writes this new data back to your Google Sheet and updates the status to "Generated".
⚙️ Setup Instructions You should be able to set up this workflow in about 10-15 minutes ⏱️.
🔑 Prerequisites You will need the following accounts and API keys:
A Google Account with access to Google Sheets.
A Google AI / Gemini API key.
A SerpApi key for Google search data.
A ScrapingDog API key for reliable website scraping.
🛠️ Configuration Google Sheet Setup: Create a new Google Sheet. The workflow requires the following columns: URL, Status, Current Meta Title, Current Meta Description, Generated Meta Title, Generated Meta Description, and Ranking Factor.
Add Credentials:
Google Sheets Nodes: Connect your Google account credentials to the Google Sheets Trigger & Google Sheets nodes.
Google Gemini Nodes: Add your Google Gemini API key to the credentials for all three Google Gemini Chat Model nodes.
Scrape Website Node: In this HTTP Request node, go to Query Parameters and replace <your-api-key> with your ScrapingDog API key.
Googl SERP Node: In this HTTP Request node, go to Query Parameters and replace <your-api-key> with your SerpApi API key.
Configure Google Sheets Nodes:
Copy the Document ID from your Google Sheet's URL.
Paste this ID into the "Document ID" field in the following nodes: Google Sheets Trigger, Get row(s) in sheet1, and Update row in sheet.
In each of those nodes, select the correct sheet name from the "Sheet Name" dropdown.
✅ Activate Workflow Save and activate the workflow. To run it, simply add a new row to your Google Sheet containing the URL you want to process and set the "Status" column to New.
Generate SEO Meta Tags with Gemini AI & Competitor Analysis using Google Sheets
This n8n workflow automates the generation of SEO meta tags (title and description) for your products or services. It leverages Google Gemini AI for intelligent content creation and integrates with Google Sheets for both input (competitor data) and output (generated meta tags). Additionally, it performs basic competitor analysis by extracting existing meta tags from competitor URLs.
What it does
- Triggers on Google Sheet Updates: The workflow starts whenever a new row is added or an existing row is updated in a specified Google Sheet. This sheet is expected to contain competitor URLs.
- Extracts Competitor Meta Tags: For each URL provided in the Google Sheet, it makes an HTTP request to fetch the webpage content.
- Parses HTML for Meta Information: It then uses an HTML node to extract the existing meta title and meta description from the competitor's webpage.
- Prepares Data for AI Generation: The extracted competitor meta tags are combined with input from the Google Sheet (e.g., product name, keywords) to form a comprehensive prompt for the AI.
- Generates New Meta Tags with Gemini AI: It utilizes the Google Gemini Chat Model via a Basic LLM Chain to generate new, optimized SEO meta titles and descriptions based on the provided context and competitor analysis.
- Structures AI Output: A Structured Output Parser ensures the AI's response is consistently formatted into distinct meta title and meta description fields.
- Updates Google Sheet: Finally, the newly generated meta tags are written back to the original Google Sheet, enriching your data with AI-powered SEO content.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Google Sheets Account: A Google account with access to Google Sheets.
- Google Sheets Credential: An n8n credential configured for Google Sheets (OAuth 2.0).
- Google Gemini API Key: Access to the Google Gemini API.
- Google Gemini Credential: An n8n credential configured for Google Gemini.
- Competitor Data Google Sheet: A Google Sheet set up with at least a column for "Competitor URL" to trigger the workflow and receive the generated meta tags.
Setup/Usage
- Import the Workflow:
- Download the provided JSON file for this workflow.
- In your n8n instance, go to "Workflows" and click "New".
- Click the three dots in the top right corner and select "Import from JSON".
- Paste the workflow JSON or upload the file.
- Configure Credentials:
- Google Sheets Trigger & Node:
- Click on the "Google Sheets Trigger" node and the "Google Sheets" node.
- Select or create a new Google Sheets OAuth2 credential. Ensure it has access to your Google Drive and Sheets.
- Specify the "Spreadsheet ID" and "Sheet Name" for your competitor data.
- Google Gemini Chat Model:
- Click on the "Google Gemini Chat Model" node.
- Select or create a new Google Gemini credential, providing your API key.
- Google Sheets Trigger & Node:
- Configure Nodes:
- Google Sheets Trigger:
- Set the "Trigger On" option to "New Row" or "Updated Row" depending on your use case.
- Ensure the "Spreadsheet ID" and "Sheet Name" match your input sheet.
- HTTP Request: This node is pre-configured to fetch the URL from the Google Sheet. No specific changes should be needed unless you want to customize headers or other request parameters.
- HTML: This node is pre-configured to extract meta title and description. Review the CSS selectors if your target websites have unusual HTML structures.
- Edit Fields (Set): This node prepares the data for the AI. Ensure the fields being set (
productName,keywords,competitorMetaTitle,competitorMetaDescription) correctly map to your Google Sheet columns and the output from the HTML node. - Basic LLM Chain: This node orchestrates the prompt for Gemini. Review the prompt template to ensure it aligns with your desired meta tag generation strategy.
- Structured Output Parser: This node expects the AI output to be in a specific JSON format. Ensure the prompt in the "Basic LLM Chain" node guides Gemini to produce output that this parser can understand (e.g.,
{ "metaTitle": "...", "metaDescription": "..." }). - Google Sheets (Write Output):
- Ensure the "Spreadsheet ID" and "Sheet Name" match your output sheet (likely the same as the input sheet).
- Map the generated
metaTitleandmetaDescriptionfields to the appropriate columns in your Google Sheet.
- Google Sheets Trigger:
- Activate the Workflow: Once all credentials and nodes are configured, activate the workflow. It will now automatically process new or updated rows in your specified Google Sheet.
This workflow provides a powerful foundation for automating SEO meta tag generation, combining competitor insights with advanced AI capabilities.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.