Got the idea from #1131376: Exclude from Drupal search results I believe Search Index Options is the ideal module to implement specific node exclusions from search indexing.

CommentFileSizeAuthor
#3 exclude-nodes-3043456-3.patch7.47 KBnickonom

Comments

nickonom created an issue. See original summary.

nickonom’s picture

Issue summary: View changes
nickonom’s picture

StatusFileSize
new7.47 KB

Here is the initial patch.

  • AltaGrade committed de4a7e7 on 7.x-2.x authored by nickonom
    Issue #3043456 by nickonom: Exclude specific nodes from search index
    
altagrade’s picture

Status: Active » Fixed
nickonom’s picture

Title: Exclude specific nodes from search index » Prevent search indexing on node level
Status: Fixed » Active

The last release works well for excluding nodes of content types, which're set to be included in search index, though with the following issues and room for improvement detected.

1) If none of content types selected, then all nodes were supposed to be indexed, which means any node should be possible to exclude individually. However, in this scenario the Search index option disappears from vertical tabs completely, so despite expected behavior, it's not possible to make exclusions on node level.

2) If some content types are opted in for indexing, then the last release correctly allows users to effectively exclude nodes of the opted in content types. However, what if users want to enforce indexing excluded content types on node level? In other words, let's say content type `article` is completely excluded from indexing, however users want specific nodes of `article` type to be searchable. I believe the re-work of the last release should cover also this scenario.

3) Besides, somehow the `search_index.js` file didn't get packed, so it's giving `page not found` notice.

Sorry for too frequent releases, but the mussing file issue needs to be fixed anyway, so I will be rolling out another release addressing two other ideas above later today.

nickonom’s picture

Status: Active » Fixed

Fixed with the release of 7.x-3.1.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.