Wrong URL in schema

@harrisondg We’re sorry to hear you are experiencing this issue on your site.

Can you please let us know what you are using for the WordPress Address and Site URL for the site? Also, are those values configured manually anywhere else in the wp-config.php of the site?

Also are you able to provide an example URL of one of the pages where this is occurring so that we can review the schema output?

@devnihil The site in question is https://refugeinvestments.com/. It is set in the General settings as such in both Site Address and WordPress Address. The URL is not manually set in the wp-config.php or anywhere else that I’m aware of.

Take a look at the source on the homepage (view-source:https://refugeinvestments.com/) you’ll see in the schema output url”:”https://secureservercdn.net/198.71.233.104/993.9dd.myftpupload.com/

• This reply was modified 3 years, 7 months ago by harrisondg.
• This reply was modified 3 years, 7 months ago by harrisondg.

Thanks for sharing the relevant information here with us. The issue you are currently experiencing typically occurs when migrating the site from a development environment to the production environment and can be fixed using the Yoast Test Helper plugin.

However, we see that you have already used the Yoast Test Helper plugin to reset the Indexables tables and migrations but the issue persists for you. In this case, we recommend you please reset the Indexables and migrations again by following steps given below to see whether this resolves the issue for you:

• Install and activate Yoast Test Helper plugin;
• Go to Tools → Yoast Test → Yoast SEO → Reset indexables tables & migrations options to reset it;
• Run SEO data optimization from the SEO → Tools page.

If the issue persists, we recommend you please perform a conflict check. The fastest way to do this is to?deactivate all non-Yoast plugins and switch to a standard theme?like?Twenty Nineteen.?

Test this on your development or staging site, if you have one. If not, we recommend using the?Health Check & Troubleshooting?plugin. This plugin allows you to run a conflict check?without affecting normal visitors to your site.

As we can imagine that you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process:?How to check for plugin conflicts.

If you do not feel comfortable to do this yourself or if this does not solve your issue, our Yoast SEO Premium plugin comes with one year of (technical) support.

@mazedulislamkhan Thanks for the direction, however I’ve still got an issue.

I reset the index tables and migrations and ran the SEO data optimization once again, still seeing the temp domain URL in schema.

I performed two conflict checks:

1. On my local machine, I hosted a copy of the site and with all plugins active, I do NOT see the issue, the domain is correct.

2. Using Health Check & Troubleshooting on the live site, I am still seeing the incorrect domain url in schema with all plugins disabled (besides Yoast).

This site is hosted on Godaddy and I looked into the wp-config.php. It does not have any reference to the temp URL in the file, however I noticed a reference to another config file gd-config.php, looking in that file I see a line related to the temp domain. Would Yoast reference this additional config file?

Hello,

Thanks for sharing the feedback.

As far as we know, the gd-config.php file appears related to GoDaddy managed WordPress service. The file defines some parameters such as staging site, caching setup etc. Therefore, we recommend reaching out to GoDaddy regarding clearing the relevant cache.

@maybellyne Understood. However, wouldn’t it be under Yoast’s control as to which URL it displays in the schema produced by your plugin?

@harrisondg Can you please let us know what the exact reference to gd-config.php in the wp-config.php file is?

Sure, this is what I’m seeing

require_once( dirname( __FILE__ ) . '/gd-config.php' );
define( 'FS_METHOD', 'direct');
define('FS_CHMOD_DIR', (0705 & ~ umask()));
define('FS_CHMOD_FILE', (0604 & ~ umask()));

And within the gd-config.php:

define( 'GD_TEMP_DOMAIN', '993.9dd.myftpupload.com' );
define( 'GD_VIP', '198.71.233.104' );

• This reply was modified 3 years, 6 months ago by harrisondg.

Thanks for your confirmation. We’re not aware of such an issue with GoDaddy-specific WordPress websites and the Yoast SEO plugin. The code you have shared with us only shows the value of the constant that doesn’t confirm anything whether it’s interfering with the WordPress URLs structure. We recommend you please reach out to GoDaddy to see whether they can shed some light on this.

However, if you’d like us to investigate the issue further for you, we’ll need to take a look at your setup that we are unable to do it here as this is a public forum.

So, if you have an active Yoast SEO Premium subscription or if you can consider buying one, we can investigate the issue further directly on your setup privately through email.

However, if you don’t wish to get the Yoast SEO Premium subscription, that’s completely fine. In this case, you’ll need to troubleshoot the issue further on your setup as we are literally out of any clue at this moment without taking a look at the setup. So, someone from the community might step forward as well who has experienced or familiar with the issue.

Thanks for your understanding!

Understood, I can reach out to the host. But can you tell me where the URL in the schema data is sourced? It’s apparent it’s not the WordPress Address or Site URL for the site.

Hi,

As far as we are aware, it should just be the Site Address URL under WP admin dashboard > Settings > General. We’d need to take a further look at your setup, but we are unable to do so here. As mentioned, you might want to consider Yoast SEO Premium so we can take a closer look at this issue.

Otherwise, we’d like to refer you to our schema documentation on our developer blog — https://developer.yoast.com/features/schema/overview

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.