- The second index wave is when it renders your site in full, and can be harmful as it results in lost traffic.
- One way to bypass the issue is to apply static rendering to a pre-rendered version of your URL and store it in the cache to aid Google’s indexing.
GUESTS & RESOURCES
- Björn Darko: Website // LinkedIn
- The Voices of Search Podcast: Email // LinkedIn // Twitter
- Benjamin Shapiro: Website // LinkedIn // Twitter
Ben: All right on with the show. Here’s my conversation with Björn Darko, director of the digital strategies group at Searchmetrics. Björn welcome to the Voices of Search podcast.
Björn: Thanks for having me again.
Björn: Actually, actually it’s a developers’ language, which is created after HTML. It’s actually the code language, which developers use to code stuff and code functions and code websites.
Björn: Yeah, exactly.
Ben: So, what is second way of indexing?
Ben: Okay? So you have the ability to say, “Hey, Google, I’ve already unpacked this box for you. Here’s what it looks like when it’s unpacked that way you don’t have to double back and do this second crawl experience.”
Björn: Exactly. And there are different ways you can do the rendering. So there’s one thing called static rendering. And what you do here is like you have a pre-rendered version of your URL and store it in the cache so that the server is sending this already pre-rendered file to Google, whenever Google comes. And there’s another thing which is called dynamic rendering, which actually allows requests based on the navigation. There’s a navigation point coming to this type. Then the output will be HTML. That’s already doing the job for Google on the server and sending another pre-rendered version here to Google.
Björn: Yes. In the earlier days we would say this actually cloaking, right? So because what you do is you are providing Google something which is different from the file character, then a normal user, the browser, because the normal user who comes through the browser gets the hours for the base website. Right. And you’re completely right. There are a lot of pitfalls, which we also have seen with clients, and this is what people actually see.
Björn: So let’s take one example. We have a publisher, they are running on Angular JS, and they’re using Brenda Tron as a rendering machine who does the job Google. But what they do is static rendering, meaning that they make a snapshot of the website site and the cache and whenever Google comes they get the version of the cache. The thing is that they didn’t renew the version whenever there was a new your article published, for example. So what, who the Goggle got was a version of the website, which was maybe a month old. Whenever there was a new article published Google didn’t get this article. This is one thing. So you always need to make sure that the start version of the website gets updated as soon as there’s new content available. Right.
Ben: Understood. Go on.
Björn: Understood. And another thing which we saw is paginated pages. So you have a pagination on the website, 1, 2, 3, 4, 5, 6, right?
Björn: And if you have a pagination on the website, the content on page 1 should be different than on page 2, 3 or 4 or 5 or 6, But because these pre-caching of the website’s content costs so many resources, this publisher, just did one cache version of page one, and then mirrored it up to page 10. So that you had exactly the same content on 10 pages, which is of course causing duplicate content for example, and is not really good also that triggered a lot of duplicate content as well with some parameter URLs, because what you can do an audit to see what it actually indicates, that you can use a parameter, which actually then shows you the cache version. And what they did is they made it fully accessible even with a non-canonical tech and just throw it into the index so that you actually had two different or sometimes two or three different sites’ content on three different URLs.
Björn: You are Welcome. Thank you.
Ben: All right. And that wraps up this episode of the Voices of Search Podcast. Thanks for listening to my conversation with Björn Darko, director of the digital strategies group at Searchmetrics. We’d love to continue the conversation with you. So if you’re interested in contacting Björn, you can find the link to his LinkedIn profile in our show notes, you can contact him on Twitter. His handle is Björn underscore Björn that’s bjorn_darko. You could watch his famous IGTV show it’s SEOpresso or you could visit his company’s website, which is searchmetrics.com.
Ben: Just one more link in our show notes. I’d like to tell you about, if you didn’t have a chance to take notes while you were listening to this podcast, head over to voicesofsearch.com, where we have summaries of all of our episodes, contact information for our guests. You can send us your topic, suggestions, your SEO questions. You can even apply to be a guest speaker on the Voices of Search podcast. Of course, you can always reach out on social media. Our handle is voicesofsearch on Twitter. and my personal handle is BenJShap, B E N J S H A P. And if you haven’t subscribed yet, and you want a daily stream of SEO and content marketing insights in your podcast feed, we’re going to publish episodes every day during the workweek. So hit that subscribe button in your podcast app, and we’ll be back in your feed tomorrow morning. All right. That’s it for today. But until next time, remember the answers are always in the data.