Technical SEO · Supporting checklist

JavaScript SEO Checklist

A JavaScript SEO checklist is a technical audit workflow for checking what scripts add, change or remove from a public page. Compare the delivered HTML with rendered content, test real crawlable links, and check metadata, status handling, hydration and client-side routes. Use this JavaScript SEO audit checklist to finish with a rendered-versus-source test matrix across your key templates.

Free to useNo account neededSaved in your browser
Source and rendered page panels connected to two destination pages by continuous link routes.
Compare source and rendered content, then test crawlable links and destination routes.
Your working checklist

Work through the checklist

Click a square to mark a task as Pass. Click again to undo. Use the result menu for a problem, a blocker or a task that does not apply. You do not need to enter notes.

15 checks

Compare Delivered and Rendered Content

Delivered HTML is the response sent by the server. The rendered DOM is the document after scripts run. Compare both for representative templates, then use Google’s testing output to investigate a search-specific rendering concern.

Choose representative routes and expected content

Make the JavaScript audit cover different rendering paths.

Use this for: Sites whose public content, navigation or metadata depends on JavaScript.

Choose at least one important URL from each relevant template, such as an article, category, product and application landing page. Include a recently changed page, a deeper route and an unavailable item where those states exist. A passing homepage cannot establish how another template behaves.

For each sample, decide what should appear without logging in or taking another action: the page heading, useful main text, key item details and links to the next relevant pages. Keep that short expectation beside the route so the source and rendered views can be compared meaningfully.

Example

Hypothetical example: A course site tests the course catalog, a course detail page and a withdrawn course. Each has a different expected content and response state.

  1. Choose samples across templates and meaningful route states.
  2. Name the essential content and links for each sample.
  3. Use the same samples throughout the source-versus-rendered comparison.
More help and optional notesHigh · SEO lead and developer
PassThe sample covers the relevant templates and states with a clear expected result for each.
FailOnly a convenient page is tested while materially different templates or error routes are omitted.

If it fails: Add the missing template or state before generalizing the result.

Retest: Refresh the sample when routing, templates or rendering behavior changes.

Not applicable: The site has no JavaScript-dependent content, routing or metadata to review.

Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Read the original HTML response for each route

Identify which useful content and signals depend on script execution.

Use this for: Every sampled public route.

In a private browser window, open Developer Tools → Network, reload the exact URL and select the main document request. Read its status, headers and Response tab. Search the response for the page’s heading, a distinctive main-content sentence, title, canonical and robots declarations.

Distinguish actual HTML text and links from content stored only inside a script or data object. Missing main text in the response establishes JavaScript dependence; it does not by itself prove Google cannot render or index the page. Keep the response result separate from the next rendered check.

Example

Hypothetical example: The response contains a product name inside a JSON object but the visible product heading is built later by JavaScript. That is not the same as a ready HTML heading.

  1. Reload the direct URL with Network open.
  2. Read the main document’s response, status and relevant headers.
  3. Identify which expected content is present as HTML and which depends on JavaScript.
More help and optional notesHigh · SEO analyst or developer
PassThe original response is understood and any JavaScript-dependent essentials are identified for rendered testing.
FailA shell or data object is mistaken for visible HTML, or the response serves an unintended page.

If it fails: Correct the route response where wrong, then test the actual rendered content.

Retest: Reload the same direct route after the fix and inspect its response again.

Not applicable: No URLs in the stated scope.

Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check the rendered HTML in Google’s testing output

Find content or resource differences that a normal browser view may miss.

Use this for: Public routes with a suspected Google rendering issue.

For a public page you are authorized to inspect, open URL Inspection in Search Console and run a live test. Open the tested-page details to review rendered HTML, screenshot and available resource/error information. The Rich Results Test can provide rendered output for a public URL when Search Console access is unavailable.

Search the rendered HTML for the exact expected heading, main-content sentence and a key link. Compare the test time and tested URL with your browser sample. A live test describes that fetch; it is not proof that the same version is indexed, and a rich-result eligibility result is a separate question.

Example

Hypothetical example: A course description appears in the normal browser but is absent from the tested HTML, where its API request failed. Investigate that dependency rather than declaring the whole framework unusable.

  1. Run an available Google live rendering test for the sampled public URL.
  2. Search rendered HTML for the expected content and links.
  3. Inspect resource failures and compare the result with the original response.
