Search function rendering cached pages incorrectly

[MickEdwards]

On a category page the products are listed via/in connection with the search function on the site.  Page source and front-end match as they should.

However when viewing a browser rendered version of a google cached page the URL for the product has changed from, as an example -

https://www.example.com/products/some-product

to

https://www.example.com/search/products/some-product

The source is a relative URL in the correct format, so therefore /search/ is added at browser rendering.

The developer insists that this is ok as the query string in the Google cache page result URL is triggering the behaviour, confusing the search function - all locally.  I can see this but just wanted feedback that internally Google will only ever see the true source or will it's internal rendering mechanism possibly trigger similar behaviour?

[JohnSammon]

Hi Michael,

Can you post the site URL so I can review further?

Thanks!

John