Google is building on its AMP announcement from yesterday by offering a series of tips on implementing AMP for your content. With AMP pages now appearing in Google’s regular search results, publishers face increased pressure to adapt.
Here are some tips and recommendations from Google on how to do that. Keep in mind that some of these are general guidelines rather than tips, but they are still important to understand.
### 1. Getting Started
If you’re new to this, create your website using a content management system that supports AMP. For example, WordPress can make your content AMP-ready with a simple plugin.
### 2. Is Your Content Suitable?
Google acknowledges that not all content is ideal for AMP. Static pages work well with AMP, whereas pages with more dynamic or interactive elements may not be as suitable.
### 3. AMP Integration Can Be Gradual
Adopting AMP doesn’t mean your entire site has to be AMP-ready immediately. Start with a few static content pages first, and then gradually work on other types of pages that people often visit via search results.
### 4. Open Source and Evolving
AMP technology is open for development by everyone. If your specific needs aren’t currently supported, you can submit a feature request on GitHub.
### 5. Validity is Key
Only valid AMP pages are eligible to appear in Google’s search results. Ensure you learn how to validate and debug AMP pages properly.
### 6. No Direct Ranking Boost
AMP is not a ranking factor by itself. While AMP pages will be marked with a lightning bolt icon in search results, which may draw more clicks, this does not automatically improve search rankings.
### 7. Expansion Plans
AMP search results on Google are set to roll out worldwide soon, and the top stories carousel is already available in several countries.
### 8. Ask for Help if Needed
Google reminds you that resources like the Webmaster Help Forum, Stack Overflow, and GitHub are always available if you have any questions about AMP.
For further assistance, you can refer to a complete guide to making your content AMP-friendly.
