Hi. Yes you are correct the AMP pages are using a special template amp_thread_view which extends another one called AMP_CONTAINER
I would advice against changing the canonical URL on the AMP page though, as google can be very picky that the AMP page matches what is on the canonical page
13 of our customers are running UIX, and 3 are running UIX Pro, so I would say they work fine.
The only thing that might be needed with ThemeHouse themes is to enable the font-fix that is under advanced settings..
That is a good question, and would be hard to measure, since even a 500% growth on 0 visitors is still 0 visitors
If the forum is very niche'd and doesn't have big competitors in the same niche, it might help you get some first page ranking, but this all depends so much on various factors.
All things considered, for a new forum without any content, it probably isn't the biggest prio to have it installed, but once you have a couple 100 threads it might start making sense.
My suggestion is: Revert the AMP_CONTAINER template to the original..
The AMPXF addons adds what is needed (in early version some things were missing, but now should be fine for 95+% of cases)
As for the Twitter + AMS/AMP, @arn
raised this as an idea for an advanced option to automagically redirect the visitors landing on the AMP pages (i.e. when not on Google/Bing AMP caches) to the real site instead. I think it might be a good addition, but I'm still letting it mull in my head:
- How to handle so that you can still debug own pages / only redirect twitter visitors (maybe some referer header)
- Can this negatively affect the UX / Ranking or other things (I doubt it, but never know)
- This is not the immediate thing that needs to be added to AMPXF (@Bob's addons, along with bugfixes are)
Another option might maybe be to hide the AMP links from twitter bots?