templatic-google-amp
Templatic-Google-AMP
To work with Templatic AMP plugin just type 'amp' keyword after any archive, category, details or any page URL it will display AMP version o …
Proof Health
Open evidenceCommercial opportunities need traceable source links before they are treated as build-worthy.
50.0% of this page's analysis has direct source links.
0 rows here require auditable proof before promotion.
0 rows have source counts but still need direct links.
Related Opportunities
3 marketsSource Evidence
Open evidence explorerAdd AMP link markup to regular page?: users show bugs, missing feature pain that may indicate a product gap.
Buyer: site owners, SEO consultants, and agencies · Wedge: monitor amp drift, schema/indexing failures, and client-readable search-impact fixesShow only excerpt in AMP with “more” to real page using template?: users show missing feature, support pain that may indicate a product gap.
Buyer: site owners, SEO consultants, and agencies · Wedge: monitor amp drift, schema/indexing failures, and client-readable search-impact fixesAmp implementation and JSON-LD: users show missing feature, support pain that may indicate a product gap.
Buyer: site owners, SEO consultants, and agencies · Wedge: monitor amp drift, schema/indexing failures, and client-readable search-impact fixesFront-page AMP displays posts, like Home: users show missing feature, support pain that may indicate a product gap.
Buyer: site owners, SEO consultants, and agencies · Wedge: monitor amp drift, schema/indexing failures, and client-readable search-impact fixesHierarchical taxonomies not working: praise conversation with limited structured signal.
Buyer: site owners, SEO consultants, and agencies · Wedge: monitor amp drift, schema/indexing failures, and client-readable search-impact fixesBlog Page Displays Instead of Home Page: users praise reliable, quality, which suggests what competitors already do well.
Buyer: site owners, SEO consultants, and agencies · Wedge: monitor amp drift, schema/indexing failures, and client-readable search-impact fixesCompetitor Context
4 shownRepeated Themes
0 shownNo repeated plugin-level themes have been generated yet.
Collected Signals
6 shown from 6 collectedBlog Page Displays Instead of Home Page: users praise reliable, quality, which suggests what competitors already do well.
Evidence: Blog Page Displays Instead of Home Page The plugin works great for all pages and posts except for the home page.Hierarchical taxonomies not working: praise conversation with limited structured signal.
Evidence: Hierarchical taxonomies not working https://books.micnode.com/subject/bio/000000-bio/amp https://books.micnode.com/subject/bio/002000-bio/amp https://books.micnode.com/subject/bio/000000-bio/amp https://books.micnode.com/subject/bio/002000-bio/amp But working the parent https://books.micnode.com/subject/bio/amp/ But working the parent https://books.micnode.cAdd AMP link markup to regular page?: users show bugs, missing feature pain that may indicate a product gap.
Evidence: It’s the only AMP plugin I have found that also works for pages and works without crashing.Show only excerpt in AMP with “more” to real page using template?: users show missing feature, support pain that may indicate a product gap.
Evidence: I would like the option to turn this on on the “post” and “page” pages -I already purchased the AMP Ads add-on, I would purchase this option as an add-on as well if it was made available!!!Amp implementation and JSON-LD: users show missing feature, support pain that may indicate a product gap.
Evidence: Amp implementation and JSON-LD I think it might be an idea to add a field in the plugin settings for inserting google’s recommended method of adding structured data: json-ld 😛 Right now it, well, using the header field mutilates the json-ld (unsupported format).Front-page AMP displays posts, like Home: users show missing feature, support pain that may indicate a product gap.
Evidence: Front-page AMP displays posts, like Home front-page and home are something quite different for WP, but it seems that this is not yet or not fully supported by your plugin.