How can you check your CMS's AMP compliance without using Search Console?

Why does Google emphasize browser validation for AMP?

Google's statement focuses on a client-side validation method rather than server-side. The AMP Validator built into browsers analyzes HTML code in real time and reports compliance errors as soon as the page is opened.

This approach meets a practical need: detection of issues before publication. WordPress or Drupal plugins dynamically generate AMP code, and template errors often go unnoticed until crawl time. Browser validation bypasses this delay.

What is the difference between browser validation and Search Console validation?

The browser checks the technical compliance of the markup: allowed tags, required attributes, DOM structure. It's purely a syntactical validation, performed by the AMP.js library itself.

Search Console, on the other hand, reports errors after indexing and can highlight issues that the browser doesn't detect: resources blocked by robots.txt, mobile incompatibilities, server-side rendering issues. The two approaches are complementary, not interchangeable.

Do CMS plugins always generate compliant AMP code?

No, and this is where validation becomes crucial. Plugins like AMP for WordPress or AMP for Drupal rely on modifiable templates. Once adjustments are made—adding tracking, custom widgets, CSS modifications—there's a risk of breaking compliance.

WordPress themes often overload AMP templates to retain branding elements. The result: code that passes in preview but fails validation. Browser verification allows you to catch these issues in development before Google indexes them.

• Browser validation: immediate syntactical check of generated AMP markup
• CMS plugins: generate AMP code but do not guarantee compliance in case of customization
• Recommended approach: validate each modified template before going live
• Limitation of the approach: does not detect crawl-related errors or blocked external resources
• Complementarity: combine browser validation (development) and Search Console (production) for complete coverage

Is this statement aligned with observed practices on the ground?

Yes, but it deliberately simplifies a more complex process. In practice, SEOs deploying AMP face errors that bypass browser validation: resources loaded via third-party CDNs, unwhitelisted analytics scripts, conflicts between WordPress plugins.

The browser validation catches markup errors, not performance or rendering issues. I've seen AMP pages that are technically valid but not eligible for Top Stories carousels because the images exceeded accepted ratios. Google doesn't mention this, and it's a blind spot for practitioners who rely solely on this method.

Should we still invest in AMP with the rise of Core Web Vitals?

The question changes depending on the sector. For news sites targeting the Top Stories carousel, AMP remains a competitive advantage—even though Google claims non-AMP pages can appear there. In practice, AMP results still dominate this carousel.

For other sectors, the decision is less clear-cut. Core Web Vitals reward fast pages, AMP or not. Investing in a dual template system (AMP + standard) incurs maintenance costs. [To verify]: Google has never published clear data on the AMP ranking boost outside of news contexts.

What are the pitfalls of browser validation that Google overlooks?

The first pitfall: false positives. A page can validate locally but fail in production if external resources (fonts, images, iframes) violate AMP policies. The browser validator doesn't test CORS headers or SSL certificates of third-party resources.

The second pitfall: post-validation modifications. Some WordPress plugins inject code after AMP template generation—tracking, A/B testing, chatbots. These injections break compliance but occur after the initial validation. The result: we publish a page that we think is compliant, and Google rejects it upon crawl.

How can you establish an efficient AMP validation routine?

First step: install the AMP Validator extension on Chrome or Firefox. It shows an icon that turns green when the page is compliant and red otherwise. Systematically test each modified template, especially after a plugin or theme update.

Second step: automate validation in continuous integration. Tools like amphtml-validator (npm package) allow for batch URL validation in your CI/CD pipeline. This prevents broken code from being pushed to production. Set up a job that fails if validation fails on your key pages.

What CMS configuration errors most often block AMP compliance?

WordPress themes often overload AMP templates to inject non-whitelisted elements: custom social widgets, JavaScript sharing buttons, in-house analytics trackers. The result: code that appears visually valid but fails validation.

Another source of errors: WordPress shortcodes. Many content builders (Elementor, Divi) generate shortcodes that produce non-AMP HTML. If a writer inserts them into an article, the page breaks. Disable incompatible shortcodes in AMP templates or replace them with AMP-friendly equivalents.

What should you do if browser validation succeeds but Search Console reports errors?

This happens more often than you'd think. Typical causes include: resources blocked by robots.txt (fonts, external CSS), images hosted on domains without CORS, or server response times that are too long. Search Console sees what Googlebot sees; the local browser does not test these dependencies.

Use the URL inspection tool in Search Console to compare Googlebot's rendering with local rendering. If a critical resource is blocked, move it to your domain or add the necessary CORS headers. Also, check server logs for tracking 403 or 500 errors on AMP assets.

• Install the AMP Validator extension and test each template after modification
• Integrate amphtml-validator into your CI/CD pipeline for batch validation
• Disable AMP-incompatible shortcodes and WordPress plugins
• Check CORS headers on all external resources loaded by AMP pages
• Compare Googlebot's rendering with local rendering using the Search Console inspection tool
• Monitor Search Console logs after each deployment to catch post-indexing errors