The KJ KB

Navigation

Security

What It Means

  • The page is served through unsecured HTTP, so data can be intercepted and browsers may show a “Not secure” warning. Google prefers a consistent HTTPS version, and having both HTTP and HTTPS accessible can split URL signals.

Try These Steps

  1. Confirm SSL is active and the HTTPS version loads.
  2. Force HTTP-to-HTTPS redirects at the host, CDN, or server.
  3. Update hardcoded HTTP URLs in WordPress content/theme files or Shopify theme/app code.

What It Means

  • The sitemap is advertising HTTP addresses even though HTTPS should be the preferred version. Search engines may waste time following redirects and receive conflicting signals about which protocol should be indexed.

Try These Steps

  1. Check the sitemap output and confirm the site URL is set to HTTPS.
  2. Regenerate the sitemap after correcting WordPress Address/Site Address or SEO-plugin settings.
  3. On Shopify, verify the primary domain and remove old HTTP references from apps or custom sitemap logic. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

What It Means

  • An HTTPS page declares the HTTP version as the preferred URL. This can push search engines toward the insecure version or cause them to ignore the canonical because it conflicts with redirects and other site signals.

Try These Steps

  1. Inspect the page source to see which theme, plugin, app, or code outputs the canonical. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Correct the canonical in the SEO plugin, theme template, or custom code. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Check site/domain settings so generated URLs use HTTPS everywhere. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • An HTTPS page requests an image, script, stylesheet, font, or iframe over HTTP. Browsers may block the resource, which can break the page, weaken security, and prevent search engines from seeing the same rendered content as users.

Try These Steps

  1. Use the browser console or audit URL list to identify the HTTP file.
  2. Replace the URL in the page builder, media library, theme, app, or custom code.
  3. Run a safe search-and-replace for old HTTP domain URLs, then clear caches.

What It Means

  • The server still accepts an older TLS protocol such as TLS 1.0 or 1.1. Modern browsers, crawlers, or security services may reject the connection, turning a security configuration problem into an accessibility problem.

Try These Steps

  1. Test the domain with the host/CDN security tools.
  2. Ask the host or CDN to disable TLS 1.0/1.1 and enable modern TLS.
  3. Check old proxies, load balancers, or third-party checkout/subdomain services.

What It Means

  • The SSL certificate does not cover the hostname being visited, such as www versus non-www or a subdomain. Browsers can show a full-page warning, and crawlers may be unable to access the affected host normally.

Try These Steps

  1. Check whether the error affects www, non-www, a subdomain, or the main domain.
  2. Reissue/install a certificate that covers every active hostname.
  3. Correct DNS, CDN, or domain mappings that point to the wrong server.

What It Means

  • The server uses weak or deprecated cipher settings. Some clients may refuse the connection, and the site remains exposed to avoidable security and compatibility risks.

Try These Steps

  1. Run an SSL configuration test to confirm the failing cipher or key setting.
  2. Ask the host/CDN to apply a modern TLS configuration.
  3. Replace legacy server, proxy, or certificate settings if the host cannot update them.

What It Means

  • The certificate is still valid but is close to expiration. If renewal fails, browsers will block or warn on the site and search crawlers may no longer be able to fetch pages reliably.

Try These Steps

  1. Confirm auto-renewal is enabled and the renewal contact is current.
  2. Renew or reissue the certificate through the host, CDN, or registrar.
  3. Check that DNS validation and certificate-install automation still work.

Crawling & Indexing

What It Means

  • The URL returns a client error such as 404 Not Found, 403 Forbidden, or 410 Gone instead of a usable page. This is correct for intentionally removed content, but it is a problem when the URL should exist or is still linked, indexed, or included in a sitemap.

Try These Steps

  1. Decide whether the URL should exist; restore it if it should. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Update internal links to the correct live URL or add a relevant 301 redirect. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. If removal is intentional, remove the URL from menus, sitemaps, canonicals, and hreflang. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • The server failed while trying to load the URL, commonly because of hosting, application, database, or resource-limit problems. Persistent 5XX errors prevent crawling and can cause important pages to disappear from search over time.

