Mohammadreza azari
SEO & Automation Consultant focused on optimizing sales and marketing processes through n8n and smart workflow automation solutions.
Templates by Mohammadreza azari
Send Telegram notification for new WooCommerce orders
🔧 How it works: • The workflow triggers when a new order is created in WooCommerce. • It extracts order details including ID, status, total, and products list. • Sends a formatted message via Telegram to the store admin. • Includes a clickable button that links directly to the order view page. ⚙️ Set up steps: • Estimated setup time: 5–10 minutes. • Requires active WooCommerce REST API credentials. • Requires a Telegram bot and your admin chat ID. • Replace the Telegram chatId and WooCommerce credentials in the workflow. • Make sure your WooCommerce site allows external API access.
By Mohammadreza azariDetect cannibalized keywords and competing pages with Google Search Console
Find Cannibalized Pages (Google Search Console) This n8n template helps you detect page cannibalization in Google Search Console (GSC): situations where multiple pages on your site rank for the same query and more than one page gets clicks. Use it to spot competing URLs, consolidate content, improve internal linking, and protect your CTR/rankings. --- Good to know Data source: Google Search Console Search Analytics (Dimensions: query, page). Scope: Defaults to last 12 months and up to 10,000 rows per run (adjustable). Logic: Keeps only queries with >1 page and where the second page has clicks > 0 → higher confidence of true cannibalization. Privacy: Template ships with a placeholder property (sc-domain:example.com) and a neutral credential name; replace both after import. Cost: n8n nodes used here are free. GSC usage is also free (subject to Google limits). --- How it works Manual Start — run the workflow on demand. Google Search Console — fetch last 12 months of query–page rows. Summarize — group by query, building two arrays: appended_page[] → all pages seen for that query appendedclicks[] → clicks for each page-query row (aligned with appendedpage) Filter — pass only queries where: count_query > 1 (more than one page involved), and appended_clicks[1] > 0 (the second page also received clicks) Output — list of cannibalized queries with the competing pages and their click counts. Example output json { "query": "best running shoes", "appended_page": [ "https://example.com/blog/best-running-shoes", "https://example.com/guide/running-shoes-2025" ], "appended_clicks": [124, 37], "count_query": 3 } How to use Import the JSON into n8n. Open the Google Search Console node and: Connect your Google Search Console OAuth2 credential. Replace siteUrl with your property (sc-domain:your-domain.com). Press Execute Workflow on Manual Start. Review the output — focus on queries where the second page has meaningful clicks. 💡 Tip: If your site is large, start with a shorter date range (e.g., 90 days) or raise rowLimit. --- Requirements Access to the target property in Google Search Console. One Google Search Console OAuth2 credential in n8n. --- Customising this workflow More robust detection: In the Summarize node, change clicks aggregation from append to sum. Then filter for “at least 2 pages with sum_clicks > 0” to avoid any dependency on row order. Scoring & sorting: Add a Code/Function node to sort competing pages by clicks or impressions and compute click-share per page. Deeper analysis: Include impressions and position in the GSC node and extend the summary to prioritize fixes (e.g., high impressions + split clicks). Reporting: Send results to Google Sheets or export a CSV; create a dashboard of top cannibalized queries. Thresholds: Expose minimum click thresholds as workflow variables (e.g., second page clicks ≥ 3) to reduce noise. --- Troubleshooting Empty results: Widen date range, increase rowLimit, or temporarily relax the filter (remove the second-page click condition to validate data flow). No property data: Ensure you used sc-domain: vs. https:// property format correctly and that your user has GSC access. Credential issues: Reconnect the OAuth2 credential and reauthorize if needed.
By Mohammadreza azariTrack new search queries with zero-click analysis in Google Search Console
Google Search Console – Discover New Keywords (Last 7 Days) This n8n template demonstrates how to identify new queries in Google Search Console that had no impressions in the past but appeared for the first time in the last 7 days. It also segments them into two groups: queries with impressions but no clicks yet (Zero Click) and queries that already have clicks (Has Click). Use cases include: Finding emerging SEO opportunities. Identifying keywords where you already get impressions but need to optimize for clicks. Tracking newly discovered queries week over week. --- Good to know This workflow requires a connected Google Search Console account. You can adjust the date ranges in the Compare search analytics node to suit your needs. Works best when scheduled weekly, but in this template we start with manual execution for flexibility. --- How it works Manual Start – Run the workflow manually to fetch fresh data. Compare Search Analytics – Compares the last 7 days against a custom reference period in Google Search Console. Filter (No Past Impressions) – Keeps only queries that had zero impressions in the reference period. Zero Click – Filters queries with impressions but no clicks. Has Click – Filters queries with impressions and clicks. The final output is two clean data sets: Zero Click queries: impressions but no clicks → improve meta descriptions, titles, or content relevance. Has Click queries: new queries already generating clicks → consider creating supporting content and optimizing further. --- How to use Start with the Manual Start node. Add your Google Search Console credentials in the Compare search analytics node. Optionally, replace the Manual Start with a Schedule Trigger (e.g., weekly) to automate monitoring. Export results or connect them to Slack, Email, or Google Sheets for reporting. --- Requirements Google Search Console account (with property access). n8n instance with the Google Search Console integration enabled. --- Customising this workflow Adjust the date ranges in the compare node (e.g., last 30 days vs. previous 30 days). Replace the output branches with integrations like Slack, Notion, or Google Sheets to automatically deliver keyword reports. Extend the workflow with additional filters, such as filtering by CTR, country, or device.
By Mohammadreza azari