Timeline for Can I use pushState for SEO on a single page application that is fully loaded on the first request?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 16, 2017 at 10:49 | history | edited | GDVS | CC BY-SA 3.0 |
deleted 1 character in body
|
| Jul 31, 2017 at 21:42 | comment | added | Rober |
Mmmmh... It is a magazine-like site, with no flip-page effect, but the pieces look like "pages" or sections. I can decide how the not active sections are hidden (simply outside of the view, display:none, visibility:hidden, opacity...). It is a one-page site if we talk about loading and URLs, but not from the point of view of the user experience.
|
|
| Jul 31, 2017 at 21:06 | comment | added | GDVS |
It depends what you mean by "hiding". Per the Google sources I linked to, whether you're showing individual pages of a sequence by normal pagination or infinite scroll, rel="prev" etc. takes care of unifying them as contiguous pieces of a whole. Bear in mind, though, if they're separate pieces of content shown in a one-page UX, it's not paginated content and rel="prev" etc. isn't required.
|
|
| Jul 31, 2017 at 20:58 | comment | added | Rober |
I know it is not a good idea to load everything. Now it is a matter of doing the best I can regarding to SEO. Ok, thanks, I will take another look to prev/next. I want to tell Google what content relates specifically to each page of the series. Is it enough simply showing a part of the site and hiding others?
|
|
| Jul 31, 2017 at 15:10 | history | edited | GDVS | CC BY-SA 3.0 |
added 2 characters in body
|
| Jul 31, 2017 at 13:35 | history | answered | GDVS | CC BY-SA 3.0 |