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
1 read
CURATED FROM
IDEAS CURATED BY
The idea is part of this collection:
Learn more about marketingandsales with this collection
The importance of networking in podcasting
How to grow your podcast audience
How to monetize your podcast
Related collections
Similar ideas to The issue with client-rendered content
How Search Engines Work
Search engines utilise web crawlers (also called spiders or bots) to crawl the web and fetch information about web pages. As they crawl each page, they index and store data such as page content, metadata, links and more.
This indexed data i...
Read & Learn
20x Faster
without
deepstash
with
deepstash
with
deepstash
Personalized microlearning
—
100+ Learning Journeys
—
Access to 200,000+ ideas
—
Access to the mobile app
—
Unlimited idea saving
—
—
Unlimited history
—
—
Unlimited listening to ideas
—
—
Downloading & offline access
—
—
Supercharge your mind with one idea per day
Enter your email and spend 1 minute every day to learn something new.
I agree to receive email updates