Configure Search Results in Modern page (Modern Search Center)

%3CLINGO-SUB%20id%3D%22lingo-sub-110020%22%20slang%3D%22en-US%22%3EConfigure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-110020%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20been%20able%20to%20modify%20the%20search%20results%20page%20of%20Modern%20Pages%20which%20seems%20to%20have%20missing%20that%20at%20present.%20There%20is%20no%20way%20to%20customize%20the%20results%20view%2C%20switch%20to%20classic%20view%2C%20use%20custom%20result%20sources%20or%20redirect%20to%20enterprise%20search%20center.%20It%20always%20defaults%20to%20%22%2Fsearch%2Fsitefiles%22%20location%20instead%20of%20only%20%22%2Fsearch%22.%20Is%20there%20a%20way%20to%20hook%20into%20the%20route%20and%20default%20it%20to%20global%20or%20do%20any%20of%20the%20above.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20the%20modern%20search%20results%20page%20is%20not%20customizable%2C%20is%20there%20a%20way%20(powershell%2C%20csom%20or%20configurable)%20way%20to%20redirect%20to%20classic%20SharePoint%20search%20center%20page.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-110020%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EModern%20Experience%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EModern%20Site%20Page%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esearch%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-290181%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290181%22%20slang%3D%22en-US%22%3EWe%20will%20be%20there%20at%20some%20point...what%20it's%20happening%20is%20that%20new%20search%20experience%20are%20being%20rolled%20out%20at%20a%20slowest%20pace%2C%20it's%20just%20a%20question%20of%20time%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-290158%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290158%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Juan%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20happen%20to%20Ignite%20announcement%20on%202017%3F%20Because%20now%20its%20the%20end%20of%20the%20year%202018.%20I%20can%20not%20see%20any%20option%20for%20customization%20in%20office%20365%20search.%20At%20least%20Microsoft%20should%20give%20options%20to%20add%20the%20refiners.%20As%20of%20now%20only%20modified%20and%20fietype%20refiners%20are%20available.%20Please%20note%20I%20am%20talking%20about%20Modern%20Search.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265603%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265603%22%20slang%3D%22en-US%22%3EAre%20able%20to%20share%20the%20CSS%20code%20to%20hide%20the%20search%20box%20as%20that%20is%20what%20I%20require%20at%20the%20moment%20on%20my%20communication%20site.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-207807%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207807%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20still%20waiting%20on%20this%20to%20come.%20Did%20they%20also%20say%20when%20to%20expect...%20Few%20months%20and%20the%20next%20ignite%20is%20there%20%3B)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206497%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206497%22%20slang%3D%22en-US%22%3Ehi%20Asish%2C%20do%20you%20have%20an%20update%20on%20this%20matter%3F%20I%20ran%20into%20the%20same%20problem%20today.%20Thanks%20in%20advance.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-177530%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177530%22%20slang%3D%22en-US%22%3E%3CP%3EI%20tried%20using%20the%20out%20of%20the%20box%20ways%20to%20adjust%20the%20search%20settings%20and%20set%20another%20search%20result%20page%20there.%20But%20no%20luck...it%20is%20not%20reflected%20on%20the%20modern%20sites.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174631%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174631%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Asish%2C%3C%2FP%3E%0A%3CP%3EI%20actually%20prefer%20your%20solution%20as%20well%20since%20the%20maintenance%20would%20be%20too%20complicated%20for%20me.%3C%2FP%3E%0A%3CP%3ECould%20you%20kindly%20tell%20me%20how%20exactly%20you%20were%20able%20to%20hide%20the%26nbsp%3Bexisting%20the%20search%20box%20controls%3F%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-171408%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-171408%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%20great%20blog.%20Our%20scope%20didn't%20include%20the%20flexibility%20of%20a%20new%20component.%20We%20were%20only%20be%20able%20to%20modify%20the%20existing%20the%20search%20box%20controls%20which%20turned%20out%20to%20be%20a%20limitation%2C%20so%20we%20have%20hidden%20it%20using%20some%20fancy%20CSS%20and%20added%20a%20left%20hand%20link%20to%20Enterprise%20Search%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134452%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134452%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20check%20out%20my%20blog%20post%20on%20how%20to%20%22%3CA%20title%3D%22Create%20an%20Enterprise%20Search%20Web%20Part%20for%20Modern%20Pages%22%20href%3D%22https%3A%2F%2Fgoo.gl%2F83rR1M%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ECreate%20an%20Enterprise%20Search%20Web%20Part%20for%20Modern%20Pages%3C%2FA%3E%22%20that%20show's%20how%20to%20redirect%20the%20user%20to%20your%20enterprise%20search%20site.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-110181%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-110181%22%20slang%3D%22en-US%22%3EAFAIK%2C%20you%20cannot%20currently%20modify%20the%20modern%20search%20results%20but%20following%20announcements%20Today%20at%20Ignite%2C%20customizations%20at%20Office%20365%20search%20is%20something%20that%20will%20come%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-918251%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-918251%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20has%20been%20almost%20a%20year%20any%20update%20on%20this%20yet%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-918353%22%20slang%3D%22en-US%22%3ERe%3A%20Configure%20Search%20Results%20in%20Modern%20page%20(Modern%20Search%20Center)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-918353%22%20slang%3D%22en-US%22%3EIf%20you%20need%20a%20custom%20search%20experience%2C%20right%20now%20the%20only%20option%20is%20the%20PnP%20SPFx%20Search%20Webparts.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fsharepoint%2Fblogs%2Fpnp-webcast-sharepoint-framework-modern-search-web-part%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fsharepoint%2Fblogs%2Fpnp-webcast-sharepoint-framework-modern-search-web-part%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E
Contributor

