AMP reviews changed because AMP itself stopped being a must-have publishing format for many WordPress sites. Google no longer requires AMP for Top Stories, WordPress publishers have better Core Web Vitals tools, and many review widgets do not work cleanly inside AMP pages. As a result, site owners who once treated AMP as essential now treat it as optional, limited, or not worth the hassle.
TLDR: AMP did not disappear, but its role shrank. A WordPress publisher that once used AMP for every article may now see only a small mobile speed gain, such as a 5% faster load time, while losing review widgets, ad controls, or design features. For example, a product review blog with 300 posts may find that star ratings vanish on AMP pages because the rating plugin uses JavaScript that AMP blocks. Many publishers now prefer a fast responsive theme, caching, image compression, and clean schema instead.
What “AMP Reviews” Usually Means
The phrase “AMP reviews” can point to a few related issues. Some people mean reviews of AMP plugins in WordPress. Others mean product reviews, star ratings, comments, or review schema shown on AMP pages. In both cases, the story is similar: AMP became less central, and the weak spots became harder to ignore.
AMP, short for Accelerated Mobile Pages, was built to make mobile pages load quickly. It did that by forcing strict rules. Pages had limited JavaScript, controlled CSS, and a fixed set of approved components. That helped speed. It also broke many normal WordPress features.
Review sites felt this pain early. Star rating plugins, sliders, comparison tables, affiliate boxes, comment tools, and third-party badges often depended on scripts that AMP would not allow. Honestly, it feels like half the job became checking what vanished on the AMP version of a page.
[ai-img]mobile publishing, wordpress dashboard, amp pages[/ai-img]
Why AMP Became Less Important
For several years, AMP had a clear reward. Google gave AMP pages special visibility in mobile search features, especially the Top Stories carousel. Publishers cared because traffic mattered. If AMP helped a page appear in high-traffic news spots, the tradeoff looked reasonable.
That changed. Google opened Top Stories eligibility to non-AMP pages, as long as they met quality and page experience standards. The message was clear. A fast, well-built standard mobile page could compete.
This changed how WordPress teams made choices. Instead of asking, “How can this site support AMP?” many started asking, “Why keep AMP at all?”
- Speed tools improved. Better hosting, caching, lazy loading, and image formats helped normal pages load faster.
- Core Web Vitals became central. Publishers focused on LCP, CLS, and INP instead of AMP validation alone.
- Design expectations rose. Readers expected rich layouts, filters, galleries, and smooth shopping features.
- Ads and tracking became harder. AMP often required different setups for analytics, consent, and revenue tracking.
What Happened Inside WordPress Publishing
WordPress did not remove AMP from the web. The official AMP plugin still exists. Other plugins and themes may still support it. But the old habit of adding AMP to every post has faded.
Many publishers now disable AMP after a site audit. Some keep it only for articles. Some run it in a “transitional” mode, where AMP and non-AMP templates try to match. Others remove it fully and redirect AMP URLs back to canonical pages.
The annoying part is cleanup. Expect to waste time on URL checks, Search Console warnings, analytics gaps, and plugin conflicts. A publisher may disable AMP in five minutes, then spend two weeks checking why old AMP links still appear in reports.
Why Reviews Often Break on AMP Pages
Review content is rarely plain text. It usually includes ratings, pros and cons boxes, product images, buttons, price updates, schema, and user comments. AMP can support some of this, but not every plugin does it well.
Common review problems include:
- Missing stars: Rating widgets may not render because their scripts are blocked.
- Broken comparison tables: Tables can overflow or lose interactive filters.
- Affiliate boxes disappearing: Third-party scripts may be stripped from AMP templates.
- Invalid schema: Review markup may differ between AMP and canonical pages.
- Comment issues: Native or third-party comments may need a special AMP setup.
For review publishers, this is not a small problem. If star ratings or affiliate buttons are gone, users may trust the page less. Revenue can drop. A page may still load fast, but it fails at its main job.
[ai-img]star ratings, product review, mobile page[/ai-img]
Did Google Penalize AMP?
No. Google did not penalize AMP as a format. AMP pages can still rank. They can still be indexed. They can still perform well if they are useful and valid.
What changed is the special treatment. AMP lost some of its unique advantage. A strong non-AMP page can now earn the same search placement in many cases. That made publishers more willing to drop AMP when it caused friction.
Search results now depend more on page quality, relevance, performance, structured data, and user value. AMP can help with speed, but speed alone does not make weak content useful.
What Publishers Should Do Now
A WordPress publisher should not remove AMP blindly. The better move is to check data first. Search Console, analytics, ad revenue, and template tests should guide the choice.
- Check AMP traffic. If AMP pages bring little traffic, the case for keeping them is weaker.
- Compare revenue. AMP ad income may be lower or higher. Guessing is risky.
- Test review features. Ratings, schema, buttons, and tables should appear on both page versions.
- Run speed tests. A fast standard mobile page may remove the need for AMP.
- Plan redirects. If AMP is removed, old AMP URLs should resolve cleanly.
For many WordPress sites, the best setup is now simple. Use a fast theme. Reduce plugin bloat. Compress images. Use caching. Keep schema clean. Test mobile pages often. This usually gives better control than maintaining a second AMP version.
When AMP Still Makes Sense
AMP is not useless. Some publishers still get value from it. News sites with simple article templates may keep it. Sites with limited development support may use AMP to enforce cleaner mobile output. Some teams also like the strict rules because they stop editors from adding heavy embeds.
AMP can work well when content is mostly text, images, and basic ads. It is less attractive for review sites that need rich blocks, live prices, calculators, custom forms, or user-generated ratings.
[ai-img]website speed, analytics chart, mobile traffic[/ai-img]
The Practical Answer
AMP reviews changed because the web moved on. AMP is now one option, not the default answer. WordPress publishers have more control through performance plugins, better themes, and cleaner hosting. Google also no longer makes AMP feel required for major mobile visibility.
For review sites, the decision is even sharper. If AMP strips key rating features, hurts affiliate clicks, or creates schema mismatches, it may cost more than it helps. If it still brings measurable traffic and works cleanly, it can stay. The choice should come from data, not old SEO habits.
FAQ
Is AMP dead?
No. AMP still exists and can still be used. It is just no longer required for many Google search features that once made it feel essential.
Should WordPress publishers remove AMP?
Not always. They should review traffic, rankings, revenue, and page quality first. If AMP adds little value or breaks key features, removal may make sense.
Why do review stars disappear on AMP pages?
Many rating plugins use JavaScript that AMP does not allow. The plugin may need AMP support, a compatible template, or server-side schema output.
Does AMP help SEO?
AMP can help with speed, but it is not a ranking shortcut. Helpful content, strong mobile performance, clean structure, and valid schema matter more.
What should replace AMP on a WordPress site?
A fast responsive theme, good hosting, caching, image optimization, reduced scripts, and proper structured data can usually replace the old need for AMP.