Blog / Technical SEO /

A workflow for reviewing important pages with JavaScript disabled

The product page looks perfect in your browser. Turn JavaScript off and the description vanishes. Just a polite blank space where the selling should be.

Checking a page with scripts disabled shows you which content depends on client-side code. It’s a useful diagnostic. It isn’t a full simulation of how every search engine reads your site.

So use the test to answer one specific question: can the essential content and navigation still be found, and what changes when scripts don’t run? Then compare what you see with the rendered output and the page’s purpose.

Choose representative pages

Start with important templates, not random URLs. Pick examples like a product, collection, article, service page or key form. Include a page with a distinctive component, such as a tabbed description or filter, if that behaviour matters to users. On a client audit, I usually begin with the product template, because that’s where missing content costs the most.

Write down what must stay available: page title, main content, price or product details, links, canonical and primary actions. Not every interaction needs to work without JavaScript. The question is whether essential information and routes disappear, or whether the page degrades sensibly.

Record the URL, browser and test date. Extensions and browser settings can affect what you see, so make the test repeatable. If several people are investigating, agree on the same steps and note any differences.

Disable scripts and inspect the page

Use a browser’s site settings or a trusted testing method to disable JavaScript for the page. Reload it rather than assuming the current content will disappear. Observe what remains, what changes and whether the page shows a useful fallback.

Check more than the first screen. Scroll through the content, open navigation where possible and inspect links. A page can have a visible heading but still hide the substantive text behind a script. Conversely, a script-dependent filter may fail while the underlying collection links remain available.

Note the exact behaviour without jumping to conclusions. “The description is missing when scripts are disabled” is an observation. “Google can’t index the description” is a much bigger claim that needs more evidence. Search systems can render JavaScript, although implementation and timing matter. This simple browser test doesn’t tell you how a crawler processes the page. I try to keep those two sentences separate in every report I write.

Compare source, rendered page and expected content

Inspect the initial HTML and the browser’s rendered output where you have the tools and access to do so. Compare these views with the no-script version. Identify which component supplies the missing content and whether the content is also available through an accessible URL or HTML response.

If the page relies on a client-side request, check whether the request succeeds and whether important content appears after rendering. A slow or blocked request may create a different experience from the no-script test. Look for errors in the browser console and network panel, but do not copy sensitive data into a public issue.

Check internal links and navigation. If a menu disappears entirely without scripts, consider whether users and crawlers have another route to important pages. Do not assume that a sitemap solves every discovery or usability issue.

Judge the impact before proposing a fix

A missing decorative animation is different from a missing product description or purchase option. Prioritise by importance to the page, user task and crawlability. Ask whether the content is available in the rendered DOM, whether it can be reached without an interaction, and whether the script failure affects real visitors.

Possible fixes range from leaving a non-essential interaction alone to changing the rendering approach, improving a fallback, or fixing a blocked request. The right choice depends on the platform and the evidence. Don’t recommend server-side rendering just because one test looks sparse.

Retest after a change with scripts enabled and disabled, and on a mobile viewport. Confirm that the normal experience still works and the fallback is useful. Keep before-and-after observations in the issue record so the team can see what changed.

Make the test useful to the right team

Share findings in a way that helps a developer reproduce the behaviour. Include the page URL, browser setting, what was expected, what appeared and whether the issue happened in the rendered page with scripts enabled. A recording can help explain a sequence, but add a written note so the finding can be searched and handed over.

Prioritise a missing purchase detail or essential navigation differently from a decorative animation. Include the task the page is meant to support, such as reading an article, comparing a product or submitting an enquiry. This gives the team a reason to fix the issue rather than a screenshot without context.

After a fix, test the intended experience again and check the no-script state if the original problem concerned it. Close the issue with the observed result, not a guess about how a crawler might behave. If the result is uncertain, state what still needs a separate rendering or indexing check.

Avoid a false pass or false alarm

A browser extension that blocks scripts may also block styles, fonts or network requests, so check what the test actually disabled. Use a clean browser profile or a documented method, and repeat the check if the result surprises you. Compare with the normal page in the same browser and viewport.

A page that looks incomplete without JavaScript may still provide important content in its rendered response; a page that looks complete may rely on an interaction that does not work for a user. Write down the limitation of the test and use a separate rendering or accessibility check when the question requires it.

Testing without JavaScript uncovers fragile assumptions, but it belongs alongside other checks, not instead of them. Try it today on one page: switch scripts off in your browser’s site settings, reload, and write down what’s missing. Which important page on your site would you check first?