Merchant Center Errors, Decoded: What Each One Means and How to Clear It
⏱ 18 min read
One line in a Google Shopping feed errors report can quietly pull your best selling product out of the auction. Order volume dips, the campaign keeps spending against a thinner catalogue, and the weekly report looks soft for reasons nobody can name. Google rarely emails you about item level problems, so the symptom reaches you as lost revenue long before it reaches you as a notification. The gap between what you think is live and what Google actually considers eligible is where margin leaks.
This guide decodes the Google Shopping feed errors you meet inside Merchant Center, what each one means in operational terms, and the exact sequence that clears it. It assumes you already run Shopping or Performance Max campaigns and want the mechanism behind each flag rather than a surface level checklist. Every fix below maps to how Google verifies your data against your storefront, so you resolve the cause instead of chasing the symptom week after week.
What Google Shopping Feed Errors Actually Are
Google grades these Google Shopping feed errors by severity, and the grade dictates the blast radius. An item level error disapproves a single product, so it drops out of Shopping ads and free listings until the data is corrected. A warning leaves the product serving but caps its reach or marks a quality risk that suppresses impressions. An account level issue is the tier that ends weekends, because one unresolved pattern can disable the entire catalogue at once.
The commercial point is that a disapproval rarely costs only paid clicks. The same flag removes the product from free listings across Search, Images and the Shopping tab, so a single disapproved hero line bleeds organic and paid visibility together. When products vanish from Shopping with no obvious flag at all, the cause can sit upstream in indexing rather than the feed, which is a different diagnosis from why products are not indexed.
Scope is the fastest way to read the stakes of any flag. The graphic below shows how the three severity tiers escalate from one product to the whole account.
Here is how the three tiers differ and where each one surfaces in the interface.
| Severity | What it does | Where it shows |
|---|---|---|
| Error | Product removed from ads and free listings | Needs attention, item level |
| Warning | Product still serves, reach or quality limited | Needs attention, item level |
| Account issue | All products can be disabled at once | Setup and policy issues |
Where to Find Google Shopping Feed Errors in Merchant Center Next
If your mental model of the interface still says Diagnostics, it is a version behind. Merchant Center Next replaced the classic experience for every account on 30 September 2024, and the old Diagnostics view now lives as the Needs attention tab inside Products. Your google merchant center diagnostics data did not disappear, it was relocated and renamed, which is why half the feed guides online now point at controls that no longer exist.
Because most of those guides still describe the classic layout, the mapping below translates the old terminology into where each control actually sits today.
| Classic Merchant Center | Merchant Center Next | What you do there |
|---|---|---|
| Diagnostics tab | Needs attention, under Products | Triage item errors and warnings |
| Item level issues | Needs attention, per product | Fix the attribute, resubmit |
| Account issues | Setup and policy issues | Resolve policy and suspension flags |
| Feed processing report | Products, feed, processing results | Audit errors per attribute |
In practice you triage Google Shopping feed errors across three places, in this order:
- Needs attention, under Products, for item level errors ranked by revenue impact.
- Product status history, through View history, to see exactly when a product flipped from approved to disapproved.
- Setup and policy issues, for account level problems and any suspension notice.
For a large catalogue, the feed processing report is faster than clicking through products, because it lists every error and warning per attribute in one downloadable file. That split between item data and account policy matters, because the two demand different responses. A product data feed error usually means an attribute is missing or malformed, and you fix it in the feed. A policy flag means Google distrusts something about the page or the business, and no feed edit alone will clear it, which is why feed hygiene is really one surface of your wider technical SEO for Shopify.
Merchant Center Product Statuses: Not Approved, Limited and Under Review
Before you fix anything, read the status correctly, because each one asks for a different response. Merchant Center shows one of five values in the Status column (as of October 2026), and only two of them mean you have work to do.
| Status | What it means | What you do |
|---|---|---|
| Under review | Google is checking the product for issues | Wait. Google lists up to 3 to 5 business days for Shopping ads and a few weeks for other features such as free listings |
| Processing | Google is applying an update, usually after an edit | Nothing. Google lists up to 15 minutes |
| Approved | Reviewed and showing on Google | Nothing |
| Limited | Shows only in some cases, such as certain countries or marketing methods | Open Needs attention and read the issue |
| Not approved | Cannot be shown because of a policy or data quality error | Select Fix errors and clear the cause |
If a product sits in Under review far beyond those windows, Google says you can submit a review request from Merchant Center. Until then, resubmitting the same data does not speed anything up.
Product Page Unavailable and Pending Website Check
Two issue names account for a lot of confusion on the Needs attention tab, because they look like feed errors but describe the page. Product page unavailable means Google cannot access the landing page set in your link attribute, so the product stops showing in ads and free listings until it can. Google lists these causes: a 404, a URL that redirects more than twice, a connection failure or 5xx response, an unreachable robots.txt file, a hostname that does not resolve, a URL that does not start with http:// or https:// on your verified domain, and, if you use regional availability, region ID URLs that cannot be crawled.
The fix sequence is short:
- Test the page with the URL Inspection tool on desktop and smartphone to expose server side problems.
- Correct the link on the product in Needs attention, or filter the affected products, download the CSV, fix the URLs in your source data and re-upload.
- Select Request website check. Google says the review can take up to 12 hours, and you cannot submit another request in that window.
Pending website check is gentler. Google has not yet crawled the product page, so it cannot confirm the data is accurate, and the product waits for a crawl. Google gives no timeframe, so confirm the URL is correct and reachable, then check back instead of editing the feed repeatedly.
Google Merchant Center Price Mismatch Error: Why It Happens and How to Clear It
The google merchant center price mismatch error is the most common reason a healthy looking product stops serving. Google’s content crawler reads the price on your live page and reconciles it against your feed; if the two disagree, the product is disapproved until they align. It is the single most expensive member of the Google Shopping feed errors family, and rarely a typo.
The usual causes are structural, not clerical: a sale price that never reached the feed, a currency that differs from the target country, one price submitted for a variant that spans a range, or taxes and fees shown on the page but missing from the feed. A cached feed lagging behind a flash sale does the same in reverse.
These are the triggers worth checking first, ordered from most to least common.
| What triggers it | What Google sees | Clear it by |
|---|---|---|
| Sale price only on page | Feed price higher than live price | Send sale_price in the feed |
| Currency does not match market | Wrong currency for the country | Match feed currency to market |
| Variant price range | One price for many variants | Submit a price per variant |
| Stale cached feed | Feed lags a live change | Schedule more frequent fetches |
The structural fix is to let Google keep price in sync for you. Automatic item updates read price, availability and condition from the structured data on your page and correct small drifts before they harden into disapprovals. The feature is enabled by default, but it only functions when the page carries valid markup that the crawler can actually see.
That markup is the catch most Shopify stores miss. Your price has to sit in structured data markup inside the HTML the server returns, because Google will not reliably read a value injected by JavaScript after load. Themes that render price client side are a frequent offender, so it is worth auditing how your Shopify JavaScript rendering exposes price to crawlers before you blame the feed.
Clean product markup pays back well beyond Shopping, because the same structured data feeds every other channel that reads your catalogue, which is the argument for treating Shopify product schema as infrastructure rather than an SEO afterthought. Validate it with Google’s Rich Results Test, correct any price or availability field it flags, then resubmit. Repetition is what escalates this error: a single mismatch disapproves one product, but the same drift across many lines can push Google to switch off automatic updates for the whole account and move it toward suspension, so a recurring Google Shopping feed errors pattern is a louder signal than any isolated disapproval.
Put accurate price and availability into server rendered structured data. It clears the two mismatch errors that cause most disapprovals and most suspensions at the same time.
Missing Inventory Data in Google Merchant Center and Availability Mismatches
Missing inventory data in Google Merchant Center and availability mismatches belong to the same trust family as price, and Google treats them with equal suspicion. If the feed declares in stock while the page reads sold out, or the availability attribute is absent entirely, the product is disapproved until the signal is consistent across both. Availability also sits among the Google Shopping feed errors that silently cut free listings, so the damage lands on organic reach as well as paid.
The remedy mirrors the price case. Submit a valid availability value, keep it current, and back it with availability markup in your structured data so automatic updates can correct short lived drifts between syncs. For lines you are winding down, decide early whether to mark them out of stock or retire them, and handle the search side deliberately rather than letting dead URLs rot, as covered in discontinued product SEO.
Missing or Invalid GTINs and Product Identifiers
Identifiers tell Google precisely which product you are selling and let it match your listing against the same item sold elsewhere. You supply a GTIN, or a brand plus MPN, through the unique product identifiers attributes. When a manufactured product that clearly carries a GTIN is submitted without one, Google does not always disapprove it outright. More often it serves the product but constrains its performance, which makes this a softer failure than the harder Google Shopping feed errors above.
So a missing identifier is usually a warning rather than a hard error, which makes it one of the few Google Shopping feed errors you can safely deprioritise. That changes how you triage it. The fix is to add the correct GTIN from the manufacturer, or both brand and MPN, following Google’s guidance on missing identifiers. For genuinely unique items, custom, handmade or vintage, set identifier_exists to no so Google stops expecting a code that does not exist. Google asks you to use no only when you are sure the product has no unique identifiers assigned. For a Shopify specific walkthrough, see how to fix a missing GTIN in Merchant Center.
Match your product to the right row below and submit only what applies to it.
| Your product | What to send | Result |
|---|---|---|
| Mass produced with a GTIN | gtin attribute | Best performance |
| Has brand and part number | brand plus mpn | Eligible, good performance |
| Custom, handmade, vintage | identifier_exists set to no | No warning, stays eligible |
| Wrong or guessed code | remove it, use the real one | Avoids a hard error |
A guessed or borrowed GTIN that does not match the brand registry is a hard error, not a shortcut. Leave it blank and declare identifier_exists as no instead.
Missing Required Attributes and Weak Product Data
Beyond price and identifiers, most product data feed errors trace back to required attributes that are absent, truncated or malformed. Title, description, image link, price, availability, condition, brand and the correct Google product category are the fields Google validates first, and missing one that is required for your category disapproves the product immediately. Attributes that are present but thin do quieter damage, capping reach long before any disapproval appears. They are also the most preventable Google Shopping feed errors, because every required field is documented in advance.
Images carry their own rules and their own looming deadline. A missing image_link disapproves the product outright, while a low resolution file, a promotional overlay or a generic placeholder triggers a quality flag that suppresses impressions without ever showing as an error. Clean source images are the reliable fix, and they lift click through at the same time, which is the practical case for treating product image SEO as revenue work rather than housekeeping.
Resolution requirements are tightening, so this is worth getting ahead of. Google’s current image requirements reject anything below 100 x 100 pixels for non apparel and 250 x 250 for apparel, but from 31 January 2027 the floor rises to 500 x 500 pixels for every product submitted through image_link and additional_image_link. The table below sets the current minimums against the incoming ones.
| Product type | Minimum now | From 31 Jan 2027 |
|---|---|---|
| Non apparel | 100 x 100 px | 500 x 500 px |
| Apparel | 250 x 250 px | 500 x 500 px |
| Recommended | 800 x 800 px | 1500 x 1500 px |
Hitting those dimensions without ballooning page weight is its own discipline, which is where disciplined Shopify image optimisation earns its place in the workflow. Titles and categories then decide most of your remaining reach: a title that front loads the attributes shoppers actually search, brand, product type and key variant, matches far more queries than a vague one, and an accurate product category tells Google which auctions to enter you into. These are not hard Google Shopping feed errors, but weak data here caps performance long before a disapproval ever would.
Google Shopping Feed Requirements: What Google Validates First
Many product data feed errors are simply a requirement the feed never met. The table below summarises the product data specification as Google publishes it (as of October 2026), so you can check a feed against the rules before Google does.
| Attribute | Requirement | Limit or format |
|---|---|---|
| id | Required, unique per product | Max 50 characters |
| title | Required | Plain text, max 150 characters |
| description | Required | Plain text, max 5,000 characters |
| link | Required | Landing page URL starting with http or https |
| image_link | Required | JPEG, WebP, PNG, non animated GIF, BMP or TIFF; 500 x 500 px minimum, enforced from 31 Jan 2027 |
| price | Required | Number plus ISO 4217 currency code, for example 15.00 USD |
| availability | Required | in_stock, out_of_stock, preorder or backorder |
| brand | Required for all new products except movies, books and music recordings | Max 70 characters |
| gtin and mpn | GTIN recommended for every product that has one; mpn required only if there is no manufacturer GTIN | GTIN up to 14 digits; mpn up to 70 characters |
| condition | Required if the product is used or refurbished | Optional for new products |
| color, size, gender, age_group, item_group_id | color, size, gender and age_group required for apparel targeted to Brazil, France, Germany, Japan, the UK and the US; item_group_id required for variants in those countries | Color and size up to 100 characters |
Two practical readings of that table. First, most Shopify feeds fail on the optional looking rows, not the obvious ones: a variant without item_group_id in a country that requires it, or an apparel line without size and color, is invalid even though id, title and price are fine. Second, there is no separate trick for a template or an example file. Build one row per variant, upload the file as a data source, and read the feed processing report to see which rows and attributes Google rejected before you send traffic to the feed.
Attribute Warnings and Invalid Product Identifier Errors
Attribute warnings are the quiet half of the list. A warning keeps the product live but flags a value that is missing, truncated or outside the specification, so the cheapest time to clear them is in the same pass as the errors. Open Needs attention, filter by the issue name, and use the download icon to export every affected product for that issue as a CSV. Fix the value at its source, whether that is the Shopify product field, a metafield or a feed rule, then re-upload. Editing in Merchant Center is fine for one product but gets overwritten by the next fetch if the source stays wrong.
An invalid product identifier is a different problem from a missing one. The GTIN has to be a real number from the manufacturer, in a valid GTIN length and with a correct check digit, so a typo, a stripped leading zero or a spreadsheet that converted the value to scientific notation will all fail validation. Check the value on the packaging or with the supplier, store it as text, and never fill the field with a placeholder.
Landing Page and URL Mismatch Errors
Some Google Shopping feed errors have nothing to do with the product and everything to do with the link. If the URL in your feed points to a domain you have not claimed, redirects through a chain, or lands on a page the crawler cannot render, the product is disapproved. The product URL has to resolve to the verified domain and return a live, crawlable page on the first request.
Three checks clear most landing page Google Shopping feed errors:
- Confirm the feed URL uses the exact domain claimed in Merchant Center.
- Strip stray redirects or tracking parameters that break the match.
- Make sure the page returns real content to a crawler, not a shell that fills in afterward.
A concrete example shows how subtle this gets. Say your verified domain is example.com, but your feed tool appends ?utm_source=google to every product URL for tracking, and the storefront then 301-redirects that tagged link to the clean canonical. On the first fetch Google sees a redirect instead of a direct 200, the destination no longer carries the exact claimed path, and the product is flagged for a URL mismatch. The fix touches no product data at all: strip the tracking parameter from the feed URL, or map it with a feed rule, so the link resolves straight to the claimed domain with a 200.
Canonical confusion can also muddy which URL Google treats as the product, so a clean implementation of Shopify canonical URLs keeps the feed and the indexed page pointed at the same destination.
Multi country stores add another layer of alignment. If you target several markets, each feed needs the right language, currency and landing page for its country, and the hreflang signals on your pages have to agree with what the feed declares. Getting hreflang on Shopify right stops Google from serving the wrong regional page and flagging the mismatch that follows.
Misrepresentation and Account Suspension
This is the expensive one, where Google Shopping feed errors cross from feed hygiene into policy enforcement. Misrepresentation is the most common cause of Merchant Center suspensions under Google’s Misrepresentation policy, and Google characteristically suspends first and explains little, often with no prior warning. It operates as a catch all for anything that makes a store look untrustworthy: price and availability mismatches at scale, missing contact or returns information, or claims the site cannot substantiate.
In October 2025, Google clarified the policy with extra examples covering non delivery and inoperable return or refund processes. Google framed this as a clarification rather than a change in enforcement, but the practical effect is plain: a weak or broken returns page can draw scrutiny on its own, independent of the feed. The through line is trust: Google wants the shopper who clicks your listing to meet the price, product and policies they were promised, and it reads any gap as a signal that they will not.
Clearing a suspension is far slower than clearing a Google Shopping data feed error, so prevention is the only sensible strategy. Publish an unambiguous returns and refund policy, show real contact details and a business address, keep pricing and availability consistent with the feed, and secure the checkout. Resolve every underlying item first, then submit one request for review. Google says the review can take up to seven business days, typically three to seven in practice, not an instant reinstatement. If you are already suspended, work through the Merchant Center misrepresentation reinstatement checklist before you submit that request.
Creating a fresh Merchant Center account to dodge a suspension is treated as circumventing systems and usually leads to a permanent ban. Fix and appeal on the original account instead.
Content API Sunset and Merchant API: What It Means for Feed Errors (as of October 2026)
Google’s Content API for Shopping reached its sunset on 18 August 2026, and the Merchant API is its replacement. Since 1 September 2026, requests without an active extension fail intermittently with HTTP 410 Gone, and Google lists full decommissioning for early 2027, a date it says may change. For most stores this is invisible. For anyone who pushes products, prices or stock through a custom integration, it can become the quietest source of feed errors, because a sync that fails now and then leaves the catalogue ageing instead of breaking outright, and the first symptom you see is the price and availability mismatches described above.
Whether you need to act depends on how your data reaches Merchant Center:
| How your feed reaches Google | What Google says | What you do |
|---|---|---|
| Through an ecommerce platform or its app | The platform partner handles the migration; no action required from you | Spot check that price and stock changes still reach Merchant Center |
| Custom scripts, ERP or internal tools calling the API | Update them to use the Merchant API | Migrate, complete developer registration, or request an extension that cannot run past early 2027 |
| File or scheduled fetch feeds | The notice addresses API integrations | Ask whoever built the feed whether any step calls the Content API |
If a custom build is involved, a Shopify app development agency can audit the sync against the Merchant API before the errors start. If you rely on the Google and YouTube app, our guide to the Shopify product feed URL explains what that app does and does not expose.
One reporting detail catches teams out when they build dashboards on the new API. The Merchant API reports product statistics per destination and country, so a product sold in several countries can appear in several rows, and issue totals summed across them can look larger than the number you see in the interface. Google also notes that issue descriptions from the API might differ from the wording in Merchant Center. Compare like with like before you conclude that errors went up.
When a feed rebuild, a migration and your ad structure all need to change at once, it helps to work with a Shopify agency that treats feed, tracking and campaigns as one system, and a Shopify marketing agency can sequence the work so Shopping spend is not paused longer than necessary.
Bing and Microsoft Shopping Feed Errors
If you also run Microsoft Advertising, expect the same families of problems: stale price and availability, missing identifiers and landing pages that do not match the feed. When a product is clean in Merchant Center but flagged in Microsoft Merchant Center, compare three things in order: the live page, the value in the feed Microsoft actually imported, and how often that feed refreshes. Our guide to Bing Shopping feed setup covers the channel specifics.
How to Prioritise Google Shopping Feed Errors by Revenue Impact
A long issues list of Google Shopping feed errors is intimidating only until you sort it by money. Not every Google Shopping feed error deserves equal urgency, and working through them in list order wastes effort on products that barely sell. Triage instead by what the error does and what the product earns, then clear from the top down.
This order protects revenue and the account in the same pass. One disapproved hero product can outweigh a hundred warnings on items that rarely move, and a single unaddressed account flag can undo every item fix in one suspension. When the backlog is large or recurring, structured feed work pays for itself quickly, which is where a focused Shopify SEO agency or a dedicated feed specialist earns its keep.
To make the full cycle concrete, here is a worked example on a mid-sized catalogue. The figures are illustrative and yours will differ, but the sequence is exactly what a cleanup looks like in practice.
- Diagnose. A 2,000-product store opens Needs attention and finds 180 disapproved products: 90 price mismatches, 60 missing GTINs, 25 image or attribute errors, plus one account-level warning on returns.
- Triage. Sorted by revenue, 22 of the 90 price mismatches sit on best sellers that carry most of the Shopping spend, so they go first, ahead of the long-tail GTIN warnings.
- Fix. Server-rendered price and availability schema clears the mismatches, a feed rule fills brand plus MPN where GTINs are missing, compressed 800-pixel images replace the flagged ones, and a rewritten returns page answers the account warning.
- Result. After one feed resubmission and one account review, the disapprovals clear, the best sellers return to ads and free listings within a day, and the warning resolves inside the review window.
How to Prevent Google Shopping Feed Errors From Coming Back
Most Google Shopping feed errors are repeat offenders. The same price drift, the same missing attribute and the same out of stock lag return every week unless the feed is actively monitored rather than fixed once and forgotten. A handful of standing habits keep the catalogue clean without daily firefighting.
- Schedule frequent feed fetches so price and stock never lag the live site.
- Turn on email alerts in Merchant Center for critical item and account issues.
- Keep valid structured data on every product page so automatic updates can self correct.
- Use feed rules to standardise attributes and patch gaps before upload.
- Add supplemental data for fields your platform does not export cleanly.
Monitoring is what converts feed health from a recurring emergency into a quiet routine. The crawlability, structured data and canonical signals that keep Google approving your products are the same ones that keep the rest of your organic Shopping presence intact, which is why the stores with the cleanest feeds tend to be the ones that treat feed accuracy and search hygiene as a single job rather than two.
A Clean Feed Is a Growth Channel, Not a Chore
Every Google Shopping feed error is, underneath the error code, a trust check between your feed, your page and the shopper standing between them. Clear the price and availability mismatches, give Google clean identifiers and complete attributes, keep the landing pages crawlable and the business demonstrably trustworthy, and disapprovals stop being a weekly surprise. The payoff is not only a shorter issues list. It is more products eligible across both Shopping ads and free listings, which is free visibility most stores leave sitting on the table.
Treat the feed as a living asset rather than a file you upload once. Fix by revenue impact, prevent with monitoring, and the same discipline that clears today’s Google Shopping feed errors compounds into steadier Shopping performance quarter after quarter.
Stuck on disapprovals, mismatches, or a suspension? Skalum can take the feed off your plate.
We clean, structure and monitor your Google Shopping feed so products stay eligible.
Fix my feed →Find the structured data, crawl and canonical gaps feeding your disapprovals.
Get an audit →A clean feed is the base. We turn it into profitable Shopping and PMax campaigns.
Scale my Shopping →Frequently Asked Questions
After you fix the data and resubmit, item level problems usually clear within a few hours to three days, once Google recrawls the product and the feed. Account or policy issues take longer, often up to seven business days after you request a review. Resubmitting a corrected feed speeds things up.
A single disapproval normally stays at the item level and only removes that product. The risk comes from patterns. If the same price or availability mismatch repeats across many products, Google can escalate it to an account wide issue and, in serious cases, suspend the account entirely.
Under review means Google is still checking the product for issues, which is normal for new items or a freshly submitted feed. As of October 2026 Google lists up to 3 to 5 business days for Shopping ads and a few weeks for other features such as free listings. If a product stays under review well beyond that, check the Needs attention tab and submit a review request.
Yes. Enable automatic item updates and add valid price markup to your product pages in server rendered structured data. Google then reads the live price when it crawls the page and corrects small drifts for you. It is not a replacement for keeping the feed current, but it prevents most mismatch disapprovals.
No. If a product genuinely has no manufacturer assigned identifier, such as handmade, custom or vintage items, set the identifier_exists attribute to no. That tells Google not to expect a GTIN and keeps the product eligible. Never invent or borrow a GTIN, because a wrong one is a harder error than a missing one.
An error disapproves the product, so it stops showing in Shopping ads and free listings until fixed. A warning lets the product keep serving but limits its reach or flags a quality risk. Errors are urgent because they cost sales now. Warnings cap performance and should be cleared once errors are handled.
Yes. A disapproved product disappears from both paid Shopping ads and free product listings, so clearing the error restores organic Shopping visibility at the same time as paid. Clean titles, images and attributes also lift ranking and click through across both surfaces, not just the paid campaign.
Schedule frequent feed fetches so price and stock never lag the site, turn on Merchant Center email alerts, keep valid structured data on every product page, and use feed rules to standardise attributes before upload. Monitoring turns feed health into a routine instead of a weekly emergency.
Every product needs a unique id, title, description, link, image_link, price and availability. Brand is required for most new products, and you send a GTIN, or an mpn when no manufacturer GTIN exists. Apparel targeted to markets such as the US, UK, Germany and France also needs color, size, gender and age_group, and variants there need item_group_id. From 31 January 2027 images must be at least 500 x 500 pixels.
Not reliably. Google’s Content API for Shopping reached its sunset on 18 August 2026 and the Merchant API replaces it. Since 1 September 2026, requests without an active extension fail intermittently with HTTP 410, and full shutdown is listed for early 2027. If you use a platform integration, the partner handles the migration. Custom scripts must be moved to the Merchant API.
It means Google cannot access the landing page in your link attribute, so the product stops showing in ads and free listings. Typical causes are a 404, more than two redirects, a server error, an unreachable robots.txt or an invalid URL. Fix the link, test the page with URL Inspection, then select Request website check.