Give Your SEO Agency Cloudflare Access Without Sharing a Login

If your site runs through Cloudflare, a large part of your technical SEO lives there: DNS, redirects, caching and the firewall rules that decide which crawlers get in. Sooner or later an SEO consultant, developer or agency needs to look at it. The worst way to arrange that is to hand over your own login. There is a better way, and it takes about a minute.

The video shows how to add another person as a member of your Cloudflare account, so they sign in with their own credentials and your login stays yours.

Why shared Cloudflare logins stopped working

Cloudflare added a verification step to sign-ins. When someone logs in from an IP address the account has not seen before, Cloudflare emails a PIN to the address on file and waits for it to be entered. That is good security, but it breaks the old habit of several people sharing one login. Every time your agency signs in from a new location, you get an email and someone has to pass the code along.

Member access solves this. Each person signs in to their own Cloudflare account and sees yours alongside it. When the video was recorded this was a fairly new option; before that, multi-user access was a feature of the higher paid plans.

How to add a member

1. Log in to Cloudflare as the account owner.
2. Open Members. In the video it is a link in the main menu; in the current dashboard it sits under Manage Account.
3. Enter the email address of the person or team you want to add, and choose a role if your plan offers a choice.
4. Click Invite. Cloudflare emails them an invitation.
5. They accept it. They need their own Cloudflare account to do so, and the invitation can throw an error if they do not have one. The fix is simply for them to sign up on the Cloudflare website first.

That is the whole process. No passwords change hands and no PINs need forwarding.

What your SEO team will look at in Cloudflare

Knowing why they need access helps you decide what level to give. The usual reasons:

• Security events. Firewall rules, bot protection and country filters can challenge Googlebot or block the crawlers used to audit the site. The security event log is where an SEO confirms whether search engines are getting through.
• DNS. Verifying a Domain property in Google Search Console means adding a TXT record. Setting up a subdomain, pointing a landing page platform at the domain or fixing a www and non-www split all happen in DNS too.
• Redirects and rules. Redirects configured in Cloudflare never appear in WordPress, so anyone auditing redirect chains needs to see them.
• Caching. Cache settings affect how fast pages load for visitors and crawlers, and whether Google sees an updated page promptly after you change it.

If someone only needs to diagnose a problem and your plan offers a read-only role, that is enough. Give edit rights when you want them to make changes.

Checking whether Cloudflare is affecting search

With access in place, the checks are quick. Compare the Crawl stats report in Search Console (Settings, then Crawl stats) with Cloudflare’s security events for the same dates. A rise in failed Googlebot requests that lines up with a new firewall rule is the classic pattern. A URL Inspection live test then confirms what Google receives right now. Without member access, this kind of cross-check tends to turn into a week of screenshots and emails.

Housekeeping once access is shared

• Remove members when an engagement ends. Access stays until you take it away.
• Invite named people or a team address rather than a shared personal mailbox, so you know who has access.
• Ask contractors to turn on two-factor authentication for their own Cloudflare accounts. Their personal login now opens your account too, so its security matters as much as yours.
• Keep the owner login, and the email address that receives the sign-in PINs, with the business rather than a contractor.
• When rankings or crawl stats move unexpectedly, ask everyone with access whether they changed anything in Cloudflare that week. A rule added for security reasons is a common cause of crawl problems nobody connects to search.