Together, they took turns answering a series of rather technical questions with each of them adding their own unique insight.
Here’s a quick recap of each question and answer.
Question 1: What to Do With Old Assets?
“When using Rails Asset Pipeline for caching what status code do we give the old asset? Googlebot crawls these stale assets which we currently have 404’d. Do we 410 instead or keep the old assets alive for a couple months?”
In general, old assets should be kept around until they’re no longer being crawled. Eventually, Google will re-crawl the HTML content and get the new assets.
If you 404 old assets then you may end up with broken renders, which is something that should be avoided.
Question 2: Irrelevant Elements
“In prerendering can we replace or skip irrelevant elements? I.e. svg bar graphs generated by JS?”
Everything should be included in pre-rendering, or at least as many elements as possible, so Googlebot can see the full content.
Question 3: Rewritten Title Tags
“If your site has a chat function that rewrites the title tag for notifications to the visitor, how do you or the app supplier prevent Google from indexing the JS rewritten version of the title tag?”
In this particular instance, you can get around the issue by delaying the chat behind a user interaction. That would make it so the user has to click on the chat button before it opens up and changes the title tag. Since Googlebot doesn’t interact with anything it will never see the re-written title tags.
“In prerendering: can still be JS inside? JS that generates minor content layout changes, but not AJAX requests.”
Question 5: Will Pre-rendering or Dynamic Rendering Go Away?
“Will pre-rendering or dynamic rendering ever go away?”
Dynamic rendering may go away eventually, as it’s more of a workaround that will hopefully not be needed much longer.
Server side rendering and pre-rendering, on the other hand, are more useful in the long-term because they allow users (and crawlers) to receive content faster.
See the full video below: