AMPXF - AMP for Xenforo 2

AMPXF - AMP for Xenforo 2 [Paid] 1.4.9

No permission to buy (€50.00)
What did you say about this: https://plausible.io/blog/google-amp

Is AMP death now?
Okay some more things to consider: plausible.io is an analytics platform which is a direct competitor with Google Analytics, and they don't have support for the amp-analytics component.. i.e. They are very biased against Google.

Here is a much less biased summary of the upcoming changes, with no clickbaity title :)


Also: I guess someone forgot to tell the AMP project developers that AMP is dead?? :ROFLMAO: (poor developers..)




About the new Core Web Vitals that will become important soon:

In our own site's GSC when we open the Core Web Vitals tab we can see the following:
1621539444491.png

Digging further, all of the "poor" pages are the normal pages that XF serves without AMP.
1621539551444.png

All of the Good pages are the AMP variants of the same pages (i.e. URLs end with ?amp=1):
1621539528948.png


So to summarize: even with the new changes coming to the ranking signals, you are covered if you are running AMPXF :) 👍
 
Last edited:
It does make me wonder, if Google does kill it off, will they then end up penalising sites for duplicate content if they're still trying to run an amp version of all the content on their site? Duplicate content has always been a big no no and it seems in the coming months you'll now have normal pages that have been optimised in accordance with core web vitals competing for the same spots as amp pages.
 
It does make me wonder, if Google does kill it off, will they then end up penalising sites for duplicate content if they're still trying to run an amp version of all the content on their site? Duplicate content has always been a big no no and it seems in the coming months you'll now have normal pages that have been optimised in accordance with core web vitals competing for the same spots as amp pages.
Simple answer no.

The canonical page links to the AMP page with a meta tag in the <head>-section of the page, and the AMP page also links back to the canonical page with a <link rel="canonical" href="https://linktothecanonicalpage" />. The search engines know how to handle these tags :) 👍

If you want to read more about duplicate content and how the canonical tag helps:

(btw, the AMP spec actually requires linking back to the canonical page for it to be a valid AMP page)

Has AMP ever been alive then? :X3:
Schrödinger's AMP? :D 🤷‍♂️
 
google has created a monster though. potentially millions of links pointing to amp cache pages all over the web. they would need to be preserved if they ever decide to stop supporting amp platform.

and to stop people from sharing amp urls, they started using canonical link in chrome when you try sharing on the mobile app. this becomes a problem on sites that have misconfigured canonical pages.
 

Attachments

  • 1621592769694.webp
    1621592769694.webp
    25.7 KB · Views: 20
google has created a monster though. potentially millions of links pointing to amp cache pages all over the web. they would need to be preserved if they ever decide to stop supporting amp platform.
The thing with the AMP Cache pages is that they are very easy to convert back into the normal URL, so that isn't a problem really :)
Also: Google isn't stopping support for AMP, they just have to play down the importance of it due to monopoly and anti-trust claims..

and to stop people from sharing amp urls, they started using canonical link in chrome when you try sharing on the mobile app. this becomes a problem on sites that have misconfigured canonical pages.
If the canonical page and the AMP page are not pointing correctly towards each other (1 to 1) the AMP page and googlebot will trigger a warning until it is fixed, and the AMP page won't show up as such in the results..

So I find it hard to believe that that screenshot would be "due to chrome" and not due to the site triggering the share-dialogue incorrectly some other way :)

