DataForSEO + Google Search Console, client-ready audits
You know the drill. A “quick” content audit turns into five tabs open, exports that don’t match, and a report you end up rewriting at midnight because the numbers feel off.
This is the pain SEO consultants deal with constantly. It also hits agency leads trying to standardize deliverables, and in-house marketers who need a reliable GSC audit automation without building a spreadsheet monster.
This workflow combines a DataForSEO crawl with Google Search Console metrics, then outputs a branded HTML audit you can send to a client. You’ll see what it automates, what results to expect, and what you need to run it.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: DataForSEO + Google Search Console, client-ready audits
flowchart LR
subgraph sg0["When clicking ‘Start’ Flow"]
direction LR
n0@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Fields", pos: "b", h: 48 }
n1@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Start’", pos: "b", h: 48 }
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Check Task Status"]
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Create Task"]
n4@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "Wait", pos: "b", h: 48 }
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get RAW Audit Data"]
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Extract URLs"]
n8@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
n9["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Query GSC API"]
n10@{ icon: "mdi:cog", form: "rounded", label: "Wait1", pos: "b", h: 48 }
n11@{ icon: "mdi:swap-vertical", form: "rounded", label: "Map GSC Data to URL", pos: "b", h: 48 }
n12["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Merge GSC Data with RAW Data"]
n13["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Build Report Structure"]
n14["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Generate HTML Report"]
n15["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Extract 404 & 301"]
n16@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items1", pos: "b", h: 48 }
n17["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Map URLs Data"]
n18["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get Source URLs Data"]
n19@{ icon: "mdi:cog", form: "rounded", label: "Download Report", pos: "b", h: 48 }
n4 --> n6
n4 --> n5
n5 --> n2
n10 --> n11
n0 --> n3
n3 --> n2
n7 --> n8
n17 --> n16
n9 --> n10
n8 --> n12
n8 --> n9
n16 --> n13
n16 --> n18
n2 --> n4
n15 --> n16
n6 --> n7
n11 --> n8
n14 --> n19
n18 --> n17
n13 --> n14
n1 --> n0
n12 --> n15
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n1 trigger
class n4 decision
class n2,n3,n6,n9,n18 api
class n7,n12,n13,n14,n15,n17 code
classDef customIcon fill:none,stroke:none
class n2,n3,n6,n7,n9,n12,n13,n14,n15,n17,n18 customIcon
The Problem: SEO audits take too long to turn into client-ready reports
A content audit is supposed to create clarity. Instead, it often creates more work. You crawl a site in one tool, pull performance from Google Search Console in another, then spend hours trying to line up URLs, normalize data, and explain what matters in a way a client will actually understand. And if you’re doing this monthly, the busywork becomes a permanent tax on your calendar. Worse, manual audits drift. You change thresholds, skip checks when you’re rushed, and the “method” depends on who did the audit that week.
It adds up fast. Here’s where it usually breaks down.
- Pulling crawl data and GSC metrics separately leads to mismatched URLs and confusing conclusions.
- Manual issue spotting (thin content, duplicate metadata, orphan pages) is slow, and you end up sampling instead of auditing everything.
- Turning findings into a polished, branded deliverable often takes as long as the analysis itself.
- Scaling past a few hundred pages becomes a slog, so bigger sites get “good enough” audits.
The Solution: one automated crawl + GSC merge, delivered as a branded HTML audit
This n8n workflow runs a crawl in DataForSEO, waits until the task is complete, and pulls the raw audit data back into your automation. From there, it extracts the URLs you care about (like status 200 pages), then batches through those URLs to fetch clicks and impressions from Google Search Console. Once both datasets are in the same place, the workflow merges crawl findings with performance signals, builds a structured report model, and renders a branded HTML report with summaries, issue breakdowns, and prioritized recommendations. Finally, it exports the report as a downloadable HTML file, so you can share it as-is or drop it into your delivery process.
The workflow starts with you setting the domain, crawl limit (up to 1,000 pages), and branding fields. DataForSEO runs the crawl while n8n periodically checks status. When it’s done, the workflow enriches the crawl with GSC data, then produces a client-friendly HTML report that doesn’t need “one more formatting pass.”
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you run a monthly audit for a client site with about 500 indexable pages. Manually, you might spend about 2 hours pulling a crawl export, another hour cleaning URL formats, and about 2 more hours pulling GSC data, merging it, and packaging it into something client-ready. With this workflow, you set the domain and branding once, launch it, and wait about 20 minutes for the crawl/report run to finish. The output is a branded HTML audit you can send the same day, without rebuilding the report every time.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- DataForSEO for website crawling and audit data.
- Google Search Console to pull clicks and impressions per URL.
- DataForSEO API credentials (get them from the DataForSEO API Access page).
Skill level: Intermediate. You’ll connect API credentials, edit a few fields, and run batches safely.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
You launch the workflow and set the inputs. In the “Assign Input Values” step, you choose the target domain, max crawl pages (up to 1,000), JavaScript rendering preference, and your branding details like logo URL and colors.
The workflow runs the crawl and checks progress. n8n creates the DataForSEO task, then loops with a short wait and a status check until the crawl is complete. No babysitting.
It enriches crawl URLs with Google Search Console performance. URLs are parsed, processed in batches, and each batch gets GSC clicks and impressions via an HTTP request to the Search Console API. If an API call needs a moment, the workflow pauses and retries.
Your audit becomes a branded HTML report. The workflow merges datasets, identifies issue categories (status problems, metadata, content quality, internal linking, performance), then renders an HTML report and exports it as a downloadable file.
You can easily modify crawl limits and issue thresholds based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Start the workflow with the manual trigger so you can run the audit on demand during setup and testing.
- Add the Manual Launch Trigger node as the starting point.
- Keep default settings (no parameters required) to allow manual execution from the editor.
Step 2: Connect Data Inputs and Branding
Define the crawl target, company details, and branding used throughout the audit and HTML report.
- Open Assign Input Values and set dfs_domain to
example.com. - Set dfs_max_crawl_pages to
1000and dfs_enable_javascript tofalse. - Fill in branding fields: company_name
Example Company, company_websitehttps://example.com, company_logo_urlhttps://example.com/logo.png. - Set brand_primary_color to
#252946and brand_secondary_color to#0fd393. - Set gsc_property_type to
domainto use domain-level Search Console data.
url-prefix if you want property-specific metrics instead of domain-wide data.Step 3: Configure the DataForSEO Crawl and Polling Loop
These nodes submit a crawl task, check progress, and fetch the raw audit data once the crawl is complete.
- In Initiate Crawl Task, keep URL as
https://api.dataforseo.com/v3/on_page/task_postand set JSON Body to the provided expression:=[{"target":"{{ $json.dfs_domain }}","max_crawl_pages": {{ $json.dfs_max_crawl_pages }},"load_resources": false,"enable_javascript": {{ $json.dfs_enable_javascript }},"custom_js":"meta = {}; meta.url = document.URL; meta;","tag":"{{ $json.dfs_domain + Math.floor(10000 + Math.random() * 90000) }}"}]. - Credential Required: Connect your httpBasicAuth credentials in Initiate Crawl Task, Verify Task Progress, Retrieve Raw Audit Data, and Retrieve Link Sources.
- In Verify Task Progress, set URL to
=https://api.dataforseo.com/v3/on_page/summary/{{ $json.tasks[0].id }}and keep Content-Type header asapplication/json. - In Branch Completion Check, set the condition to check
{{ $json.tasks[0].result[0].crawl_progress }}equalsfinished. - Set Pause Interval to wait 1 minutes to poll progress if the crawl is not finished.
- Configure Retrieve Raw Audit Data with URL
https://api.dataforseo.com/v3/on_page/pagesand JSON Body=[{"id":"{{ $json.tasks[0].id }}","limit":"1000"}].
Step 4: Enrich URLs with Search Console Metrics
This section extracts 200-status URLs, batches them, and pulls 90-day Search Console metrics for each page.
- In Parse Page URLs, keep the code that filters only
status_code === 200and outputs{ url: page.url }. - Set Batch Iterate URLs to batchSize
100for scalable processing. - In Fetch GSC Metrics, keep the dynamic URL expression that switches between domain and URL-prefix properties:
{{ $('Assign Input Values').first().json.gsc_property_type === 'domain' ? 'https://searchconsole.googleapis.com/webmasters/v3/sites/' + 'sc-domain:' + $node["Batch Iterate URLs"].json.url.replace(/https?:\/\/(www\.)?([^\/]+).*/, '$2') + '/searchAnalytics/query' : 'https://searchconsole.googleapis.com/webmasters/v3/sites/' + encodeURIComponent($node["Batch Iterate URLs"].json.url.replace(/(https?:\/\/(?:www\.)?[^\/]+).*/, '$1')) + '/searchAnalytics/query' }}. - Keep the Body expression that sets a 90-day range and filters by the page URL:
{"startDate":"{{ new Date(new Date().setDate(new Date().getDate() - 90)).toISOString().split('T')[0] }}","endDate":"{{ new Date().toISOString().split('T')[0] }}","dimensionFilterGroups":[{"filters":[{"dimension":"page","operator":"equals","expression":"{{ $node['Batch Iterate URLs'].json.url }}"}]}],"aggregationType":"auto","rowLimit":100}. - Credential Required: Connect your googleOAuth2Api credentials in Fetch GSC Metrics.
- Set Pause Retry to wait 1 minutes before mapping results if the Google API throttles.
- In Map GSC Metrics to URL, set URL to
{{ $('Batch Iterate URLs').item.json.url }}, Clicks to{{ $('Fetch GSC Metrics').item.json.rows[0].clicks }}, and Impressions to{{ $('Fetch GSC Metrics').item.json.rows[0].impressions }}. - Batch Iterate URLs outputs to both Combine GSC with Audit and Fetch GSC Metrics in parallel to enrich the audit while the batch loop runs.
Step 5: Build the Report Model and HTML Output
These nodes merge audit data with GSC metrics, gather link sources for 404/301 pages, and render the branded HTML report.
- In Combine GSC with Audit, keep the JavaScript that merges GSC metrics into each page’s
googleSearchConsoleData. - Use Filter 404 and 301 to isolate error and redirect URLs from Retrieve Raw Audit Data.
- Batch Link Sources outputs to both Assemble Report Model and Retrieve Link Sources in parallel to enrich 404/301 pages with source links.
- In Retrieve Link Sources, keep URL as
https://api.dataforseo.com/v3/on_page/linksand JSON Body as=[{"id":"{{ $('Retrieve Raw Audit Data').first().json.tasks[0].id }}","page_to":"{{ $json.url }}"}]. - In Format Link Source Data, keep the mapping of
link_from,type, andtextinto a structured sources array. - In Assemble Report Model, keep the long-form JavaScript that categorizes issues and builds the
summary,issues, andpagesoutput. - In Render HTML Report, keep the HTML template logic referencing Assign Input Values and Assemble Report Model.
- In Export HTML File, set Operation to
toText, Source Property tohtml, and Binary Property Name tocontent audit report.
Step 6: Test and Activate Your Workflow
Run a manual test to validate data collection and verify that the HTML report is generated correctly.
- Click Execute Workflow starting from Manual Launch Trigger to run the audit end-to-end.
- Confirm that Retrieve Raw Audit Data returns crawl items and Fetch GSC Metrics returns rows for each URL.
- Verify Render HTML Report outputs a full HTML string and Export HTML File generates a downloadable file.
- When results look correct, toggle the workflow to Active to use it in production runs.
Common Gotchas
- DataForSEO credentials can expire or need specific permissions. If things break, check your DataForSEO API access status and the n8n credential assignment on the crawl-related HTTP Request nodes first.
- If you’re using Wait nodes or external processing, timing varies. Bump up the wait duration if downstream nodes fail on empty responses while the crawl task is still finishing.
- Default AI prompts can be generic. Add your audit “voice” and recommendation style early in the AI Agent/OpenAI steps or you’ll be editing outputs forever.
Frequently Asked Questions
About 30 minutes if you already have DataForSEO and Search Console access ready.
No. You will connect credentials and edit a few fields in n8n. The workflow’s logic is already built.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in DataForSEO API usage (they include a small test credit) and any Google API limits on your account.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. Update branding fields (company name, logo URL, primary/secondary colors) in the “Assign Input Values” step, then adjust issue thresholds in the report-building logic, such as thin content word count (currently 1500), click depth flags (currently deeper than 4), and readability (currently below 55). If you want a different title/description policy, modify the title and description length checks as well. Many teams also add an extra delivery step after the “Export HTML File” output to send the report by email or upload it to storage.
Usually it’s incorrect Basic Auth credentials or the credential isn’t assigned to every DataForSEO HTTP Request node. Double-check the “Initiate Crawl Task” and “Retrieve Raw Audit Data” nodes first, then confirm your DataForSEO API access is active. If it still fails, it can be rate limiting on larger runs, so lowering batch pressure and extending waits can help.
Up to 1,000 crawled pages per run, and it batches the GSC lookups so the enrichment stays manageable.
Often, yes. This workflow relies on looping, batching, waiting for long-running crawl tasks, and merging datasets reliably, which is where n8n tends to be more flexible (and cheaper to run at volume if you self-host). Zapier or Make can work for simple “send me a report” flows, but this type of audit build usually gets awkward once you add batching and retries. Also, generating a full branded HTML report is easier when you control the logic end-to-end. If you’re torn, Talk to an automation expert and you’ll get a straight recommendation based on your volume and delivery needs.
Set it up once and your audits stop being a recurring fire drill. The workflow handles the repeatable work so you can focus on decisions, not data-wrangling.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