More help and optional notesHigh · SEO analyst and developer

Before you begin: Access to an appropriate Google testing tool for the public URL.

PassThe expected main content and links appear in the tested rendered HTML, with relevant failures resolved.
FailThe tested output omits or replaces essential content or links.

If it fails: Trace the missing content to its script, API, state or access dependency and repair that cause.

Retest: Repeat the same test after repair and separately review the later indexing record if needed.

Not applicable: No URLs in the stated scope.

Keep in mind: A local crawler rendering result is another diagnostic view; it does not reproduce every Google rendering condition.

Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Find required scripts and data requests that fail

Identify the dependency that prevents essential content from rendering.

Use this for: Routes with missing content or failed required resources.

In the browser’s Network and Console panels, reload a failing sample and look for failed JavaScript chunks, CSS or data requests that supply the missing content. Use the request’s initiator and error details to identify the responsible component. Compare those failures with the tested-page resource information.

Test the public route in a fresh session. Main content should not require a previous page visit, saved browser storage, a location permission or a button press. Ask the developer to provide an appropriate public content path or fallback; do not expose private APIs, credentials or restricted account data to solve a rendering issue.

Example

Hypothetical example: A store description loads only after a saved location preference is read. A direct fresh visit stays blank, so the template needs useful public content before optional personalization.

  1. Reload the failing route and find its relevant request or console error.
  2. Repeat in a fresh session without prior stored state.
  3. Repair the dependency or provide an appropriate content fallback.
More help and optional notesHigh · Developer
PassEssential public content loads without a failing required dependency or prior-session state.
FailA required request, permission or saved state prevents the intended public content from appearing.

If it fails: Fix the actual dependency and keep private services protected.

Retest: Repeat the fresh-session and Google rendered-output checks.

Not applicable: No URLs in the stated scope.

Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Keep essential content stable through hydration

Check that client code preserves the useful server-rendered page.

Use this for: Server-rendered or pre-rendered pages that hydrate on the client.

On a server-rendered or pre-rendered route, compare the document response with the page after scripts initialize. Hydration attaches interactive behavior to that initial HTML. Watch whether the main text, item details or navigation disappear, switch to another item or stay replaced by a loading shell.

Review the console with the developer for hydration mismatch errors. Align the initial client data with the server output and move browser-only decisions out of the initial content render where appropriate. Cosmetic differences need different priority from losing the product name or description.

Example

Hypothetical example: The server sends a workshop’s description, but client initialization replaces it with an empty loading state when an optional request fails. The description should remain usable.

  1. Compare the response content with the page after initialization.
  2. Check console errors and identify a content-changing mismatch.
  3. Repair the shared initial state and repeat the direct visit.
More help and optional notesHigh · Developer
PassEssential content and links remain correct after hydration.
FailHydration removes, misidentifies or leaves essential content unavailable.

If it fails: Align server/client initial data and repair the component that replaces the correct content.

Retest: Test a fresh direct load and a client-side visit to the same route after repair.

Not applicable: The route does not hydrate server-rendered or pre-rendered HTML.

Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Test Deferred Content and Release Changes

Deferred loading and deployment changes can alter what a fresh visitor or renderer receives. Test the useful page content through these conditions without expanding this audit into every performance metric.

Expose useful content without requiring a click or scroll gesture

Keep deferred loading from hiding the page’s essential answer.

Use this for: Lazy-loaded text, accordions, tabs, media or content behind optional prompts.

Load a sample without clicking, accepting optional prompts or scrolling manually. Check whether the main content arrives and inspect the rendered HTML from the Google test. Google Search does not interact with a page like a user, so do not make the only copy of important text depend on a user action.

For appropriate below-the-fold media, use loading behavior that works when the content enters the viewport and test it. A collapsed section with its text already present in the document is different from an empty section whose content is fetched only after a click.

Example

Hypothetical example: A details accordion already contains the course syllabus in HTML and only changes visibility. Another accordion fetches all syllabus text after clicking; that second pattern needs a crawlable content path.

  1. Load the route without interacting and inspect its essential content.
  2. Compare the relevant text with tested rendered HTML.
  3. Repair interaction-only dependencies while preserving useful interface behavior.