Try These Steps

  1. Retest the URL and check whether the failure is temporary or repeatable. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Review hosting logs, plugin/app errors, PHP limits, database issues, and CDN/firewall rules. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Escalate sitewide or repeated failures to the host or developer immediately. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • The crawler waited for the page but did not receive a complete response in time. The cause may be a slow server, overloaded database, firewall, bot protection, or an external service that delays page generation.

Try These Steps

  1. Retry the URL manually and in another speed or header-checking tool. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Check slow plugins/apps, database calls, external scripts, firewall rules, and server load.
  3. Ask the host to review timeout, CPU, memory, and error logs. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • The page tells search engines to consolidate ranking signals into a canonical URL that is broken or unavailable. Google may ignore the canonical and choose another URL, which makes indexing less predictable.

Try These Steps

  1. Open page source and confirm the canonical target. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Change the canonical in the SEO plugin, theme, app, or template to a live 200 URL. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Restore or redirect the target only when it is truly the preferred page. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • The declared canonical target is failing at the server. A temporary outage may resolve itself, but a persistent failure makes the preferred URL unreliable and weakens canonical consolidation.

Try These Steps

  1. Confirm whether the canonical target is temporarily down. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Fix the target page/server issue or point the canonical to the correct live URL. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Check template-wide canonical rules if many pages are affected. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • The canonical points to a URL that redirects again instead of directly to the final preferred page. Search engines can follow it, but the extra hop adds ambiguity and unnecessary crawling.

Try These Steps

  1. Follow the redirect and identify the final 200 URL. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Update the canonical to point directly to the final URL. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Check SEO-plugin settings, domain changes, slash rules, and old template URLs. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • URL A points canonically to URL B, which then points canonically to URL C or another destination. Every duplicate should normally point directly to the same final 200-status canonical URL.

Try These Steps

  1. Map the chain and identify the one final preferred URL. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Point every duplicate directly to that final canonical. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Remove conflicting canonicals added by themes, plugins, apps, or custom code. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • The robots.txt file cannot be reached directly because it redirects repeatedly or loops. Crawlers may stop following the chain and be unable to read the site’s crawl rules.

Try These Steps

  1. Open /robots.txt and trace every redirect. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Remove redirect rules affecting robots.txt or point directly to the final file. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Check CDN, HTTPS, www, maintenance, and security-plugin redirect rules. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

What It Means

  • The robots.txt file returns a server, network, DNS, or permission error instead of a readable file or a normal 404. Google may temporarily reduce crawling or rely on an older cached copy while the file is unavailable.

Try These Steps

  1. Open /robots.txt while logged out and test its HTTP status. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Remove authentication, firewall, CDN, or security-plugin blocks.
  3. Ask the host to fix server errors or routing for the file. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

What It Means

  • The robots.txt file contains unsupported syntax, malformed rules, or an incorrect format. Crawlers ignore lines they cannot understand, so the actual crawl behavior may differ from what the site owner intended.

Try These Steps

  1. Test the file in Google Search Console or a robots validator. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Correct syntax, user-agent groups, paths, and encoding.
  3. On Shopify or WordPress, review custom robots templates/plugins before editing server files. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

Redirects

What It Means

  • The redirect sends visitors and crawlers to a destination that is broken or unavailable. The redirect does not solve the original problem because there is still no usable final page.

Try These Steps

  1. Follow the redirect to identify the final failing URL. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Change the redirect destination to the correct live page. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Restore the destination only if it should still exist. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • Two or more URLs keep redirecting back to one another, so no final page can load. Browsers and crawlers eventually stop, making the content completely inaccessible.

Try These Steps

  1. Trace the full redirect path with a header checker. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Remove or rewrite the conflicting redirect rules. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Check host/CDN rules, WordPress redirect plugins, .htaccess, theme code, and Shopify URL redirects. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • A URL passes through multiple redirects before reaching the final page. Each extra hop adds delay, consumes crawl requests, and increases the chance that a link or rule breaks later.

