The Fix Library
Real Errors. Real Fixes. Documented As We Solve Them.
Every post here is one production problem we actually hit and fixed — the exact error message, the real cause (including the ones tutorials skip), and the step-by-step solution. No fluff, no 'try clearing your cache'.
Indexing & SEO
Page indexing: Discovered – currently not indexed URL is unknown to Google Sitemap: 129 submitted · 0 indexed
How to Fix Pages Not Getting Indexed in Google Search Console
Search Console shows "Discovered – currently not indexed" or "URL is unknown to Google", and your sitemap sits at 0 indexed. Here is the diagnostic order that finds the real cause — including two duplicate-content traps most sites have without knowing.
Read the fix
Google Search Console → AMP No AMP pages detected on this site. (old tutorials: "You MUST add AMP for mobile rankings!")
AMP Pages in 2026: Why "None Detected" Is Good News (and How to Remove Them Safely)
Google Search Console flags "no AMP pages" and every old tutorial says you're leaving mobile traffic on the table. In 2026, the opposite is true: AMP earns nothing, costs maintenance, and doubles your URL count. Here is the evidence — and the safe removal procedure if you still run it.
Read the fix
Search Console → robots.txt report Warning — Rule ignored by Googlebot (line 30) Content-Signal: search=yes,ai-train=no,use=reference
How to Fix "Rule Ignored by Googlebot" — the Content-Signal robots.txt Warning
A robots.txt warning on a line you never wrote: "Content-Signal: search=yes,ai-train=no". Cloudflare injected it, Google doesn't recognize it, and the warning is cosmetic — but the decision behind it (AI search visibility vs. training opt-out) is worth making deliberately.
Read the fix
Performance
Lighthouse Performance: 54 Total Blocking Time: 2,140 ms Largest Contentful Paint: 5.8 s "Reduce unused JavaScript — potential savings of 1,240 KiB"
Why Your Lighthouse Score Is Stuck (and the Site Architecture That Fixes It)
You compressed the images, added lazy-loading, installed the caching plugin — and Performance is still stuck in the 50s or 60s. That is not a tuning problem, it is an architecture ceiling. Here is how to diagnose it and what actually fixes it.
Read the fix
Use efficient cache lifetimes — Est savings of 509 KiB fbevents.js — Cache TTL: 20m js.hs-analytics.net — Cache TTL: 5m static.hsappstatic.net — Cache TTL: 1m First-party assets — Cache TTL: 14d
How to Fix "Use Efficient Cache Lifetimes" — the Honest Version
Lighthouse says you could save 500 KiB with better cache lifetimes — but Facebook, HubSpot, and LinkedIn set those headers on their own servers, and your platform sets yours. Here is what is genuinely actionable in this audit (more than you'd think, just not where the audit points).
Read the fix
Issues were logged in the Issues panel in Chrome Devtools Issues logged to the Issues panel in Chrome DevTools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Issue type: Cookie /video-preloader/38093 (play.hubspotvideo.com)
How to Fix "Issues were logged in the Issues panel in Chrome DevTools"
Your Best Practices score is stuck because a video embed — HubSpot, YouTube, Vimeo — sets a third-party cookie the moment the page loads. You cannot fix cookie headers you do not control. What you can do is stop loading the player until someone actually clicks play. Copy-paste facade code for HubSpot video and YouTube inside.
Read the fix
Uses deprecated APIs — 2 warnings found Attribution Reporting is deprecated and will be removed. /li.lms-analytics/insight.old.min.js (snap.licdn.com) Unload event listeners are deprecated and will be removed. blob:https://www.yoursite.com/8e015f4b-... (1st party) Browser errors were logged to the console bat.bing.com — Failed to load resource: 400 (Bad Request)
How to Fix "Uses deprecated APIs" When the Deprecated Code Belongs to Your Ad Tags
Attribution Reporting is deprecated (LinkedIn). Unload event listeners are deprecated (a mystery blob: script). A 400 from bat.bing.com in the console. None of it is your code — it all ships inside marketing tags you cannot edit. Here is the one deferral gate that clears all three audits at once, how to add ANY troublesome script to it, and the hidden duplicate-tag trap that almost kept our score off 100.
Read the fix
Image elements do not have explicit width and height Set an explicit width and height on image elements to reduce layout shifts and improve CLS. <img class="home_tabs_main_image" src="/hubfs/hr-solutions.webp" alt="HR Software and Solutions" loading="lazy">
How to Fix "Image elements do not have explicit width and height"
Every image without width and height attributes is a surprise the browser discovers mid-load: it lays out the page, the image arrives, and everything below it jumps. That jump is Cumulative Layout Shift — a Core Web Vitals metric Google actually ranks you on. The fix is two attributes per image, and no, they will not break your responsive layout. Here is why they matter, every reason to add them, and how to find the images missing them in one paste.
Read the fix
Your Meta Pixel hasn't received any activity in the last 7 days. Events Manager — no recent activity detected for pixel.
How to Verify Your Tracking Tags Are Actually Firing
The most expensive analytics failure is the silent one: the script is on your page, but no data ever leaves. Here is why tags break after any website change, how to verify them at the network level, and the free tool that does it in 90 seconds.
Read the fix
Accessibility
Accessibility — Image elements do not have [alt] attributes Informative elements should aim for short, descriptive alternate text. Failing Elements: img.vpm-badge (×4)
How to Fix "Image Elements Do Not Have [alt] Attributes"
Alt text is the highest-value, lowest-effort fix in any accessibility audit: it serves screen-reader users, replaces broken images, and hands Google a plain-text description of every image. Here is how to write it, when to leave it empty on purpose, and where the setting hides on every major platform.
Read the fix
Buttons must have discernible text Failing: button.hamburger — <button class="hamburger" type="button"> Links must have discernible text Failing: ul.footer__social > a — <a href="https://www.linkedin.com/company/…" target="_blank">
How to Fix "Buttons Must Have Discernible Text" (and Why AI Agents Care Too)
Your hamburger menu and social icons look obvious — but in the accessibility tree they are nameless buttons and empty links. Screen readers announce them as "button" and nothing more, and AI browsing agents can't operate them either. The fix is usually one attribute.
Read the fix
Heading elements are not in a sequentially-descending order Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. <h4 class="eyebrow">TURN VISION INTO VALUE</h4> <h2>Your partner for digital transformation</h2>
How to Fix "Heading elements are not in a sequentially-descending order"
Your Accessibility score is stuck because an H4 appears right before an H2 — and nine times out of ten the culprit is a decorative "eyebrow" label (the small ALL-CAPS line above a big headline) that someone marked up as a heading to make it look right. Headings are structure, not styling. Here is why the order matters and the two-minute fix.
Read the fix
Free · 60 seconds · no signup
Get your site audited like these
Every fix in this library started with an audit. Run our free analyzer and get your site's real Lighthouse scores — performance, accessibility, SEO — plus the specific issues holding it back, reviewed by a human before it reaches you.
Hit an error that isn't here yet?
Send us the exact error message. If we can solve it, we'll fix it with you — and it becomes the next post in the library so the next person doesn't lose their afternoon to it. And if you're troubleshooting with AI tools yourself, read our guide on working with AI the right way first — it will save you from the confident wrong answers.