What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Your page should work for people after it renders, but its essential meaning should also be available to machines that may not run JavaScript. Google does render JavaScript for Search, though rendering can be delayed; other crawlers and preview bots may behave differently. Put important text, headings, links, and metadata in the initial HTML where practical, then use JavaScript to enhance the experience.
What does a machine see before JavaScript runs?
When a browser or crawler requests a page, the server returns an HTML document. That initial response is often called the raw HTML. JavaScript may then add, replace, or reorganize content, producing rendered output that a person sees in a browser.
If the initial response contains only an app shell and scripts, a reader that does not execute those scripts may receive little more than that shell. Google’s own process includes crawling, rendering, and indexing, but it queues eligible JavaScript pages for rendering, and the wait can take longer than a few seconds. Google also cautions that not all bots can run JavaScript. Google’s JavaScript SEO basics explains its process and implementation guidance.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →This does not mean JavaScript makes a page invisible to Google. Google uses an evergreen Chromium version to render pages for Search. It does mean that Google’s capabilities should not be treated as proof that every crawler, social preview bot, or other machine reader will see the same result.
#1 Best Overall
What should be available in the initial HTML?
Make the page understandable before client-side code runs. For an important page, inspect the server response and confirm it includes:
- The main heading and essential explanatory text.
- Important internal and external links as ordinary anchor elements with usable
hrefvalues. - A descriptive title element and meta description.
- Relevant canonical and robots information, where applicable.
- Structured data that accurately describes information visible to users.
Google says server-side rendering or prerendering remains a good idea because it can make a site faster for users and crawlers, and because some bots cannot run JavaScript. The goal is not to avoid JavaScript altogether: it is to avoid making every reader depend on it for the page’s basic content and navigation.
Rank #2
Keep navigation discoverable
Use crawlable anchors for links rather than relying only on click handlers or script-generated destinations. For a single-page application with distinct views, Google recommends using the History API instead of URL fragments to represent those pages. Review Google’s JavaScript SEO guidance for details on links and routing.
Recommended Free Tools
Make metadata and structured data match the page
Google recommends unique, descriptive title elements and useful meta descriptions to help people identify relevant search results. Link previews may rely on metadata in the initial response too, so server-delivered Open Graph metadata is a practical choice when previews matter.
Structured data gives Google explicit clues about page meaning and may make a page eligible for rich results. It should describe the page and information people can actually see, not hidden or unrelated content. Google’s structured data introduction describes the markup and content guidance.
How to check what machines can read
- Inspect the initial response. Fetch the page or view its source, then search for its main heading and representative body text. If the important copy is missing, the server response is not carrying that content.
- Compare it with rendered output. Identify text, metadata, or links that appear only after JavaScript executes. Decide whether each item is essential, and make essential information available in the initial HTML where practical.
- Check Google-specific rendering. Use Search Console’s URL Inspection or the Rich Results Test, as appropriate, to inspect Google’s rendered view and structured-data implementation. These tools help diagnose Google Search; they do not test every crawler or preview service.
- Check crawl access and page signals. Verify the HTTP status, canonical URL, robots directives, and access to resources needed to render the page. Google says it skips an HTTP request and JavaScript rendering for URLs disallowed by robots.txt. See its robots.txt guide.
- Test other target systems separately. If social previews or another search or answer engine matter to you, check those systems directly. A successful Google rendering check does not establish what another service sees.
How to choose an implementation
Use the implementation that meets your site’s needs while delivering meaningful initial HTML. The key distinction is whether essential content is present in the response or depends on browser execution.
Rank #4
| Approach | What the initial response contains | Practical consideration |
|---|---|---|
| Server-rendered HTML | The server returns page content as HTML. | Useful when content should be available immediately to users and crawlers; JavaScript can still add interactive features. |
| Prerendered or statically generated HTML | HTML for the page is produced ahead of the request. | Can provide readable content without waiting for client-side rendering, while the site may still use JavaScript for enhancement. |
| Client-rendered app shell | The response may contain a shell, with page content added after scripts execute. | Google may render eligible pages, but rendering can be delayed and some bots cannot run JavaScript. Verify that the approach serves the readers and systems you care about. |
These approaches can be combined. A site can send useful HTML first and hydrate it with JavaScript for richer interactions. Choose based on the page’s content, performance needs, and target readers rather than assuming every machine has the same rendering capabilities.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchQuick Recap
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.