Try These Steps

  1. Identify the final live URL. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Update internal links, canonicals, and sitemap entries to the final URL. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Replace the first redirect so it goes directly to the final destination. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • The page redirects through HTML after the page begins loading instead of using a normal server-side 301 or 302. Search engines can often process it, but it is slower, less reliable, and can create a poor user experience.

Try These Steps

  1. Confirm whether the redirect is intentional and permanent. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Replace it with a 301 or 302 at the server, CDN, plugin, or Shopify redirect tool. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Remove page-builder, theme, or script-based refresh code. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • The audited URL redirects to another URL. A redirect may be intentional, but internal links, sitemap entries, canonicals, and hreflang tags should normally reference the final URL directly.

Try These Steps

  1. Check whether the redirect is intentional.
  2. Update internal links to the final destination when possible.
  3. Use 301/308 for permanent moves and temporary codes only for temporary routing.

What It Means

  • The server says the move is temporary rather than permanent. That is appropriate for short-term routing, but it can delay consolidation when the old URL has actually been replaced for good.

Try These Steps

  1. Confirm whether the move is truly temporary. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Change permanent moves to a 301/308. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Check redirect plugins, server rules, Shopify redirects, geolocation, and app routing. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

Sitemap

What It Means

  • The sitemap lists URLs that return client errors instead of indexable pages. A sitemap should contain the live canonical URLs the site wants search engines to crawl and consider for indexing.

Try These Steps

  1. Open the listed URLs and confirm whether they should exist. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Restore them or remove them from sitemap generation. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Update publishing, SEO-plugin, app, or custom-sitemap rules. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

What It Means

  • The sitemap lists URLs that are failing at the server. This tells search engines the pages are important while the server simultaneously prevents them from being crawled.

Try These Steps

  1. Retest the pages and review server logs. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Fix the page/server failure, then regenerate the sitemap. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Remove URLs only if they are intentionally retired. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

What It Means

  • The sitemap contains old URLs that redirect elsewhere. Search engines must follow the redirect and receive a weaker, less direct signal than if the sitemap listed the final URL.

Try These Steps

  1. Find each final 200 destination. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Update the sitemap source so it lists final canonical URLs. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Check domain, permalink, collection, product, and slash changes. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

What It Means

  • One or more URLs listed in the sitemap did not respond before the crawler timed out. This usually indicates a page-speed, server-load, firewall, or application reliability issue rather than a sitemap-format problem.

Try These Steps

  1. Retest affected URLs outside the audit. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Fix server, plugin/app, database, firewall, or third-party delays.
  3. Ask the host to review resource limits and logs if many URLs time out. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

What It Means

  • The sitemap says the page should be discovered for search, while a noindex directive says it must not appear in search results. These two instructions contradict each other.

Try These Steps

  1. Decide whether each page should be indexed. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Remove noindex from pages that belong in search. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Exclude intentionally noindexed pages from the sitemap. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

What It Means

  • The sitemap lists a URL that declares another URL as canonical. Sitemaps should reinforce the preferred URL set, not advertise duplicate or alternate versions.

Try These Steps

  1. Confirm the intended canonical URL. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Change the sitemap source to output only canonical 200 URLs. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Review SEO-plugin, Shopify app, translation, parameter, and duplicate-template settings. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

What It Means

  • A sitemap exceeds the supported limit of 50,000 URLs or 50 MB uncompressed. Oversized files may not be processed completely and should be split into smaller sitemaps under a sitemap index.

Try These Steps

  1. Confirm URL count and uncompressed file size.
  2. Split it into smaller sitemaps and use a sitemap index.
  3. Fix custom generators or apps that fail to paginate sitemap files. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

What It Means

  • SE Ranking could not find an XML sitemap. Small, fully linked sites can still be crawled without one, but most WordPress and Shopify sites benefit from a sitemap for discovery and monitoring.

Try These Steps

  1. Check common sitemap URLs and Search Console submissions.
  2. Enable sitemap output in the SEO plugin or platform.
  3. Create a sitemap only for canonical, indexable URLs. Clear caches, regenerate the file, and rerun the audit after confirming the public URL returns the expected response.

