The issue with client-rendered content - Deepstash
The Podcasting Ecosystem

Learn more about marketingandsales with this collection

The importance of networking in podcasting

How to grow your podcast audience

How to monetize your podcast

The Podcasting Ecosystem

Discover 44 similar ideas in

It takes just

7 mins to read

The issue with client-rendered content

The issue with client-rendered content

  • The standard implementation of a single-page app provides a page “shell” to the browser without any meaningful content included. The content is instead loaded on demand from the server with AJAX and then added to the page by JavaScript.
  • This allows a user to view the “pages” of an SPA site without a page refresh, theoretically improving UX.
  • While this architecture works for human users, what about search engine crawlers? 
  • It’s important to know this, as it could determine whether or not the site’s content is indexable by a search engine, and just as importantly, how well its content is ranked.

2

0 reads

MORE IDEAS ON THIS

What to do if SEO is critical

If SEO is critical, you can’t rely on your SPA’s client rendering and must ensure content comes included in your pages.

This doesn’t mean you need to abandon the SPA architecture, though. There are two techniques, server-side rendering and prerendering, that both can ac...

2

0 reads

CURATED FROM

CURATED BY

trstro

Dramatherapist

Read & Learn

20x Faster

without
deepstash

with
deepstash

with

deepstash

Access to 200,000+ ideas

Access to the mobile app

Unlimited idea saving & library

Unlimited history

Unlimited listening to ideas

Downloading & offline access

Personalized recommendations

Supercharge your mind with one idea per day

Enter your email and spend 1 minute every day to learn something new.

Email

I agree to receive email updates