Duplicate Root URL

Hello!

This issue may be related to a known bug, where we don’t correctly discover the domain you used as we sanitize the image URL. This was discovered during a bug-hunt, and it’s fixed for the upcoming update.

However, this was marked as an edge case, especially since this shouldn’t ever happen when using the uploader (which also prevents you from further adjusting the URL). I’m afraid you’re using another image-processing or URL-processing plugin that manipulates fully-qualified URLs, like making them scheme-relative instead?

As a workaround, I’d like to suggest clearing the image entered via the image-processor and filling in the image-URL manually instead. To be certain, always use the complete, fully-qualified, absolute URL:

Don't: //example.com/path/to/image.jpg
Do:    https://example.com/path/to/image.jpg

I hope this resolves your issue, if only as an intermediate. If you’re still finding issues, do let me know! Cheers ??

Hi Sybre,

Thanks for your reply. Unfortunately, I tried to manually enter the fully-qualified image URL as you suggested, but the output is still the same, with the duplicate domain. I also tried inputting the relative path to the image, but that did not work either, as the field required a URL format.

I also double-checked any other plugins in use and cannot see any image-processing or URL-processing plugins in use.

Do you know when the next update will be rolled out with a fix? I’m afraid we may have to look elsewhere for an SEO plugin, but I really like the user interface on yours and would like to keep it.

Thank you very much!

Hello again ??

If that even didn’t work, then I don’t believe the next update will save you in this. That said, the update was planned for release last Tuesday, but we postponed it by a week due to time constraints.

Now, there must be something going on that I’m not aware of. A closer look would help tremendously. Would you mind sharing the URL to the affected page(s)? You may send those links confidentially, via our contact form. Thanks!

Thank you! I just sent the link via the contact form. I appreciate your assistance.

Cheers!

Hello again!

I received your email and inspected the source of your website.

I found that there’s a plugin or theme active, that makes all local absolute URLs relative.

From: https://example.com/path/to/file.css
To:  /path/to/file.css

This “URL-cleaning” happens deep in the WordPress escaping-API. Absolute URLs are required for Google and Facebook, and that’s why we try to enforce it when outputting the URL. This is where the edge-case bug I talked about can happen.

Even though The SEO Framework v4.0 should be able to mitigate and cope with this issue, I don’t believe this should be happening in the first place; other unforeseen issues may prevail down the line.

See if you can find the plugin or option active that is responsible for this, and deactivate it. There’s no need in WordPress to make URLs relative; that’s something only required for archaic static HTML-builders, like Adobe Dreamweaver and Microsoft Frontpage.

If you need help with this, please go to /wp-admin/site-health.php?tab=debug, and copy the site info to clipboard. This may yield more information that you wish to share. So, alternatively, please send a contextual list of active plugins; that’ll help me find the issue, too ?? Cheers!

Thanks Sybre,

Upon further inspection of our plugins, it would appear that the developer who created the site added some specialty plugins that are required by the site. They must be the culprit, as the only “mainstream” plugins we have are WPForms, WordFence and Classic Editor. I doubt those are responsible for the absolute URLs. Unfortunately, we are unable to go without the proprietary plugins, so we are going to have to find an alternate option for SEO until I can get in touch with the original developer of the site.

Thank you very much for the assistance.

Hi again, @clcreative!

A quick heads-up: The v4.0 update of TSF has just been released, which may resolve the issue of reparsing the URLs. In that, be sure to reprocess the URL in your settings.

If even that doesn’t resolve the issue you’re facing, then I’m afraid the conflicting code needs to be purged. And, if you require assistance with that, we’re here for you!

Cheers ??