Has anyone been able to modify the search results page of Modern Pages which seems to have missing that at present. There is no way to customize the results view, switch to classic view, use custom result sources or redirect to enterprise search center. It always defaults to "/search/sitefiles" location instead of only "/search". Is there a way to hook into the route and default it to global or do any of the above.

If the modern search results page is not customizable, is there a way (powershell, csom or configurable) way to redirect to classic SharePoint search center page.

17 Replies
AFAIK, you cannot currently modify the modern search results but following announcements Today at Ignite, customizations at Office 365 search is something that will come

Please check out my blog post on how to "Create an Enterprise Search Web Part for Modern Pages" that show's how to redirect the user to your enterprise search site.

Yeah great blog. Our scope didn't include the flexibility of a new component. We were only be able to modify the existing the search box controls which turned out to be a limitation, so we have hidden it using some fancy CSS and added a left hand link to Enterprise Search

Hi Asish,

I actually prefer your solution as well since the maintenance would be too complicated for me.

Could you kindly tell me how exactly you were able to hide the existing the search box controls?

Thanks

 

Jan

I tried using the out of the box ways to adjust the search settings and set another search result page there. But no luck...it is not reflected on the modern sites.

hi Asish, do you have an update on this matter? I ran into the same problem today. Thanks in advance.

I am still waiting on this to come. Did they also say when to expect... Few months and the next ignite is there ;)

Are able to share the CSS code to hide the search box as that is what I require at the moment on my communication site.

Hi Juan,

 

What happen to Ignite announcement on 2017? Because now its the end of the year 2018. I can not see any option for customization in office 365 search. At least Microsoft should give options to add the refiners. As of now only modified and fietype refiners are available. Please note I am talking about Modern Search.

We will be there at some point...what it's happening is that new search experience are being rolled out at a slowest pace, it's just a question of time

@Juan Carlos González Martín 

 

It has been almost a year any update on this yet?

 

 

If you need a custom search experience, right now the only option is the PnP SPFx Search Webparts.

https://developer.microsoft.com/en-us/sharepoint/blogs/pnp-webcast-sharepoint-framework-modern-searc...

@Trevor Seward 

 

Has there been any movement on the ability to edit the search results page in modern site collections?

PnP webparts are still the go-to - https://microsoft-search.github.io/pnp-modern-search/, but you can also repoint where the top nav search bar goes to, i.e. a custom results page using the above PnP webparts.

https://docs.microsoft.com/microsoftsearch/create-search-results-pages
Thanks Trevor. This defect and the fact site templates cannot be used any longer are both very significant issues that need rectification.
Site templates are dead and you need to move onto Site Designs (with or without PnP templates). I'm not exactly sure what the issue is with search, though. It's functional and highly customizable.
Yes site designs is the way we have gone, but we have it had alot of limitations, eg web parts, custom views etc we found very challenging to set. Also you have to be technical enough to know what you are doing, ie some SharePoint development expertise. The limitation of not being able to just add the refiners as you were able to do before is also disappointing. It would be good if there was more 'official' MS technical documentation around these issues. Both issues took me a couple of hours to find the relevant references. This blog was useful for the search one though - thanks