Je kan informatie over je locatie aan je Tweets toevoegen, bijvoorbeeld je stad of exacte locatie, via het web en applicaties van derden. Je kan altijd de locatiegeschiedenis van je Tweets verwijderen. Meer informatie
My developers want clear direction. I’m trying to provide clear and testable acceptance criteria.
I'd use what's in the docs. Our tools might be a bit more permissive, but if you want to be sure to do it the recommended way, follow the guidance in the docs.
Cool, cheers for replying. We've kept to G documentation in our validation for search features, so 2-letter ISO 3166-1 alpha-2 country codes it is!
I've found that in reality Google is more lenient than the testing tools. But best to follow rules as best as you can. E.g. including $ in the price is technically wrong, but will not stop Google from working it out.
Don't think G is penalising me for using Thailand as the country on this page :)pic.twitter.com/KFqzqBZ1Cu
Also, The testing tool is not schema. It warns or errors about Google specific things, and ignore other technical errors related to the schema specs. Focus on it for gaining rich results and compliance with other readers like Facebook and Google shopping.
Thanks for the response. Shared with our dev team to document.
Twitter is mogelijk overbelast of ondervindt een tijdelijke onderbreking. Probeer het opnieuw of bekijk de Twitter-status voor meer informatie.
