diff --git a/apps/datahub-e2e/src/e2e/datasetDetailPage.cy.ts b/apps/datahub-e2e/src/e2e/datasetDetailPage.cy.ts
index 0e9813850e..ef55ee7586 100644
--- a/apps/datahub-e2e/src/e2e/datasetDetailPage.cy.ts
+++ b/apps/datahub-e2e/src/e2e/datasetDetailPage.cy.ts
@@ -246,7 +246,7 @@ describe('dataset pages', () => {
       })
       it('should go to dataset search page when clicking on org name and filter by org', () => {
         cy.get('[data-cy="organization-name"]').eq(1).click()
-        cy.url().should('include', '/search?publisher=')
+        cy.url().should('include', '/search?organization=')
       })
       it('should go to dataset search page when clicking on keyword and filter by keyword', () => {
         cy.get('gn-ui-expandable-panel').eq(2).click()
diff --git a/docs/reference/search-fields.md b/docs/reference/search-fields.md
index 0625fe8192..614f8495e9 100644
--- a/docs/reference/search-fields.md
+++ b/docs/reference/search-fields.md
@@ -11,7 +11,7 @@ GeoNetwork-UI has built-in logic for several search fields, each of them relying
 These fields are used in the following context:
 
 - when building a URL or permalink from several search criteria; these fields will appear as query parameters in the URL, for instance:  
-  `/search?publisher=MyOrg&format=csv&format=excel`
+  `/search?organization=MyOrg&format=csv&format=excel`
 - when specifying advanced filters [in a configuration file](../guide/configure.md#search)
 
 ## Fields