Welcome to the Q&A Forum

Hey Olivier, You could detect the user agent and hide the button. The difference isn't substantial enough to be called cloaking. Or you could make the button not actually a button tag, but another tag with that traps clicks with a JS event. I'm not sure Google's headless browser is smart enough to automate that. I would try this first and if it doesn't work switch to the user agent detection idea. Let us know how it goes! -Mike

I also wish! But my impression at this moment was I have to make double linkbuiling work, for singular and plurial. In facts, It's 4x times the work, beacause we also have a french accent ( a and à ) in our brand name... D'OH! Thanks for the link. We probably test something with our newsletter to help resolving this.

Maybe it's partly because most of my visitors came from Google.ca, but at this moment, "not provided" is under 0,5% of my search traffic.