More help and optional notesHigh · Developer
PassEssential content is available to the tested renderer without requiring a user interaction.
FailThe only useful content or navigation is fetched exclusively after a click, gesture or optional permission.

If it fails: Render the essential content or provide a non-interaction-dependent public route for it.

Retest: Repeat the no-interaction load and rendered-HTML check.

Not applicable: No deferred or interaction-loaded content is used.

Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Give infinite-scroll content persistent linked pages

Make later items accessible outside a scrolling session.

Use this for: Infinite-scroll or load-more listings containing items intended to be discoverable.

If a listing loads more results as you scroll, find the URL for a later group of items and open it directly. It should consistently show that group with a stable address. Inspect whether normal anchors connect the sequential pages.

Keep the enhanced scroll experience if it helps visitors, but provide the paginated route underneath it. Do not rely only on a button whose destination exists in JavaScript state or on a relative date label that changes which items the URL represents.

Example

Hypothetical example: A class directory loads the next 20 cards only after scrolling. A stable second-page route and linked pagination make that later group independently reachable.

  1. Find the address for a later result group.
  2. Open it directly and confirm the expected items.
  3. Inspect sequential page links and repair missing routes or anchors.
More help and optional notesHigh · Developer
PassLater result groups have stable working URLs connected by crawlable links.
FailLater items exist only in an interactive session or lack a stable linked route.

If it fails: Implement persistent paginated routes and expose their links alongside the enhanced listing.

Retest: Open early and later pages directly and follow the sequential links.

Not applicable: No infinite-scroll or load-more listing is used.

Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Keep generated structured data aligned with the page

Catch stale or missing structured data after route and content changes.

Use this for: Routes that generate or update structured data with JavaScript.

If JavaScript generates structured data, inspect the rendered document for the expected JSON-LD and run the relevant supported test. Compare its page identity and properties with the visible content on that exact route.

Navigate to a second item and check that data from the first one is replaced appropriately. Do not add a supported-looking type or property solely to make a test green. Mark this task Not applicable when the site has no relevant structured data implementation.

Example

Hypothetical example: A course route changes its visible name, but the generated data still describes the previous course. Fix the shared route state so both describe the same item.

  1. Inspect generated data in the rendered document.
  2. Compare its identity and facts with visible content.
  3. Test a route transition and correct stale or unsupported properties.
More help and optional notesHigh · Developer and SEO lead
PassThe tested generated data describes the correct visible page and has no relevant validation error.
FailGenerated data is absent, invalid or describes stale/different content.

If it fails: Correct the route-bound data generation using supported properties and visible facts.

Retest: Repeat validation and a transition to another representative route.

Not applicable: No relevant structured data is generated with JavaScript.

Keep in mind: Valid structured data does not guarantee a rich result.

Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check that a release serves the matching JavaScript files

Find stale or missing assets that break otherwise correct templates.

Use this for: JavaScript deployments that change bundled scripts or route chunks.

After a JavaScript release, open a representative deep route in a fresh session and inspect its script requests. Check for missing chunk files, an HTML error page returned as a script or old code paired with new page data. Repeat from an already open session if the application supports long-lived visits.

Ask the developer to use content-versioned asset names and a deployment strategy that keeps referenced assets available. When only one rendering view is stale, compare the actual script versions before repeatedly changing page content. Do not assume disabling the browser cache changes Google’s resource cache.

Example

Hypothetical example: A visitor with an older open catalog clicks a course after deployment. The app requests an old chunk that was removed, leaving the page blank. The release needs compatible asset availability.

  1. Check script responses after the release on direct and ongoing-session visits.
  2. Compare loaded asset versions with the deployed page.
  3. Repair missing/stale asset handling and retest the route.
More help and optional notesHigh · Developer
PassThe sampled entry paths load matching available assets and render the intended page.
FailMissing or stale scripts break essential content after deployment.

If it fails: Correct asset versioning and release compatibility for the affected bundle or route.

Retest: Repeat fresh and existing-session visits after the release repair.

Not applicable: No relevant JavaScript release or asset-version issue is in scope.

Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Retest the source-versus-rendered matrix after fixes

Verify the repaired behavior across the templates it affects.

Use this for: Any JavaScript SEO implementation change.

Repeat the same direct-load, client-navigation and rendered-output checks for each affected template. Compare essential content, links, metadata, directives and response/error states with the expected result. Keep the original failing route and an unaffected route in the sample.