Meta Tags

What It Means

  • The page has no HTML title tag for search engines and browsers to use. Google may create its own title from headings or links, but the site loses its clearest opportunity to describe the page in search results.

Try These Steps

  1. Add a unique SEO title in the page, product, post, or SEO-plugin settings. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Check whether the theme or builder template failed to output the title. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Fix template or code conflicts if many pages are missing titles. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • The page contains more than one title tag, usually because a theme, SEO plugin, app, or custom template outputs an additional copy. Search engines may ignore one or choose unpredictably between them.

Try These Steps

  1. View page source and identify each title source. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Disable duplicate output from the theme, SEO plugin, app, or custom code. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Check header templates and client-side scripts that inject metadata. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • Multiple URLs use the same title tag even though they represent different pages. This makes pages harder to distinguish in search results and often signals duplicated templates, thin variations, or missing page-specific variables.

Try These Steps

  1. Confirm whether the pages are truly different or accidental duplicates. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Write unique titles for important indexable pages. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Use template variables for product, service, category, and location pages. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • The page has no meta description. This does not prevent ranking, but Google must create the search snippet from page content and the site loses control over the suggested search-result message.

Try These Steps

  1. Write one for important indexable pages. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Set it in the SEO plugin, Shopify search listing, or page settings. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Fix template output if descriptions are entered but missing from source. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • The page outputs more than one meta description, usually from overlapping plugins, theme code, or app injections. Search engines may ignore the duplicates or select one unpredictably.

Try These Steps

  1. View source and identify the duplicate source. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Disable one theme, plugin, app, or custom-code output. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Check old proxies, load balancers, or third-party checkout/subdomain services.

Content

What It Means

  • Two or more URLs contain the same or very similar primary content. Google usually groups the URLs and selects one canonical, but conflicting versions can waste crawling and cause the wrong URL to rank.

Try These Steps

  1. Confirm whether both URLs need to exist.
  2. Choose a preferred URL and use canonical tags, redirects, or noindex as appropriate.
  3. Fix duplicate templates, parameters, tags, archives, products, or copied page content.

What It Means

  • The page contains more than one canonical tag, especially harmful when they point to different URLs. Google may ignore all of them because the page is giving contradictory instructions.

Try These Steps

  1. View source and list every canonical tag. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Keep one correct canonical and disable the others. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Check SEO plugins, themes, apps, translation tools, and custom header code. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • The audited URLs do not end with a trailing slash. This is only a real problem when slash and non-slash versions both load, redirect inconsistently, or appear separately in links, sitemaps, and canonicals.

Try These Steps

  1. First confirm whether slash and non-slash versions both load.
  2. Choose one format and enforce it with redirects and canonicals. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Update internal links and sitemap URLs; do not change format only to satisfy the audit.

What It Means

  • A URL contains two slashes inside the path, such as /services//design/. Depending on the server, this may create a duplicate URL, redirect, or 404 and usually points to a broken URL-building rule.

Try These Steps

  1. Find where the malformed URL is linked or generated.
  2. Correct it in the builder, menu, theme, app, or database. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Fix URL-joining code that combines a base URL and path incorrectly.

What It Means

  • Both the www and non-www hostnames may be accessible without one consistently redirecting to the preferred version. This can create duplicate host versions and split links, canonicals, analytics, and crawl signals.

Try These Steps

  1. Test all HTTP/HTTPS and www/non-www versions. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Choose one primary host and redirect all alternates to it. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Align domain settings, canonicals, sitemaps, Search Console, CDN, and DNS. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • The page has no primary on-page heading. An H1 is not a strict indexing requirement, but it helps users and search engines quickly understand the page’s main topic and supports clear page structure.

Try These Steps

  1. Add one clear H1 in the page builder or content editor. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Check theme/builder templates where the visible page title may be disabled.
  3. Fix template logic if many pages are affected. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • An H1 element exists but contains no readable text. This usually means a page-builder field, dynamic title, hidden element, or template output failed to provide the page’s main heading.

