← All posts

FIELD GUIDE · NOVEMBER 18, 2026 · 3 MIN READ

Reading console errors when you’re not a developer

The browser console looks intimidating, but a few patterns explain most of what you will see there. A plain-language guide for designers, marketers, and site owners.

By The FeedbackDots team

View .md

TL;DR

  • The browser console records what went wrong on a page, and a few patterns explain most of it.
  • Red lines are errors, yellow are warnings, and gray is usually safe to ignore.
  • Learn the common messages: 404s, 5xx errors, undefined properties, CORS, mixed content, and CSP blocks.
  • Errors from extensions or third-party widgets often are not your problem.
  • When reporting, copy the exact text, note when it appeared, and include the page URL.

The browser console is where a web page writes down what went wrong. Developers live in it. Everyone else tends to avoid it, because it's full of red text and words like "uncaught" and "undefined."

You don't need to understand every line to get value from it. Most console messages fall into a handful of patterns, and knowing them lets you tell whether a problem is serious, who should fix it, and what to put in your bug report.

Opening the console

  • Chrome or Edge: right-click anywhere on the page, choose Inspect, then click the Console tab.
  • Safari: turn on the Develop menu in Settings → Advanced, then choose Develop → Show JavaScript Console.
  • Firefox: right-click, choose Inspect, then Console.

Reload the page with the console open so you see everything from the start.

Colors first

  • Red lines are errors. Something failed.
  • Yellow lines are warnings. Something might be wrong, or something is outdated.
  • Gray or white lines are information. Usually safe to ignore.

Start with the red ones. Warnings matter less unless they line up with the problem you're seeing.

The patterns you'll see most

"Failed to load resource: 404" A file the page asked for doesn't exist. Often an image, font, or script with the wrong address. Look at the file name: if it's your logo or a key script, that's your bug.

"Failed to load resource: 500" (or any 5xx) The server had a problem. This usually isn't about the page itself. Note the time and the address and pass it to whoever runs the backend or the hosting.

"Uncaught TypeError: Cannot read properties of undefined" A script expected some data and got nothing. This often explains features that silently do nothing, like a button that won't respond. Copy it exactly, including the file name and line number after it.

"Blocked by CORS policy" The page tried to load something from another website, and that site didn't allow it. Common after moving a site to a new domain. Usually needs a developer or a setting on the other service.

"Mixed content" The page is on https but asked for something on http. Browsers block it, so images or scripts quietly go missing. Look for old links in your content or settings.

"Refused to execute script" or "Content Security Policy" A security setting blocked a script. Common after adding a new embed or tracking code. The fix lives in your site or hosting settings, not the script.

Which errors you can ignore

Not every red line is your problem. Browser extensions, ad blockers, and third-party widgets often log errors that have nothing to do with your site. A good rule: if the file name in the error is from your domain, or the error happens right when the broken thing happens, it matters. If it's from an extension or appears on every site you visit, it probably doesn't.

What to put in the report

When you find an error that looks related, include:

  1. The exact text, copied, not retyped.
  2. When it appeared: on page load, or when you clicked something.
  3. The page URL.

That's enough for a developer, or an AI assistant, to start in the right place.

Or skip the console entirely

The reason this guide exists is that asking people to open the console is a big ask. FeedbackDots captures the page's console output with every report automatically, so the reporter never has to find it, and the person fixing the bug sees the errors next to the screenshot and the replay.

Next Wednesday: setting severity so the right bugs get fixed first.