URL is .net... Backend is .com... XML map is .com... Help!

[ageorgi0621]

This post is deleted!

[Hurf]

Separating the front end of a Wordpress site from the back end isn't unheard of. Sometimes, people may do it for security reasons, or it could be a WP multi-site installation.  So, in isolation, the separation of both halves doesn't have to be an issue, but the sitemaps need to be handled correctly. Firstly, read through this article to get a better understanding of WP Mulitsite and how to identify it: https://premium.wpmudev.org/blog/ultimate-guide-multisite/. When we can confirm that, we can better understand what's needed to tidy this up. You'll also need to know for ongoing maintenance of the site as Multisite is a slightly different beast to Single site.

I suspect, however, that this could simply be a case of someone eciding change the domain within WordPress and only changing the site URL, which would explain the foul up with the sitemap and redirects.

Has the site always been structured this way?

[ageorgi0621]

THank you so much for your response.  My friend has always owned the .net.  I can see the in the dashboard that it is a multisite so I am assuming this is the issue, but can you explain what you mean by "someone deciding to change the domain with Wordpress and only changing the site URL?"

[Hurf]

If it's multisite,"someone deciding to change the domain with Wordpress and only changing the site URL" isn't something you'd concern yourself with - I only mentioned it as there was a chance they'd split a regular Wordpress site (presumably) in error. If you're using multisite this isn't a concern. Using Multisite for a single site (as the name suggests) isn't common, so there was a smaller chance of it being multisite; I just wanted to cover all possibilities.