Resources · Make integration

DataForSEO OnPage API Make integrationAutomate DataForSEO OnPage API with Make.

Can Make run your on-page SEO checks for you? The DataForSEO OnPage API Make integration gives you 20 action modules and no trigger. This guide is for SEO leads and site owners: connect your API key, then build a first scenario that audits a page.

Try the DataForSEO OnPage API integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the DataForSEO OnPage API Make integration do?

The DataForSEO OnPage API Make integration links your DataForSEO account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule or when another app calls Make. Each module is one brick of that chain. Here, all 20 modules are actions that ask DataForSEO for audit data.

Audit a page when its URL lands in your sheet. A marketing team adds a landing page to a spreadsheet, and Get Live Lighthouse Audit Results pulls its Lighthouse scores straight into the next module. Add Get a Page Screenshot and the report carries a picture of the page too.

Run a full site check, then read it piece by piece. Create a Task opens the job, and modules such as Get Non-Indexable Pages, Get Redirect Chains or Get Duplicate Tags By Task ID read what that task found. An agency can send each finding to its ticketing tool.

Feed content work with page data. Get Keyword Density Data and Get Parsed Content give a writer the words and structure of a page before a rewrite.

What the app does not do in Make: it has no trigger, so nothing starts on its own. The scenario opens on another app or on Make's schedule. The official doc is thin too, and warns that its content is AI-generated and may contain mistakes, so test every module with real data. For the same app, n8n often has a node; our n8n vs Make page lays out the criteria. New to the editor? The Make training starts from zero, and Make pricing explains how operations are counted.

Connect

How do you connect DataForSEO OnPage API to Make?

  1. 01

    Get your API credentials

    You need an active DataForSEO account with an API key. In the DataForSEO dashboard, open API access in the navigation menu, then copy the API token and the password shown on screen. Keep both at hand.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any DataForSEO OnPage API module and click Create a connection. A connection is your DataForSEO account linked to Make once, then reused by all 20 modules.

  3. 03

    Name it and paste the credentials

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the token and password you copied, or follow the on-screen instructions, and save.

First scenario

Your first scenario with DataForSEO OnPage API

GoalWhen a new URL appears in another app, Make runs a Lighthouse audit on it with DataForSEO OnPage API and grabs a screenshot of the page.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Start with the app where your URLs live, such as a spreadsheet row or a form entry.

  2. 02

    Add the Lighthouse audit

    Click the + on the right of that first module, search DataForSEO OnPage API and pick Get Live Lighthouse Audit Results. Create the connection, then map the URL from the previous module.

  3. 03

    Add the screenshot

    Add Get a Page Screenshot after the audit and map the same URL. Each bundle, one item passed from module to module, now carries scores and an image.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and check that the audit answered.

  5. 05

    Schedule and switch on

    Set the clock on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What the DataForSEO OnPage API modules do

DataForSEO OnPage API gives you 20 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

DataForSEO OnPage API1

Create a Task

ActionIn the docs only

This is the module that opens a new audit job in DataForSEO OnPage API. Several other modules carry “by Task ID” in their name, which suggests they read the results of such a task.

When to use it
at the start of a site-wide check, when you want one job and several readings of it further down the scenario.
Watch out
the doc gives no detail on its fields, so run it once and inspect the bundle before you map anything.
DataForSEO OnPage API3

Get Data on Pages

ActionIn the docs only

Page-level results come back here: one set of audit data per page, ready to map into a report or a task tool.

When to use it
when you need the overall state of each page rather than one precise issue like redirects or duplicates.
Watch out
pick a narrower module when you only care about one problem, the scenario stays easier to read.
DataForSEO OnPage API4

Get Duplicate Content by Task ID

ActionIn the docs only

Pages whose content looks duplicated are what this module is named for, read from an existing task through its ID.

When to use it
on a catalog or a blog with many similar pages, to hand a content editor the list of pages to merge or rewrite.
Watch out
it needs a task ID, so place Create a Task, or a stored ID, before it in the flow.
DataForSEO OnPage API5

Get Duplicate Tags By Task ID

ActionIn the docs only

Duplicate tags, such as repeated titles or descriptions, are the target here, again pulled from a task you already created.

When to use it
when a store owner suspects that product pages share the same title and wants proof before fixing them.
Watch out
keep it separate from Get Duplicate Content by Task ID in your notes: one looks at tags, the other at page text.
DataForSEO OnPage API6

Get Instant Pages

ActionIn the docs only

Going by its name, this module checks pages on the spot rather than through a prepared task, so a single URL gets an answer in the same run.

When to use it
a new page goes live and you want a quick look at it before sharing the link.
Watch out
for a whole site, Create a Task followed by the task-based modules keeps the work in one job.
DataForSEO OnPage API7

Get Keyword Density Data

ActionIn the docs only

Writers get a view of which words a page repeats and how often, useful before rewriting a page that slipped in search.

When to use it
when a content brief is being prepared and the team wants the current wording of the page as a starting point.
Watch out
density is a reading aid, not a verdict; map it to a doc or a sheet where a person reviews it.
DataForSEO OnPage API8

Get Lighthouse Audit Results

ActionIn the docs only

Lighthouse scores, the performance and quality checks many SEO teams read first, come back from an audit already run.

When to use it
when the audit was launched earlier and you want to collect its results in a later step or a second scenario.
Watch out
if you need the score right away for a single URL, the live variant below fits better.
DataForSEO OnPage API9

Get Live Lighthouse Audit Results

ActionIn the docs only

The “Live” in its name points to an audit run inside the same scenario run, which is why the first scenario on this page uses it.

