This would a very important feature for SEO to prevent Google constantly us there is errors because we've to put a no follow/no index on the pages.

It would also be a good idea to have far better XML sitemap created that includes times and dates of when a page was last updated. As far as I know, at the moment, this would have to be done manually via a bespoke XML uploaded to Webflow.

I don't see why this is such a hard thing to do. There are some pages that just shouldn't be visible as part of the sitemap. For indexing and access reasons such as thank you pages. Please make this feature work as expected.

+1 on this. For websites with hundreds of pages, manually updating the sitemap is not a sustainable solution. Please let us know what the expected timing is on this feature (or a Yoast-like plugin or integration to a 3rd party tool that will accomplish the same goal)

Please consider adding this SEO feature - it's crucial for bigger corporate sites that can't have all their pages listed on Google..

Isn't it just adding one on/off button in the page settings?

Not being able to remove pages from the auto generated sitemap is extremely necessary. Please add this functionality Webflow!

Make this happen, guys! This is a very basic feature that should already be implemented.

Since this is a critial SEO feature, are there any plugins to assist with this? Like the following

https://rankmath.com/kb/how-to-noindex-urls/

I often would love to omit marketing pages or similar from client sites

Such a basic CMS feature, I upload articles to my site daily, so it's no practical to create and upload a new sitemap every time I make an update! Just a simple toggle to remove the hidden page from the sitemap. How hard can it be!!

Totally agree, but there are multiple places to impact;

1. META tag in the page HEAD;
   <meta name="robots" content="noindex">

2. HTTP response header
   X-Robots-Tag: noindex

3. sitemap.xml exclusion for the page

4. Possibly, add noindex attributes to Links to the page

Interestingly, the page probably should NOT be excluded from robots.txt . When a page is excluded, Google won't scan it again, which means it will never be removed from the search index either.

The current 'Exclude this page from site search results' checkbox option should be reworded: 'Exclude this page from internal search results (Remove content from Googles index)' or similar.

Need this feature for WebFlow's ideal use case - which is marketing sites.

Common people, please, it's such a small effort for a huge impact.

Seems like a relatively easy implementation. Do you plan on working on this issue soon?

Any news???

I am happily switching from Wordpress to Webflow and I am very pleased. However, when it comes to things like this, I am shocked to not have an option for this. So many options, but nothing to hide a file from search engines and XML sitemaps?

Not having this feature means this having to deal with this set of workarounds:

1. You must enter in manual meta description tag on each page

2. You must then override the auto-generated Sitemap XML if you wish to exclude it

3. Once you override the Sitemap XML and make a custom one, you now lose the benefit of having CMS content (blog articles) published automatically

4. Which means every time you publish a new article you need to go in and modify the sitemap manually

Webflow team - please help out. This is not too difficult of an ask.

Still would really love this :) Super frustrating to have to manually update the sitemap every time we post a blog or create a new page.

The description on this wishlist item does not fully describe what the real issue is around how these types of pages show up in sitemap.xml files. This article (https://discourse.webflow.com/t/auto-generate-sitemap-publish-and-unpublish/38054/6) was used as a reference to create this request here. Just adding this in for reference.

Please add this. It would be greatly appreciated.

Extremely important from a SEO Perspective. Please do it fast.

webflow implements some amazing stuff. but it blows my mind that this feature from 2017 hasnt been implemented.