How do we do that?

[kexej28769@nongnue]

This location means that Googlebot is not viewing our content the way we want it to, which is a problem.

Let's go ahead and see what we can recommend to the client.

Question 3: If we believe Googlebot is not crawling our content properly, what should we recommend?
Now that we know that the domain is using bosnia and herzegovina number data to load important content and we know that Googlebot is probably not seeing that content, the final step is to suggest an ideal solution to the client. Key word: suggest , not implement. It is 100% our job to communicate the problem to our client, explain why it is important (as well as the potential implications), and highlight an ideal solution. It is 100% not our job to try to find an ideal solution for the developer with their unique stack/resources/etc.



You want server-side rendering.
The main reason Google is currently having trouble seeing Sitecore’s landing page is because Sitecore’s landing page is asking the user (us, Googlebot) to do the heavy lifting of loading JavaScript onto their page. In other words, they are using client-side JavaScript.

Googlebot is literally landing on the page, trying to run the JavaScript as best as possible, and then needs to leave before it has a chance to see any content.

What we need to fix here is to load the Sitecore landing page on their server instead. In other words, we want to take the heavy lifting off of Googlebot, and put it on Sitecore's servers. This will ensure that when Googlebot comes to the page, it doesn't have to do any heavy lifting and can crawl the rendered HTML instead.