When to use it
a developer ships a page and the team wants its scores posted to a chat channel once the URL is logged.
Watch out
each URL is one operation; feed it only the pages you care about, not a whole export.
DataForSEO OnPage API10

Get Live Parsed Content

ActionIn the docs only

A page's content comes back broken into readable parts during the run, with no prepared task in between.

When to use it
when a competitor page or a fresh article needs to go into an AI step or a doc for a quick analysis.
Watch out
the doc does not describe the output structure, so click Run once and look at the bundle before mapping fields.
DataForSEO OnPage API11

Get Microdata by Task ID

ActionIn the docs only

Structured data found on the audited pages, the microdata that search engines read, is what this module retrieves from a task.

When to use it
after adding product or article markup, to check which pages actually carry it.
Watch out
like every “by Task ID” module, it depends on a task created before it; without an ID to map, it has nothing to read.
DataForSEO OnPage API12

Get Non-Indexable Pages

ActionIn the docs only

Pages that search engines cannot index are singled out, which saves hunting through a full crawl for them.

When to use it
right after a site release, when one wrong setting could hide whole sections from search.
Watch out
some pages are meant to stay out of the index, such as a cart or a login page; filter those before alerting anyone.
DataForSEO OnPage API13

Get Pages By Resource

ActionIn the docs only

Judging by its name, you start from one resource, such as an image or a script, and get back the pages that use it.

When to use it
a heavy file slows the site and you need to know which pages load it before replacing it.
Watch out
pair it with Get Resources, which gives you the resources to ask about in the first place.
DataForSEO OnPage API14

Get Parsed Content

ActionIn the docs only

This one returns the content of audited pages split into parts, taken from the audit rather than fetched live.

When to use it
during a content inventory of a whole site, when an editor wants every page's text in one sheet.
Watch out
for one URL checked on the fly, Get Live Parsed Content avoids the task step entirely.
DataForSEO OnPage API15

Get Raw HTML Data

ActionIn the docs only

You receive the page's HTML as is, the raw material for anyone who wants to check a tag or a script by hand.

When to use it
a developer needs proof of what the server actually sent, for example to debug missing markup.
Watch out
raw HTML is long; send it to a file or a storage app rather than into a chat message.
DataForSEO OnPage API16

Get Redirect Chains

ActionIn the docs only

Redirects that hop through several URLs before reaching a page show up here, so you can shorten them.

When to use it
after a domain change or a URL cleanup, when old links pile up redirect after redirect.
Watch out
the module reports the chains; fixing them still happens on your server or CMS, outside Make.
DataForSEO OnPage API17

Get Resources

ActionIn the docs only

The files that pages load, such as images, scripts and stylesheets, are listed from the audit.

When to use it
when a performance review starts and the team wants an inventory of what each page pulls in.
Watch out
expect many bundles per site; an aggregator in Make can group them into one table before you send a report.
DataForSEO OnPage API18

Get a Page Screenshot

ActionIn the docs only

A picture of the page comes back, which makes an audit report easier to read for someone who never opens the site.

When to use it
when a client report or a ticket needs to show the page as it looked at audit time.
Watch out
images add weight; on the Free plan, files are capped at 5 MB, so check the size in a Run once test.
DataForSEO OnPage API19

Get a Waterfall

ActionIn the docs only

The waterfall shows the order in which a page loads its resources, the view developers use to find what blocks rendering.

When to use it
a Lighthouse score drops and you need to see which file loads late or too long.
Watch out
the data is technical; route it to a developer's tool rather than to a marketing report.
DataForSEO OnPage API20

Make an API Call

ActionIn the docs only

Any endpoint of the DataForSEO OnPage API can be called through this module, with the connection you already set up.

When to use it
the other modules do not cover a request you found in the DataForSEO documentation.
Watch out
you write the request yourself, so keep the API documentation open and test with Run once before switching on.
Need help

Need help automating DataForSEO OnPage API with Make?

A person reads every message.

FAQ

DataForSEO OnPage API and Make: common questions

01Is the DataForSEO OnPage API Make integration free?
Yes on the Make side: DataForSEO OnPage API is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits per month. On the DataForSEO side, you need your own active account and API key, and its pricing page sets what that costs.
02What do you need to connect DataForSEO OnPage API to Make?
You need an active DataForSEO account and its API credentials. In the DataForSEO dashboard, open API access and copy the API token and the password displayed there. In Make, add any DataForSEO OnPage API module, click Create a connection, optionally name it, and paste both values. The connection then serves all 20 modules, so you enter the credentials only once per account. Watch out: the password to paste is the one shown under API access, not the one you use to log in to DataForSEO.
03Does DataForSEO OnPage API trigger Make scenarios in real time?
No. The app has no trigger module in Make, so it never starts a scenario by itself. Two ways around it: open the scenario with another app's trigger, such as a new row in a sheet that holds a URL, or rely on the scenario schedule set on the first module. A new scenario runs every 15 minutes by default, and paid plans can go down to 1 minute. The audit modules then run in the order you placed them.
04What if a DataForSEO OnPage API module is missing in Make?
Use Make an API Call. It calls any endpoint of the DataForSEO OnPage API with the connection you already created, so a request that none of the listed modules covers stays reachable. Keep in mind that the Make doc for this app is short and flags itself as AI-generated content that may contain mistakes, so check each request against the DataForSEO documentation and test it with Run once before switching the scenario on.
05Should you use Make or n8n for DataForSEO OnPage API?
It depends on the tool your team already runs. In Make, the app comes with 20 modules plus a generic API call, a visual editor and the Free plan to start. n8n often has a node for the same app, so check its catalog before choosing. Compare how each tool handles the modules you actually need, how usage is counted and who will maintain the scenarios. The n8n vs Make comparison on this site lays out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations