The goal of this awesome article is to equip you with the minimal viable knowledge required to do so. This awesome article won’ t go into the nitty gritty information, describe the history, or give you severe detail on specifics. There are a lot of amazing write-ups that already do this — I suggest giving them a read in case you are interested in diving deeper (I’ lmost all link out to my favorites at the bottom ).
- If not, what is the ideal alternative?
I’ meters going to be using Sitecore’ s Conference, seminar landing page through each of these talking factors to illustrate how to answer the particular questions above.
We’ ll cover the “ how can i do this” aspect first, with the end I’ ll expand on the few core concepts and url to further resources.
How do we go about achieving this?
Ask the client
Ask, and you shall obtain! Seriously though, one of the quickest/easiest actions you can take as a consultant is contact your own POC (or developers on the account) and ask them. After all, these are individuals who work on the website day-in plus day-out!
As you create progress, jot down notes about articles that isn’ t being packed in, is being loaded in incorrect, or any internal linking that isn’ t working properly.
In order to get a more accurate depiction associated with what Googlebot is seeing, we have to attempt to mimic how it crawls the page.
How can we do that?
Make use of Google’ s new mobile-friendly tests tool
At the moment, the particular quickest and most accurate way to try to replicate what Googlebot is viewing on a site is by using Google’ ersus new mobile friendliness tool. The colleague Dom recently wrote an in-depth post comparing Research Console Fetch and Render, Google crawler, and the mobile friendliness tool. Their findings were that most of the time, Online search engine bots and the mobile friendliness tool led to the same output.
Within Google’ s mobile friendliness device, simply input your URL, strike “ run test, ” after which once the test is complete, simply click “ source code” on the correct side of the window. You can take that will code and search for any on-page content (title tags, canonicals, and so forth ) or links. If they show up here, Google is most likely seeing the information.
Search for visible articles in Google
It’ ersus always good to sense-check. An additional quick way to check if GoogleBot provides indexed content on your page can be by simply selecting visible text on your own page, and doing a site: look for it in Google with quotations close to said text.
Within our example there is visible text for the page that reads…
“Whether you are in advertising, business development, or IT, you are feeling a sense of urgency. Or maybe opportunity? inch
When we perform a site: search for this exact term, for this exact page, we obtain nothing. This means Google hasn’ to indexed the content.
Crawling with a tool
From here you can input your own domain/URL and see the rendered page/code once your tool of choice provides completed the crawl.
When trying to answer this question, my choice is to start by inputting the area into Google’ s mobile friendliness tool, copy the source code, plus searching for important on-page elements (assume title tag, < h1>, entire body copy, etc . ) It’ t also helpful to use a tool such as diff band to compare the made HTML with the original HTML (Screaming Frog also has a function where one can do this side by side).
For our example, here is what the outcome of the mobile friendliness tool displays us.
After a few lookups, it becomes clear that important on-page elements are missing here.
We also did the 2nd test and confirmed that Google hasn’ t indexed the body content available on this page.
The inference at this point is that Googlebot is not viewing our content the way we want this to, which is a problem.
Let’ s jump ahead and find out what we can recommend the client.
Question 3: If we’ lso are confident Googlebot isn’ t viewing our content properly, what need to we recommend?
How do we accomplish that?
You want server-side object rendering
The particular fix here is to instead possess Sitecore’ s landing page load on their server. In other words, we want to take the heavy raising off of Googlebot, and put it upon Sitecore’ s servers. This will make sure that when Googlebot comes to the web page, it doesn’ t have to do any kind of heavy lifting and instead may crawl the rendered HTML.
In this scenario, Googlebot gets on the page and already views the HTML (and all the content).
There are more specific choices (like isomorphic setups)
This is where it gets to be a little bit in the weeds, but there are cross solutions. The best one at the moment is known as isomorphic.
In this design, we’re asking the client to load the very first request on their server, and then any kind of future requests are made client-side.
If you’ lso are looking to recommend this as an answer, please read this post from the AirBNB group which covers isomorphic setups in more detail .
AJAX moving = no go
(However, I am interested to hear any situation studies from anyone who has implemented this particular solution recently. How has Search engines responded? Also, here’ s a great post on this from the colleague Rob. )
- Ask the developers.
- Check to see if GoogleBot is viewing content the way we intend this to.
- Google’ s mobile friendliness checker.
- Doing a site: search for noticeable content on the page.
- Provide an ideal recommendation to client.
- Server-side rendering.
- Hybrid solutions (isomorphic).
- Not AJAX crawling.