Server rendering
Server rendering is producing a page’s HTML on the server so that the response already contains the content, rather than sending a shell for the browser to fill in.
The relevance to agents is direct: what the server sends is what a client that does not run scripts receives. A server rendered product page carries its price; a client rendered one carries a container where the price will go.
There is a second, less obvious case. A page can be rendered at build time rather than per request, and if the build had no database access it bakes an empty result into the artifact and serves that until a cache expires.
Why it matters to a store
Both failures look identical from the outside and neither reports an error. The page is green, the build passed, and the content is simply absent for anything that did not render the page itself.