The SEO audit crawls the client’s site and points out what holds back search: pages with errors, noindex, missing title or meta description, thin content, missing structured data. It lives in Performance › SEO, next to the Search Console data. To crawl, Relator needs to know the domain belongs to the client, so the first step is verifying ownership with a TXT record in DNS.
Before you start
Enter the right client: the domain is registered under it.
Registering, verifying and auditing require being able to edit the client (agency team, or the client’s admins and editors). Read-only users see the results.
You’ll need access to the domain’s DNS panel (Cloudflare, GoDaddy, Namecheap, Registro.br, etc.) or someone who has it.
The site must be public. IP addresses, localhost and hosts without an extension (such as .com) aren’t accepted.
The audit doesn’t depend on Search Console, but the cross-check with search only appears when it’s connected. See Connect Search Console.
Step by step
1
Step 1
Open Performance › SEO
In the sidebar, click Performance and choose the SEO tab. With no domain registered, the Site Audit section shows open, with the domain field.
2
Step 2
Register the domain
In Domain, type only the address, without http:// and without a path: client.com or www.client.com. Click Add domain.
Illustrative screen
Korra/Performance
Ask RelatorAIPT
SEOKorra / SEO
OverviewPaid mediaOrganic
SEO1
Leads & sales
Site Audit
Domainkorra.com.bre.g. client.com
2
3
1The SEO tab in Performance.
2Type the domain without http:// and without a path.
3Add domain registers it and creates the verification record.
3
Step 3
Copy the TXT record
The domain enters the list with the Pending verification badge and the Verify ownership via DNS box, with three fields and a Copy button on each:
Type: TXT.
Name: relator-verify. If your panel asks for the full name, use relator-verify.yourdomain.com.
Value: the code generated for this domain. Copy it exactly as shown.
Illustrative screen
Korra/Performance
Ask RelatorAIPT
SEO
korra.com.br
Pending verificationVerify
3
Verify ownership via DNS
TypeTXT
Namerelator-verify
2
Value8f3c1a7e5b2d4f90a6c1e2b7d9f04a3c
1
1The box with the record to create in DNS.
2Use Copy on each field and paste into the DNS panel.
3Verify checks the record once it’s created.
4
Step 4
Create the record in the DNS panel
In your domain provider’s panel, add a new TXT record with the copied name and value. TTL can stay on default or automatic. Save.
5
Step 5
Click Verify
Go back to Relator and click Verify. When the record is found, you see Domain verified! You can run the first audit now. and the badge changes to Verified. DNS propagation can take a few minutes; if it isn’t found, wait and try again.
6
Step 6
Run the first audit
Click Audit now. The status goes through Queued and Auditing… and ends at Completed (or Failed). The screen updates on its own; you can leave and come back.
What happens next
Relator starts from the home page and the sitemaps listed in robots.txt, follows the robots.txt rules and audits up to 100 pages per audit.
The result shows in Results for your domain, with the Audit report and the page list. See Read the SEO audit.
The audit doesn’t run on its own: each new round is a click on Audit now. The history stays in Completed audits.
Once a domain is verified, the raw audit takes a single line on the SEO tab (Site audit), with See full audit and domains → to open everything. The Search Console cross-check comes first.
Common problems
Invalid domain
Cause
http://, a path, an IP or a host without an extension was typed
What to do
Type only client.com
This domain is already registered for this client
Cause
The domain is already on the list
What to do
Use the existing entry
TXT record not found
Cause
The record hasn’t propagated yet, or the name or value differ
What to do
Check the fields, wait a few minutes and click Verify
Couldn’t query DNS right now
Cause
Temporary lookup failure
What to do
Try again in a moment
Verify domain ownership before auditing
Cause
The domain hasn’t been verified yet
What to do
Complete the TXT verification
An audit is already running for this domain
Cause
An audit is queued or running
What to do
Wait for it to finish
Message
Cause
What to do
Invalid domain
http://, a path, an IP or a host without an extension was typed
Type only client.com
This domain is already registered for this client
The domain is already on the list
Use the existing entry
TXT record not found
The record hasn’t propagated yet, or the name or value differ
Check the fields, wait a few minutes and click Verify
Couldn’t query DNS right now
Temporary lookup failure
Try again in a moment
Verify domain ownership before auditing
The domain hasn’t been verified yet
Complete the TXT verification
An audit is already running for this domain
An audit is queued or running
Wait for it to finish
Frequently asked questions
Can I delete the TXT record after verifying?
Verification is recorded in Relator once it’s done. Still, keeping the record in DNS doesn’t affect the site and helps if you ever need to register the domain again.
Why do I need to prove the domain is mine?
So Relator only crawls sites with the authorization of whoever controls them, the same model Google uses in Search Console.
Can I register more than one domain per client?
Yes. Each domain is verified and audited separately.
Does the audit slow the site down?
No. It visits at most 100 pages per round and follows the site’s robots.txt.