When adding a WordPress website to CheckView, you may notice that the registered URL includes an unexpected subdirectory (e.g., /dev, /wp, or /blog) even though you entered the root domain. This article explains why this happens and how to fix it.
When you add a website to CheckView, we query your WordPress installation’s REST API to retrieve its canonical URL. This is the URL that WordPress itself reports as its own address. If WordPress is installed in a subdirectory (such as /dev, /wp, or /blog), it will report that subdirectory as its site URL – even if your domain’s root points to the same installation.
You can confirm this yourself by visiting the following URL in your browser (replace yourdomain.com with your actual domain):
https://yourdomain.com/?rest_route=/
This returns a JSON response from your WordPress REST API. Look for the "url" field near the beginning of the response. If it shows a subdirectory path (e.g., https://yourdomain.com/dev), that confirms your WordPress Site URL is configured to include that subdirectory.
To resolve this, you’ll need to update your WordPress site URL settings:
https://yourdomain.com) without the subdirectory.Important: The WordPress Address (URL) is where your WordPress files live on the server. The Site Address (URL) is the public-facing URL visitors use to reach your site. These can be different – for example, WordPress files might be in /dev but the site is served from the root domain.
Once you’ve updated your Site Address in WordPress:
https://yourdomain.com/?rest_route=/ again and confirming the "url" field now shows your root domain.