Lazy-loaded content
Lazy content is deferred until a viewport, interaction, or application state triggers its retrieval.
How it works
Deferral saves bandwidth for people but introduces an additional condition before a crawler can observe the content or links.
How to validate it
Record network requests and DOM mutations while scrolling through fixed checkpoints, and distinguish native image loading from script-driven text insertion.
Common failure
Infinite scroll without paginated URLs creates content a person can reach but a crawler cannot address, revisit, or cite reliably.
Machine-readable editions
The same article is available as Markdown and JSON. These alternates are linked here but are not submitted through the sitemap or IndexNow.