no_search is a suboptimally chosen field to exclude pages from sitemap

[DenisMir]

It is a big problem that dd_googlesitemap uses the no_search field for its decision on excluding pages from the sitemap.
no_search should be used for excluding pages from the page search (like the index search or solr search etc.).
At the moment it is not possible to exclude pages from the internal search and include it in the sitemap and vice versa.
It would be awesome if dd_googlesitemap could use a configurable field or at least a different field from no_search.

[dmitryd]

If you exclude it from page search, to me it means you want to exclude it from search in general, which means it should not be in the sitemap because sitemap show a list of searchable pages.

[hhchrizzo]

I have problems with this too.
In my installation there are some pages for detail view, e.g. tx_news detailpage. The page is set to 'nav_hide=1' and 'no_search=0'. Im using indexed_search and need to index my singlenews.

The problem now is that the singlepage itself is listed in the xml sitemap. If the crawler touches the page without any given news id it will end up in 404 or an exeption.

My current workaround is to exclude pages with type nav_hide=1 in protected function shouldIncludePageInSitemap

[djangones]

Basically I agree with Dmitry, but I came across the same problem Chris mentioned, which should be quite a standard situation in Typo3.
So it would definitely be nice to have an additional checkbox to explicitly exclude a page from the sitemap in addition to no_search.