Could you send me the link where you get that weirdness to trigger and I can check if my suspicion is correct? :) (I tried finding that page/site from google and I can't get it to react the way that you show in the screenshot)
 
I have been noticing amp canonical url issue on a lot of domains ever since chrome started using canonical link instead of the actual link you have opened in chrome on android for sharing.

mid-day.com was in the screenshot. i reported the problem to them and they now seem to be linking to AMP page itself from the AMP pages in canonical which as you said is also not correct.

https://www.mid-day.com/amp/news/opinion/article/torment-of-muslims-in-covid-time-23169112

<link rel="canonical" href="http://www.mid-day.com/amp/news/opinion/article/torment-of-muslims-in-covid-time-23169112" />

here another example.

1621603427394.png

economist.com is linking to their homepage in canonical on their amp pages.

https://amp.economist.com/leaders/2021/05/20/even-with-a-ceasefire-israel-and-hamas-will-not-stop-fighting-each-other

<link rel="canonical" href="https://www.economist.com"/>
 
I have been noticing amp canonical url issue on a lot of domains ever since chrome started using canonical link instead of the actual link you have opened in chrome on android for sharing.

mid-day.com was in the screenshot. i reported the problem to them and they now seem to be linking to AMP page itself from the AMP pages in canonical which as you said is also not correct.

https://www.mid-day.com/amp/news/opinion/article/torment-of-muslims-in-covid-time-23169112

<link rel="canonical" href="http://www.mid-day.com/amp/news/opinion/article/torment-of-muslims-in-covid-time-23169112" />

here another example.

View attachment 252223

economist.com is linking to their homepage in canonical on their amp pages.

https://amp.economist.com/leaders/2021/05/20/even-with-a-ceasefire-israel-and-hamas-will-not-stop-fighting-each-other

<link rel="canonical" href="https://www.economist.com"/>
Interesting, I don't have that share button in chrome that you have :) (I have to go under the ellipsis icon and share)

But yeah I think it makes sense to share the real url instead of the AMP variant anyway, as there is no use to open an AMP link on a desktop, and when you share to someone you can't really know if they will open it on mobile or desktop :)



Interesting, I didn't know Chrome used the canonical link for sharing, it has apparently been doing it since Chrome 64 (released Jan 2018) so it is not exactly new :)

But yeah, It makes sense to do that as all kinds of tracking params in the URL would otherwise be shared onwards to your friends and probably skew some data..

If some site has wrongly/badly set canonical links they anyway have bigger SEO problems as that is also used to indicate that the page is a copy of some other page..
I guess the googlebot is smart to ignore it if it goes to a completely different domain, but you never know as there might even be use cases for that scenario (although probably uncommon ones..)
 
on related note. i have also seen some sites (indian news sites as usual) which stop using amp but forget to remove amp urls from their source code. here is one.

http://www.millenniumpost.in/big-stories/pm-modi-lauds-doctors-frontline-workers-of-varanasi-for-fight-against-covid-19-440840

and then there are others which stop using amp but do not redirect amp urls (which become dead as a result) to regular pages.

enough offtopic chat for now 😪
 
Great app, I have started to see a rise in traffic in recent days, a couple of weeks after installing it.

I have one comment about an area for improvement: IMHO we shouldn't get prompts to install the latest version in the admin control panel until it is out of beta. Thanks for listening to user feedback @mazzly.
 
Hi @mazzly - I'm getting the following warnings in GSC, but not ampxf; any ideas?
@CivilWarTalk got that also at some point, but I think it went away by itself? Thinking it has something to do with CF changing the certificate used for the AMP Real URL..

Great app, I have started to see a rise in traffic in recent days, a couple of weeks after installing it.

I have one comment about an area for improvement: IMHO we shouldn't get prompts to install the latest version in the admin control panel until it is out of beta. Thanks for listening to user feedback @mazzly.
that option exists in addon setting.

Yes, I think we should change it however to be enabled by default, because likely most forum owners want only stable releases :)
 
Was just wondering. Probably already answered. AMP page views do not add to views on threads right? Not even when you load the amp page right on the domain and not through amp cache?
 
Hey @mazzly did you read about the Signed Exchange from Google?


Yes 👍

Basically this is out of the scope of the AMPXF addon as it requires lower level things in place for the certificates etc..

However, if you are using cloudflare as your DNS you can easily get this enabled by activating the "AMP Real URL" option :) 👍

Was just wondering. Probably already answered. AMP page views do not add to views on threads right? Not even when you load the amp page right on the domain and not through amp cache?
AMP page views are also counted, both when served from AMP caches and directly from the server 👍

I've alreay buy it. how can i test it
Open a thread and add ?amp=1 at the end :) 👍

 
if you are using cloudflare as your DNS you can easily get this enabled by activating the "AMP Real URL" option :) 👍
huh! thanks! somehow I missed this:

Signed exchange service providers​

Here is a list of CDNs and hosting providers offering out-of-the-box support for signed exchanges. Using one of these is the easiest way to get started with signed exchanges:

 
Top Bottom