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.
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.
- Choose samples across templates and meaningful route states.
- Name the essential content and links for each sample.
- Use the same samples throughout the source-versus-rendered comparison.
More help and optional notes
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.
Changing this result updates your checkmark and progress immediately. Notes are optional.

