Back to Community
Home / Community / Plugin → Amp

Troubleshooting Common AMP Plugin Redirect and 404 Errors

33 threads Sep 10, 2025 Plugin → Amp

Content

Users of the official AMP for WordPress plugin often encounter issues where their AMP pages either fail to load, redirect incorrectly, or result in 404 errors. These problems can be frustrating, as they prevent your AMP content from being properly indexed by search engines and create a poor experience for visitors. Based on common community reports, this guide will help you diagnose and resolve the most frequent causes of these issues.

Why Do These Redirect and 404 Errors Happen?

These problems typically stem from conflicts between the AMP plugin's URL rewriting rules and other elements of your WordPress setup. Common culprits include:

  • Permalink Conflicts: Custom post types with unique rewrite rules or slugs that conflict with the /amp/ endpoint.
  • Plugin or Theme Interference: Caching plugins, SEO plugins, or other URL-altering plugins (like Pretty Links) can inadvertently modify or block AMP URLs.
  • Validation Errors: Kept validation errors in the AMP plugin can cause it to disable AMP on certain pages, leading to redirects.
  • Specific URL Paths: Threads indicate that URLs containing certain paths, like /video/, can unexpectedly halt AMP conversion.
  • Multisite Configuration: AMP plugin settings in a WordPress multisite network can sometimes lead to widespread 5XX errors.

How to Troubleshoot and Resolve These Issues

1. Check for Validation Errors and Reset Data

A primary step is to review the AMP Validator tool within your WordPress dashboard. If you have "kept" validation errors for certain templates or posts, the plugin may be forced to redirect away from the AMP version. Navigate to AMP > Validation Errors and review any kept errors. Consider using the "Delete plugin data" option upon reinstallation to clear all existing validation state, which can often resolve redirection problems, especially for custom post types.

2. Investigate Plugin and Theme Conflicts

Conflicts are a leading cause of AMP issues. To test for this:

  1. Temporarily switch to a default WordPress theme (like Twenty Twenty-Four).
  2. Deactivate all other plugins except AMP.
  3. Check if the AMP pages (/?amp=1 or /amp/) load correctly.
  4. If they do, reactivate your plugins and theme one by one, testing after each, to identify the culprit.

Pay particular attention to plugins that affect URLs, such as Pretty Links, or those that manage redirects and caching. Some plugins may automatically append /amp to their own generated links, causing 404 errors. For caching plugins like W3 Total Cache, ensure any mobile device detection groups are configured to work with your chosen AMP mode.

3. Verify Your Paired URL Structure Settings

The AMP plugin offers different URL structures for its paired modes (Transitional and Reader). You can choose between a query parameter (?amp=1) or an endpoint (/amp/). If one structure is not working, try switching to the other. This setting is found under AMP > Settings > Paired URL Structure. Note that the plugin may display an admin notice on the Permalinks settings page reminding you of this configuration; this is normal and can be ignored.

4. Review Custom Code and Rewrite Rules

Custom functions that modify permalinks or post type slugs can break the expected AMP URL. If you have code that removes a custom post type's name from its slug (e.g., changing /news/post-name to /post-name), the AMP plugin may still be trying to generate URLs with the original structure, leading to 404s. Review any custom rewrite rules for compatibility with AMP endpoints. Similarly, avoid using a base like /video/ for custom routes, as this is known to interfere with AMP processing.

5. Confirm AMP is Enabled for All Desired Content Types

Ensure that AMP is enabled for the specific content types you are having issues with. Go to AMP > Settings > Supported Templates and verify that your custom post types (e.g., News Posts, products) are checked. If you are using Standard mode, also confirm that your active theme is fully AMP-compatible to avoid unexpected behavior.

When to Seek Further Help

If you have tried these steps and the issue persists, the problem may be more complex. When seeking help in community forums, be prepared to provide:

  • The UUID found in the AMP plugin's support section.
  • Your current AMP mode (Standard, Transitional, Reader).
  • Examples of URLs that are working and not working.
  • A list of your active plugins and your theme name.

By methodically working through these common conflict points, you can successfully resolve most AMP redirect and 404 errors, ensuring your mobile pages are served correctly to users and search engines.

Related Support Threads Support