arnaudbroes

Hey @nims,

I just had another look at this, but we’re unable to reproduce this issue from our end. Would you mind reaching out to us via our Basic Question form. I’d be happy to look into this for you personally, so you can mention my name.

Hey @hamodi1983,

It is possible that our scanner is being blocked by a firewall or bot-blocking mechanism. Do you mind posting some of those URLs here?

If these are internal URLs on your own website, please ask your hosting partner to whitelist these two IP addresses for our Broken Link Checker service –

• 45.55.120.151
• 174.138.52.74

Hey @nexgraphics, @namrur,

If you’re still experiencing any issues, please reach out to our support team directly via our?free Basic Question form here?so they can take a look for you.

Hey @yeremyan,

Those are old hooks that we haven’t had for years now. We updated all of our hooks back in 2020 when we did a full rewrite of the plugin. We had to do so because the data format changed for a number of them.

You can find docs for our new hooks below:

• https://aioseo.com/docs/aioseo_title/
• https://aioseo.com/docs/aioseo_description/
• https://aioseo.com/docs/aioseo_keywords/

Hi?@justho,

Thank you for feedback.

I totally understand your frustration about having to enter a credit card. The reason why we request one is so that we can automatically upgrade you to a higher plan in case you reach your links quota, in order to prevent the service from being disrupted and working non-optimally.

In case users are auto-upgraded and did not want to upgrade, we happily refund them, no questions asked. Any credit card info that you submit when you sign up is stored in the most secure way by our payment partner, Stripe, not us, so we never have access to your payment info directly.

In case you have any other feedback for us or any questions, please let me know!

Hey @damiantk,

We had an unsuccessful crack at this so it’s still on our roadmap. From a technical standpoint this is quite complicated because the script is loaded by a service worker and those seem to load the script every single time, potentially even bypassing the cache. In any case, we’re still looking into it.

We’re looking to release on Feb 27 which is approximately two weeks from now.

Hey @almoore01,

Could you open the browser’s dev console (F12), reload the page and post a screenshot of the error you see in there? That will help our support team narrow down what’s causing this.

Hey @snowbedding,

I’ve added a new filter hook to our next release, version 4.8.0, which you can use to disable sitemap localization. If you add this code snippet in your theme’s functions.php file or through a plugin like WPCode, then it should stop including them.

add_filter( 'aioseo_sitemap_localization_disable', '__return_true' );

Hey @realdh1,

Can you try saving in a different browser? I’ve never seen this error before, but from what I’m reading, it could be caused by a conflict with a Chrome extension.

If it works fine in a different browser, you could try disabling some of your Chrome extensions to narrow down the conflict to a particular one.

Let us know what you find!

Hey @spale,

Thank you for reaching out.

For some reason your canonical URL is missing a slash near the end of the path. The easiest way for us to troubleshoot this would be to have a developer take a closer look at this. Do you mind reaching out to us via our free Basic Question form here?

Hey @bobjgarrett,

What is the name of the option record where you see these JS filenames that you mentioned?

@dmarin in addition it may be worthwhile to try deactivating all of your other plugins/theme temporarily to see if you still experience the issue with just ARVE and AIOSEO activated. I recommend doing this on a staging site if you have one available.

If you do not experience the issue with just those two activated, then you can reactivate your other plugins one-by-one to figure out which one is causing the conflict.

Hey @nico23,

I believe your personal thread was previously prematurely closed by myself, which I apologized for.

While it indeed seems that EDD has a policy to resolve tickets as soon as they’ve replied, this is not the case at AIOSEO. You can verify this by looking at our resolved threads. We close threads when they are resolved or when the user did not reply in a timely manner. If they reply after a period of inactivity, we also typically reopen the thread.

Awesome Motive does indeed have multiple plugins under its umbrella but all of our teams operate independently from one another and we do not necessarily share the same policies. Whilst everyone is entitled to their own opinion on Awesome Motive or any of its products, please refrain from asking people to leave a negative review based on assumptions. I’d rather that we simply work together to help @dmarin resolve the issue he is experiencing.

Hey @stoianalex,

This error occurs in rare cases when a database migration failed to run on your website. I recommend reaching out to our support team directly here via our free Basic Question form so they can help remedy this for you.