Milind More

Hello @3xploiton3

As the message suggested the amp_has_paired_endpoint is being called incorrectly meaning it has been used before the the amp plugin has not been fully loaded, if you have third-party plugin, theme or small code snippet that you is using amp_has_paired_endpoint hook please make sure to use it after the wp hook it will make sure that AMP plugin is fully loaded.

eg:

add_action( 'wp', function() {
  // useamp_has_paired_endpoint here.
});

@passionsadnplaces

As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.

Hello @passionsadnplaces

Thank you for reaching out to us, The message is sourcing from AMP plugin, As AMP pages are being served on mobile it’s likely that it only appears on mobile

In a normal (non-AMP) site, when a user clicks “Submit,” the page usually refreshes. However, AMP requires forms to submit via “AJAX” (in the background without a refresh).

The AMP plugin tries to “upgrade” your existing contact form to work this way. When the form is submitted, the server sends back a “200 OK” signal, but it doesn’t include a specific “Success Message” in a format that AMP understands. Because the plugin is “unsure” if the data actually reached its destination correctly, it shows that generic, cautious green box.

How to fix it

AMP handles redirects much better than “on-page” success messages.

In your form settings (Contact Form 7, WPForms, etc.), set the form to Redirect to a new URL (e.g., yoursite.com/thank-you) upon successful submission.

If you are a developer or have one, you need to modify the code that handles the form submission to send a specific JSON response. Instead of a generic success, the server needs to return a JSON object that includes a message.

eg: As we are unsure which form plugin or form service you are using, I’m giving a generic response example

if ( wp_is_json_request() ) {
    $message = __( 'Thank you! Your message has been sent.', 'text-domain' );
    wp_send_json( compact( 'message' ), 200 );
}

We hope this helps!

Hello @robdasailorgmailcom

As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.

@ozkutlusan As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.

Hello @educationnewshub

Thanks for the update. As I checked your website on AMP test, it no longer shows any errors, indicating that your AMP pages are now valid. The warning from the search console will clear automatically within 2-3 weeks once Google bots re-crawl your website for updates.

We hope this helps!

Hello @educationnewshub

Thank you so much for sending over your site health information! We really appreciate you taking the time to gather that for us; it helps immensely with troubleshooting.

We’ve been looking into the issue, and root cause appears to be the presence of an injected script, specifically the one starting with <script data-cfasync="false" nonce="..."> which seems to be related to a service called Zaraz.

While your site health report didn’t pinpoint a specific plugin adding this script, the script itself looks like it’s being introduced by an external service, often Cloudflare.

Here is what we recommend you investigate:

🔎 Actionable Steps to Investigate and Resolve
Check Cloudflare Settings:

– Log in to your Cloudflare dashboard for this domain.

– Navigate to the Speed section.

– Look for an option called Zaraz (formerly known as ‘Cloudflare Apps’ or ‘Cloudflare Insights’) or anything related to Analytics/Performance tools.

If you find it, please turn it off or disable the tool that is injecting the Zaraz script.

Theme or Custom Code:

– If you are not using Cloudflare, please check if your theme or any custom code snippets (like those added via a child theme or an Insert Headers/Footers plugin) might be inserting this script.

The script that has been added to site:

<script data-cfasync="false" nonce="ad809f7c-0569-4d56-aa26-56c8df720de8">...</script>

…is a very strong indicator of a third-party performance/analytics service, with Cloudflare being the most common source for the cdn-cgi/zaraz path mentioned inside the code.

Once you have identified and disabled the setting responsible for injecting this script, please clear all your caches (including any caching plugins and Cloudflare cache), and check if the issue is resolved.

Thanks again for your patience as we continue to work on this together!

Let us know what you find in your Cloudflare settings.

• This reply was modified 7 months ago by Milind More.