HumationHuman + Automation
Back to Catalog

Website SEO health analytics with Google Sheets, PDF reports & Gmail alerts

WeblineIndiaWeblineIndia
547 views
2/3/2026
GitHubAutomationWebhooksPull RequestTemplating
Official Page

Automated SEO Health Monitoring & Reporting

This workflow automatically monitors the SEO health of websites stored in a Google Sheet. It fetches each website’s HTML, analyzes key SEO metrics (title, meta description, H1 count, canonical, robots, performance score, etc.) and updates results back into Google Sheets. If performance is poor (<50), it sends an alert email. For healthy sites, it generates a detailed PDF report and stores it in Google Drive.

Who’s it for

  • Digital marketing teams
  • SEO agencies
  • Website administrators who want automated SEO health checks
  • Businesses with multiple websites or landing pages to monitor

How it works

  1. Daily Trigger – Runs every day at 9 AM.
  2. Fetch Website List – Reads website URLs from Google Sheets.
  3. Crawl Websites – Uses HTTP requests to fetch each website’s HTML.
  4. SEO Analysis – Extracts SEO-related metadata (title, meta description, H1, etc.).
  5. Health Check – Scores SEO performance based on predefined rules.
  6. Decision Node – If score < 50 → Send alert email; else → Generate full SEO report.
  7. Update Logs – Logs results back into Google Sheets.
  8. Generate PDF Reports – Converts HTML reports into PDFs via PDF.co API.
  9. Save to Drive – Stores the PDF reports in Google Drive for long-term access.

How to set up

  1. Open n8n and import the workflow.
  2. Configure your Google Sheets credentials and specify the sheet containing your website URLs.
  3. Add your Gmail account to allow automated alert emails.
  4. Set up your Google Drive credentials for storing PDF reports.
  5. Obtain an API key from PDF.co and configure the HTTP Request node.
  6. Adjust the Schedule Trigger to the time that works best (default: 9 AM daily).
  7. Test the workflow with a sample domain list.

Requirements

  • n8n instance (self-hosted or cloud)
  • Google Sheets account (to store website URLs and logs)
  • Gmail account (for sending alerts)
  • Google Drive account (to save SEO reports)
  • PDF.co API Key (for HTML → PDF conversion)

How to customize

  • Change performance threshold: Modify the IF node condition (default <50).
  • Custom SEO rules: Edit the “SEO Health Check” Function node to add/remove checks (e.g., missing schema tags, page load times).
  • Different output storage: Replace Google Drive with Dropbox, S3 or OneDrive.
  • Alternate notification channels: Swap Gmail with Slack, Microsoft Teams or Telegram.

Add-ons

  • Send Slack/Teams notifications for low scores.
  • Add PageSpeed Insights API for performance scoring.
  • Generate weekly summary reports per domain.
  • Integrate with Notion/Confluence to log SEO health history.

Use Case Examples

  • An SEO agency monitors 100+ client websites daily and sends alerts when a site has poor SEO signals.
  • A company’s marketing manager gets a daily SEO health PDF report stored in Drive.
  • A SaaS product team automatically logs performance changes for each release.

Common Troubleshooting

| Issue | Possible Cause | Solution | | ------------------------------------ | ------------------------------------------------ | --------------------------------------------------------------------------- | | Workflow fails at HTTP Crawl | Website blocks requests / timeout | Increase timeout in Set Config node or add retry logic. | | Always returns https://example.com | Missing canonical / OG tags in HTML | Enhanced code now infers from JSON-LD or domain detection. Update analyzer. | | PDF not generated | Invalid API key or wrong endpoint in PDF.co node | Verify PDF.co API key and endpoint URL. | | Email not sending | Gmail credentials not set or blocked | Reconnect Gmail in n8n credentials manager. | | Google Sheet not updating | Wrong column mapping in Update Sheet node | Check node mapping: domain column vs performance/date columns. | | Google Drive upload fails | Missing folder permissions | Ensure correct Drive folder ID and credentials. |