Try These Steps

  1. Inspect the page and source to find the empty heading. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Add the intended heading or remove the empty widget/element.
  3. Check dynamic fields, hidden responsive elements, and template conditions. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • An image URL redirects before the image loads. The image may still display, but the extra request slows loading and leaves old asset URLs in the page, CSS, srcset, structured data, or sitemap.

Try These Steps

  1. Find the final image URL.
  2. Replace the image in the builder, media library, theme, or code. On WordPress, check the Media Library and builder widget; on Shopify, check the image picker, product data, and Liquid output.
  3. Regenerate thumbnails/CDN URLs if old image paths are being redirected.

What It Means

  • An image request returns a client error, so the image does not load. Broken images harm usability, accessibility, visual quality, and the page’s ability to appear properly in image search.

Try These Steps

  1. Open the image URL and locate every page using it. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Re-upload/replace the image or correct the file path. On WordPress, check the Media Library and builder widget; on Shopify, check the image picker, product data, and Liquid output.
  3. Update old media URLs in content, CSS, theme files, database, or app settings. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • The image server, CDN, or transformation service failed while delivering the file. Repeated failures can break layouts, reduce trust, and delay important above-the-fold content.

Try These Steps

  1. Retest the image URL and check whether the issue is intermittent. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Review CDN, image optimization, permissions, hotlink protection, and origin errors. On WordPress, check the Media Library and builder widget; on Shopify, check the image picker, product data, and Liquid output.
  3. Replace the image service or escalate repeated failures to the host/developer. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • An image has no alt attribute or no useful text alternative. Informational and linked images need concise context for accessibility and image understanding, while purely decorative images should normally use an empty alt attribute.

Try These Steps

  1. Add concise alt text to informative images. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Use empty alt text for purely decorative images. On WordPress, check the Media Library and builder widget; on Shopify, check the image picker, product data, and Liquid output.
  3. Update repeated template images in the media library, builder, theme, or product data.

What It Means

  • The delivered image file is much larger than needed for its displayed size or uses inefficient compression. Oversized images increase mobile data use and often worsen Largest Contentful Paint.

Try These Steps

  1. Resize and compress the source image.
  2. Use WebP/AVIF and responsive image sizes where supported. On WordPress, check the Media Library and builder widget; on Shopify, check the image picker, product data, and Liquid output.
  3. Replace oversized builder backgrounds, hero images, product media, or theme assets.

Localization

What It Means

  • An hreflang value uses an unsupported or malformed language or region code. Search engines may ignore that annotation, preventing the intended language or regional page from being matched to users.

Try These Steps

  1. Check the exact hreflang value against supported language/region formats.
  2. Correct it in the translation plugin, app, theme, or template.
  3. Use language-region pairs such as en-US only when a regional version truly exists.

What It Means

  • The hreflang annotation identifies one language while the HTML lang attribute identifies another. Google primarily evaluates visible text, but the mismatch creates maintenance confusion and can harm accessibility tools.

Try These Steps

  1. Confirm the actual language of the page. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Correct the HTML lang or hreflang value in the translation system. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Check template overrides and mixed-language content. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • The same language or language-region value is assigned to more than one URL in the same hreflang set. Search engines cannot tell which URL should represent that audience.

Try These Steps

  1. Identify which URL should represent that language/region. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Remove or correct duplicate hreflang entries. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Check translation plugins/apps, pagination, canonicals, and alternate-domain rules. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • An hreflang tag points to a URL that canonicalizes somewhere else. The localization signal and canonical signal disagree, so the alternate language relationship may be ignored.

Try These Steps

  1. Confirm the correct canonical URL for that language. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Update hreflang to the canonical 200 URL. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Fix translation templates so canonical and hreflang systems agree. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • An alternate-language URL redirects, is missing, or is failing at the server. Hreflang targets should resolve directly to live, indexable, canonical pages.

