#ampresults by @aleyda at #pubcon AMP Real World Results
#ampresults by @aleyda at #pubcon
AMP Real World Results
#ampresults by @aleyda at #pubcon
I’m Aleyda Solis
#ampresults by @aleyda at #pubcon#ampresults by @aleyda at #pubcon
I help companies to connect with them
#ampresults by @aleyda at #pubcon#ampresults by @aleyda at #pubcon
Some of them brands you likely know
#ampresults by @aleyda at #pubcon
Having a fast mobile Website is one of the fundamental aspects to achieve this goal
#ampresults by @aleyda at #pubcon
#ampresults by @aleyda at #pubcon
Which will be even more critical with Google’s upcoming mobile first index too
#ampresults by @aleyda at #pubcon
Users have minimum expectations
#ampresults by @aleyda at #pubcon
But this is our speed reality
#ampresults by @aleyda at #pubcon
Let’s see… how much time the Buzzfeed home page takes to load?
#ampresults by @aleyda at #pubcon
#ampresults by @aleyda at #pubcon
Ouch
https://testmysite.thinkwithgoogle.com/
#ampresults by @aleyda at #pubcon
And the Walmart one?
#ampresults by @aleyda at #pubcon
#ampresults by @aleyda at #pubcon
Yup
https://testmysite.thinkwithgoogle.com/
#ampresults by @aleyda at #pubcon
And the Best Buy one?
#ampresults by @aleyda at #pubcon
I think I’ve made my point
https://testmysite.thinkwithgoogle.com/
#ampresults by @aleyda at #pubcon
The solution is to implement WPO principles to make Mobile sites to load fast
https://developers.google.com/speed/docs/insights/rules
#ampresults by @aleyda at #pubcon
But big sites have restrictive legacy platforms & small ones little resources to improve them
#ampresults by @aleyda at #pubcon
This is why Google launched AMP
#ampresults by @aleyda at #pubcon
It uses a “simplified” HTML version with optimised resources & cache to serve faster in Mobile SERPs
https://www.ampproject.org/learn/overview/
#ampresults by @aleyda at #pubcon
AMP is published “parallely” and canonicalized to your current (slower) Mobile Web pages
https://www.forbes.com/sites/alanwolk/2017/09/07/apple-is-losing-its-cool-factor-and-thats-a-problem-if-they-want-to-break-
into-tv/#4707740c71f8
https://www.forbes.com/sites/alanwolk/2017/09/07/apple-is-losing-its-cool-factor-and-thats-a-problem-if-they-want-to-break-into-tv/amp/
#ampresults by @aleyda at #pubcon
It’s also cached and pre-rendered by Google when shown in Mobile SERPs
Google AMP Viewer URLthat is pre-rendered
Canonical URL of the Page
Content served from AMP Cache URL
#ampresults by @aleyda at #pubcon
Making it certainly much faster
https://www.forbes.com/sites/alanwolk/2017/09/07/apple-is-losing-its-cool-factor-and-thats-a-problem-if-they-want-to-break-
into-tv/#4707740c71f8
https://www.forbes.com/sites/alanwolk/2017/09/07/apple-is-losing-its-cool-factor-and-thats-a-problem-if-they-want-to-break-into-tv/amp/
#ampresults by @aleyda at #pubcon
AMP usage is not a ranking factor
#ampresults by @aleyda at #pubcon
But Google made it a requirement to be included in the News Carrousel
#ampresults by @aleyda at #pubcon
and can be also shown in organic results
AMP article rich resultsCan be free-standing in the results page, or embedded in a carousel of
similar result types. All AMP article rich results are also rich results.
AMP non-rich resultsA basic, non-graphical search result
pointing to the AMP page.
#ampresults by @aleyda at #pubcon
Which has given it an impressive SERP visibility
https://www.rankranger.com/amp-on-google-serp
#ampresults by @aleyda at #pubcon
As well as traffic to the sites using itAMP Rich Results
AMP Non-Rich Results
Non-AMP Results
More Mobile organic visibility and traffic from
AMP than non-AMP results
#ampresults by @aleyda at #pubcon
However, AMP is not a replacement of your Mobile site
#ampresults by @aleyda at #pubcon
Even Google representatives agree that is not a “bullet-proof” solution for all sites
“It wouldn’t be reasonable for us to expect that a group of limited functionalities replace all what you can do at the moment in the mobile environment…AMP its meant to serve in certain use cases”
https://www.youtube.com/watch?v=wtOjUwGnrVY
#ampresults by @aleyda at #pubcon#ampresults by @aleyda at #pubcon
AMP is a fast “add-on” to your already existing (but still slow) mobile Website
Just what happens with Batman as a super hero… he
doesn’t have any superpowers
#ampresults by @aleyda at #pubcon#ampresults by @aleyda at #pubcon
Sorry Batman
AMP A fast Mobile site
#ampresults by @aleyda at #pubcon
But due to the way it is presented and its expansion efforts it might look like it
#ampresults by @aleyda at #pubcon
Just what happens to Batman as a superhero too
#ampresults by @aleyda at #pubcon
#ampresults by @aleyda at #pubcon
That’s why there are reservations about it: “AMP has a good intentions… but sacrifice the open Web”
#ampresults by @aleyda at #pubcon
You shouldn’t then use AMP as a silver bullet Mobile speed solution but a resource in certain scenarios…
#ampresults by @aleyda at #pubcon
Thanks Alfred :)
#ampresults by @aleyda at #pubcon
You will be able to minimize situations like this
#ampresults by @aleyda at #pubcon
Use AMP when your Mobile site is too slow and/or you want to be included in the carrousel
#ampresults by @aleyda at #pubcon
and/or
Too slow and can’t be improved
Needs to be included in carrousel
#ampresults by @aleyda at #pubcon
Avoid implementing AMP when you have an independent mobile Web Version
Desktop Web Parallel Mobile Web Version with M subdomain
AMP version under the M subdomain
Google AMP Viewer URL
Canonicalize to
Generates
#ampresults by @aleyda at #pubcon
Verify if you can Implement your current Mobile Web UI & functionality with AMP
#ampresults by @aleyda at #pubcon
#ampresults by @aleyda at #pubcon
Your AMP URLs should replicate your own Mobile Web UI & functionality, instead of this
ORIGINAL MOBILE PAGE AMP VERSION
#ampresults by @aleyda at #pubcon
Validate that your mobile Web functionality can be replicated by using AMP components
https://www.ampproject.org/docs/reference/components
#ampresults by @aleyda at #pubcon
Check with your development team if you have the capacity and flexibility to use them
https://ampbyexample.com/
#ampresults by @aleyda at #pubcon
You can even test while validating your code directly in the AMP Playground editor
https://ampbyexample.com/playground/
#ampresults by @aleyda at #pubcon
Plan ahead using the roadmap with a reference of the functionalities to come
https://www.ampproject.org/roadmap/
#ampresults by @aleyda at #pubcon
There are also free Wordpress plugins that highly facilitate the implementation
#ampresults by @aleyda at #pubcon
You can also use freemium and paid WP plugins like AMP for WP and weeblrAMP
#ampresults by @aleyda at #pubcon
They will allow you to personalise more, but you’ll likely need further development support
#ampresults by @aleyda at #pubcon
They’re not an “out of the box” solution and will still need design personalisation
ORIGINAL MOBILE PAGE AMP URL VERSION
#ampresults by @aleyda at #pubcon
The goal should be to keep the UI and functionality consistent
ORIGINAL MOBILE PAGE = AMP VERSION
#ampresults by @aleyda at #pubcon#ampresults by @aleyda at #pubcon
Check your AMP visibility potential to prioritize your implementation
accordingly
#ampresults by @aleyda at #pubcon
Verify the share and type of queries for which AMP results are shown in your industry
https://www.sistrix.com/
#ampresults by @aleyda at #pubcon
Identify which of them are shown along SERP features to prioritise and format your content
#ampresults by @aleyda at #pubcon
Like this
#ampresults by @aleyda at #pubcon#ampresults by @aleyda at #pubcon
Avoid linking to your AMP URLs unless you’re using them as your
canonical mobile Web pages
#ampresults by @aleyda at #pubcon
There’s an inconsistent mobile user experience when accessing to AMP pages from SERPs
#ampresults by @aleyda at #pubcon
Which ends-up causing that users link and share the non-canonical Google AMP Viewer URLs
#ampresults by @aleyda at #pubcon
Start avoiding these by making sure to only link internally to your canonical URLs from AMP
#ampresults by @aleyda at #pubcon
You can also refer your users to your original Website version to continue browsing your site
#ampresults by @aleyda at #pubcon
Remember to also redirect based on the user agent to avoid showing non-mobile visitors your AMP URLs
DON’T DO THIS DO THIS
#ampresults by @aleyda at #pubcon#ampresults by @aleyda at #pubcon
Validate your AMP implementation before and after launch with SEO
crawlers to minimise issues
#ampresults by @aleyda at #pubcon
+70% of top publishers with AMP across 8 countries (including the US) have implementation errors
#ampresults by @aleyda at #pubcon
Most common AMP mistakes are related to usage of disallowed and non-supported attributes & tags
https://www.semrush.com/blog/amp-mistakes-semrush-study/
#ampresults by @aleyda at #pubcon
For real
THIS IS NOT THE AMP VERSION OF THE ABOVE ARTICLE
#ampresults by @aleyda at #pubcon
Avoid them by using the AMP validator Chrome extension to go through your main pages
https://chrome.google.com/webstore/detail/amp-validator/nmoffdblmcmgeicmolmhobpoocbbmknc
#ampresults by @aleyda at #pubcon
Crawl all of your site pages to validate AMP implementation issues before and after launching
https://sitebulb.com/
#ampresults by @aleyda at #pubcon
SEO crawlers like Sitebulb, Deepcrawl & SEMrushalready include AMP configuration problems
deepcrawl.com
#ampresults by @aleyda at #pubcon
You’ll be able to obtain and fix quickly those that would generate critical issues in the Search Console
#ampresults by @aleyda at #pubcon
https://www.screamingfrog.co.uk/log-file-analyser/
Validate if possible in your logs if Googlebot’s crawling behavior of your AMP URLs is consistent
19 OF THE 20 CRAWLED URLs ARE AMP
#ampresults by @aleyda at #pubcon#ampresults by @aleyda at #pubcon
Monitor AMP implementation errors with GSC AMP report, where you should focus on fixing critical
issues first
#ampresults by @aleyda at #pubcon
It’s usual to be overwhelmed by the increase of AMP issues when launching or updating
SIGH
#ampresults by @aleyda at #pubcon
Prioritise to fix critical issues first, which will be the ones preventing to be shown in SERPs
THIS
#ampresults by @aleyda at #pubcon
Start with those affecting the highest number of pages and check them directly there
#ampresults by @aleyda at #pubcon
Focus on identifying how the non-supported code is included to establish a pattern and remove it
#ampresults by @aleyda at #pubcon
YES
Rinse and repeat until you minimise critical errors
#ampresults by @aleyda at #pubcon#ampresults by @aleyda at #pubcon
Monitor your AMP visibility impact to prioritize your efforts along the
on-going content development and optimization process
#ampresults by @aleyda at #pubcon
Opt-in for Google Analytics AMP Client ID API to correctly track AMP on Cache
https://support.google.com/analytics/answer/7486764
#ampresults by @aleyda at #pubcon
Beyond the AMP vs. Non-AMP traffic trend, what’s the impact of AMP on users behavior?
#ampresults by @aleyda at #pubcon
Follow-up w/ your own AMP results via the Google Search Console too
#ampresults by @aleyda at #pubcon
Verify the top queries per AMP URL to identify further AMP content opportunities
#ampresults by @aleyda at #pubcon
Be mindful of Search Console false positives though
#ampresults by @aleyda at #pubcon
Use SEOmonitor to track AMP for your targeted (ranked or unranked) keywords
https://www.seomonitor.com/
#ampresults by @aleyda at #pubcon
You can also spot AMP opportunities vs. your competitors with SEMrush rank tracking
https://www.semrush.com
#ampresults by @aleyda at #pubcon
rankranger.com
Do the same with your News Carrousel AMP rankings by using RankRanger
#ampresults by @aleyda at #pubcon#ampresults by @aleyda at #pubcon
If at some point you want to disable AMP, follow SEO best practices to
avoid losing that traffic
#ampresults by @aleyda at #pubcon
Remove the rel=”amphtml” link tag and 301-redirect AMP URLs to your canonical ones
https://developers.google.com/search/docs/guides/remove-amp
HANDY WORDPRESS
PLUGIN
#ampresults by @aleyda at #pubcon
Here’s a list with all of these, so you don’t forget
Verify if you can Implement your current
Mobile Web UI & functionality with AMP
Check your AMP visibility potential to prioritise your
implementation accordingly
Monitor AMP implementation errors with GSC AMP report, where you
should focus on fixing critical issues first
Avoid linking to your AMP URLs unless you’re using them as your canonical mobile Web
pages
Validate your AMP implementation before
and after launch with SEO crawlers to minimise issues
Monitor your AMP visibility impact to prioritize your
efforts along the on-going content development and
optimization process
If you want to disable AMP, don’t forget SEO best
practices, removing tag to AMP and redirecting to your
mobile pages
#ampresults by @aleyda at #pubcon
Now is your turn
#ampresults by @aleyda at #pubcon