If rendering remains unreliable, discuss an appropriate server-rendered or statically generated content path with the developer. Client-side rendering is not an automatic failure, and changing frameworks is not the default fix. Choose the smallest implementation change that makes the required public content reliable.

Example

Hypothetical example: Fixing shared route state restores the description, title and canonical on several course pages. The team repeats direct and client-side visits plus a missing-course case before closing the issue.

  1. Repeat the same checks on the original failing samples.
  2. Test other routes using the repaired component and an unaffected example.
  3. Close the rendering finding only for the behavior actually retested.
More help and optional notesHigh · SEO lead and developer
PassThe repaired templates satisfy their expected source/rendered/route outcomes in the completed tests.
FailThe original rendering defect persists or the shared fix introduces a route regression.

If it fails: Repair the remaining component issue and repeat the affected matrix rows.

Retest: Recheck relevant template rows after future routing, rendering or major asset changes.

Not applicable: No JavaScript SEO change has been made yet.

Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Reset this checklist?

This removes saved statuses, evidence and result dates for the checks on this page. Other checklists keep their records. Export a CSV first if you need a copy.

A useful result, every time

Check a task. Choose a result.

This is a manual SEO workflow. It helps you decide what to investigate and keep a usable record. It does not crawl your website or verify your answers automatically.

  1. Choose your scope. Pick the relevant task group and representative pages you are authorized to inspect.
  2. Run the stated check. Follow the steps, then choose your result. Click the square for Pass, or use the result menu for another status. You do not need to type anything.
  3. Assign the next action. Fix a problem when you can, or ask the right person for help. Optional notes can remind you what to do next. Check the result again after a fix.

What your progress means

Review progress counts passes and failures against applicable checks. Failed work still counts as reviewed. Blocked and untested checks remain unfinished. This is not an SEO score.

Untested
You have not checked this yet.
Pass
You checked it and it works as described.
Fail
You checked it and found something to fix.
Blocked
You need access, information or someone’s help.
Not applicable
This task does not apply to your website.

Export CSV downloads the checks currently shown and any optional notes. Print expands the instructions for that view. Saved results stay in this browser; there is no account sync.

Apply the workflow

What Should You Do With the JavaScript SEO Results?

Turn differences between the response, rendered document and route transitions into a concrete repair and a repeatable template test.

What Goes in a Rendered-Versus-Source Test Matrix?

A rendered-versus-source test matrix compares the same route across the server response, rendered document and client navigation. Give each row an expected result so a difference has a clear meaning.

Use this hypothetical format in your own spreadsheet or issue tracker. Add the test date and the rendering tool you actually used. The checklist’s Export CSV saves the checklist view and optional notes; it does not fetch your pages or create this matrix automatically.

Hypothetical template checks and the repair each result suggests.
Route stateOriginal responseRendered / navigation resultDecision
Course detail, direct load.Title and course text present.Hydration leaves the same useful content.Keep; retest when this template changes.
Category to course transition.Direct course response is correct.Client navigation keeps the category canonical.Repair route-bound head updates.
Unknown course.Document returns 200.App shows a not-found message.Implement appropriate error response or supported error-state handling.
Later listing page.A stable page URL exists.Only a button exposes later items; no destination anchor.Add sequential links to the persistent pages.

Does Every JavaScript Site Need Server-Side Rendering?

Not every JavaScript site needs server-side rendering to be eligible for Google Search. Google renders JavaScript, but the actual content, links and signals still need to survive its rendering process. A reliable client-rendered route and a broken server-rendered route should be judged by their observed behavior.

Server rendering or static generation can reduce dependence on client execution and help visitors or crawlers that do not execute JavaScript. Consider the site’s content freshness, infrastructure and audience with the developer. A rendering architecture alone does not guarantee indexing or rankings.

Which Checklist Handles a Related JavaScript Finding?

Use the specialist workflow for the underlying signal or route decision, then return here to confirm that JavaScript preserves the result after rendering and navigation.

Continue With a Focused Technical Review

Use the workflow that matches the discovery, rendering or delivery issue you are investigating.

A clear process, with honest limits.

Follow the steps, choose the result that matches what you found, and check again after changes. Notes are optional. A completed check does not guarantee indexing, traffic or rankings. How the checklists work.