Try These Steps

  1. Open the alternate URL and determine its final status. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Point hreflang directly to a live canonical 200 URL. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Restore or remove obsolete translated pages and update all language clusters. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • Page A lists Page B as an alternate, but Page B does not list Page A in return. Google may ignore the unconfirmed relationship because hreflang clusters are expected to be reciprocal.

Try These Steps

  1. Compare hreflang tags on every page in the language set. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Add matching reciprocal entries. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Fix translation-plugin, app, sitemap, or template rules generating incomplete clusters. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • The page’s hreflang set lists alternate versions but does not include a self-referencing entry for the current URL. A complete cluster should identify every member, including the page itself.

Try These Steps

  1. Inspect the full hreflang set on the page. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Add a self-referencing hreflang entry. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Correct the shared translation template or plugin configuration. If many pages share the issue, fix the template or global setting instead of editing every page individually.

What It Means

  • The hreflang set has no fallback URL for users whose language or region does not match a listed version. This is optional, but useful for global homepages, selectors, and default-language pages.

Try These Steps

  1. Decide whether the site needs a global fallback or language selector. Check the rendered page source, not only the editor, so you can see what search engines actually receive.
  2. Add x-default to that fallback page. On WordPress, inspect the SEO plugin plus theme/builder output; on Shopify, inspect theme.liquid, templates, and SEO or translation apps.
  3. Skip it when there is no meaningful fallback page. If many pages share the issue, fix the template or global setting instead of editing every page individually.

Speed & Performance

What It Means

  • The page is slow overall, but this audit line does not identify one single cause. Server response, images, scripts, CSS, fonts, apps, page-builder output, and third-party tools can all contribute.

Try These Steps

  1. Run PageSpeed Insights and check the request waterfall. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Optimize the largest images, fonts, scripts, styles, and third-party tools.
  3. Review hosting, caching, CDN, plugins/apps, and builder bloat. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

What It Means

  • Visible content appears slowly during a lab test. Speed Index is a diagnostic Lighthouse metric rather than a Core Web Vital, but it helps show whether the page looks blank or incomplete for too long.

Try These Steps

  1. Check render-blocking CSS/JS and above-the-fold assets. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Preload or prioritize critical hero images and fonts.
  3. Reduce sliders, animations, popups, and heavy builder sections. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

What It Means

  • Real users are waiting too long for the largest above-the-fold content element to appear. Field LCP is a Core Web Vital and often points to slow server response, a late-loading hero image, blocking CSS, or client-side rendering.

Try These Steps

  1. Identify the LCP element in PageSpeed Insights or Chrome DevTools. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Optimize and prioritize that image, heading, video poster, or content block.
  3. Improve server response, caching, CDN delivery, and render-blocking resources. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

What It Means

  • A controlled performance test found that the largest visible element loads too slowly. Lab data is useful for diagnosis, but it should be compared with real-user data before deciding how severe the issue is.

Try These Steps

  1. Identify the lab LCP element and compare it with field data. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Reduce its file size and make it discoverable early.
  3. Defer noncritical scripts/styles and improve server response. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

What It Means

  • Real users experience unexpected movement while the page loads or updates. Field CLS is a Core Web Vital and commonly comes from images without dimensions, fonts, ads, banners, forms, or dynamically inserted content.

Try These Steps

  1. Review field data and reproduce shifts on mobile and desktop. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Set width/height or aspect-ratio for images, videos, ads, and embeds.
  3. Reserve space for banners, forms, fonts, cookie tools, and injected widgets. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

What It Means

  • A controlled test detected layout movement during page load. Lab testing can reveal repeatable shifts, but it may miss movements caused later by user interaction, personalization, or third-party tools.

Try These Steps

  1. Watch the Lighthouse filmstrip or layout-shift regions. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Add dimensions and reserved space to moving elements.
  3. Fix late-loading fonts, sticky headers, sliders, and builder animations. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

What It Means

  • Real users wait too long before any text, image, or other page content appears. FCP is not a Core Web Vital, but it helps show whether the delay begins with the server, blocking resources, fonts, or initial rendering.

