Chris Spann is Ar WaithBack to slides

Presenter instructions

1. Client rendering

  1. Open the JavaScript page and let it load.
  2. View Page Source: the body has only an empty app container and no article or links.
  3. Inspect the live DOM: the article and links now exist.
  4. In Network, inspect the separate JavaScript and JSON requests.
  5. Disable JavaScript in Firefox’s developer-tools settings and reload. The page goes blank. Re-enable it afterwards.

Teaching point: a plain HTML fetch and a browser that runs scripts receive different amounts of usable content. Google can render JavaScript; this example does not prove that client-rendered pages cannot be indexed.

2. Interaction-dependent navigation

  1. Reload the navigation example. Search the Inspector for guide-nav. It does not exist.
  2. Wait a moment. Rendering alone still does not add the navigation.
  3. Click “Open guides menu”. Three links are created.
  4. Close it. The links are removed again.
  5. Open the comparison: its menu starts collapsed, but the links already exist in the HTML.

Teaching point: hidden presentation and missing link markup are different problems. Google generally does not interact with a page to load content. The linked guides might still be discovered through another route.

3. Real redirects

  1. Open Network and enable Persist Logs. Clear the log.
  2. Follow the chain. Inspect the three 301 responses and their Location headers, then the final 200.
  3. Return to the example and follow the direct route: one 301, then the same final 200.
  4. Use the measurement buttons for a readable list of actual server responses.

Teaching point: redirect chains add requests. They do not automatically mean a penalty or a fixed amount of lost ranking value.

4. Useful speed work

Open the speed examples. Compare each bad version with its good version and reload to replay. Image: compare actual bytes in Network, using the same throttling. Content: compare initial HTML with the delayed JSON, then try the separate slow-server route. Clicks: start the calculation and immediately try the counter or typing. Layout: reload and watch the article when the banner arrives. The delays are controlled teaching examples, not field performance measurements.

5. Pagination crawl trap

Open the broken archive. Follow Next through pages 1–4: there are only six articles, but the fourth page still returns 200 and links onward. Try page 1,000. Compare the fixed archive: page 3 has no Next link and page 4 returns a real 404. The links exist in the initial HTML. Google might stop crawling or treat empty pages as soft 404s; do not promise infinite crawling.

Using these examples

These examples run on this website. Open the slides and demonstrations in separate tabs. The examples deliberately send noindex and no-store headers; the broken versions are teaching fixtures. You do not need to start a local server.

Sources

Google: JavaScript SEO basics · Google: interaction and incremental loading · Google: redirects