: Can I use pushState for SEO on a single page application that is fully loaded on the first request? I maintain a magazine-like website. It is a one page site with no AJAX involved, ie. the
I maintain a magazine-like website. It is a one page site with no AJAX involved, ie. the whole content is loaded every time a user enters the site. Dynamic content loading is not an option for now.
I would like to utilize pushState to perform URL and page title changes each time a user navigates from one magazine page to another, so that search engines index each page of the magazine as a different webpage (with its own URL).
Would it be a problem for SEO to fully load the whole magazine no matter what page of it the user enters by?
If so, could I prevent it by presenting the visible content somehow to tell search engines that the current magazine page is the relevant content?
I assume that rel="canonical" (or next / prev) will not help me, since it would reduce search results to an unique URL.
More posts by @Angie530
1 Comments
Sorted by latest first Latest Oldest Best
Loading the whole thing regardless of entry page would, I imagine, create a load speed problem. That will negatively impact user engagement (i.e. higher abandonment rates, etc.) and harm rankings in Google.
Using rel="prev" and rel="next" shouldn't "reduce search results to an unique URL", if I'm understanding you correctly.
According to Google, it should have the effect of consolidating signals (backlinks, etc.) for the whole series of pages, and help ensure searchers are served the most relevant page. That might often be the first page, but not necessarily: a search relating specifically to content on page 3 should still return page 3.
It's also recommended in Google's model for search-friendly infinite scrolling.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.