14
UPDATE Sept-2019: Google's recent changes to Google Search Console has made my original answer (below) a bit outdated and in some respects incorrect.
You can now submit two different types of properties in GSC:
"URL-prefix property", which is the same as the property type mentioned here. In this case you would still submit all variations as required, ie ...
9
I like the HTML verification method. I use it myself. There are several reasons to prefer it:
It is the oldest verification method. For a long time Google only supported this method. It is tried and true.
It is usually easy to do, just upload a file and you are done. It doesn't usually require you to install plugins in your CMS or modify your website'...
answered Sep 8 '18 at 20:14
7
After verifying site ownership, is it ok to remove the <meta name="google-site-verification"> tag?
No. If you want to remove it and remain verified, you'll need to use another form of verification.
Reference
6
Yes, it failed verification as a means of verifying site ownership in Google Search Console.
This does not mean the GA tracking is not installed and working, just that the current method of installation, cant be used to verify site ownership.
If GA is setup via tags in GTM, then GA cannot be used for verification. it needs to be the GA tracking code snippet ...
5
How much code do you want to write?
One possible way to do this is to have the musician log in to your site with the Facebook account that controls their Facebook page. You can then automatically check with the Facebook API to see if that account actually does have admin access to the band's Facebook page, and then you have instant, hassle-free verification....
4
Are you afraid from bots and spam? Or from people who pretend to be real bands, but are actually garage amateurs?
I believe it's the latter - Therefore a requirement of a website/social media page for a manual check seems the best way for me. Bands usually put their songs/images/performances.
You can also require a band to have 3 publicly accessible songs ...
3
Try this:
RewriteCond %{REQUEST_URI} !^/mygooglefile.txt$ [NC]
RewriteRule ^(.*)$ http://www.example.com/$1 [R=301,L]
Of course you will need to change the file name and the target domain name.
3
As a good practice, you should always keep old, new and all variations of both as a property on Google Search Console. But why? this is due to the fact that should a problem arise Google can notify you. This includes but not limited by redirect hacks, malware and even penalties.
3
Airbnb solved this issue by using both online and offline indicators.
https://www.airbnb.com/help/article/450
However, for your product, this seems a bit excessive but will solve the identity issue.
Online
You can require people to link to their social media accounts such as Facebook & Twitter. This would even open up possibilities in the future ...
2
Google app engine has documentation for static files. Treat your googleXXXXXXXXXXXX.html verification file as a static file:
By default, all files in the WAR are treated as both static files and resource files, except for JSP files
So just put that file into the root of your war file.
If for some reason you have configured HTML to be non-static, the ...
answered Dec 20 '14 at 12:08
2
For initial testing in IE this may be sufficient, but there will always be some differences between how a site loads in an emulator to the real thing. The amount of testing you do should really be strategically influenced by the target user base and the amount of traffic the site receives.
By using a web analytics tool such as Google Analytics or Piwik (...
2
While revising this post to add more detail I went through the steps to add a property again. However, this time I googled "Google Webmaster Tools" and then used the link in search (https://www.google.com/webmasters/tools/home). Voila -- It worked this time!
POSSIBLE REASONS IT WORKED THIS TIME
When I wrote the post I used a link from a post on a website ...
2
Your best option is probably to verify using DNS. This will work no matter what sort of redirects you have in place. It also doesn't require you to keep up with any special redirect rules.
According to Google's help page, you should:
On the Search Console Home page, click the Manage Site button next
to the site you want, and then click Verify this ...
2
You can ask them to post a photo to their social media profile holding a paper in front of them with your site written on it and the date. This proves they control the social media profile, they are specifically referencing your site, and it is a current image.
2
I am pretty sure that this happens for one of two reasons:
Unlikely, but you submit the site as http://example.com/, but it redirects to HTTPS.
Most likely your server blocks some incoming requests (at least PageSpeed and Host-Tracker cannot access it).
1
Okay, first do what it says: click on Edit methods -> Get record.
You need to copy the value of the Host field and go to Domain list -> Select your domain and click Manage -> Advanced DNS -> ADD NEW RECORD -> Select CNAME RECORD -> Paste the value of Host that you just copied on the Host field of the CNAME Record. Now, copy the Target field'...
1
Domain properties can't connect with GA for the moment.
To link with GSC with GA just added the URL of your website as property (you just need to add the actual URL of your website). Normally it's https://example.com or https://www.example.com
1
Each person that has site ownership, should have their own verification code via Google Search Console.
Verified owners can delegate ownership to other persons too, however if the verified ownership expires, then the delegated owners lose their access to the Google Search Console Property too
Verify your site ownership
1
The Google webmaster verification code for your website & it's subdomains are shared. For example if you verified example.com the same code can and will be used to verify www.example.com
1
Based on my experience, no impact to the data and ranking result.
The new owner's data have the same data as the old owner's data. Nothing is different.
Note: I just tried after I read your question.
1
There should be no data loss, but the new domain property may take a while to populate.
Note that some integrations do not support domain properties yet. Like linking to Google Analytics.
I'd not delete any site level properties. Keep them as a backup. Even consider adding the www variants.
1
The best way is the one you mentioned in point 2.
You will have to add two separate properties in your search console
http://example.com
http://subdomain.example.com
The procedure in point 1 is not possible as of now, because the new search console will not allow you to add a sitemap for any subdomain, inside the http://example.com property.
Also the new ...
1
If not already done so, try verifying the non-www first and then verifying the www version. www is a subdomain. The non-www version must be verified first. You may also then want to put in a redirect so it resolves to just one or the other.. not both, and then elect the preferred domain via settings in Google Search Console
1
Only the EV = Extended Validation certificates give you the green bar.
It looks different, though, in each browser, these are just examples:
None of the OV / DV give it to you.
The OV certificates just contain company information in it, are worth in my opinion only to State authorities.
1
The customer's site is actually available only at example.com/login.
Let's make an assumption that Google isn't advanced as we thought it would be.
Your link suggests to me that the default page on your server when someone uses example.com is a 404 page (or HTTP/1.x 404 Not found header to the browser). This alone (to 99% of the world population) would ...
answered Aug 16 '17 at 5:15
Mike -- No longer here
13.4k4 gold badges22 silver badges52 bronze badges
1
Domains support multiple TXT record entries, so adding multiple TXT records to one domain is not a problem for either your domain or Google.
However you need to use a different alias, for example:
Root Domain will use alias @ or leave it blank
Sub Domain should be set to the name of the subdomain, if your subdomain is sub.domain.com, write sub for the Host....
1
Since you have clearly mentioned that you saw the history after you deleted and added the property again, nothing can be done and you will have to just live with it.
1
It isn't hard to see if your DNS TXT records are set up correctly and have propagated yet (it may take a few days).
You can use the command line tool dig to see your DNS text records and see if they include the Google verification:
$ dig +short -t TXT jelqtools.com
"google-site-verification=9lhJSkzu2UDWGrzgTSfk2q8m-sLN8cp5fk0atqV6XOI"
There are also ...
answered Jan 12 '16 at 13:20
1
In my opinion, a good ID verification would be a non invasive and private process (non visible by all).
The best way is most probably a verification of a government issued id (sent by post or mail) but it's a little bit a heavy process and you don't want to. That's why in your case, I think a Skype call could be the best solution. Just require a thumbnail ...
1
There is a lot of important stuff that is missing from this question. One of which is whether your DNS server is the authority for your site. I am making some assumptions here.
Assuming that your DNS server is acting as the SOA (authority) for your domain, then you would, I assume since I have no idea what this is for, add an A text record for your site. ...
Only top voted, non community-wiki answers of a minimum length are eligible