Use the URL Inspection tool's Live Test feature in Search Console to render a representative page and compare the rendered HTML against the raw server response
Identify critical content or links that appear only after client-side JavaScript execution and confirm they are present in the rendered DOM snapshot shown by the inspection tool
Test lazy-loaded images by confirming they have explicit width and height attributes and are within the initial viewport or use loading=eager for above-the-fold images
Check that internal links are standard HTML anchor tags with href attributes pointing to canonical URLs; JavaScript-only navigation using onclick or history.pushState without corresponding href values may not be followed by Googlebot
Consider server-side rendering (SSR) or dynamic rendering for content that is critical for indexing but depends heavily on client-side data fetching
Known gotchas
Googlebot executes JavaScript but processes pages in a queue rather than in real time; there can be a significant delay between first crawl and JavaScript rendering, meaning freshly published JS-rendered content may not be indexed for days
Resources blocked by robots.txt that are required for JavaScript execution will cause rendering failures; ensure that JS files, CSS, and API endpoints called during rendering are not disallowed in robots.txt
Single-page applications that use fragment-based routing (e.g., /#/page) cannot be crawled as distinct URLs; each indexable URL must have a distinct full path accessible via a server-side route
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp