Knowledge base
Connect your DataForSEO API login and API password, so the SEO data checks for your sites run on your own DataForSEO account.
Connecting your own DataForSEO key means the SEO data we fetch for your sites is fetched with your DataForSEO account instead of ours. You see the same metrics in your dashboard, drawn from your own subscription.
A DataForSEO account with credit on it. One DataForSEO account covers every check we run there — backlinks, keyword research, product data and rank tracking.
Sign in to the DataForSEO dashboard and open the API Access tab. It shows your API login and your API password.
The API password is generated by DataForSEO and is not the password you sign in with. Using your sign-in password is the most common reason a DataForSEO connection is refused.
Open Integrations in your dashboard and choose Connect an account. Pick Your own SEO data as the group and DataForSEO as the account, fill in API login and API password, and press Connect account.
We test what you paste before anything is saved. A key that does not work is never stored, and the answer says what was wrong with it. A key that works is kept encrypted in our secrets vault — never in our database — and is never shown again, not even to you.
plan's quota, and stop using ours. We do not charge you for checks that run on your key.
the metrics appear — rather than quietly switching back to our account. Fix the key at the vendor, or disconnect it to go back to what your plan includes.
against your quota.
It was rejected. Copy the API password from the API Access tab rather than using your dashboard password.
Checks stop. Your DataForSEO balance has run out. Top it up in DataForSEO; checks resume on their next run.
It says the key was rejected. Almost always one of three things: a space or a line break copied with it, a key that has expired, or a key that was revoked or regenerated after you copied it. Create a fresh one and paste it again.
It connects, but something later fails. The key authenticates but lacks a permission the action needs. Create a new key with the permissions listed above, then disconnect the old connection and connect the new key.
Open Integrations, find the account and press Disconnect. That deletes the stored key at once. Anything that was using it stops at its next action, and the screens that depended on it say so rather than failing quietly.
Disconnecting does not undo what was already done — records, deployments or settings we changed on your account stay as they are. If you think the key itself may have leaked, also revoke it at the vendor; disconnecting removes our copy, not theirs.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →