How to manage old assets and cache
The first question immediately leads us into the practical issues: a user asks in fact for advice to manage the old assets when using the Rails Asset Pipeline for caching. In particular, he wonders about the status code to be returned: “Googlebot scans these old resources that we currently put in 404, but is it better to set up a 410 or keep those assets alive for a few months? Is it something that can destroy our crawl budget?”
The answer is entrusted to Martin splitt, Developer Advocate at Google, who says that in fact the issue generally concerns every type of obsolete resource that we want to update. In particular, the Rails Asset Pipeline is a way by which “rails process and pre-process your assets as you have them during the development phase for the loading part of the site”, and so, it is “an automatic pipeline that treats site assets in the rails application”.
What to do with irrelevant elements in pre-rendering
There is not much to do, according to the googlers, if not completely avoid this scenario beforehand: when it renders the page, Googlebot takes the written titles it finds and could then read the unwanted one. The solution could be to hide or delay the chat behind the user’s interaction, because Googlebot does not interact with these things: therefore, an ideal process would be the one that starts with the click on the button, continues with the appearance of the chat popup and then determines the change to the title.
What to include in the pre-rendering?