Custom XML sitemap problems

so basically from webflow answer, i can understand that we have 2 options and both are not helping:

  • The first is to auto generate sitemap and include no index and robots.txt pages (totally bad for SEO).
    OR
  • secondly, we can create a custom sitemap and upload it to the webflow root but every time we will update the site we will need to send it manually again to webflow root and then to google search console again?
    seriously?

webflow official answer:
"It is not possible to exclude a page from the automatically generated sitemap. CMS Collection pages with no content in them will not be included in sitemaps by default.

If you prefer to write your own custom sitemap.xml, you can and add that to your Webflow project.

  1. Disable the auto-generated sitemap by switching the Auto-generate sitemap toggle to “No”
  2. Paste your custom sitemap.xml in the text area
  3. Save and publish"

I believe that’s a non-issue. Google uses sitemap simply as a guide to navigate your site more efficiently, it is not a directive on what to index. The meta noindex is what determines index state, not the sitemap.

If you did manual ( but, why ), yes you’d have to updated it each time you changed your site page structure.

No you would not need to resubmit it. Once Google has it, it rechecks it regularly.

From what I recall, GSE will continue to show a warning or error for urls in sitemap that are not indexable, which is annoying because as GSE admins we’ll always have to see them and won’t get a clean alert for actual issues.

Hi Jonas, since this original post, WF has made some changes-

  • You can now configure any static page to be suppressed from search engine indexing. It adds a meta noindex tag, and removes it from the sitemap.
  • Paginated collection lists now show the paginated URL as the canonical for each page, so they’re individually indexable.

The scenario described by OP is no longer an issue with the possible exception of special cases where someone wants to exclude all pages in a specific collection, or an individual CMS page. I use a reverse proxy for those situations.