thetechnologyvault

Thanks Corrina.

Have you ever had a setup like this where the WordPress instances were hosted on a separate host from BigCommerce?

From what I understand, you can set txt records to make sub-domains to a different web host from the top-level domain.

Do you think there would be any preference to that kind of setup versus keeping everything on BigCommerce?

I know that BigCommerce tends to get very expensive when hosting lots of data on its servers, so if I’m just publishing a lot of pictures and articles rather than making use of the store features of BigCommerce, I’m leaning towards hosting the WordPress part of the website on a separate host.

I’m getting this same error on my website: https://sweatshirtstation.com

The WordPress SEO by Yoast plugin creates an sitemap index page (sitemap_index.xml), which references other sitemaps that are automatically created unless the plugin is configured not to include them. WooCommerce product categories are included in the configuration options.

I have configured the Yoast sitemap tool configured to create the following sitemaps, but some of them (as noted below) return 404 errors.

https://sweatshirtstation.com/page-sitemap.xml – working
https://sweatshirtstation.com/product-sitemap.xml – working
https://sweatshirtstation.com/category-sitemap.xml – 404 Error
https://sweatshirtstation.com/post_tag-sitemap.xml – 404 Error
https://sweatshirtstation.com/product_cat-sitemap.xml – working
https://sweatshirtstation.com/product_tag-sitemap.xml – 404 Error

It seems somewhat random that some of these sitemaps work just fine, while others don’t. I can’t see an obvious differentiator in how they’re created.

If anyone could give a hint as to why there would be sitemap errors with the XML files noted above, I’d appreciate it. I’ll keep doing some testing to see if I can come up with a solution also.

Many of the crawl errors reported by Google are incorrect. If the URL really does work and isn’t returning a 404 or other error, I’d recommend marking the error as fixed and check back in a week to see if Google has marked the page as an error.

To see if Google really can’t crawl the error, I’d try using site:[url] to see if Google really does have it in its database.