Can crawlers read a JavaScript meta description?
Rubric check: meta description that needs JavaScript (check id js_only_meta)
Google can, because it runs JavaScript before indexing. Many other crawlers, including most AI crawlers, can't. Rubric flags pages whose meta description only appears after scripts run, so the HTML your server sends has none.
Why it matters for SEO
Google renders pages, though rendering can lag behind the first crawl. Bing and other search engines are less reliable with script-built tags. A description in the server HTML is read by everyone on the first visit, so there's no gap.
Does this matter for ChatGPT and AI Overviews?
Many AI crawlers fetch the raw HTML and don't run JavaScript. For them, a page whose description is added by script has no description at all. The effect on citation is modest, since they also read the body text, but it's an easy gap to close.
How Rubric scores it
MinorMinor checks cost a quarter to a half of a standard check when they fail.
Why this tier: Meta description needs JS.
It is judged on every page Rubric scores.
Every Rubric score starts at 100. When this check fails, it takes up to 6 points off. Even one failing page costs at least 3 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.
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 8 of 277 sites where Rubric could judge it (2.9%). That is 8 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 14 of its findings by hand and 1 was wrong (7.1%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Latest review round: 0 of 13 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
- WordPress and SEO plugins such as Yoast SEO and Rank Math print the meta description in the server HTML, so standard sites pass.
- If you run WordPress headless (a separate front end), render the description on the server in that front end.
- Turn off any script or tag that rewrites the description in the browser.
Shopify
- Shopify themes print the description in the server HTML from Search engine listing, so standard stores pass.
- If an SEO app rewrites it with JavaScript, set the description in the product or page's Search engine listing instead and turn off that app feature.
- Headless storefronts (Hydrogen or other) must render it on the server.
Webflow
- Webflow prints the description from Page settings > SEO settings > Meta description in the server HTML.
- If a script in Custom code sets or changes it, remove the script and put the text in the SEO settings field. On CMS templates, bind it to a CMS field.
- Publish.
Custom code
Render the tag on the server. In Next.js, use the Metadata API rather than setting it in a client component:
export const metadata = {
description: "Waterproof hiking boots, tested on Scottish hills.",
};With other frameworks, use server-side rendering or static generation, then check "View page source" shows the tag.