Try These Steps

  1. Check server response time and field data by template. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Reduce render-blocking CSS, fonts, and synchronous scripts.
  3. Improve caching, CDN delivery, and critical content rendering. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

What It Means

  • A controlled test found that the first visible page content appears slowly. Use it as a diagnostic metric alongside server response, render-blocking CSS, fonts, and JavaScript.

Try These Steps

  1. Review TTFB and render-blocking requests. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Inline or prioritize critical CSS and defer noncritical assets.
  3. Reduce plugin/app and third-party script startup work. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

What It Means

  • Real users experience slow responses after clicking, tapping, or typing. INP is a Core Web Vital and usually indicates heavy JavaScript, long main-thread tasks, expensive event handlers, or large rendering updates.

Try These Steps

  1. Use DevTools performance traces or RUM data to find slow interactions. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Reduce JavaScript work and break up long tasks.
  3. Remove or delay heavy third-party scripts, widgets, filters, and animations. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

What It Means

  • The page takes a long time before it can respond reliably to user input in a lab test. TTI is an older diagnostic metric; INP and Total Blocking Time are usually more useful for current troubleshooting.

Try These Steps

  1. Check long tasks and JavaScript execution in Lighthouse. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Defer or remove noncritical scripts. Temporarily disable or defer one suspected plugin, app, widget, or third-party script at a time on a staging copy.
  3. Reduce builder effects, app/plugin scripts, and third-party tags. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

What It Means

  • Long main-thread tasks block the browser from responding during the lab test. TBT is not a field Core Web Vital, but it is a useful clue for JavaScript execution and often correlates with poor INP.

Try These Steps

  1. Review Lighthouse long tasks and script execution time. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Split, defer, or remove heavy JavaScript. Temporarily disable or defer one suspected plugin, app, widget, or third-party script at a time on a staging copy.
  3. Delay chat, tracking, sliders, maps, reviews, and other third-party widgets. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

What It Means

  • The page sends an unusually large HTML document before images, CSS, and JavaScript are even considered. Large builder markup, mega menus, hidden duplicate sections, inline data, and app output can slow transfer and browser parsing.

Try These Steps

  1. Inspect source size and DOM complexity. Compare the affected template in PageSpeed Insights and Chrome DevTools to identify the largest contributor.
  2. Remove hidden, duplicated, or unused builder sections and widgets. Temporarily disable or defer one suspected plugin, app, widget, or third-party script at a time on a staging copy.
  3. Reduce oversized menus, inline data, app blocks, shortcodes, and template markup. Retest both mobile and desktop after each change; keep only changes that improve the affected metric without breaking the page.

JavaScript

What It Means

  • A required JavaScript file is missing or failing at the server. Depending on the file, this can break navigation, forms, content rendering, tracking, structured data, or other page functionality.

Try These Steps

  1. Open the file URL and identify which page/theme/plugin/app loads it. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Restore, replace, or remove the broken script reference. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Clear caches and rebuild generated assets after updates. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • A JavaScript request redirects before the file loads. The script may still work, but the extra request adds delay and usually means the page references an outdated asset URL.

Try These Steps

  1. Follow the redirect to the final script URL.
  2. Update the reference in theme, plugin, app, template, or custom code. Temporarily disable or defer one suspected plugin, app, widget, or third-party script at a time on a staging copy.
  3. Rebuild asset/CDN URLs and clear caches.

What It Means

  • A third-party JavaScript file redirects or fails. The site may have limited control over it, but the dependency can still delay the page or break widgets, consent tools, analytics, forms, and visible content.

Try These Steps

  1. Confirm whether the external tool is still needed. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Update to the vendor’s current URL or reinstall the integration. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Remove or replace the tool if failures continue. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

CSS

What It Means

  • A stylesheet is missing or failing, so the browser cannot apply some or all of the intended design. This can make content unreadable, hide elements, break mobile layouts, and create major layout shifts.

