Can Google see an H1 added by JavaScript?
Rubric check: H1 that only appears after JavaScript (check id js_only_h1)
Google usually can, once it renders the page. Most AI crawlers can't: they read the HTML your server sends, and an H1 added by script isn't there, so to them the page has no main heading.
Why it matters for SEO
Google renders JavaScript, but it can happen after the first crawl, and anything that fails to load leaves the page without a heading. Putting the H1 in the server HTML removes that risk.
This is common on single-page apps and on sites where a page builder or slider injects the hero heading with JavaScript.
Does this matter for ChatGPT and AI Overviews?
This matters more for AI search than for Google. Many AI crawlers don't run JavaScript, so the H1 is the topic signal they miss.
The main heading helps them match your page to the question before they read the body. Without it, the topic has to be guessed from the text.
How Rubric scores it
StandardStandard checks are the baseline every other tier is measured against.
Why this tier: H1 invisible without JS.
It is judged on every page Rubric scores.
Every Rubric score starts at 100. When this check fails, it takes up to 12 points off. Even one failing page costs at least 6 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 13 of 277 sites where Rubric could judge it (4.7%). That is 13 of 265 judged sites in Rubric's 313-site test set and 0 of 12 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 3 of 3. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)
Real sites: people checked 12 of its findings by hand and 3 were wrong (25%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Latest review round: 0 of 38 findings judged were still wrong after the last fix.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- View the page source (not the browser's Elements panel) and search for
<h1. - If the H1 is missing, a slider, animation or page-builder widget may be adding it with JavaScript. Replace it with a normal Heading block or widget set to H1.
- Check animation plugins that hide headings until a script runs: the heading should still be in the HTML.
Shopify
- Search View page source for
<h1. - If the hero heading comes from an app or a slideshow script, add a section with a real heading in Online Store > Themes > Customize (for example Rich text or Image with text) and check it renders as H1.
- Product and collection titles are server-rendered in most themes. Check yours hasn't been changed to load them by script.
Webflow
- Webflow renders headings in the server HTML, so check for an Embed or a script that builds the heading.
- Replace it with a native Heading element set to H1 in Element settings.
- On CMS templates, bind the H1 to the item's name field. Publish.
Custom code
Render the H1 on the server:
<h1>How to choose a hiking backpack</h1>In React, Vue or Svelte apps, use server-side rendering or static generation. Check with curl -s https://example.com/page | grep -i "<h1".