AMP Content Management System
Here in the system, the AMP pages are dynamically generated and delivered. After the Google stores the page once, delivers from the time Google your page. AMP pages containing errors are not indexed. This means that this prevents your current Google indexed page is not affected then. And continue to deliver error-free until you deliver a bug-free page to Google.
The CSS file is limited and as soon as it is exceeded the page can not be indexed. The indexing you can imagine as a cache, the page is stored as it is. Changes will only become visible once the new page has been indexed or saved.
The Accelerated Mobile Pages project is a source open framework and is supported by Google. Mobile Internet usage is growing very fast, the evaluations of search engines and other sources of information prove this.
It is becoming more and more important for mobile users to do justice, as the bounce rate is also dependent on the load time of the website. That's why the Page Speed test is so important nowadays and also in the future to supply mobile devices properly.
tnado is more than just designed for SEO but has lots of on board u.a. also Google AMP (Accelerated Mobile Pages) and that's what it's about. The tnado AMP engine mirrors each of your pages as AMP pages (all dynamic), all themes bring an AMP version so you do not need any technical knowledge. The system is designed for efficient and successful work, Diese Seite als AMP Seite if you are not already on it :) You will have all the features AMP offers here in tnado.
You can find it here in the blog What is AMP more about AMP and tnado. There are several opinions, one that AMP should or should not integrate into a CMS as a plugin, but this difference of opinion also exists with Dynamic System. The opinions differ, because one assumes that it slows down the AMP sides and one should use only pure AMP.
What should an AMP CMS bring?
An AMP CMS should offer all possibilities the AMP brings and the AMP sides deliver error-free for an indexing. Separate template system to better control the quality. AMP templates should be integrable in the system. Reference should be made to AMP specifications, i.a. like the CSS size, to ensure in advance that you do not exceed the given size.
If I surf on websites then I also notice the weird URL forms like
/kategorie/amp/ and that's the amp side and some category, I wonder what happens if the person now has a category that also contains amp one of the sites will not be watching. I'm more against something like that and not the AMP pages are being spent dynamically.
AMP Extension and Indexing
If you have already installed the tool for your browser you can see if this is the AMP site. Of course you can also search mobile for the AMP version, as soon as it has been indexed by Google it will appear or appear in the search results.
Here's a screenshot from the old Google Search Console:
Google also shows you errors there and also which page it is. So you can react and make the site fit to index again.
Learn more about AMP development:
AMP
AMP Start
AMP Templates
AMP Examples