Source evidence

Sitemap Unknown Error

Yoast SEO – Advanced SEO with real-time guidance and built-in AI · support · 2026-06-04T16:29:00+00:00

Yoast SEO – Advanced SEO with real-time guidance and built-in AI plugin evidence original source source API

mixedsentiment

mediumseverity

0.84relevance

2replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 34 rows with source links

14.7% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

silveraden resolved

I excluded post tags from showing on search engines and then I get this error. Please help. I already removed the plugin and reinstalled it but the same error happen. Thank you This topic was modified 2 hours, 31 minutes ago by silveraden . The page I need help with: [ log in to see the link] Hello @silveraden , Thanks for reaching out about your sitemap. https://www.sellmobilehome.com/sitemap_index.xml works but https://sellmobilehome.com/sitemap_index.xml does not work. I confirmed the error in Mozilla Firefox, though the sitemap is blank in Google Chrome. Also, the stylesheet and sitemap source (including the sub-sitemaps) work as expected. The non-www sitemap URL ( https://sellmobilehome.com/sitemap_index.xml ) returns a 200 OK response instead of redirecting to the preferred www version. Since Yoast SEO generates the sitemap based on the site’s configured URLs, we would expect the non-www URL to redirect to the www URL if that is your preferred domain format. This redirect is typically handled at the server, hosting, or CDN level rather than by Yoast SEO. Could you please confirm the values of WordPress Address (URL) and Site Address (URL) under Settings → General ? Hi Maybellyne, Sorry, it was a mistake on my part. I didn’t noticed that the url has no www. Thanks again, there is no issue, just typing the url incorrectly.

Commercial Context

Opportunity

search visibility operations

SEO search visibility assurance for protecting search visibility and structured data quality

Buyer: site owners, SEO consultants, and agencies

Wedge: monitor SEO drift, schema/indexing failures, and client-readable search-impact fixes

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Sitemap Unknown Error: users show bugs, missing feature, support pain that may indicate a product gap.

Evidence quote: Sitemap Unknown Error I excluded post tags from showing on search engines and then I get this error.

Affected feature: form

bugs missing feature support setup

Plugin

API

Yoast SEO – Advanced SEO with real-time guidance and built-in AI

10.0M active installs · 959.2M downloads · rating 96.0

content analysis readability schema seo xml sitemap

Comments

2 shown

Maybellyne 2026-06-04T17:36:00+00:00

Hello @silveraden , Thanks for reaching out about your sitemap. https://www.sellmobilehome.com/sitemap_index.xml works but https://sellmobilehome.com/sitemap_index.xml does not work. I confirmed the error in Mozilla Firefox, though the sitemap is blank in Google Chrome. Also, the stylesheet and sitemap source (including the sub-sitemaps) work as expected. The non-www sitemap URL ( https://sellmobilehome.com/sitemap_index.xml ) returns a 200 OK response instead of redirecting to the preferred www version. Since Yoast SEO generates the sitemap based on the site’s configured URLs, we would expect the non-www URL to redirect to the www URL if that is your preferred domain format. This redirect is typically handled at the server, hosting, or CDN level rather than by Yoast SEO. Could you please confirm the values of WordPress Address (URL) and Site Address (URL) under Settings → General ?

silveraden 2026-06-04T17:40:00+00:00

Hi Maybellyne, Sorry, it was a mistake on my part. I didn’t noticed that the url has no www. Thanks again, there is no issue, just typing the url incorrectly.