joined:Apr 1, 2016
I recently posted in another thread
Could making pages load faster inadvertently damage your rankings?
And my post gave me an idea which I would like to validate.
First my problem (as stated in the other post), in order to increase page speed I have delayed rendering so SVG graphics until after the user scrolls. The SVG contains content that I assume Google is able to crawl and index. I had initially thought that the gain in page speed would offset any benefit provided by the added content. But after a few weeks with no positive results I am really starting to question my logic.
So now, I thought, why don't I properly lazy load the content using pushState and a url for each graph or sub-section.
Let me backup and explain the page. The page provides stats and ratings of events. So for each event I accumulate some data and then generate a page. The top of the page, the main content provides a description of the event and a rating that is computed based on the data and stats shown further down the page, a summary. Below this I provide graphs on some relevant statistics for the events, like "top number of widgets sold", "most popular widgets offered", etc.. I typically have about 8 such sections. Each section has one interactive chart (SVG) and a brief written summary specific to the content of the chart.
If I view this from a very basic perspective, that is if I took each subsection and made it its own page, I would be concerned that the content could be thin. It would be a terrible UX for sure so that is not a real option. But if I treat each subsection as its own page, but lazy load it like a single page app (Fb,twitter time, cnn etc...), each subsection would get its own url, but the ux would be similar to what it is now.
Google could have access to all the content of the page when it crawls it, as opposed to now where some of the content remains hidden. Moreover it may consider subsection content as main content as opposed to secondary content to the main page. So it may give more weight to a query such "what are the highest number widgets sold at event xyz" and it would take the user directly to the content as opposed to the top of a page that shows the content well below the fold.
So what do you think? Change to a "Lazy load - pushState - SPA" type layout or leave it as is and hope that users will someday show-up?
Note to the lazy-load, SPA nay-sayers out there (I know you are out there!) the actual page layout will likely not change much from its current state. So I am not planning on making the whole site into an SPA.