The intention is that AMP plugin will only handle AMP specifically. SEO would be the responsibility of a plugin like Yoast. Now with 1.0 the plugin is intended to be used with your existing themes and plugins, so it can just focus on issues related to AMP.

@jameseze Site nav menu is available with 1.0. If you switch from Classic mode to Paired (e.g. http://make.xwp.co/?amp) or Native (e.g. http://weston.ruter.net) then your active theme’s templates and stylesheets are also used in AMP responses. It isn’t a turn-key solution, especially if you’re using a theme that heavily relies on JS, but it is a good starting point.

If it appears that the styles are broken then it is likely that the theme or a plugin has too much CSS for AMP, or the admin bar from WordPress is causing too many styles to be added to the page. You can disable the admin bar for AMP pages to prevent this from happening, and that will help bring the limit down. I did a quick check of Hueman on a vanilla install and it showed the template looked fine in AMP.

You can open a new support topic for specific issues.

@jameseze That URL is not an AMP page, so that is why it is giving validation errors. Here is an AMP page for one of your posts: https://marineandoffshoreinsight.com/liferaft-five-important-things-to-learn-about/amp/

However, this is also generating AMP errors: https://validator.ampproject.org/#url=https%3A%2F%2Fmarineandoffshoreinsight.com%2Fliferaft-five-important-things-to-learn-about%2Famp%2F

It is due to this code not being inside the head:

<script async custom-element="amp-auto-ads"
        src="https://cdn.ampproject.org/v0/amp-auto-ads-0.1.js">
</script>

• This reply was modified 8 months, 1 week ago by Weston Ruter.

I don’t know how why the script is being put in that incorrect place. Try turning off WP Fastest Cache. It may be to blame.

@jameseze please do a search in the forum for info on that. For example: https://wordpress.org/support/topic/menu-in-classic-template-mode/