The question is now whether publisher will revert their migrations and stop using AMP, or if they will continue to use it just because they already support it. I guess only few will be the first ones to dare stop supporting AMP before there is significant evidence that non-amp pages are treated fairly.
The question is now whether publisher will revert their migrations and stop using AMP, or if they will continue to use it just because they already support it. I guess only few will be the first ones to dare stop supporting AMP before there is significant evidence that non-amp pages are treated fairly.
Github already block FloC so this will not be different people are waking
I’m willing to bet in classic Google fashion, they will be “deprecating” AMP, causing a mad dash to get back off of it.