How to Automate Google Analytics SEO Reporting?
Description
Get a weekly SEO digest without manual work. The automation pulls web traffic, search landing page performance, and country trends, then compares this week to last week. It sends the data to an AI writer and saves the summary in a Baserow table for easy tracking.
A schedule trigger runs the job each week, and a manual trigger lets you test on demand. Google Analytics nodes fetch page engagement, search landing pages, and country views for both time frames. Code nodes format the results, then three HTTP requests pass the page, search, and country data to an AI endpoint. The final output is written to Baserow so teams can view insights across time.
Setup needs Google Analytics access, an OpenRouter API key, and a Baserow table with the listed fields. Expect faster reporting, clear week over week changes, and one place for your SEO notes. Great for marketing teams, content owners, and anyone who needs quick status updates before weekly standups.
Tools Required
What this workflow does?
- Weekly and manual runs using schedule and manual triggers
- GA4 page engagement pull with views, users, and events by page
- GA4 search landing page data using landing page plus query string
- Country level views for this week and last week
- Code nodes format and compare data week over week
- Three AI calls generate summaries for pages, search, and countries
- Results saved to Baserow with fields for Name, Country Views, Page Views, Search Report, and Blog
- Date ranges use expressions to capture this week and prior week
What are the benefits?
- Reduce manual reporting work from 3 hours to 10 minutes
- Streamline weekly SEO reporting by about 80 percent
- Improve data consistency by 90 percent with one source of truth
- Connect three systems seamlessly for end to end reporting
- Run on a fixed weekly schedule with no reminders needed
How to set this up?
- Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
- You'll need accounts with Google Analytics, Baserow and OpenRouter. See the Tools Required section above for links to create accounts with these services.
- In the n8n credentials manager, create Google Analytics credentials. Double click any Google Analytics node, choose the credential dropdown, click Create new credential, and follow the on screen steps to connect your Google account with GA4 read access.
- Set your GA4 property ID in each Google Analytics node. Open a GA node and paste your property ID in the Property field to match your site.
- Confirm the date ranges. The flow uses expressions for this week and last week. Adjust time zone in n8n if your reporting week needs a different cut off.
- Open each HTTP Request node for the AI calls. Set Authentication to Header Auth. Username should be Authorization. Password should be Bearer followed by a space and your OpenRouter API key.
- In Baserow, create a table with columns Name, Country Views, Page Views, Search Report, and Blog. Copy your Baserow API token from your account settings.
- In n8n, create Baserow credentials. Double click the Baserow node, select Create new credential, paste your API token, and save.
- Map the Baserow fields in the Save output node so each AI summary lands in the correct column. Add your website name in the Blog field.
- Set the Schedule Trigger to run weekly. You can change the interval to fit your reporting cycle.
- Run a test with the manual trigger. Check the execution log to verify GA nodes return data, AI requests return status 200, and a new row appears in Baserow.
- If errors occur, confirm the GA property ID and permissions, fix any missing Authorization header in AI calls, and check that your Baserow token and table ID are correct.
Need help or want to customize this?
Ask in the Free Futurise Community.
Similar Templates
Credits: Article about this workflow - these templates were sourced from publicly available materials across the web, including n8n’s official website, YouTube and public GitHub repositories. We have consolidated and categorized them for easy search and filtering, and supplemented them with links to integrations, step-by-step setup instructions, and personalized support in the Futurise community. Content in this library is provided for education, evaluation and internal use. Users are responsible for checking and complying with the license terms with the author of the templates before commercial use or redistribution. If you are the author and would like this template removed from the template library, email us at info@futurise.com and we will remove it promptly.
