Reference
Site audit issue reference
Every issue an audit can raise, with why it matters and how to fix it.
Every issue a NdovuSEOLabs site audit can raise (82 in all), grouped as in the app, with why it matters and how to fix it. Priority (P0–P3) is worked out for your site; see how priority is scored.
Recheck means you can verify the fix on just its URLs with Recheck these URLs; the others need a new audit.
HTTP & accessibility
Server error (5xx)
Critical Blocks indexing Recheck
Why it matters. The page returned a 5xx server error. Search engines that repeatedly see server errors will crawl the site less and may drop the page from the index.
How to fix. Check the server logs for this URL and fix the underlying error. If the page is gone, return a 404/410 or redirect it to a relevant page instead of erroring.
Page returns an error (4xx)
Warning Blocks indexing Recheck
Why it matters. This crawled URL returned a client error (e.g. 404). If it is referenced from your sitemap or other pages, crawlers keep wasting requests on it.
How to fix. First check where the URL comes from. If a template generates it (a page number past the last page, a filter link that keeps a stale page parameter), fix the template that builds the link; making that URL return 200 would serve an empty or misleading page. If a real page should exist here, restore it. If it is intentionally gone, remove it from the sitemap and internal links, and consider a 301 redirect to the closest live page.
Retired page (410 Gone)
Info New audit to verify
Why it matters. This URL answers 410 Gone, and nothing on the site points at it any more: no internal link in a complete crawl, no sitemap entry. The audit only knows it from Search Console, Analytics or an imported list. A 410 tells search engines the page was removed on purpose, so they drop it quickly; this is a record of a retirement, not breakage.
How to fix. No action is needed if the removal was intended. If the page had a true successor (the same product, article or listing at a new address), a 301 redirect to it keeps its visitors and links; never redirect to an unrelated page just to avoid the 410.
Missing page known only from outside data (404)
Info Medium confidence New audit to verify
Why it matters. This URL answers 404 Not Found, and nothing on the site points at it any more: no internal link in a complete crawl, no sitemap entry. The audit only knows it from Search Console, Analytics or an imported list, so visitors reach it from old search results, bookmarks or other sites, not from your pages.
How to fix. If the page has a true successor, 301-redirect to it. If it was removed on purpose, answering 410 Gone makes that explicit and search engines drop it sooner. Leaving a 404 is also acceptable when there is no relevant replacement.
Redirect chain
Warning Recheck
Why it matters. Reaching the final page requires two or more consecutive redirects. Each hop adds latency, leaks link equity, and burns crawl budget; long chains may not be followed at all.
How to fix. Point the first URL (and any internal links) directly at the final destination so there is at most one redirect.
Redirect loop
Warning Blocks indexing Recheck
Why it matters. This redirect eventually points back to itself, so the URL never resolves. Browsers and crawlers give up with an error.
How to fix. Trace the redirect rules for this URL and break the cycle so the chain terminates at a real 200 page.
Crawl control
Crawler was blocked
Critical Blocks indexing Recheck
Why it matters. The site returned a bot challenge or access denial (e.g. a Cloudflare challenge or a 403) instead of the page. We report this honestly rather than pretending the page is broken — but it means this page could not be audited, and other crawlers like search engines may face similar friction.
How to fix. If you own this site, allowlist the "NdovuBot" user agent in your WAF/bot-protection settings (on Cloudflare: a WAF custom rule that skips bot protection when the user agent contains "NdovuBot"; on some free tiers you may need to relax bot protection). Then re-run the audit. On Shopify, use Crawler access instead (Online Store → Preferences → Crawler access) and paste the signature into NdovuSEOLabs under Settings → Crawler access. How to allow and verify the crawler: https://ndovuseolabs.com/ndovubot/
Rate limited (429)
Warning Recheck
Why it matters. The server answered 429 Too Many Requests, so this page could not be audited. The crawler paused for the server's Retry-After and tried the page once more before moving on.
How to fix. Raise the rate limit for crawlers, or allowlist the "NdovuBot" user agent in your rate-limiting rules (on Cloudflare: a rate-limiting rule exception matching that user agent). Then re-run the audit. Re-running with fewer pages also helps if the limit is strict. On Shopify, use Crawler access instead (Online Store → Preferences → Crawler access) and paste the signature into NdovuSEOLabs under Settings → Crawler access. How to allow and verify the crawler: https://ndovuseolabs.com/ndovubot/
Crawl stopped early: rate limit
Warning New audit to verify
Why it matters. The site refused several pages in a row with 429 Too Many Requests, or kept the crawler waiting for too long, so we stopped requesting pages. This report is incomplete; URLs we did not fetch are not recorded as broken or rate limited.
How to fix. Re-run the audit after the site's rate limit resets, or ask the site owner to allow the NdovuBot crawler (https://ndovuseolabs.com/ndovubot/). On Shopify, use Crawler access instead (Online Store → Preferences → Crawler access) and paste the signature into NdovuSEOLabs under Settings → Crawler access.
Crawl stopped early: bot protection
Warning New audit to verify
Why it matters. Nearly all of the first pages the crawler fetched came back blocked (403, 401 or a bot challenge), so the audit stopped crawling instead of collecting more refusals and built the report from what it had. The site itself may be fine for visitors; its firewall or bot protection is refusing this crawler.
How to fix. Allowlist the "NdovuBot" user agent in the site's firewall or bot protection (on Cloudflare: a WAF custom rule that skips bot protection for that user agent), or on Shopify use Crawler access. Then run the audit again.
Crawl stopped early: time limit
Warning New audit to verify
Why it matters. Audits that render JavaScript stop crawling after 22 hours, and this one reached that limit. This report is incomplete; URLs we did not fetch are not recorded as broken.
How to fix. Re-run the audit with a lower page limit, or without Render JavaScript if the site's content and links are in its HTML. Rendering is billed only for pages actually rendered.
Crawl stopped early: cost limit reached
Warning New audit to verify
Why it matters. Many pages on this site needed our advanced renderer, so the audit reached its cost limit and stopped. You were only charged for the pages we rendered.
How to fix. If the site doesn't need JavaScript to show its content, re-run with Render JavaScript off.
Crawl stopped early: page limit
Warning New audit to verify
Why it matters. The audit reached its page limit before visiting every URL it found, so this report covers part of the site. Orphan pages are not checked on a partial crawl.
How to fix. Re-run the audit with a higher page limit. If it is already at the maximum, add a robots.txt group for the "NdovuBot" user agent that disallows sections you don't need audited, such as tag archives or filtered listings, so the limit goes to the pages that matter: https://ndovuseolabs.com/ndovubot/
Possible crawl trap (URL explosion)
Warning Medium confidence New audit to verify
Why it matters. One path produced an unusually large number of distinct query-string variants during the crawl (facets, sorting, session IDs, calendars), and search engines are still led to them: a followed link, redirect or sitemap reaches at least one variant, or a crawled variant is indexable. Such URL spaces can consume a search engine's crawl attention on near-duplicate pages. The evidence lists the parameters involved and how many variants are followed and indexable.
How to fix. Check which parameters create the variants. Stop linking to non-useful combinations (or mark those links nofollow), canonicalize them to the clean URL or noindex them, or disallow the parameter pattern in robots.txt if it should never be crawled.
Many parameter URLs, kept out of search
Info Medium confidence New audit to verify
Why it matters. One path produced an unusually large number of distinct query-string variants (often enquiry, booking or quote links), but every link to them is nofollow, no sitemap lists them, and none of the crawled variants is indexable. Search engines are already steered away, so this is not a crawl trap in practice. It stays on record because a server that accepts any value for a token parameter can still answer an unlimited number of URLs.
How to fix. No action is needed if the variants are deliberate. To close the space completely, have the server answer 404 for unknown token values, or move the action behind a form (POST) or a fragment instead of a crawlable URL.
Indexability
Robots meta tag and X-Robots-Tag disagree
Warning Recheck
Why it matters. The page's robots meta tag and its X-Robots-Tag HTTP header give opposite indexing instructions: one says noindex, the other says index. Search engines obey the most restrictive directive, so the page stays out of the index whichever one was meant.
How to fix. Decide whether the page should be indexed and declare that in one place. Usually the header comes from the server or a security plugin and the meta tag from the SEO plugin; remove or align the one that is wrong.
Conflicting canonical signals
Warning Recheck
Why it matters. The page declares different canonical URLs in its HTML <link rel=canonical> and its HTTP Link header. When signals conflict, search engines ignore both and choose their own canonical.
How to fix. Pick one canonical URL and declare it in exactly one place (HTML head is the most common); remove or align the other declaration.
Page is noindex
Info May be intentional Recheck
Why it matters. The page asks search engines not to index it (via robots meta tag or X-Robots-Tag header). That's often intentional — this is a heads-up, not an error.
How to fix. If this page should rank, remove the noindex directive. If it's intentional (admin, thank-you, filter pages), no action is needed.
Canonicalized to another URL
Info May be intentional Recheck
Why it matters. The page declares a different URL as its canonical, telling search engines to index that URL instead. Fine when intentional (parameter pages, syndication) — a problem if this page was meant to rank.
How to fix. If this page should rank on its own, set its canonical to itself. Otherwise no action is needed.
Canonical points to a non-indexable URL
Warning New audit to verify
Why it matters. The page's canonical URL was crawled and redirects, returns an error, or is noindex. Google usually ignores a canonical that points at a page it cannot index and picks its own.
How to fix. Point the canonical at the final, live, indexable URL.
Sitemaps
No XML sitemap found
Warning New audit to verify
Why it matters. No sitemap was declared in robots.txt, found at /sitemap.xml or /sitemap_index.xml, or submitted in Search Console. Small, well-linked sites can be crawled without one, but a sitemap is how Google learns about new and changed URLs on everything else.
How to fix. Publish an XML sitemap of the canonical, indexable URLs you want in search, reference it with a Sitemap: line in robots.txt, and submit it in Search Console.
Sitemap cannot be fetched
Warning New audit to verify
Why it matters. A sitemap referenced by robots.txt, Search Console or a sitemap index returned an error, timed out, or redirected off-site. Google cannot read the URLs it lists.
How to fix. Make the sitemap URL return 200 with the XML document, or remove the stale reference from robots.txt, the sitemap index, and Search Console.
Sitemap is not valid XML
Warning New audit to verify
Why it matters. The sitemap response is not a parseable <urlset> or <sitemapindex> document (an HTML page, malformed XML, or the wrong root element). Search engines reject the whole file.
How to fix. Serve the file as XML following the sitemaps.org protocol. Check the generator plugin or route that produces it; an HTML error page at the sitemap URL is the most common cause.
Sitemap exceeds protocol limits
Warning New audit to verify
Why it matters. A sitemap file lists more than 50,000 URLs or is larger than 50 MB uncompressed. Google ignores what is past the limit, so some URLs are never read from it.
How to fix. Split the file into several sitemaps of at most 50,000 URLs and reference them from a sitemap index.
Sitemap lists URLs on another host or protocol
Warning New audit to verify
Why it matters. The sitemap contains URLs whose host or protocol differs from the sitemap's own location (for example http:// URLs in an https sitemap, or a staging hostname). Google ignores URLs outside the sitemap's scope.
How to fix. Generate sitemap URLs from the site's canonical scheme and hostname. Check the CMS's configured site URL.
Sitemaps list the same URL more than once
Info New audit to verify
Why it matters. The same URL appears more than once across the site's sitemaps. It is harmless to Google but usually means two generators or overlapping partitions.
How to fix. List each canonical URL in one sitemap file only.
Invalid or future lastmod dates
Info New audit to verify
Why it matters. Entries have <lastmod> values that are not W3C datetimes or lie in the future. Google uses lastmod only when it is consistently accurate, so bad values make the whole file's dates untrustworthy.
How to fix. Emit lastmod as the date the page's main content last changed, in W3C datetime format (YYYY-MM-DD or a full timestamp).
Lastmod appears to be generated at request time
Info Medium confidence New audit to verify
Why it matters. Nearly every entry in this sitemap carries the day it was fetched as its lastmod. That usually means the generator stamps the current time instead of each page's real modification date, which teaches Google to ignore the field.
How to fix. Set lastmod from each page's content-modified date. Leave it out rather than faking freshness.
Sitemap lost a large share of its URLs
Warning Medium confidence New audit to verify
Why it matters. Compared with the previous audit, this sitemap lists far fewer URLs, or it disappeared, and its URLs were not moved to another sitemap (a file that was renamed or split is not reported). The evidence says where the URLs it used to list are now: listed elsewhere, still live but listed nowhere, kept out of search (noindex, redirected or gone), or not crawled this time. It can be a deliberate cleanup, but sudden drops are a common symptom of a broken generator, a failed export, or a section unpublished by mistake.
How to fix. If the removed URLs are now noindex, redirected or gone on purpose, no action is needed. If live, indexable pages are listed nowhere, check the sitemap generator and the section whose URLs disappeared.
Sitemap lists a redirecting URL
Warning New audit to verify
Why it matters. The sitemap lists a URL that redirects. Sitemaps should contain final, canonical URLs; redirects waste crawl requests and send mixed signals about which URL to index.
How to fix. Replace the URL in the sitemap with the redirect's final destination.
Sitemap lists a broken URL
Critical Blocks indexing New audit to verify
Why it matters. The sitemap lists a URL that returns a 4xx or 5xx status. You are asking Google to index a page that does not load.
How to fix. Restore the page, or remove it from the sitemap (and redirect it if it moved).
Sitemap lists a noindex URL
Warning New audit to verify
Why it matters. The sitemap asks Google to index a URL whose robots meta tag or X-Robots-Tag says noindex. One of the two signals is wrong.
How to fix. Remove the URL from the sitemap if noindex is intended; otherwise remove the noindex directive.
Sitemap lists a non-canonical URL
Warning New audit to verify
Why it matters. The sitemap lists a URL that declares a different canonical URL. Sitemaps should list only canonical URLs.
How to fix. List the canonical URL in the sitemap instead, or fix the canonical tag if this URL is the one that should rank.
Sitemap lists a URL blocked by robots.txt
Warning New audit to verify
Why it matters. The sitemap lists a URL that robots.txt disallows. Google cannot crawl it, so it cannot read its content or directives.
How to fix. Remove the URL from the sitemap, or allow it in robots.txt if it should be crawled.
Indexable page missing from sitemaps
Info New audit to verify
Why it matters. This page returned 200, is indexable and self-canonical, and was found through internal links, but no sitemap that was read lists it. Pages left out of the sitemap may be discovered and refreshed more slowly.
How to fix. Add the page to the sitemap if it should be in search. If it should not, make it noindex or canonicalize it.
Internal linking
Broken internal link
Critical Recheck
Why it matters. This page links to an internal URL that returns an error status (4xx/5xx). Broken links waste crawl budget, leak link equity, and frustrate users — they are among the most common and most damaging technical SEO issues.
How to fix. Update the link to point at the correct live URL, or remove it. If the target was moved, prefer linking directly to the new URL rather than relying on a redirect.
Orphan page
Warning Medium confidence New audit to verify
Why it matters. No crawled page links to this URL; the crawl found it only through a sitemap, Search Console, Analytics or an imported list. Reported only after a complete crawl, so the absence of links is measured, not assumed, and only for indexable, self-canonical HTML pages: feeds, files, noindex pages and URLs canonicalized elsewhere need no links of their own. Pages without internal links receive little crawl attention and no internal link equity, and users can't find them by browsing.
How to fix. Link to this page from relevant pages (navigation, related content, hub pages), or remove it from the sitemap if it shouldn't be indexed.
Page has no outgoing links
Warning Recheck
Why it matters. The page contains no links at all — a dead end. Link equity that flows into it stops there, crawlers have nowhere to go next, and users have to reach for the back button.
How to fix. Add links to related pages, the parent category, or the homepage. If the page's navigation is rendered by JavaScript, make sure it also exists in the server-rendered HTML.
Page is deep in the site structure
Info New audit to verify
Why it matters. The page is 5+ clicks from the homepage. Deep pages get crawled less often and receive less link equity. Only indexable pages are reported: a noindex page is not meant to rank.
How to fix. Add links from higher-level pages (hubs, category pages, navigation) to flatten the path to this page.
Internal link points to a redirect
Warning New audit to verify
Why it matters. This page links to an internal URL that redirects. Every such link costs users and crawlers an extra request, and redirected links are a common sign of stale navigation after a migration.
How to fix. Update the link to point directly at the redirect's final destination.
Page has a single internal link
Info Medium confidence New audit to verify
Why it matters. Only one other crawled page links to this indexable page. Weakly linked pages receive little crawl attention and internal link equity.
How to fix. Link to the page from relevant categories, hubs and related content.
Page with search demand is buried deep
Warning New audit to verify
Why it matters. Search Console shows this page earning impressions, yet the shortest internal link path from the start page takes four or more clicks. Pages Google already shows for queries usually benefit from links nearer the top of the site.
How to fix. Link to the page from a higher-level hub, category or the navigation, so it is reachable in fewer clicks.
Valuable page has a low internal link score
Warning Medium confidence New audit to verify
Why it matters. The page earns search clicks, Analytics sessions or key events, but the site's own links treat it as one of its least important pages (link score 20 or below on this crawl's 0-100 scale). Reported only after a complete crawl. Link score measures internal link structure only; it is not Google's PageRank.
How to fix. Add contextual links from strong, related pages and consider featuring the page in navigation or hub pages.
Metadata
Missing title tag
Critical Recheck
Why it matters. The page has no <title>. The title is the strongest on-page relevance signal and the headline shown in search results; without it search engines generate one themselves, usually badly.
How to fix. Add a unique, descriptive <title> of roughly 50–60 characters that includes the page's primary topic.
Duplicate title
Warning New audit to verify
Why it matters. Multiple pages share the same title tag. Search engines use titles to differentiate pages; duplicates make pages compete with each other and depress click-through rates.
How to fix. Write a unique title for each page describing its specific content. For templated pages, include the distinguishing attribute (name, category, location) in the template.
Duplicate meta description
Warning New audit to verify
Why it matters. Multiple pages share the same meta description, so search results show identical snippets and users cannot tell the pages apart.
How to fix. Write a unique meta description per page, or remove the duplicated one entirely — search engines will generate a snippet from page content, which beats a wrong duplicate.
Missing meta description
Warning Recheck
Why it matters. The page has no meta description. Search engines will assemble a snippet from page text, which is often less compelling and hurts click-through rate. Only indexable pages are checked: a noindex page never shows a snippet.
How to fix. Add a meta description of roughly 70–160 characters that summarizes the page and gives a reason to click.
Title too long
Info Recheck
Why it matters. The title is over ~60 characters. Search engines set no character limit: Google cuts title links to fit the width of the results page, so a title this long is likely to lose its ending there. This is a review signal, not an error; a long title that names a distinct product, model or variant can be the right one.
How to fix. Check whether the words that tell this page apart from its siblings come first. If they do, the title can stay; if not, front-load them and trim generic words.
Title too short
Info Recheck
Why it matters. The title is under ~10 characters, which is usually too generic to describe the page or attract clicks.
How to fix. Expand the title into a descriptive phrase (roughly 30–60 characters) that states what the page offers.
Meta description too long
Info Recheck
Why it matters. The meta description is over ~160 characters. Search engines cut snippets to fit the results page, so its ending is likely to be dropped, and they may show text from the page instead.
How to fix. Trim the description to roughly 70–160 characters while keeping the core message and call to action.
Meta description too short
Info Recheck
Why it matters. The meta description is under ~70 characters. Short descriptions waste the snippet space search results give you, and search engines often ignore them in favor of text pulled from the page.
How to fix. Expand the description to roughly 70–160 characters that summarize the page and give a reason to click.
Content structure
Duplicate page content
Warning Medium confidence New audit to verify
Why it matters. Two or more URLs serve byte-identical visible text. Search engines pick one version to index and ignore the rest, and ranking signals get split across the duplicates.
How to fix. Consolidate duplicates: pick the canonical URL, add rel=canonical from the others, and 301-redirect duplicate URLs where possible (common causes: trailing-slash variants, URL parameters, http/https or www variants).
Missing H1 heading
Warning Recheck
Why it matters. The page has no H1. The H1 tells users and search engines what the page is about; pages without one tend to have weaker topical clarity. Google does not require one, and a homepage led by sliders and product rows can rank without it.
How to fix. If the page shows a heading that names it, make that heading the H1, consistent with the title tag. Don't add a hidden or extra H1 only to clear this check: when the design has no natural page heading, leave it.
Multiple H1 headings
Warning Recheck
Why it matters. The page has more than one H1, which dilutes the main-topic signal and usually indicates a templating mistake (e.g. a logo and a headline both marked up as H1).
How to fix. Keep one H1 for the page's main heading and demote the others to H2/H3 (or unstyled elements for non-headings like logos).
Thin content
Warning Medium confidence Recheck
Why it matters. The page has very little visible text. Thin pages rarely rank, can drag down sitewide quality assessments, and (if the site renders client-side) may indicate content invisible to plain-HTML crawlers. Listing pages (categories, locations, tags, pagination) are not checked: their value is the items they link to.
How to fix. Either expand the page with genuinely useful content, noindex it, or consolidate it into a stronger page. If the content exists but is rendered by JavaScript, ensure it is server-rendered or pre-rendered.
Heading levels skip
Info Recheck
Why it matters. The heading hierarchy skips levels (e.g. an H4 directly after an H2). This weakens document structure for accessibility tools and content parsing. The evidence names the first two headings where the outline jumps, so you can find the template or block that produces them. Noindex pages are not checked.
How to fix. Find the named headings on the page. If a theme or plugin block outputs them (a sidebar widget, a card title), change the level in that template once rather than page by page; otherwise adjust the levels so they descend one step at a time (H1 → H2 → H3).
Near-duplicate page content
Warning Medium confidence New audit to verify
Why it matters. The page's main content is at least 90% the same as one or more other indexable pages (estimated overlap of five-word phrases). Navigation, headers, footers, sidebars and text repeated on most pages of the same template are left out, so only the content specific to each page is compared. Search engines usually index one page from such a group and filter the rest.
How to fix. First compare the pages side by side in the URL detail (title, length, photos and any extraction values such as price or size). Pages that differ in price, size, bedrooms, transaction type or photos are separate offers: keep them and make each one's title, heading and description name what is different. Only true duplicates should be consolidated: pick one URL, point the others at it with rel=canonical or a 301 redirect, and link internally to that URL only. Product variants are often better served as one page with options.
Structured data
Structured data cannot be parsed
Warning Recheck
Why it matters. A JSON-LD block on the page is not valid JSON, so search engines discard it and the page loses any rich-result eligibility it carries.
How to fix. Fix the JSON syntax (trailing commas, unescaped quotes and unrendered template placeholders are the usual causes) and validate the page with Google's Rich Results Test.
Product page without Product structured data
Warning Medium confidence Recheck
Why it matters. The URL pattern classifies this page as a product or vehicle page, but it carries no Product, Car or Vehicle JSON-LD. Product markup drives price, availability and review rich results.
How to fix. Render Product JSON-LD (name, image, offers with price, currency and availability) from the product template. When most product pages are affected, fix the shared template once.
Page without the structured data its type calls for
Info Medium confidence New audit to verify
Why it matters. The page is a property listing, an article or a business location page, known from its address, its CMS or its sitemap, but it carries no JSON-LD for that: RealEstateListing (or a Residence with an Offer), Article or BlogPosting, LocalBusiness. Google shows article and local-business details from this markup, and search engines and AI assistants read it to understand what the page is. Property listings get no rich result of their own; the markup helps them be read correctly. The evidence names the type expected.
How to fix. Add the named JSON-LD to the page type's template (your SEO plugin or theme usually has a setting for it), filled from the page's own fields. When most pages of the type are affected, fix the shared template once.
Images & media
Images missing alt text
Warning Recheck
Why it matters. One or more images on the page lack alt attributes. Alt text is an accessibility requirement and the main way search engines understand images.
How to fix. Add descriptive alt text to meaningful images; use an empty alt (alt="") only for purely decorative ones.
JavaScript
Content may require JavaScript
Warning Medium confidence Recheck
Why it matters. The page's HTML contains a JavaScript app container with very little readable content and no headings, links, or images. The page may load its content in the browser, or it was still loading when rendered. Content checks were skipped because this HTML may not represent the complete page.
How to fix. If this audit did not render JavaScript, start a new audit with "Render JavaScript" enabled to check the loaded content. For reliable crawling, serve important content and navigation in the initial HTML using server-side rendering or prerendering. This warning does not prove that search engines cannot index the page.
Performance
Slow server response
Info Recheck
Why it matters. The HTML response took over 1.5 seconds in this crawl. It is one request from the audit's crawler location, not sustained measurement: compare it with the field data (Chrome UX Report) on the Performance tab before acting. Consistently slow time-to-first-byte drags down every downstream performance metric and reduces crawl rate on large sites.
How to fix. If many pages of one template are affected and field data agrees, investigate server/database time and caching for that route; serving cached or statically generated HTML usually fixes it.
HTML document over 1 MB
Warning Recheck
Why it matters. The page's HTML is larger than 1 MB. Large documents take longer to download and parse on mobile connections, and usually mean inlined data, scripts or repeated markup. The audit reads the first 1 MB, so checks for things that may appear later in the document (structured data, headings, links) were skipped on this page rather than reported as missing.
How to fix. Find what inflates the HTML (inlined JSON or SVG, page-builder markup, embedded variation data) and move it to separate resources or remove it.
Most pages respond slowly: one server-side cause
Warning Medium confidence New audit to verify
Why it matters. Over half of the pages this audit fetched took more than 1.5 seconds to start answering. When slowness is site-wide the cause is almost always one thing on the server (no full-page cache, a slow database or host, a plugin running on every request) rather than each page, so it is reported once. The evidence gives the median and 95th-percentile time overall and per template, and the cache headers the slow responses carried. Times are measured from the audit's crawler location to the first response header, one request per page; queue waits are not included.
How to fix. Check the cache evidence first: responses marked MISS, DYNAMIC or BYPASS (or with no cache header) are built by the origin on every request, so enable or repair full-page caching for them. If cached responses are slow too, look at hosting, the database and plugins. Confirm with field data (Chrome UX Report) on the Performance tab, then re-run the audit.
International SEO
Invalid hreflang value
Warning Recheck
Why it matters. An hreflang annotation uses a value that is not an ISO 639-1 language code, optionally followed by an ISO 3166-1 alpha-2 region (for example en, en-GB, sw-KE), or x-default. Google ignores invalid values.
How to fix. Correct the hreflang value. Regions must follow a language ("en-KE", not "KE"), and the United Kingdom is "GB", not "UK".
Hreflang annotation has no return link
Warning New audit to verify
Why it matters. This page names an alternate language version that was crawled but does not link back with its own hreflang annotation. Google ignores hreflang pairs that are not confirmed in both directions.
How to fix. Make every page in the language cluster list all the others, including itself.
Hreflang set does not reference itself
Info Recheck
Why it matters. The page declares hreflang alternates but none of them points at the page itself.
How to fix. Include a self-referencing hreflang annotation for the page's own language.
Security
HTTPS page loads insecure resources
Warning Recheck
Why it matters. The page is served over HTTPS but references images, scripts, stylesheets or frames over plain http://. Browsers block or warn on mixed content, which can break the page.
How to fix. Load every resource over https://. Update hard-coded http:// URLs in templates, the CMS's site URL, and content.
Google observations
Page with search traffic now returns an error
Critical Blocks indexing New audit to verify
Why it matters. Search Console reports clicks for this URL in the last 28 days, but the crawl received a 4xx or 5xx status. Search traffic to it is being lost.
How to fix. Restore the page, or 301-redirect it to its closest live replacement.
Page with search traffic now redirects
Warning New audit to verify
Why it matters. Search Console reports clicks for this URL in the last 28 days, but it now redirects. Fine after an intended migration; otherwise the ranking page was replaced by accident.
How to fix. Confirm the redirect is intended and points at the most relevant equivalent page; update internal links and the sitemap to the destination.
Page with search traffic is now noindex
Critical Blocks indexing Medium confidence New audit to verify
Why it matters. Search Console reports clicks for this URL in the last 28 days, but the page now says noindex. Google will drop it from search the next time it crawls the page.
How to fix. Remove the noindex directive unless dropping this page from search is intended.
Google chose a different canonical
Warning New audit to verify
Why it matters. Google's URL Inspection reports a Google-selected canonical that differs from the canonical the page declares. Google is consolidating this page into another URL, usually because of duplicate content or conflicting signals.
How to fix. Compare the two URLs. Make the content distinct, or align internal links, sitemaps and redirects with the canonical you want.
Google reports noindex on a page this crawl found indexable
Critical Blocks indexing Medium confidence New audit to verify
Why it matters. The latest URL Inspection says Google excluded the page for a noindex directive, but this audit fetched it as indexable: 200, no noindex in the HTML or X-Robots-Tag, self-canonical. The evidence gives the inspection date. Either the noindex was removed after Google's last crawl, or Google sees something this crawl did not: a different response for Googlebot, a noindex added by JavaScript, or a CDN or plugin header.
How to fix. Inspect the URL live in Search Console. If the live test shows no noindex, request indexing. If it still shows noindex, look for a header or script that adds it only for Googlebot (SEO plugin, CDN rule, JavaScript) and remove it.
Google has not recrawled a page since its noindex was removed
Info New audit to verify
Why it matters. The latest URL Inspection says Google excluded the page for a noindex directive, and an earlier audit found that noindex too, before Google's last crawl. This audit fetched the page as indexable, so the noindex has since been removed and Google's view is out of date. The evidence gives Google's last crawl and the earlier audit.
How to fix. Nothing on the page needs changing. Keep it in the sitemap and linked from crawled pages, and Google picks up the change on its next crawl. For the pages that matter most, request indexing in Search Console.
Indexable page Google reports as not indexed
Warning New audit to verify
Why it matters. The page is technically indexable (200, no noindex, self-canonical), and the latest URL Inspection result says Google knows the URL but has not indexed it: crawled and not indexed, or discovered and not yet crawled. The evidence says which, and when Google was asked. This is Google's own observation.
How to fix. Crawled but not indexed: Google read the page and chose not to index it, so improve its uniqueness and usefulness and check for near-duplicates. Discovered but not crawled: Google has not got to it yet, so strengthen internal links and keep it in the sitemap. Then request indexing in Search Console. Many cases on one template point to a pattern in that template.
Indexable page Google has not discovered
Info New audit to verify
Why it matters. The page is technically indexable, and the latest URL Inspection result says the URL is unknown to Google: it has not been discovered at all. That says nothing about the page's quality; Google has not found a link or sitemap entry that leads to it yet. The inspection date is in the evidence, and a recent page is often simply too new.
How to fix. Make the page discoverable: link to it from relevant crawled pages, list it in the XML sitemap submitted in Search Console, and request indexing for important URLs.
Analytics landing page now returns an error
Critical Blocks indexing New audit to verify
Why it matters. Google Analytics recorded organic sessions landing on this URL in the last 28 days, but the crawl received a 4xx or 5xx status.
How to fix. Restore the page or redirect it to the closest live replacement, then check the campaigns and links that still point at it.
Googlebot activity
Googlebot received server errors
Critical Blocks indexing New audit to verify
Why it matters. Your server logs show Googlebot receiving a 5xx response for this URL in the last 7 days. Repeated server errors make Google slow its crawling of the whole site and can drop the page from the index.
How to fix. Check the server or CDN logs at the times Googlebot was refused: overloaded origins, rate limiting or firewall rules that challenge verified Googlebot are the usual causes.
Googlebot keeps crawling a redirect
Warning New audit to verify
Why it matters. This URL is among the ones Googlebot requests most, but it redirects. Every request spends crawl attention on a URL that is not indexed; it usually means internal links, sitemaps or external links still point at the old address.
How to fix. Update internal links and sitemaps to the redirect's destination. Keep the redirect for external links and bookmarks.
Googlebot keeps crawling a missing page
Info New audit to verify
Why it matters. This URL is among the ones Googlebot requests most, but it returns 404 or 410. Google re-checks removed pages for a while, which is normal; persistent heavy crawling means something still links to it.
How to fix. Remove internal links and sitemap entries that point here. If the page moved, redirect it to its replacement.
Googlebot spends crawls on parameter duplicates
Warning Medium confidence New audit to verify
Why it matters. Googlebot frequently requests this query-string URL, and the audit found it noindex or canonicalized to another URL. Crawl attention spent on parameter variants is attention not spent on new or changed pages.
How to fix. Find what links to these parameter combinations (faceted navigation, sorting, tracking) and stop linking to non-useful ones; disallow parameter patterns that should never be crawled.