JavaScript SEO Project
A hands-on browser experiment testing what changes when JavaScript is disabled — and what that can mean for rendering, crawlability, content visibility, and internal linking.
Testing the JavaScript dependency
This project was created to move beyond theory and observe website behavior directly in a real browser environment.
I compared pages with JavaScript enabled and disabled, then documented the visible differences. The purpose was not to claim that disabling JavaScript perfectly reproduces a search-engine crawler, but to use it as a practical diagnostic signal for how dependent a page may be on client-side rendering.
Objective
Identify visible changes caused by disabling JavaScript and understand the SEO risks that can arise when important content or links depend on JavaScript rendering.
Load the page with JavaScript enabled
Open the target page normally and capture the rendered experience.
Disable JavaScript
Use the browser's JavaScript switcher to disable JavaScript for the test environment.
Reload the same page
Compare what remains available when client-side JavaScript execution is unavailable.
Capture visual evidence
Save screenshots for both states and document notable differences.
Interpret the SEO implications
Assess whether important content, navigation, links, or functionality appears dependent on JavaScript.
What the browser showed
The screenshots below are the original evidence captured during the live test.
Nomad Goods — JavaScript ON
Nomad Goods — JavaScript OFF
Notion — JavaScript ON
Notion — JavaScript OFF
Why JavaScript can become an SEO issue
1. Rendering dependency
If important page content only appears after JavaScript executes, the page becomes more dependent on rendering before that content can be fully understood.
2. Internal links
If navigation or contextual links are created only after JavaScript runs, important discovery paths may be harder to process consistently.
3. Content visibility
SEO-critical copy, headings, product information, or supporting content should not unnecessarily depend on client-side execution.
4. Crawl efficiency
Large JavaScript workloads can add complexity to crawling and rendering. Efficient HTML delivery reduces unnecessary dependency.
5. Progressive enhancement
Core content and meaningful links should remain available in the initial HTML whenever practical, while JavaScript enhances the experience.
6. Debugging matters
A simple JavaScript-off test can reveal issues worth investigating with source HTML, rendered HTML, crawl tools, and Search Console data.
| Test | Observation | SEO interpretation |
|---|---|---|
| Nomad Goods · JS ON | Normal rendered experience captured. | Baseline for comparison. |
| Nomad Goods · JS OFF | Page behavior changed materially in the test environment. | Indicates that JavaScript is important to the page experience and warrants deeper rendering/HTML inspection. |
| Notion · JS ON | Normal rendered experience captured. | Baseline for comparison. |
| Notion · JS OFF | No obvious visual change in this test. | Shows that a visible JS-off failure is not universal; further technical checks are needed to determine how JavaScript is used underneath. |
What an SEO team should check
Keep critical content in the HTML
Make important text, headings, product information, and other indexable content available without unnecessary client-side dependency.
Make links crawlable
Use standard HTML links with meaningful destinations and anchor text. Do not rely exclusively on click handlers to create important navigation.
Compare source vs. rendered HTML
Use technical SEO tools and browser inspection to determine whether important content and links exist in the HTML delivered and rendered.
Test important templates
Repeat the test across product, category, blog, and landing-page templates rather than relying on a single URL.
Validate with real crawl data
Use crawling and search-performance data to validate whether the observed implementation creates a real discoverability or indexing problem.
Use JavaScript as enhancement
JavaScript can power rich experiences. The goal is not to eliminate it, but to avoid making SEO-critical resources unnecessarily dependent on it.
JavaScript isn't automatically bad for SEO. Dependency is the thing to investigate.
A JavaScript-off experiment is a useful first diagnostic step. When something disappears or breaks, the next question is: Is that element important for users, crawling, discovery, indexing, or conversion?
Project type
Live technical SEO experiment
Primary focus
JavaScript rendering, content visibility, internal linking and crawlability
Test subjects
Nomad Goods and Notion
Evidence
Four original screenshots captured during the experiment