Try These Steps

  1. Open the CSS URL and identify its source. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Restore, regenerate, or remove the broken stylesheet reference. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Clear builder/plugin/theme/CDN caches and rebuild generated CSS. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • A stylesheet URL redirects before the CSS loads. Because CSS can block rendering, the extra hop can delay the first visible page and indicates that an old asset URL is still being used.

Try These Steps

  1. Follow the redirect to the final CSS URL.
  2. Update the reference to the final asset URL. Temporarily disable or defer one suspected plugin, app, widget, or third-party script at a time on a staging copy.
  3. Regenerate theme/builder assets and clear caches/CDN.

What It Means

  • A third-party stylesheet redirects or fails. This can break embedded tools, fonts, design systems, or widgets and may leave the page visibly incomplete.

Try These Steps

  1. Confirm which integration or service loads it. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Update/reinstall the integration or vendor URL. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Remove or replace the dependency if it is obsolete or unreliable. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • No crawlable internal link points to the page, making it an orphan page within the site structure. Search engines may find it through a sitemap or external link, but the site provides little context or importance signaling.

Try These Steps

  1. Confirm whether the page should be public and indexable.
  2. Add a relevant link from navigation, a hub page, related content, or a collection/category.
  3. Remove, redirect, or noindex abandoned pages that should not remain active.

What It Means

  • An internal link points to an old URL that redirects to another page. Visitors usually reach the destination, but the extra hop slows navigation and keeps outdated URLs embedded throughout the site.

Try These Steps

  1. Export the source pages and final destination URLs. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Change links directly in Elementor, Cornerstone, Avada, menus, Shopify sections, or content. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Use a link-update/search-replace tool, then handle stubborn cases in the database or code. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • An outbound link points to a page that is missing, forbidden, or otherwise unavailable. This is mainly a usability and content-maintenance issue, especially when the link supports an important claim or resource.

Try These Steps

  1. Verify the link manually in a normal browser. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Update it to the current resource or a suitable replacement. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Remove the link if no useful destination remains. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

What It Means

  • An outbound link points to a server that is currently failing. The outage may be temporary, so confirm it more than once before replacing or removing the link.

Try These Steps

  1. Retest later to rule out a temporary outage. Test the exact URL in an incognito browser and with a header/status checker before changing anything.
  2. Replace the link if the failure persists. Look for the source in menus, builder buttons, templates, redirect plugins/apps, server rules, and hardcoded theme code.
  3. Remove it when the resource is no longer reliable or necessary. After the fix, update all internal references to the final URL and rerun the crawl to confirm no other source still uses the old one.

Mobile Optimization

What It Means

  • The page does not tell mobile browsers to size the layout to the device width. Mobile users may see a shrunken desktop page with tiny text, awkward zooming, and broken responsive behavior.

Try These Steps

  1. View source and confirm the viewport tag is absent.
  2. Add a standard responsive viewport tag in the theme/header template.
  3. Check theme, child theme, custom header code, or app output if only some templates fail.

What It Means

  • The viewport is locked to a specific pixel width instead of adapting to the user’s device. This undermines responsive design across phones, tablets, foldables, and accessibility zoom levels.

Try These Steps

  1. Inspect the viewport tag in source.
  2. Replace the fixed width with width=device-width.
  3. Remove duplicate viewport tags added by themes, plugins, apps, or custom code.

Other

What It Means

  • The site does not provide a usable favicon for browser tabs and eligible Google search-result attribution. It is not a ranking requirement, but it weakens brand recognition and makes the site look unfinished.

Try These Steps

  1. Upload/select a site icon in WordPress Customizer or Site Identity.
  2. Add favicon files and link tags in the theme/header when needed.
  3. On Shopify, set the favicon in theme settings and confirm the file loads.

What It Means

  • The page depends on obsolete browser plugin technology, such as Flash, Java applets, or another unsupported embedded format. Modern browsers and crawlers may not display the content at all.

Try These Steps

  1. Identify the embed/object or unsupported content.
  2. Replace Flash, Java, or legacy plugin content with HTML5, video, SVG, iframe, or JavaScript alternatives.
  3. Remove abandoned widgets, old theme elements, or outdated third-party embeds.