The SEO’s Introduction to Rendering via @Jammer_Volts
0Reported today on Search Engine Journal
For the full article visit: http://tracking.feedpress.it/link/13962/13075519
The SEO's Introduction to Rendering
Let's start this out with a bang.
Googlebot isn't what you think.
SEO professionals refer to Googlebot with a strange form of reverence reserved in prior generations for all-knowing deities and unseen powers.
It's dramatic, gives flair to a story, but oversimplifies the true identity of Googlebot.
Googlebot is simply a user-agent. It is the identifier of a request – a fancy version of caller ID.
Once the request receives a response, Googlebot's job is over and it's off to request the next URI. The collected response runs through a series of services and processes before it appears in SERP.
The scrappy user-agent gets all the glory, but we need to talk about the heavy-hitter, the hidden construct that builds your site for Google to experience it as a human would: rendering.
What Is Rendering?
Rendering is the process where Googlebot retrieves your pages, runs your code, and assesses your content to understand the layout or structure of your site.
All the information Google collects during the rendering process is then used to rank the quality and value of your site content against other sites and what people are searching for with Google Search.
Every Webpage Has Two States – Rendering Occurs Between Them
Every webpage has two states:
A website can be very different between the two states.
The initial HTML occurs first. It is the response from the server. In it is HTML and links to resources like JavaScript, CSS, and images that are needed to build to the page. To see the initial HTML for yourself, view the page source.
Rendered HTML is more widely known as the DOM, an abbreviation of Direct Object Model. Every webpage has a DOM. It represents the initial HTML plus any changes made by JavaScript that HTML called on. To view the DOM, o