Need Help?

If you’d like assistance setting up, customizing or scaling this workflow for your use case, our n8n automation team at WeblineIndia can help you:

  • Tailor SEO rules for your industry.
  • Connect to additional APIs (Ahrefs, Semrush, PageSpeed).
  • Automate weekly/monthly reporting with summary dashboards.

Website SEO Health Analytics with Google Sheets & PDF Reports

This n8n workflow automates the process of fetching website SEO health data, storing it in Google Sheets, generating PDF reports, and sending email alerts. It's designed to help you regularly monitor website performance and get notified of critical changes.

What it does

This workflow performs the following key steps:

  1. Schedules Execution: The workflow is triggered on a predefined schedule (e.g., daily, weekly).
  2. Reads Website URLs: It fetches a list of website URLs to monitor from a specified Google Sheet.
  3. Performs SEO Health Check: For each URL, it makes an HTTP request to an external SEO analytics service (e.g., a custom API or a third-party tool).
  4. Processes Analytics Data: It processes the received SEO data.
  5. Conditional Logic: It applies conditional logic to determine if certain SEO metrics meet predefined criteria (e.g., if a score drops below a threshold).
  6. Updates Google Sheet: It updates the Google Sheet with the latest SEO health data for each website.
  7. Generates PDF Report: For websites that meet specific conditions (e.g., a significant change in SEO score), it generates an HTML report and converts it into a PDF.
  8. Uploads PDF to Google Drive: The generated PDF report is then uploaded to a designated folder in Google Drive.
  9. Sends Email Alerts: If critical conditions are met, it sends an email alert via Gmail, potentially including the PDF report as an attachment.
  10. Merges Data: It merges data from different branches of the workflow to ensure all relevant information is processed.
  11. Sets Fields: It manipulates and sets data fields as needed throughout the workflow for consistent processing.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: To store and retrieve website URLs and SEO data.
  • Google Drive Account: To store generated PDF reports.
  • Gmail Account: To send email alerts.
  • External SEO Analytics Service/API: An endpoint that can provide website SEO health data when queried with a URL. This could be a custom script or a third-party SEO tool with an API.
  • Credentials:
    • Google Sheets OAuth2 credentials.
    • Google Drive OAuth2 credentials.
    • Gmail OAuth2 credentials.
    • Any necessary API keys or authentication for your external SEO analytics service.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets, Google Drive, and Gmail OAuth2 credentials within n8n.
    • Configure any required credentials for the HTTP Request node to connect to your SEO analytics service.
  3. Configure Google Sheets Node (ID: 18):
    • Specify the Spreadsheet ID and Sheet Name where your website URLs are listed.
    • Ensure the sheet has a column for URLs (and potentially other relevant data for updates).
  4. Configure HTTP Request Node (ID: 19):
    • Update the URL to point to your SEO analytics service.
    • Adjust the request method, headers, and body as per your service's API documentation.
    • Map the website URL from the Google Sheet to the request body/parameters.
  5. Configure If Node (ID: 20):
    • Define the conditions for triggering alerts or report generation based on the data received from the HTTP Request node.
  6. Configure HTML Node (ID: 842):
    • Customize the HTML template to generate your desired PDF report layout using the SEO data.
  7. Configure Google Drive Node (ID: 58):
    • Specify the folder ID in Google Drive where the PDF reports should be uploaded.
  8. Configure Gmail Node (ID: 356):
    • Set the recipient email addresses, subject line, and email body for alerts.
    • Optionally, configure it to attach the generated PDF report.
  9. Configure Cron Node (ID: 7):
    • Set your desired schedule for the workflow to run (e.g., daily, weekly).
  10. Activate the Workflow: Once all configurations are complete, activate the workflow.

This will enable automated monitoring of your website's SEO health, with data stored in Google Sheets, reports generated, and alerts sent for critical changes.

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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

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://&lt;your-instance&gt;.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.

Le NguyenBy Le Nguyen
942