To investigate a JavaScript rendering problem, compare three things for the same URL: the server's initial HTML, the browser's rendered DOM, and the rendered output available from Google's testing tools. Check whether the actual answer and navigation are present. Total bytes, a screenshot alone or an arbitrary five-second cutoff cannot establish indexing success.
Choose a URL and define what must be visible
Start with an affected page, then add representative pages using the same template and data path. Write down the expected heading, main answer, product details, internal links and relevant metadata. Include one working page for comparison and a missing-item route if routing errors are suspected.
Save the exact URL, date, response status and test conditions. A logged-in browser with stored preferences may show content that a fresh request cannot obtain.

Capture the initial response
Use browser View Source or an HTTP client to inspect the returned HTML. Record redirects, the final status, robots declarations and canonical. Search for a distinctive sentence from the main content rather than comparing file size alone.
curl -L -D response-headers.txt -o response.html "https://example.com/products/example/"
Replace the example URL with the authorized test target. This command retrieves HTTP content; it does not execute JavaScript. Changing its User-Agent to Googlebot only tests a response to that header and does not turn it into a verified Google crawler.
Inspect the browser DOM and the requests that create it
Open the page in a fresh browser context. In DevTools, compare Elements with the initial response, and use Network and Console to locate failed scripts, API requests and runtime exceptions. Confirm the important text and links are actually in the rendered page and accessible to the reader.
Disabling JavaScript shows which parts depend on client execution. That is useful diagnosis, but Google can execute JavaScript, so the disabled-script view is not a complete Googlebot simulation. Likewise, CPU or network throttling represents the chosen laboratory conditions, not a published Googlebot hardware specification.
| Observation | Next investigation |
|---|---|
| Correct initial HTML, then blank content | Hydration, client-state replacement or a runtime exception |
| Shell response, complete browser content | Identify the resources required and compare Google's rendered output |
| Loading state in every fresh browser | API availability, routing, permissions or data-loading logic |
| Works only after another page visit | Cookie, local-storage or in-app navigation dependency |
| Missing page returns normal content with 200 | Routing and soft-404 behavior |
A locally executed example: the document loads, but the product table does not
The screenshot above uses a fictional product, N-20, in two local teaching variants. Both document responses are 200 and neither initial response contains the specification table. Variant A requires a region Cookie for its content API; variant B supplies a public default. These are local HTTP/browser observations, not a Google rendering test or a client result.
| Condition | Document | Content API | Observed result |
|---|---|---|---|
| Variant A, fresh context | 200 | 403 | No specification table |
| Variant A, region=ok Cookie set | 200 | 200 | N-20 / Blue rows appear |
| Variant B, fresh context | 200 | 200 | N-20 / Blue rows appear |
| Missing local URL, HTTP check | 404 | Not requested | Error page; no table |
The first three cases were executed for two languages and two widths, giving 12 browser contexts. The missing URL was checked separately with an HTTP request. The curl command above was exercised with the actual loopback URL substituted; example.com was not treated as a real product site. The experiment identifies a Cookie dependency in this fixture, not a Google time limit or indexing probability.
A robots.txt rule does not itself make a browser response return 403 or 404. Inspect the actual response and access rule. Also examine 200 responses: a login form, an error object or an empty shell can arrive successfully without supplying the expected content.
Compare Google's test output without mixing it with indexed status
In Search Console URL Inspection, first note the indexed information, crawl time and canonical selection. A live test answers a different question: whether the current page can be accessed and processed under that test. It does not guarantee that the URL is indexed or will be selected as canonical.
When rendered HTML, screenshots, loaded resources and JavaScript messages are available, search for the same expected text and links. Google's JavaScript troubleshooting guide recommends both URL Inspection and the Rich Results Test for examining rendering-related information.
The Rich Results Test is primarily a structured-data eligibility tool. Its tested-page output can help diagnose rendering, but “no eligible rich results” does not mean the page's text is invisible, and valid markup does not establish actual search appearance.
Use a JavaScript crawler to check the affected template
Once one failure is understood, test a bounded set of related URLs. In Screaming Frog, configure JavaScript rendering and store both original and rendered HTML as described in its official JavaScript crawling tutorial. Compare the content and link differences and review blocked resources.
The crawler's AJAX timeout and viewport are local test settings. Adjust them when investigating a slow or incomplete capture, but do not publish those settings as Google's fixed render deadline. Keep the crawl within an appropriate authorized scope and rate.
Turn the observations into a reproducible repair
A useful issue report contains the URL and template, expected text or link, initial response, observed DOM, failed request or exception, and the conditions needed to reproduce it. “The page has 20% more text after rendering” is less useful than “the product specification table is absent because this request returns 403.” A 403 still needs investigation; it does not by itself identify which server or security rule caused it.
For example, if a content API is reachable only after a region selector saves a cookie, test a fresh direct request and provide an appropriate public default. If an initial noindex is later removed by JavaScript, correct the initial indexing instruction for pages intended to be indexed. Do not remove legitimate controls from private content.
After the fix, repeat the same comparisons and check a neighboring route and an error state. If the issue is architectural, the Vue and React rendering decision guide explains when static, server-side and hybrid approaches may fit. Technical success should then be followed by observation of Google's later crawl and index state, separately from ranking or traffic outcomes.
Google’s JavaScript basics describes crawling, rendering and indexing as distinct phases. A local browser result cannot establish completion of all three. For a bilingual project, the Chinese rendering diagnostic uses the same fixture and checks. Guangsuan’s site-wide SEO service coordinates technical work, content and backlink resources when the issue extends beyond a single template.