Guide · Search Console owners
Unknown “New owner” in Search Console: what it means and how to fix it
A Search Console owner nobody on your team added means someone could write to your site. Google sent an email with a subject such as “New owner for https://example.com/”, or you opened Users and permissions and found an address you do not recognise, or you found a file called google followed by a string of letters and numbers ending in .html in the web root that nobody remembers uploading. Search Console only grants ownership to someone who proves control of the site, usually by placing a file or a meta tag on it. If that person was not you, an attacker had write access, and the most common reason they want ownership is to submit sitemaps for spam pages they have added under your domain. This guide covers how to confirm it, how to remove the owner in the order Google requires so they cannot simply verify again, and why the cleanup does not end there.
Published Last reviewed
- What you see
- A “New owner” email, or an unknown verified owner in Users and permissions
- How they got it
- A google*.html file or verification meta tag they placed on the site
- Why they want it
- To submit spam sitemaps and watch how Google indexes their pages
- What it proves
- Someone had write access to the site, the database or DNS
Why it happens
Ownership is proof of control, and they had control
Search Console decides who owns a property by asking them to prove they control it. For a URL-prefix property such as https://example.com/, Google documents several ways to do that, and the two an attacker with site access can use without anything else are an HTML file uploaded to the web root and a meta tag added to the home page. A domain property, which covers every subdomain and protocol, can only be verified with a DNS record. Google re-checks the token from time to time; as long as it is there, the ownership stands.
Owners can submit sitemaps, request indexing, see the queries the site appears for and change property settings. That is exactly what someone running a spam campaign on a hacked site wants. Google has long described attackers verifying themselves on hacked sites as part of hacked-spam attacks, and it is a regular companion of the Japanese keyword hack and other injected-page spam: the attacker generates thousands of pages under your domain, then submits a sitemap so Google crawls them quickly instead of waiting to discover them.
Google tells existing owners when a new owner is verified, which is why the email is often the first sign. It is worth taking seriously even if the site looks normal: the spam pages are usually cloaked, shown to Googlebot and to visitors arriving from search but not to an owner who types the address in directly.
Figure 1 · How a stranger becomes an owner, and how the owner is removed
Ownership follows the token. Remove the token first, or the owner comes back.
How they become an owner
- Write access to the siteThrough a vulnerability or stolen login
- Token placedgoogle*.html or a meta tag
- Google verifies themAnd emails the real owners
- Spam sitemaps submittedSo the spam is crawled fast
How to remove them
- Delete the tokenFile, meta tag or DNS record
- Unverify the ownerUsers and permissions
- Remove their sitemapsAnd any users they added
- Clean the compromiseThe owner was a symptom
Confirm it in Search Console
Read the owners list and the Sitemaps report
Use an account that is already a verified owner. Labels below are as they appear at the time of writing; Google renames menus from time to time, but the reports have stayed in the same places.
- 01
Open Settings, then Users and permissions
The list shows every user with their permission level: owner, full or restricted. Owners are either verified, with their own token on the site, or delegated, added by a verified owner. Note the email address, the permission level and, under the menu next to an owner, the verification details where Search Console shows them.
- 02
Check how each owner verified
Settings also shows the property’s ownership verification, and the menu next to an owner offers to manage property owners. The verification method — HTML file, HTML tag, DNS record, Google Analytics or Tag Manager — tells you where to look for the token on the site.
- 03
Open the Sitemaps report
A sitemap you never submitted, often with a random file name or one that lives on another path of your domain, and a count of discovered URLs far higher than your site has pages, is the usual reason the owner exists. Note the sitemap URLs before you remove them; they show where the spam pages are.
- 04
Look at the Pages report and Security Issues
A sudden rise in indexed pages, or a hacked-content entry under Security Issues, confirms that spam was published. If Security Issues lists sample URLs, keep them for the cleanup and the review request.
Find the token on the site
Read-only checks for files, meta tags and DNS records
Run these from the WordPress root over SSH, and against the live site from any shell. None of them change anything. Replace example.com with your domain.
- 01
List verification files in the web root
A Google HTML verification file is named google followed by a hexadecimal string, and contains a single line naming itself. Show each one with its full timestamp and contents:
find . -maxdepth 2 -name 'google*.html' -exec ls -l --time-style=full-iso {} \; -exec cat {} \;One file per owner who used this method. A file whose timestamp matches the date of the “New owner” email, or the date other files on the site changed, is a strong lead. Do not delete anything yet.
- 02
Check the meta tags the home page actually serves
The verification tag must be on the home page Google fetches, so check what the live site returns rather than the theme files alone:
curl -s https://example.com/ | grep -io '<meta[^>]*google-site-verification[^>]*>'More than one tag is normal if several people verified this way. Each content value is one owner’s token; compare them with the tags your SEO plugin or theme settings show.
- 03
Find where a tag is written from
A tag can come from theme or plugin files, or from a value stored in the database. Search both:
grep -rn 'google-site-verification' wp-content --include='*.php' wp db search 'google-site-verification' --all-tablesSEO plugins such as Yoast SEO, Rank Math and All in One SEO store legitimate verification codes in wp_options; a match there is expected. An extra tag hard-coded into header.php or functions.php, or echoed from an encoded option, is not.
- 04
Look for a file served without a file
A token URL can also be answered by a rewrite rule or a PHP script rather than a real file. Search the rewrite rules and check what the live site returns:
grep -n 'google' .htaccess curl -sI https://example.com/google0123456789abcdef.htmlUse the exact token file name from the owner’s verification details. A 200 response with no matching file on disk means something generates it, and that something is part of the infection.
- 05
Check DNS for verification records
A domain property, or a DNS-verified owner, has a TXT record on the domain:
dig +short TXT example.com | grep -i google-site-verificationA TXT record nobody added means the attacker reached your DNS provider or registrar account, which is a separate and more serious compromise than the website.
Remove the owner
The order Google requires: token, then owner, then sitemaps
Google’s help on managing owners is explicit that removing a verified owner means removing their verification token as well; otherwise they can verify again. Preserve first, then work through this in order.
- 01
Preserve the evidence
Copy the google*.html files with their timestamps, save the home page source and the matching database rows, screenshot Users and permissions and the Sitemaps report, and keep the access logs. The file’s timestamp and the log entry that uploaded it often date the compromise.
- 02
Remove every token you cannot account for
Delete the rogue google*.html files, remove the rogue meta tags from wherever they are written, and delete DNS records nobody added. Then confirm the token URL returns 404 and the home page no longer carries the tag.
- 03
Unverify the owner
In Settings, Users and permissions, open the menu next to the owner and, at the time of writing, choose to manage property owners and unverify them. Remove any users or delegated owners you do not recognise as well.
- 04
Remove their sitemaps
In the Sitemaps report, open each sitemap you did not submit and remove it. That stops Search Console reporting on it; it does not delete the spam pages, which still have to be removed from the site.
- 05
Clean the compromise
Placing a file in the web root needed write access. Find the way in and everything that came with it: the spam generator, backdoors, rewrite rules, rogue administrators, scheduled tasks. Then rotate hosting, SFTP, database and WordPress credentials from a device you trust.
- 06
Let Google see the spam is gone
Once the generator is removed and the spam URLs return 404 or 410, request a review under Security Issues if Google flagged the site. Use the Removals tool only for a few URLs that already return 404 or 410; it hides them temporarily and is not a substitute for the cleanup.
Afterwards
Keep the property and the index under watch
For a few weeks, check Users and permissions, the Sitemaps report and the Pages report once a week. Spam URLs leave the index as Google recrawls them and gets a 404 or 410, which can take a while for a large injection; a count of indexed pages that keeps rising instead means a layer survived.
Keep the owners list short and named. Every person and agency who needs Search Console can be added as a user with the permission they need, rather than verifying with a token of their own, and a token should be removed when the person who placed it leaves. An owners list you can explain line by line is the quickest way to notice the next stranger.
If more than one site lives on the same hosting account, check each one. An attacker who could write to one site’s web root can often write to its neighbours, and may have verified ownership of those too.
Common questions
Common questions about unknown Search Console owners
I got a “New owner” email from Google. Is it a phishing email?
It can be imitated, so do not follow links in it. Open Search Console directly from your browser and look at Settings, Users and permissions. If the owner named in the email is listed there and nobody on your team added them, the email was genuine and the site needs investigating.
I removed the owner but they are back. Why?
Their verification token is still on the site, or something on the site is writing it back. Delete the google*.html file, meta tag or DNS record first, then unverify them, and look for the backdoor or scheduled task restoring the token.
Can I delete every google*.html file in the web root?
Only the ones you cannot account for. Your own and your agency’s verification files keep your access working; deleting one removes that owner’s verification. Compare each file name with the owners list before you remove it.
Does an unknown owner mean the site was hacked?
If nobody who works on the site added them, yes: verifying needed a file or tag on the site or a record in DNS, so someone had that access. The owner is the symptom; the compromise that let them in still has to be found and closed.
Will removing the spam sitemaps remove the spam from Google?
No. Removing a sitemap only stops Search Console reporting on it. The spam pages leave the index when the site no longer serves them and Google recrawls them as 404 or 410.