1. Introduction to New Release and Livestream
We're introducing our new release and livestream. Visit our website to learn more and enjoy our livestream and YouTube experiences. I'll explain what mobile-first indexing is and share what we did to improve our SEO. Teachers Pay Teachers is a platform where teachers can share and sell resources. Google's move to mobile-first indexing posed challenges for us. Let me explain how search ranking works and how mobile-first indexing fits in.
We're now introducing you to our new release and livestream. Visit our website at livestream.com to find out more and enjoy our livester and YouTube experiences, and learn more about the latest and greatest on the React team. We're also doing a live stream live, so if you want to subscribe to a live stream, please do so. We're also delivering live content that you want to see, so if you have more questions, let us know in the comments section below. We really hope to see you there. Thanks for watching.
Hi, I'm Ruth Mespin from Teachers Pay Teachers, and I'm going to show you how my team improved our SEO for mobile first indexing. Just so you know, here's my information if you'd like to connect with me after the session and geek out on React and mobile first indexing. In this talk, I'll first give you a quick background on Teachers Pay Teachers, explain what mobile first indexing is and then share with you what we did to improve our SEO.
So for anyone who hasn't heard of Teachers Pay Teachers, it's a platform where teachers can share and sell resources to each other. And the resource page is where a teacher can see if a resource is the right fit and then purchase it. It's also ranked on Google. So when Google announced that they were moving towards 100% mobile first indexing, this was our expression. We didn't really know what that meant and how it affect us. So let me tell you how search ranking works and how mobile first indexing fits into it. This is Googlebot. He's a web crawler. And what he does currently is desktop-first indexing, which is getting your information from your content of your desktop pages. And he'll also check, you know, bounce rates, et cetera. But essentially, check the relevancy of the page itself. And based on the user query, he will rank the search. And you can celebrate, because you're on page one.
With mobile-first indexing, though, it's doing the same thing, except crawling your mobile pages. And if your mobile is different from your desktop page, it can rank you very differently. Which was a big problem for us. With our mobile page, which is this, there isn't a lot of information shown at first. You need to click the button to get through the information which is a different page entirely. And then, it also has a different user experience from our desktop page. Mainly because our desktop page is in React, which is awesome. But our mobile page is in PHP.
2. Mobile-First Initiative and Optimization
The majority of our users obtained resources on our desktop page. Mobile was not a priority until Google announced their switch to mobile-first indexing. We combined teams to create a mobile-first initiative and updated the resource page. We tested performance, increased page speed, and updated mobile content. We also fixed structured data issues and showed hidden content.
To be fair, the majority of our users obtained resources on our desktop page. And since mobile was completely separate and harder to maintain, it wasn't really a priority. But it's now mainly a priority because Google shared that they were switching to mobile for indexing to 100% by September. Don't worry. They actually pushed it back to March of next year. So you have time to optimize.
So, with that said, we combined two amazing teams, Web Platform and Quality, to create the mobile-first initiative team to update the resource page. We converted from a PHP mobile page to a mobile-responsive React page, keeping the UI the same as the desktop view. So it went from this to this. Which made us very happy, especially since I love React. It also made the company very happy because it increased our purchases on mobile by 3%. So, we had a really good user experience here.
So what did we do? First, we tested our performance using these resources like House Screen Curve and Google Search Console. Using these tools, we were able to make benchmarks to see if our changes are improving performance in SEO. Also, we utilized Lighthouse, especially because it gave us recommendations on things that we needed to fix. Second thing was that we increased our page speed based on Lighthouse recommendation. We realized that we were inundating our resource page with a lot of third-party packages that were unnecessary. So we reduced them by half so we could increase the page load or we could increase the speed of our page load on our resource page. What we did was we actually swapped to smaller packages. So for instance, moment.js, we realized was a really large package and we actually chose a smaller package that had the functionalities we needed. We also replaced packages with React components. So we created our own chart components so we could remove our Chartist package. We also natively loaded images and removed unnecessary CSS and feature flags that were cluttering our resource page.
Next, we updated our mobile content. The mobile version didn't have all the content that the desktop version had. So we updated this so there wasn't any discrepancies of the content between mobile and desktop. We also fixed any structured data issues. Finally, we showed hidden content. We first checked robots.txt, which is a file. If you don't know where the file is, if you have a web platform team, check with them.
3. Optimizing Mobile Pages for Googlebot
To increase your search ranking, show hidden content, update mobile content, increase page speed, and test performance and SEO. Connect with me to share your results and ask questions.
We want to make sure that Googlebot was allowed to crawl from the mobile pages. It would have been awful if he didn't, and we did all this work. So just double check that there isn't a disallow on there.
Next, we stacked each of the sections. In our original mobile view, you could see that it's hidden behind buttons. You need to click the button, and then the data will load. The issue with that is that if it isn't initially loaded, Googlebot can't crawl the information. Think about it. Googlebot can't click a button and then wait for the data to come through.
So we stacked the sections, and so users now can easily see the content without needing to take any additional actions. I do also want to state that Google is mindful of the limited space on mobile screen, so you can load the data initially upon page load, and then hide it behind a button or an accordion and get it revealed based on the user action. Since if that's the case, if it's initially loaded, Googlebot can still crawl through the data information.
So, to recap, to increase your search ranking, you should show hidden content, update mobile content, increase page speed, and then finally test performance and SEO. Or just suit up and you'll be just fine. Please make sure to connect with me and share the stuff that you did that are based on the recommendations and share your results. I would love to see them, and if you have any questions, again, connect.