ubricHelp

Why are my CSS or JavaScript files returning 404?

Rubric check: missing CSS, JavaScript or image file (check id res_broken)

A missing resource is a style sheet, script or image the page asks for that answers "not found" or a server error. The page may then look broken or lose content, for visitors and for crawlers.

Free, no card. Your report opens with this check first.

Why it matters for SEO

Google renders pages with their CSS and JavaScript to see what visitors see. If a needed file is missing, Google may see a page with no layout, missing text or a menu that never loads.

A missing image is a smaller problem, but it can't appear in image search, and a broken hero image hurts how the page looks and loads.

Does this matter for ChatGPT and AI Overviews?

Most AI crawlers read the HTML and don't run scripts, so a missing script matters less to them than to Google. It still matters when the script is what puts the text on the page.

A missing file is also a sign of an old theme or plugin left behind, which is worth cleaning up either way.

How Rubric scores it

StandardStandard checks are the baseline every other tier is measured against.

Why this tier: Missing CSS/JS/images break rendering.

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 10 of 291 sites where Rubric could judge it (3.4%). That is 10 of 278 judged sites in Rubric's 313-site test set and 0 of 13 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.

3.4% of the sites Rubric could judge have this problem. Check yours.

Free, no card. Your report opens with this check first.

How accurate the check is

Lab test: passed. On test pages built with this problem, it caught 2 of 2. On clean test pages, it stayed quiet 2 of 2 times. (Engine build d17c9d9.)

Holdout test 5 (sites the check had never seen): 0 of 13 findings judged wrong.

Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.

How to fix it

WordPress

  1. Open the page, then your browser's developer tools (Network tab) and reload. Filter by status to find the 404s.
  2. Most broken files come from a deleted plugin or an old theme. Reinstall it, or remove the code that still loads its files.
  3. If you use a caching or minify plugin (WP Rocket, Autoptimize, LiteSpeed Cache), clear its cache so it rebuilds the combined files.

Shopify

  1. Find the broken file in the browser's Network tab.
  2. If it's left over from an uninstalled app, go to Online Store > Themes > Edit code and remove the script or stylesheet tag that still loads it (often in theme.liquid).
  3. If a theme image is missing, re-upload it in the theme editor or in Content > Files.

Webflow

  1. Webflow hosts its own CSS and scripts, so a broken file is usually in custom code: check Site settings > Custom code and each page's Custom code in page settings.
  2. Remove or correct any link to a file that no longer exists.
  3. Replace missing images in the Assets panel, then publish.

Custom code

Find the failing files:

code
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/assets/app.css

Fix the path, restore the file, or remove the reference. After a build, make sure old hashed file names (like app.3f2a.js) aren't still referenced by cached HTML.

More blocked resources checks · The full AI SEO glossary

Free, no card. Your report opens with this check first.