: Workaround for appearing to change the URL of an infinite scrolling page when pushState is not available due to analytics I'm building a website and they want it to be an infinite scroll single

@Cooney921

First, parallax is a visual effect. What you're asking about is a single "infinitely" scrolling page, or Single Page Application.

If I'm understanding correctly, you don't want to use pushState because you think you'll lose analytic data. I'm not sure why you think that: Google Analytics describes set-up for SPAs here.

That being said, if it's a "really big page" and SEO and analytics are critically important, I'd question whether an SPA is the best approach. Aside from the engineering problems, search engines other than Google still struggle to crawl AJAX and similar configurations. The extent to which you care about that will of course depend on search engine market share inn the market you're operating in.

Unless there's a highly compelling, make-or-break user experience argument for SPA, why go to the trouble?

Vote Up Vote Down

@Twilah146

You can push the page-equivalent URL to the client's browse history, not just so they can use the browser's back and forward buttons, but also so each article gets accessed independently by users of a search engine.

However, a search engine like Google is also concerned with duplicate content: if you show the same content on multiple pages (via multiple URLs) then you should declare which page is the leading (canonical) one.

With displaying several articles' contents on the same main page, that may prove difficult.

In that case, I'd suggest looking at solutions to make infinite scroll concepts accessible and SEO-friendly: they push the shown sub page into the browse history.

Vote Up Vote Down