SEO & AI Fix Guides
Clear, practical fixes for the issues our audit flags — classic on-page and technical SEO, Core Web Vitals, and the newer AI answer-engine checks (AEO/GEO).
On-Page SEO
How to Fix a Missing Meta Description
A missing meta description means your page's <head> has no <meta name="description"> tag, so Google and other engines auto-generate the snippet shown under your title in search results. Writing a concise, accurate description of 150-160 characters per page gives you control over that snippet, improves click-through, and helps AI answer engines summarize your page correctly.
How to Fix a Meta Description That's Too Long
A "meta description too long" notice means your page's meta description exceeds the width Google renders in search results, so the tail gets cut with an ellipsis. It's a low-severity, cosmetic issue that won't hurt rankings, but a truncated description weakens your click-through pitch and can lop off your call to action. The fix is simple: trim the description to fit the visible window and keep the compelling part up front.
How to Fix a Title Tag That's Too Long
A "title tag too long" notice means your page's <title> is likely to be cut off in search results because it runs wider than Google's display area, roughly 600 pixels or about 50 to 60 characters on desktop. The fix is to rewrite the title so the important keyword and value sit inside that visible range, then update it in your CMS or template and confirm it in the page source.
How to Fix a Title Tag That's Too Short
A "title tag too short" warning means the <title> element on this page falls below the useful range (roughly 30-60 characters). Short titles waste prime SERP space, give Google and AI answer engines too little to work with, and get rewritten by Google far more often than well-sized titles. The fix is to rewrite the title so it clearly describes the page, leads with the primary keyword, and fills more of the ~600-pixel space Google displays on desktop.
How to Fix a Missing Title Tag (Step by Step)
Your page has no HTML title tag (the <title> element inside <head>). This is the most important on-page tag for both rankings and click-through, and its absence is critical but quick to fix. Add one unique, descriptive title per page, front-loaded with the main topic and kept to roughly 50-60 characters. On most platforms the fix takes a few minutes.
How to Fix a Missing H1 Tag
Your page has no usable H1 heading, the single clearest label that tells search engines and AI crawlers what the page is about. This guide explains what the H1 is, why a missing one hurts rankings and AI visibility, and how to add one correctly on any platform.
How to Fix Multiple H1 Tags on a Page
Your page has more than one h1 element. Google says multiple H1s won't directly hurt your rankings, but one clear H1 per page is still best practice: it states the page's primary topic for search engines, AI answer engines, and screen-reader users. This guide shows you how to find the extra H1s and fix them across common platforms.
How to Fix Missing Open Graph Tags
Your page has no Open Graph (og:) meta tags, so when someone shares its URL on LinkedIn, Slack, WhatsApp, X, or Facebook, the preview renders with no title, no description, and no image. That same head-level metadata is read by AI answer engines and their crawlers, so weak OG data also weakens how your page appears when ChatGPT, Perplexity, or Google AI Overviews summarize or cite it. This is a notice-level issue that does not directly affect Google rankings, but it lowers click-through on shared links, where a lot of qualified traffic starts. The fix is one-time: add four required og: tags plus a couple of recommended ones to your page head, point og:image at a 1200x630 image, and re-scrape the URL in the platform debuggers.
Fix Missing Doctype: Stop Quirks Mode
Your page is missing the <!DOCTYPE html> declaration at the very top of its HTML. Without it, browsers fall back to quirks mode, a legacy rendering path that emulates old browser bugs and changes how the CSS box model, layout, and inheritance behave. The fix is a single line placed as the first characters of the page.
Fix Missing Charset Declaration (meta charset UTF-8)
A missing charset declaration means your page never tells the browser which character encoding to use, so it guesses. When the guess is wrong you get garbled text (mojibake), broken symbols, and rendering that varies by browser. The fix is one tag: add <meta charset="UTF-8"> as the first element inside <head>, within the first 1024 bytes of the HTML.
Fix Multiple Title or Meta Description Tags
Your page's HTML contains more than one <title> element or more than one <meta name="description"> tag. A page should have exactly one of each. Search engines keep one and ignore the rest, but you don't fully control which one they keep, so the snippet Google or an AI engine shows can come from the wrong tag. This almost always happens when two systems inject metadata at once: a theme plus an SEO plugin, a layout template plus a page override, or a hardcoded tag next to a dynamic one. The fix is to find the second source and remove it so one canonical tag remains.
Fix Meta Refresh Redirects: Use a 301 Instead
A meta refresh redirect uses an HTML tag to bounce visitors to another URL after the page loads, instead of a server-side 301 or 302. Google can follow it but treats it as second-class: slower to process and less reliable at passing ranking signals. Replace it with a server-side 301 (permanent) or 302 (temporary) redirect.
Fix Heading Hierarchy Skips (H2 to H4): SEO Guide
A heading-hierarchy skip means your page jumps a heading level, such as an H2 followed directly by an H4 with no H3 in between. It breaks the logical outline that screen readers, search crawlers, and AI answer engines use to understand how your content is organized. This is a low-severity (notice) issue that won't tank your rankings, but fixing it makes your page cleaner for assistive tech, more parseable for machines, and easier to lift into featured snippets and AI answers.
How to Fix a Missing Favicon (Step-by-Step)
A missing favicon means your site has no small brand icon for browsers, bookmarks, and Google's mobile search results to show. It is a low-severity notice, not a ranking penalty, but it is a fast trust win: a proper favicon makes your listing recognizable in the SERP, in browser tabs, and next to AI-answer citations. The fix is one square image (ideally an SVG plus a PNG or ICO fallback) and a couple of link tags in your page head.
How to Remove Flash Content From Your Site
Your audit found embedded Adobe Flash content: .swf files, or <object>/<embed> tags pointing at Flash. Adobe ended Flash support on December 31, 2020 and no modern browser will run it, so the content is invisible to visitors, Googlebot, and AI crawlers alike. This guide shows you how to locate every Flash element and rebuild it with HTML5 video, CSS animation, or JavaScript.
How to Fix Missing Twitter Card Tags
Your page is missing Twitter Card meta tags (twitter:card, twitter:title, twitter:description, twitter:image), so links to it can render as a bare URL instead of a rich preview on X, Slack, Discord, and similar apps. X reads your Open Graph tags as a fallback for title, description, and image, so in most cases one twitter:card tag on top of solid OG tags closes the gap. This is a low-severity notice about link-preview appearance, not a ranking factor.
Content
How to Fix Duplicate Title Tags
Duplicate title tags mean two or more pages share the same <title> text. This makes it harder for Google to tell your pages apart, splits their ranking signals, and produces generic, undifferentiated snippets in both search results and AI answer engines. The fix is to give every indexable page a unique, descriptive title that reflects its specific content.
How to Fix Duplicate Meta Descriptions
Duplicate meta descriptions mean two or more of your pages ship the identical <meta name="description"> text. It's a warning-level content issue: it won't block indexing, but it wastes your best shot at winning the click in search results and signals thin templating to Google. The fix is to give each meaningful page its own description that reflects that page's specific content.
How to Fix Thin Content on Your Pages
Thin content means a page doesn't offer enough substantive, useful information to satisfy the intent behind the query it targets. Fix it by expanding pages with genuinely helpful detail, consolidating overlapping weak pages, and either improving or removing low-value pages that exist only to fill a URL slot.
How to Fix Keyword Stuffing on a Page
Keyword stuffing means a target term or its close variants appears so densely that the text reads as written for search engines, not people. Google names it in its spam policies, and it also makes your content less quotable to AI answer engines. The fix is not deleting the keyword. It is rewriting so the topic is covered naturally with synonyms, entities, and real substance, then keeping the term in the right structural spots (title, H1, first paragraph, a subhead or two) instead of everywhere.
How to Fix Hard-to-Read Content
An audit flagged this page as "difficult" or "very difficult" to read, meaning its readability score fell into the lowest bands (roughly a Flesch Reading Ease under 50). That points to long sentences, dense paragraphs, and complex vocabulary that make readers work harder than they should. Fix it by shortening sentences, breaking up paragraphs, swapping jargon for plain words, and adding structure like subheadings and lists. Cleaner writing keeps readers engaged and makes your pages easier for AI answer engines to extract and cite.
How to Fix Keyword Cannibalization (Step by Step)
Keyword cannibalization happens when two or more pages target the same search intent, so Google can't tell which one to rank. The fix: decide which URL should own the keyword, then consolidate the rest by merging and redirecting, canonicalizing, or re-optimizing them around distinct intents.
Fix "No Focus Keyword": On-Page Targeting Guide
A "no focus keyword" notice means the audit couldn't detect a single, clear target query your page is built around. Your title, H1, URL, and opening copy don't converge on one primary term or its close variants, so search engines and AI answer engines have to guess what the page is about. This is a low-severity notice, not an error, but resolving it sharpens relevance and makes the page easier to rank and cite. The fix: choose one primary keyphrase per page based on real search intent, then place it in the title tag, H1, URL slug, first paragraph, and naturally through the body.
E-E-A-T & Authority
Fix Missing Organization Schema (JSON-LD)
Your audit found no Organization structured data on the site, or a version missing key properties. Organization schema is a block of JSON-LD, usually on your homepage, that tells Google and AI answer engines who you are: your name, logo, URL, social profiles, and contact details. Without it, search engines infer your brand identity from scattered signals, which weakens your eligibility for a logo in search results, a knowledge panel, and accurate attribution when tools like ChatGPT and Perplexity cite you. The fix is to add one valid JSON-LD block with the core properties (name, url, logo, sameAs) and validate it.
Fix Missing Author E-E-A-T Signals: Step-by-Step
Your page was flagged for missing author E-E-A-T signals: there's no clear, verifiable person attached to the content. Google's quality systems and AI answer engines both use authorship to judge Experience, Expertise, Authoritativeness, and Trust. Fix it by adding a visible byline, a truthful bio with credentials, a dedicated author page, and Person schema linked to the author's real external profiles.
Fix No Knowledge Graph Presence (Entity SEO)
This audit flags that your site does not clearly connect itself to a recognized entity in Google's Knowledge Graph. Your pages describe your brand in prose, but there is no machine-readable anchor (Organization schema with a stable @id and sameAs links) tying your domain to an entity Google and AI answer engines already know. The fix is to declare your organization as structured data, link it to authoritative profiles like Wikidata and LinkedIn, and keep your name and details consistent everywhere they appear. This is a notice-level issue, not an emergency, but resolving it strengthens how both classic search and AI systems recognize and cite your brand.
Fix Low Fact Density: Add Statistics to Content
Your page has too few concrete facts, numbers, and statistics for its length. Vague, claim-heavy prose is harder for Google to trust and for AI answer engines to extract and cite. The fix is to replace generic assertions with specific quantified facts, tie each to a named and dated source, and mark them up so they survive extraction by ChatGPT, Perplexity, and Google AI Overviews.
How to Fix "No Outbound Citations" (E-E-A-T)
The "no outbound citations" notice means your page makes claims but links to zero external, authoritative sources. Adding a few relevant links to primary sources (studies, official docs, standards bodies, original data) strengthens your E-E-A-T signals, lets readers verify claims, and helps AI answer engines treat your page as a well-sourced reference worth quoting.
Fix Missing dateModified: Add a Freshness Signal
This page has no machine-readable dateModified value, so search engines and AI answer engines can't reliably tell when your content was last updated. Add an accurate dateModified in your Article or WebPage JSON-LD, keep it in sync with real edits, and mirror it in a visible timestamp. Done honestly, this restores a freshness signal that supports both classic ranking and AI citation.
How to Add a Contact Page (E-E-A-T Trust Signal)
Your site has no discoverable contact page: no address, email, phone number, or contact form that a visitor or crawler can find. Google's Search Quality Rater Guidelines treat reachable contact information as a basic trust signal, especially for stores and YMYL sites, and AI answer engines look for the same accountability cues before treating a domain as a real, citable organization.
How to Keep Your Brand Name Consistent (E-E-A-T)
Your organization's name appears differently in different places, for example your Organization schema says one thing while your og:site_name tag says another. That drift makes it harder for Google's Knowledge Graph and AI answer engines to confirm all your site's signals describe the same entity, a low-severity but real entity-clarity problem worth fixing.
Images
How to Fix Images Missing Alt Text
Your audit flagged images with no alt attribute, or an empty one where a description belongs. Alt text is the written description that search engines, screen readers, and AI answer engines rely on to understand what an image shows. Adding accurate, concise alt text to your meaningful images closes accessibility gaps, unlocks Google Images traffic, and makes visual content legible to crawlers that can't see.
Add srcset and sizes to Fix Responsive Images
Your audit found images that ship one fixed-size file to every visitor instead of using the srcset and sizes attributes. Adding them lets the browser pick the smallest image that still looks sharp on each screen, cutting wasted bytes on mobile and helping your Largest Contentful Paint. This is a notice, not an error, but on image-heavy pages it is one of the highest-leverage speed fixes you can make.
How to Lazy-Load Images with loading="lazy"
Your audit found images that load immediately even though they sit below the fold. Lazy loading defers those off-screen images until the visitor scrolls near them, cutting initial page weight and speeding up load. The fix is usually one attribute: loading="lazy" on below-the-fold images. Keep it off your hero and LCP image, which should load eagerly.
How to Fix Alt Text That's Too Long
Your audit flagged one or more images whose alt text runs past the recommended length (a common working limit is about 125 characters). Overlong alt attributes are harder for screen-reader users to follow, dilute the signal Google reads from an image, and often mean the alt is keyword-stuffed. The fix is straightforward: rewrite each flagged alt into a concise, specific description of what the image shows, and move any extra context into a caption or the surrounding text.
Why You Should Host Images on Your Own Domain
This notice flags images served from a domain other than your own, commonly called hotlinking, rather than from your own domain or CDN. You don't control an external host's uptime, caching, or whether they block hotlinking outright, and image search tends to favor images actually hosted on the page's domain. The fix is downloading and re-serving important images from your own server, CDN, or CMS media library.
Links & Crawlability
How to Find and Fix Broken Links on Your Site
A broken link points to a page that returns an error (usually a 404 Not Found) or fails to load. Your audit flagged either internal broken links (pointing to your own pages) or external broken links (pointing to other sites). Both waste crawl budget, frustrate users, and stop link value from flowing through. Fix them by correcting the URL, restoring the target page, adding a 301 redirect, or removing the link.
How to Fix Orphan Pages (No Internal Links)
An orphan page is a page on your site that no other page links to internally.
How to Fix Broken Pages (4xx & 5xx Errors)
Your audit found pages returning 4xx status codes (client errors like 404 Not Found or 403 Forbidden) or 5xx status codes (server errors like 500 or 503) instead of a healthy 200 OK. These are dead ends for search engines and AI crawlers: the content is unreachable, ranking signals are lost, and users hit error screens. This guide explains each error class, why broken pages hurt both classic search and AI answer engines, and the exact fix per platform.
Fix Generic Anchor Text: Write Descriptive Links
Generic anchor text means links use non-descriptive words like "click here," "read more," "learn more," or a bare URL instead of text that describes the destination. Descriptive anchors help Google understand what the linked page covers, pass a topical relevance hint, and give screen-reader and AI-crawler users real context. The fix is to rewrite each link's visible text to describe where it goes, using the target page's topic naturally without keyword-stuffing.
Fix Over-Optimized Anchor Text: SEO Guide
Your audit flagged over-optimized anchor text: too many of your links use the same keyword-rich "exact match" phrase as the clickable text. That pattern looks manipulative to Google's link-spam systems and can suppress rankings for the very keyword you are stuffing. The fix is to diversify your anchors so branded, partial-match, and descriptive phrases dominate, with exact-match kept to a small share.
How to Fix Weak Internal Linking on Your Site
Your audit found one or more pages with very few internal links pointing to other pages on your site, in some cases only one or none. Internal links help search engines and AI crawlers discover pages, understand how they relate, and pass ranking signals between them. This guide explains why sparse internal linking holds pages back and gives you platform-specific steps to add contextual, descriptive links that improve crawlability and topical authority.
Fix Pages Too Deep in Crawl Depth (3-Click Rule)
The "pages too deep" notice means one or more pages sit too many clicks from your homepage in your internal link graph. Crawlers reach deep pages less often, treat them as lower priority, and pass them less link equity. The fix is to shorten click paths: link deep pages from shallow hub pages, add contextual internal links, and keep important content within about three clicks of the homepage.
How to Fix Too Many Links on a Page
"Too many links on page" means the audit counted an unusually high number of <a href> links on one URL. Google has no hard cutoff, but a bloated link count thins the equity each link passes, buries the links that matter, adds page weight, and makes it harder for Googlebot and AI crawlers to tell what the page is about. Trim boilerplate and low-value links, consolidate navigation, paginate long lists, and make your genuinely important links stand out.
How to Fix Redirect Chains and Loops
This audit bundles seven redirect problems: chains of multiple hops, loops that never resolve, temporary (302/307) redirects standing in for permanent moves, internal links pointing at a redirecting URL instead of the final one, JavaScript redirects many crawlers never execute, and http-to-http redirects that skip the upgrade to https. Each wastes crawl budget or user time in a different way, but the fix is the same shape for all seven: point every link straight at the final destination and use one correctly-typed server-side redirect to get there.
Stop Adding rel=nofollow to Internal Links
This audit found a high share of your internal links carrying rel="nofollow", which doesn't work the way it's often assumed to. The old idea that nofollowing internal links "sculpts" PageRank toward other pages has been dead since Google's 2009 clarification, and nofollow became a hint rather than a hard rule in 2019, so it isn't even a reliable way to stop a link from being crawled anymore. In practice, nofollowing a real content page just risks losing link equity and delaying discovery for nothing; reserve it for genuine utility links (login, cart, account) and remove it from everything else.
Performance & Core Web Vitals
How to Fix Images That Are Too Large
Your audit flagged one or more images whose file size or pixel dimensions are far larger than the page needs. Oversized images are the most common cause of slow Largest Contentful Paint (LCP) and wasted bandwidth. The fix: compress each image, resize it to the dimensions it's displayed at, serve a modern format (WebP or AVIF), and let the browser pick the right size with responsive srcset. WordPress, Shopify, Wix, and Squarespace can automate most of this; custom sites handle it with a build step.
How to Fix Images Missing Dimensions (CLS)
Your audit flagged one or more images that render without width and height attributes. Without them, the browser can't reserve space before the image downloads, so surrounding content jumps as each image loads. That jump is measured by Cumulative Layout Shift (CLS), a Core Web Vital. The fix is to add explicit width and height attributes (or a CSS aspect-ratio) to every content image so the browser holds the space in advance.
How to Fix Render-Blocking Resources
Render-blocking resources are CSS and JavaScript files the browser must download and process before it can paint the page. They sit in the critical rendering path and push back First Contentful Paint (FCP) and Largest Contentful Paint (LCP). You fix them by deferring non-critical JavaScript, inlining critical CSS, loading the rest asynchronously, and trimming what the browser has to parse before first render.
How to Fix Slow Server Response Time (TTFB)
Your audit flagged a slow Time to First Byte (TTFB), the delay between the browser requesting a page and receiving the first byte of the response. A good TTFB is 800ms or less at the 75th percentile of real users; 800ms to 1,800ms needs improvement, and over 1,800ms is poor. The browser can't start rendering until that first byte arrives, so a slow TTFB directly delays Largest Contentful Paint (LCP), hurts rankings, and slows how fast crawlers (including AI crawlers) can fetch your content. Fix it with server-side page caching, a CDN, faster hosting, database and back-end optimization, and by collapsing redirect chains.
How to Improve a Poor PageSpeed Score
A poor or fair PageSpeed score means your pages load and respond slowly for real users, which drags down Core Web Vitals (LCP, INP, CLS). Google uses field data from real Chrome visits as a ranking input, so this affects search position, bounce rate, and how reliably AI crawlers can fetch and render your content. Fix it by shrinking and prioritizing the largest visible element, cutting render-blocking and unused JavaScript, compressing images, reserving space to stop layout shift, and speeding up server response.
How to Reduce Unused JavaScript
Your page ships JavaScript the browser downloads and parses but often never runs on that page. This wastes bandwidth and main-thread time, delaying LCP and interactivity. The fix is to load less JS up front: code-split, defer, tree-shake, and remove dead scripts and unused third-party tags.
How to Enable Gzip or Brotli Compression
Your audit found HTML, CSS, or JavaScript being served without HTTP compression. Enabling Gzip or Brotli on your server or CDN shrinks these text files substantially, cutting transfer size and improving load time and Core Web Vitals with no visual change to your site.
Fix Poor INP (Interaction to Next Paint)
Interaction to Next Paint (INP) measures how quickly a page visually responds when users tap, click, or type. Your audit flagged INP as either "poor" (above 500ms) or "needs improvement" (200 to 500ms), which means users feel a lag between acting and seeing a result. INP is a Core Web Vital, so it feeds Google's page-experience signal and ranking eligibility. The fix is almost always about reducing main-thread JavaScript: breaking up long tasks, deferring non-critical scripts, trimming heavy event handlers, and letting the browser paint the response before running expensive logic.
Reduce JavaScript Execution Time: How to Fix It
Your audit flagged high JavaScript bootup time: the browser spends too long parsing, compiling, and executing scripts before the page becomes responsive. This blocks the main thread, delays interactivity, and drags down Core Web Vitals like INP and Total Blocking Time. The fix is to ship less JavaScript: remove unused code, split bundles so each page loads only what it needs, defer non-critical scripts, and rein in heavy third-party tags. Below is what the issue means, why it matters for both Google rankings and AI answer engines, and how to fix it on common platforms.
How to Reduce Large Page Size (Cut Page Weight)
A "large page size" warning means the total download weight of your page (HTML, CSS, JavaScript, images, fonts, and other assets) is heavier than it needs to be. Oversized pages load slowly on mobile and metered connections, hurt Core Web Vitals like LCP, and burn crawl and render budget for both Googlebot and AI crawlers. The fix is systematic: find the biggest offenders (usually images and JavaScript), compress and modernize them, defer what isn't needed for first paint, and turn on compression at the server. Most sites can cut page weight substantially without touching the design.
How to Minify CSS and JavaScript (Fix Guide)
Your audit found CSS or JavaScript files served with their original whitespace, comments, and long variable names intact. Minification strips those non-functional characters so the browser downloads and parses less code, which improves load time and Core Web Vitals. Most fixes are one setting in an optimization plugin, a build-tool flag, or a platform toggle.
How to Fix Unused CSS and Speed Up Your Pages
Your audit flagged unused CSS: your pages download stylesheet rules the current page never applies. That wastes bandwidth, adds render-blocking weight, and delays Largest Contentful Paint. The fix is to remove or defer CSS the page doesn't need, inline the critical above-the-fold styles, and stop shipping full framework stylesheets when you only use a fraction of their rules.
Fix Inefficient Cache Policy (Cache-Control)
An "inefficient cache policy" notice means your static assets (images, CSS, JS, fonts) are served with a short cache lifetime or no Cache-Control header, so returning visitors re-download files that never changed. The fix is to send a long max-age (up to a year) for versioned assets and a shorter, revalidating policy for files that change at the same URL. This speeds up repeat and multi-page visits and cuts server bandwidth without touching your content.
Fix Legacy HTTP/1.1: Enable HTTP/2 and HTTP/3
Your site is being served over HTTP/1.1, an older protocol that handles one request per connection and can't download resources in parallel over a single link. Upgrading to HTTP/2 (many requests multiplexed over one connection) and HTTP/3 (QUIC over UDP, faster on lossy networks) cuts round-trips and speeds up delivery. On most modern hosts and CDNs this is already the default or a single toggle.
How to Reduce Excessive Iframes on Your Site
This notice fires when your audit counts more than 10 iframes across the pages it crawled, typically maps, videos, ads, or third-party widgets. Each iframe loads a separate document with its own bandwidth and main-thread cost, and content rendered inside one is generally invisible to AI crawlers reading your raw HTML. The fix is lazy-loading, click-to-load facades, and cutting embeds that aren't earning their keep.
Security & HTTPS
How to Fix a Site Not on HTTPS (No SSL)
Your audit flagged that this page loads over HTTP instead of HTTPS, so traffic between the visitor and your server is unencrypted and unauthenticated. This is a critical issue: Chrome labels HTTP pages "Not Secure," HTTPS is a confirmed Google ranking signal, and unencrypted pages can be intercepted or tampered with in transit. The fix is to install an SSL/TLS certificate (free ones work fine), serve everything over HTTPS, and add a permanent redirect so every HTTP request lands on the HTTPS version.
How to Fix Mixed Content Errors on HTTPS
Mixed content means your page loads over HTTPS but pulls in some resources (images, scripts, stylesheets, iframes) over plain HTTP. Browsers block or auto-upgrade those insecure requests, which strips the padlock, can break layout and functionality, and undermines the trust signal search and AI engines rely on. Fix it by finding every http:// reference, switching it to https://, correcting the source (usually stored content or theme settings, not just one page), and adding upgrade-insecure-requests as a backstop.
Fix an Expired or Invalid SSL Certificate
An expired, invalid, or soon-to-expire TLS/SSL certificate breaks the secure connection between browsers and your server. Visitors hit a full-page "Your connection is not private" warning, Googlebot and AI crawlers get blocked at the handshake, and HTTPS-dependent features stop working. This is a critical, time-sensitive problem. Fix it by renewing or reissuing the certificate, installing the full chain, and enabling auto-renewal so it never lapses again.
Fix Unsafe target="_blank" Links (rel="noopener")
Your audit flagged links that open in a new tab (target="_blank") without rel="noopener". That reference lets the destination page reach back into your original tab through window.opener, which enables a phishing trick called reverse tabnabbing. The fix is adding one attribute to the affected anchor tags.
Fix HSTS Missing includeSubDomains
Your site sends a Strict-Transport-Security (HSTS) header, but it leaves out the includeSubDomains directive. That means the HTTPS-only policy protects only the exact hostname the browser saw, not your subdomains. An attacker can still hijack a first, unencrypted request to a subdomain like blog. or app. and downgrade it to HTTP. The fix is to add includeSubDomains once you've confirmed every subdomain works over HTTPS with a valid certificate.
How to Fix Missing SPF and DMARC Records
Your domain is missing an SPF and/or DMARC DNS record. These records authenticate email sent from your domain. Without them, receiving servers can't verify your mail is legitimate, so messages land in spam and anyone can spoof your domain. The fix is publishing TXT records in DNS: SPF on the root domain, DMARC at _dmarc, and DKIM keys from each sending service.
How to Remove Sensitive HTML Comments
Your audit found HTML comments in the page's raw source that expose internal detail: server file paths, internal IP addresses, CMS or plugin version numbers, TODO/FIXME notes, or references to staging and debug environments. These comments are invisible on the rendered page but sit in plain text in every response your server sends, so any visitor, scraper, or AI crawler that fetches the raw HTML can read them. This is a passive information-disclosure warning, not proof of a breach, and the fix is to stop shipping internal notes to production and strip comments at build time.
How to Fix Protocol-Relative URLs
A protocol-relative URL is written as `//example.com/page` instead of `https://example.com/page`, letting the browser fill in whichever protocol served the current page. It was a genuinely useful trick during the years when sites ran on both http and https, but the web is https-by-default now, and the pattern has quietly become an anti-pattern with no upside left. It's a low-severity notice: find these URLs and rewrite them to explicit `https://`, or a root-relative `/path` for links on your own domain.
Mobile
How to Fix a Missing Viewport Meta Tag
Your page is missing the viewport meta tag, so mobile browsers render it at desktop width and shrink it to fit the screen. This is a one-line HTML fix that makes the page mobile-friendly.
Fix Viewport Not Device-Width (incorrect_viewport)
Your page has a viewport meta tag, but it sets a fixed pixel width (like width=1024) instead of width=device-width. That forces every phone to render your page on a fixed canvas and shrink it, producing tiny text and horizontal scrolling. Change the tag to width=device-width, initial-scale=1 so the browser matches the real screen size.
Fix Intrusive Interstitials & Popups on Mobile
Google can demote mobile pages that hide content behind an intrusive popup or interstitial when a visitor arrives from search. The fix: make the primary content readable on arrival. Replace full-screen overlays with a small top or bottom banner, delay or scroll-trigger promotional popups so they never fire on the first landing view, and keep legally required consent dialogs proportionate.
How to Add an Apple Touch Icon to Your Site
A missing apple-touch-icon means iOS and Android have no dedicated icon to display when a visitor adds your site to their home screen or bookmarks it, so they get a blurry auto-generated screenshot instead. This is a low-severity, purely cosmetic notice with no ranking impact. The fix is a single 180x180 PNG and one link tag in your page's head.
How to Fix Mobile-Unfriendly Elements on a Site
Mobile-unfriendly elements are legacy patterns, like table-based layouts, frames, and Flash embeds, plus broader issues like fixed pixel widths, small tap targets, and undersized text, that break how your page renders on a phone. Google indexes and ranks using the mobile version of your site, so these aren't cosmetic quirks; they're what the algorithm actually sees. Most are fixed by replacing old markup with responsive CSS and auditing touch targets and font sizes.
Accessibility
Fix the Missing HTML lang Attribute
The missing_html_lang issue means the root <html> tag has no lang attribute (or an empty lang=""), so screen readers, browsers, and AI crawlers can't reliably tell what language the page is written in. The fix is a one-line change: add lang="en" (or your actual BCP 47 language code) to the <html> element. On most platforms it lives in a theme setting or template rather than raw markup.
Fix Form Inputs Missing Labels (Accessibility)
Your audit found form controls (inputs, textareas, selects) with no programmatically associated label. Screen readers announce these as unnamed, so users don't know what to type, and machines parsing the form can't tell what each field is for. Fix it by giving every control an accessible name: a real label tied by for/id, a label that wraps the control, or an aria-label / aria-labelledby attribute.
Fix Links Without Descriptive Text (Empty Anchors)
Your audit flagged links with no accessible text, or text that doesn't describe where the link goes. This covers icon-only links, image links missing alt text, and generic "click here" or "read more" anchors. Screen readers announce these as unusable, and search engines and AI crawlers lose the context anchor text is meant to carry. The fix is to give every link a clear, human-readable destination label: visible text, alt text on a linked image, or an aria-label for icon links.
Fix Viewport Zoom Disabled (user-scalable=no)
Your viewport meta tag disables zoom, usually with user-scalable=no or a low maximum-scale value, so users can't pinch-zoom to enlarge text. This fails WCAG 2.1 success criterion 1.4.4 (Resize Text) and hurts anyone with low vision. The fix is to drop the zoom-blocking parameters and keep the tag as width=device-width, initial-scale=1 so pinch-to-zoom works again.
Fix Missing Semantic HTML Landmarks (Div Soup)
Your page is built mostly from generic <div> and <span> elements instead of semantic landmark tags like <header>, <nav>, <main>, <article>, and <footer>. Landmarks tell screen readers, browsers, and AI crawlers what each region of the page is and where the primary content lives. Swapping the outermost structural divs for the correct HTML5 elements is a low-risk, markup-only fix that improves accessibility and makes your content easier for Google and answer engines to parse.
How to Add a Skip to Main Content Link
Your audit found no "skip to main content" link: a hidden-until-focused anchor that lets keyboard and screen-reader users jump straight past repeated header and navigation markup to the page's actual content. Without one, a keyboard-only visitor has to tab through the entire menu on every single page just to reach what they came for. It satisfies WCAG 2.1 success criterion 2.4.1 (Bypass Blocks) and is a genuinely quick, low-risk fix: one link, one target, a few lines of CSS.
Indexing & Sitemaps
How to Fix a Missing Canonical Tag
A missing canonical tag means the page never tells search engines which URL is the authoritative version of its content. Without it, Google and AI answer engines may index the wrong URL, split ranking signals across duplicate variants, or surface a parameterized or non-www version instead of your clean URL. The fix is to add a single self-referencing rel="canonical" link with an absolute URL in the page's head.
How to Fix a Noindex Page and Get It Indexed
Your audit found a page carrying a noindex directive, which explicitly tells search engines and AI crawlers not to include it in their index. If this is a page you want ranked, that directive is silently keeping it out of Google, Bing, and AI answer engines. The fix is to locate the directive (in the HTML head, the HTTP response header, or your CMS SEO settings), remove it if the page should be public, and confirm the page is crawlable so search engines can see it is now indexable.
How to Fix a Missing XML Sitemap
Your audit could not find an XML sitemap at the usual locations. A sitemap is a machine-readable file that lists the URLs you want search engines and AI crawlers to discover. Adding one, referencing it in robots.txt, and submitting it in Google Search Console helps crawlers find every important page faster and more reliably.
Fix Googlebot Blocked in robots.txt (Critical)
Your robots.txt contains a rule that tells Googlebot (or every crawler) not to fetch your site. Until you remove or narrow that Disallow, Google can't read your pages, and they eventually drop out of Search. It's one of the fastest fixes on any audit: usually one or two lines in a single file.
Fix Pages Missing From Your XML Sitemap
Your audit found live, indexable pages that are not listed in your XML sitemap. A sitemap is the address book crawlers read to discover URLs, so missing entries slow or block discovery, especially for pages that also lack internal links. Fix it by identifying which URLs are absent, confirming they should be indexable, getting them into a sitemap that regenerates automatically, and resubmitting in Google Search Console.
Fix "Robots.txt Not Accessible" (+ Add Sitemap)
Your audit flagged that your robots.txt either can't be fetched cleanly (it returns a server error, times out, or serves the wrong content type) or it loads but has no Sitemap directive. The unreachable case is the urgent one: when Google gets a 5xx or timeout on robots.txt, it stops crawling your site until the file is reachable again, and a long outage can cause pages to drop from the index. A missing Sitemap line is lower-stakes, but it means crawlers and AI bots have to find your sitemap on their own instead of being pointed straight to it. Both fixes are quick: serve a valid robots.txt at your root with an HTTP 200 response, and add one absolute-URL Sitemap line.
How to Reduce a High Crawl-Delay in Robots.txt
A Crawl-delay directive in robots.txt tells crawlers to wait a set number of seconds between requests, throttling how fast your site gets discovered and reindexed. Googlebot ignores it entirely, but Bing, Yandex, and some other bots honor it, so a leftover high value can quietly slow reindexing for no real benefit. Lower or remove it unless your server genuinely can't handle concurrent bot traffic, and use platform-specific tools for finer control instead.
International SEO
How to Fix Hreflang Errors: Complete Guide
Your audit flagged one or more hreflang problems: an invalid or unknown language code, a missing return (reciprocal) link, or a missing x-default. Hreflang tells Google which language and regional version of a page to show which users. When the annotations are malformed, incomplete, or non-reciprocal, Google ignores the whole cluster and falls back to guessing. That causes the wrong-language page to rank, duplicate-content confusion between regional versions, and lost clicks. This guide explains each error code, why it matters, and exactly how to fix it with correct tags and platform-specific steps.
Fix Pagination rel=next/prev & Canonical Errors
Your audit found a problem with how your paginated pages (page 2, page 3, and beyond) declare their relationships: rel=next/prev links are broken or in the wrong place, the chain loops back on itself, or a paginated page's canonical points somewhere it shouldn't. Google stopped using rel=next/prev as an indexing signal back in 2019, so the modern fix is a self-referencing canonical on every paginated page, sequential rel links kept in the head only if you use them at all, and no page that canonicalizes to page 1. Done right, this keeps crawlers on a clean path to your deeper pages and indexes the correct URLs.
AI & Answer Engines
How to Fix Content Invisible to AI Crawlers
Your audit flagged js_dependent_content: the page's main text only appears after JavaScript runs in the browser. Many crawlers, including most AI answer engines, fetch the raw HTML and never execute that JavaScript, so they see an empty or skeletal page. The fix is to deliver your real content in the initial HTML response using server-side rendering, static generation, or prerendering.
How to Fix AI Crawlers Blocked in robots.txt
Your robots.txt contains rules that disallow one or more AI crawlers (like GPTBot, Claude-User, PerplexityBot, or OAI-SearchBot) from fetching your site. That keeps your content out of ChatGPT, Perplexity, and Claude answers. The fix is to edit robots.txt so the AI user-agents you want are allowed, while keeping genuinely sensitive paths protected.
How to Add FAQ Structured Data (FAQPage Schema)
Your page shows questions and answers but has no FAQPage structured data telling machines how they pair. Valid FAQPage JSON-LD makes that Q&A explicit and machine-readable. The 2026 context matters: Google removed FAQ rich results from Search on May 7, 2026, so the payoff now is answer-engine visibility (ChatGPT, Perplexity, Google AI Overviews) and cleaner content parsing, not SERP dropdowns.
Add Organization sameAs for AI & Knowledge Graph
Your homepage's Organization structured data exists but has no sameAs property. That property is the array of official profile URLs (LinkedIn, X, Wikipedia, Wikidata, Crunchbase, GitHub) that lets search engines and AI answer engines resolve your website to a single, known brand entity. Without it, engines see a name and a logo but cannot confirm which real-world organization you are. Fix it by adding a sameAs array to your Organization JSON-LD, leading with a Wikipedia or Wikidata link if one exists, then your authoritative social and business profiles.
How to Fix Questions Without Direct Answers
Your page asks questions in headings, FAQs, or copy but never delivers a clear, self-contained answer next to them. Search engines and AI answer engines can't extract a usable response, so you lose featured snippets and citations. The fix: put a direct 40-to-60-word answer immediately after each question, then expand below it.
Fix Snippet-Blocking Robots Directives
One or more of your pages is telling Google not to show a text or image preview of its content. Directives like nosnippet, max-snippet:0, max-image-preview:none, and the data-nosnippet attribute suppress the snippet under your search listing, remove your thumbnail and image rich-result eligibility, and block the page from featured snippets and from Google AI Overviews and AI Mode. Google's docs are explicit: these same directives control what AI Overviews may quote from your page. Unless you deliberately want a page kept out of previews, remove or relax them so Google can display and cite your content.
Fix "Content Needs More Headings" (H2/H3)
This page runs long stretches of body text with too few subheadings (H2/H3) for its length. A logical heading structure breaks the content into scannable, self-contained sections that both readers and machines can navigate.
Fix "No Machine-Readable Metadata": JSON-LD Guide
This page was flagged because it has no machine-readable metadata: no structured data (JSON-LD) telling search engines and AI answer engines what the page is, who published it, and how its facts connect to known entities. The fix is to add a JSON-LD script block using schema.org types like Article, Organization, FAQPage, or Product. It's a warning, not a critical error, but resolving it makes your page eligible for Google rich results and far easier for ChatGPT, Perplexity, and Google AI Overviews to parse and cite accurately.
How to Fix Broken JSON-LD Schema Markup
Your page has structured data that's broken in one of three ways: the JSON-LD doesn't parse at all, it's missing a property Google requires for that schema type, or the same @type is declared more than once with conflicting data. Broken schema quietly forfeits rich-result eligibility, and in the duplicate case it can feed AI answer engines two different answers about the same fact. This is a warning: it won't tank your rankings, but it's a fast, high-value fix once you know which of the three problems you have.
Not sure which issues you have?
Run a free, AI-powered audit and get a prioritized list of exactly what to fix. No signup.