A web page should work for people after it renders, but its essential meaning should also be available to machines that may not run its JavaScript. Check what the server sends first: if the initial HTML contains only an app shell and the page’s main text, links, and metadata appear only after scripts execute, some crawlers and preview systems may not see them. Google can render JavaScript for Search, but its rendering can be delayed, and Google says not all bots can run JavaScript.
What does a machine see before JavaScript runs?
The initial HTML is the document returned by the server before browser JavaScript changes the page. A rendered page is what appears after scripts have run; it can include content absent from the initial response. This raw-versus-rendered distinction is the practical test behind the question, “What does a machine see when it reads my page without running JavaScript?”
As an Amazon Associate I earn from qualifying purchases.
Some pages send their main content directly in the HTML. Others send an app shell and rely on JavaScript to fetch and display the meaningful text. Google describes both patterns in its JavaScript SEO documentation. The second approach can work for Google Search, but it makes content availability depend on a rendering step that other systems may not perform.
How Google handles JavaScript—and what that does not prove
Google Search processes JavaScript pages through crawling, rendering, and indexing. Eligible pages are queued for rendering, and the wait may take longer than a few seconds. Google uses an evergreen Chromium version, but that fact describes Google’s own rendering capability; it does not establish how social preview bots, other search engines, or AI crawlers handle a particular page.
#1 Best Overall
Google’s guidance is not to avoid JavaScript altogether. It says: “Keep in mind that server-side or pre-rendering is still a great idea because it makes your website faster for users and crawlers, and not all bots can run JavaScript.” Server-side rendering or prerendering can therefore improve initial access while JavaScript continues to enhance the experience. These approaches are especially useful when important copy or navigation would otherwise depend entirely on script execution.
What should be available in the initial HTML?
Essential page content
Include the main heading and the text needed to understand the page in the server response where practical. If the first response is an empty shell, a reader’s browser may eventually fill it in, but a machine that does not execute scripts may have little useful content to interpret.
Rank #2
Descriptive metadata
Provide a descriptive, unique title element and a useful meta description in the HTML. Google says these help users identify relevant search results. For link previews, the exact-topic article recommends delivering Open Graph metadata from the server as well; preview behavior still needs to be checked in the systems you target.
Discoverable links and routes
Represent important links as ordinary anchor elements with an href value. For distinct views in a single-page application, Google recommends the History API rather than URL fragments. This gives crawlers recognizable links and routes to follow instead of relying on script-only interactions.
Accurate structured data
Structured data gives Google explicit clues about what a page means and may make it eligible for rich results. It must accurately describe information visible to people on that page; markup is not a way to make hidden or irrelevant content appear in search. See Google’s introduction to structured data.
How to audit a page from both perspectives
- Inspect the initial response. Fetch the page or use a browser’s view-source function, then search the returned HTML for the main heading and representative body text. Check that key links and descriptive metadata are present too.
- Compare it with rendered output. Inspect the page after scripts run. Identify important copy, links, or metadata that appear only in the rendered version, then decide whether they should be available earlier.
- Check Google’s view separately. Use Search Console’s URL Inspection or the Rich Results Test, as appropriate, to inspect Google-rendered content and structured data. Google recommends these tools in its JavaScript SEO guidance.
- Check crawl access and page signals. Confirm that robots rules do not block the page or resources needed to render it, that the response status and canonical URL are correct, and that important destinations use crawlable anchors. Google says it skips an HTTP request and JavaScript rendering for URLs disallowed by robots.txt; its robots.txt guide explains the file’s role.
- Test other systems on their own terms. Check social previews and any other search, scraping, or answer system you care about directly. A successful Google rendering check does not show what those systems receive.
How to interpret what you find
- Main text missing from initial HTML: Consider server-side rendering, static generation, or prerendering so essential content is present before client-side scripts run.
- Content appears for Google but not in another preview: Treat that as a difference between systems, not proof that all crawlers behave the same way. Test the specific target system.
- Google’s rendered view is incomplete: Check whether robots rules block the page or necessary resources, and review status codes, routes, and rendering errors.
- Structured data differs from visible content: Correct or remove the markup so it describes what people can actually see on the page.
What this means for a JavaScript-heavy site
You do not need to remove JavaScript to make a page machine-readable. The useful distinction is whether the page’s core meaning and navigation are available without requiring every reader to execute scripts. Build for the rendered experience people use, but make the initial response informative enough that a crawler or preview bot with limited capabilities can still identify the page and its important links.
Quick Recap
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
