Merchant Center Oops Something Went Wrong Please Try Again Later Account Linking
Based on our experience working with product feeds for over 10 000 online shops, we've put together a guide to assist yous navigate through the most common Google Shopping feed errors and warnings.
Bones product feed requirements
How to identify feed problems
Errors, warnings, and notifications in Google Merchant Eye
Book an expert feed consultation [Complimentary]
35 Mutual Google Merchant Center Feed Errors:
Availability errors
- Invalid value [availability] /or/ Missing required attribute: [availability]
- Unclear value on your website [availability]
- Automatic item updates active [availability]
Shipping & tax errors
- Missing shipping information
- Missing 'shipping weight' attribute
- Too few subattributes for attribute: shipping
- Missing value [tax] /or/ Besides few subattributes for attribute: revenue enhancement
Unique Product Identifiers (GTIN / MPN / Make) errors
- Express performance due to missing identifiers [gtin, mpn, brand]
- Limited operation due to missing value [gtin]
- Invalid value [gtin]
- Cryptic value / unsupported value / reserved or restricted [gtin]
- Incorrect value [identifier be]
- Product identifiers provided, simply 'identifier_exists' prepare to false
Cost errors
- Missing or incorrect required attribute [cost]
- Mismatched [price] (page crawl)
- Invalid value for category [price]
- Invalid toll format [auction cost]
- Automatic item updates active [price]
All price-related errors accept been covered in this guide.
Description-related errors
- Missing value [clarification] /or/ Text likewise brusque [description]
- Encoding problem in attribute: description
Image-related errors
- Promotional overlay on image [prototype link]
- Prototype besides small /or/ Low image quality [prototype link]
Incorrectly assigned Google product category
Missing additional production data errors [gender, color, historic period grouping, size]
Missing or invalid data [condition]
Excessive capitalization [title]
Invalid or missing required attribute: id
CSS non selected for this destination
Ineligible for enhanced listings on Surfaces across Google
Feed processing errors
- Offer quota full, items reje
cted
- Detail uploaded through multiple feeds (warning)
- Awaiting initial review /or/ Image not retrieved (crawl pending)
- Wrong feed URL
Item disapproved due to policy violation
Recommended Farther Reads
Book an expert feed consultation [Gratis]
Google Shopping Product Data Requirements:
The offset footstep to getting your production information aligned with Google is to follow the data feed specification. Then, you also demand to make sure to update your data every 30 days to maintain the active condition of your products in the Google Merchant Heart account.
When submitting a production to Google Merchant Middle, there are several mandatory attributes you include regardless of what you're selling:
1. ID
Every product should take its own, unique ID.
Common ID errors: ID non unique
2. Title
The most important affair to recall is that your title should be written with your customer in mind . What information is most of import for them? Brand sure to continue information technology nether 150 characters.
Common title errors: capitalization in product titles
3. Clarification
Keep it under 5000 characters. A proper clarification describes your product accurately and includes formatting, such as bullet points.
Common description errors: description includes invalid characters (encoding issue) , missing or short description
four. Link
Make certain you're using the same domain you've verified in Google Merchant Centre.
5. Image_link
Prototype is the showtime thing that shoppers volition detect, make sure you make a practiced impression. Provide a link to an image in i of the following formats: non-animated GIF, JPEG, PNG, BMP, or TIFF.
Common image errors: promotional overlay on the image, image too small
6. Availability
Utilise one of the 3 predefined values: in stock, out of stock, preorder.
Mutual availability errors: incorrect values submitted, unclear value on the website
seven. Price
Three things to always keep in listen when submitting price information:
- Don't include free items
- Always specify currency
- Make certain the p r ice in the feed matches your website p r ice
Information technology is important to mention that depending on the product category or its condition, additional attributes may exist required to run Shopping Ads. For example, if your production is used - the 'status' attribute is required in your feed.
Another exception is the Apparel category which enforces additional attributes such as color, size, gender, and age_group in many countries.
More than almost these and other attributes further in this article.
How Do I Identify Feed Problems
Identifying and troubleshooting feed issues can be quite cumbersome at times. It gets much easier once you know where to await for cardinal information.
Let's take a await at a few resources that can help us get on the right track with our product feed:
DataFeedWatch - Feed Review
Why fix the Google Merchant Middle errors if you could avoid them in the get-go place?
If you lot'd like to check your Google Shopping feed for potential errors prior to submitting products - here's a way to practice it!
DataFeedWatch Feed Review is a separate tab in your Aqueduct Mapping Interface. Asking a channel feed review, and verify whether production data y'all're well-nigh to send to Google Shopping is consummate.
The review will check your feed for the following:
- Missing information: are the required or optional fields populated with values?
- Uniqueness validator: Do your unique identifiers, SKU, UPC, take duplicates?
- GTIN validator: this feature checks if your GTINs are valid
- Pre-divers fields validator: this characteristic checks if fields with predefined values are mapped correctly
There is a list of afflicted items provided for each potential effect. This is accessible in the form of a summary and a downloadable report.
Google Merchant Middle - Feed Upload
The very first thing Google does in one case your feed is uploaded is to check for basic product data correctness. If issues are found, they will provide you with a brief report summarizing the errors.
Items that successfully pass this verification, will enter the side by side stage of the review process. The second phase can expose bug undetected during initial processing.
For a consummate overview - refer to the Diagnostics section.
Google Merchant Middle - Diagnostics
'Diagnostics' is a carve up section in Google Merchant Eye, accessible from the side navigation bar. Information technology offers detailed issue reporting across your account & feeds.
Diagnostics evidence all the errors, warnings, and notifications that need to be addressed to make your products eligible for Google Shopping. Along with a full report on affected items, which you can download as CSV.
Errors, warnings, and notifications
When uploading your products to Google Merchant Center account, you might come up across different kinds of feed issues. They could vary by severity - some issues might plough out fatal for your Shopping Ads (formerly Product Listing Ads or PLAs), some may represent an opportunity to improve feed quality.
In guild to help you prioritize issues - Google split them up into three types:
⇒ERRORS
Errors indicate disquisitional feed issues. They pb to product disapprovals and, consequently, prevent y'all from showing ads of the afflicted items. In some cases, errors might result in business relationship interruption and disrupt your marketing efforts for a longer menstruum of time.
Lesser line - better stay articulate of errors! And if you practice get them, make certain to place them right on top of your priority listing for fixing feed issues.
⇒ WARNINGS
Warnings are less severe than errors, and typically don't cause Google to turn down your items.
Those problems will negatively impact feed quality and decrease the operation of the afflicted items in your shopping campaign.
If warnings remain unaddressed for a long time, they might at some point lead to production disapproval or even business relationship suspension.
⇒ NOTIFICATIONS
You can care for the notifications simply as tips from Google. They allow you know which parts of your product feed could use adjustments for better ad performance.
It's not required to follow these recommendations, but why say 'no' to a suggestion coming straight from the equus caballus'due south rima oris?
Now that we accept clarity on what each type of issue indicates, permit's dig in and have a closer look at how to efficiently resolve some of the nigh common Google Merchant Centre issues.
Back to peak or 
The 35 Nigh Mutual Google Merchant Centre Errors
Availability errors in Google Merchant Eye
Availability is ane of the predefined Google Shopping feed fields, where yous tin can only get 3 values in:
| In stock | Out of stock | Preorder |
Anything else, including values such as 'available' / 'unavailable' or 'yes' / 'no', is going to result in item disapproval.
Why is it important to become the 'availability' field right?
In that location are 2 important reasons why you should take proper care of your availability information:
- Advertising limitations: availability errors pb to disapprovals, and availability warnings may contribute to getting your Merchant Middle account suspended
- User experience: wrongly assigned availability volition confuse buyers and can deter them from visiting your web-shop again
Invalid value [availability] & Missing required attribute: [availability]
Google uses predefined values for availability. This error means yous've either submitted a value outside of the accepted range or y'all've skipped the availability attribute entirely in your data feed.
Several shopping carts generate availability fields containing values incompatible with Google's guidelines. For instance, some platforms may exist labeling products with 'truthful' or 'false' within the 'is_available' field.
Step past Footstep Solution
Brand sure you have one of the three availability options assigned in your shopping feed: in stock, out of stock, or preorder. You may go on using the availability field from your store, only with a small modification.
Method i
In your DataFeedWatch fe ed, go into 'Edit Values' for the 'availability' attribute and overwrite the values.
Here's how an example rule might look:
Tip: If you're unsure what values were originally submitted that caused the error:
- check out the Store Products tab (on the side navigation bar) to notice out
or
- review examples of affected items in the Merchant Center Diagnostics
Method 2
Apply 'quantity' input field and build conditional statements to specify availability.
An example below:
Back to superlative or Book an expert feed consultation [FREE]
Unclear value on your website [availability]
Unclear availability upshot usually means that availability is not visible on your landing pages or that your structured schema markup requires fixing.
Stride past Pace Solution
Stride 1
Verify that availability is visible on your website landing page AND included in your structured data markup.
To verify whether your schema markup contains the correct data, y'all may apply a structured data testing tool from Google or Rich Results Test.
Step ii
Depending on the results of your cheque:
- If schema markup or your landing page is missing availability info - you demand to accept your website developer or the SEO-responsible add it.
- In case you've verified that both are in gild - the arraign might exist on Google'south glitch. Going through Google'southward support team should get this error wiped and products approved.
Automatic item updates active [availability]
This warning means your product's availability data got updated past Google due to discrepancy betwixt the feed and your online store information. Information technology's only possible if automatic item updates are enabled in your Merchant Center account:
The practiced news is: your products' stock status got fixed, which allows you to continue advertising affected items.
The bad news is: if these warnings proceed to occur it may pb to products disapproval or even account pause at some betoken.
To implement a long-term solution it's important to recognize the underlying result, which is that your feed update frequency may not match the dynamic turnover of your shop.
EXCEPTION : In some cases, the "Automated item updates active [availability]" warning may be caused by incorrect availability microdata. In this scenario, your data feed contains the right values, but the structured data markup on your website contains the wrong ones.
Every bit a upshot, Google is overwriting availability with incorrect information.
In this case, y'all should prepare your structured data markup. You can also temporarily disable Google automated updates to terminate it from overwriting values until you lot take the microdata fixed.
Step past Step Solution
To resolve this alarm, you demand to ensure your data feed contains availability info at all times.
Method i
If your store inventory is subject to frequent changes information technology's recommended to have advantage of the Inventory Update Feed.
It volition permit you to add together an boosted daily data fetch (or several if y'all're using the FTP method) that will complement the main product feed that is too granted 1 automated daily fetch by Google.
To add this supplemental feed in DataFeedWatch only select it from the list of available channels (Google Shopping - online product inventory update). Once fix, provide the feed URL in your Merchant Center account & set the daily update schedule.
Important: Don't forget to increase the frequency of data syncing between your store and the feed! After all, fetching erstwhile information to the Merchant Middle a few times per 24-hour interval won't solve the problem. You demand the feed to behave updated data. To do this, navigate to 'Edit Shop' in your DataFeedWatch interface.
Method 2
Instead of utilizing Inventory Update Feed you may as well switch to FTP/SFTP feed uploads.
That way your main product feed would be automatically pushed to Google Merchant Center every time it's updated with new information.
Before yous'll be able to submit your feed via FTP or SFTP you will need to create an FTP or SFTP account.
Y'all can achieve the aforementioned benefit past utilizing Content API for feed submission (requires a straight API connectedness with Google Merchant Middle) to provide your product data.
Note: Merely as in the previous case, ensure that your shop update frequency is aligned with the updates of your feed in Google Merchant Center.
Shipping & Revenue enhancement errors in Google Merchant Centre
Aircraft and tax feed issues ordinarily stem from providing bereft data.
Although you may submit aircraft and tax information via the master production feed, advertisers usually fix information technology up directly in the Google Merchant Center. That way the prepare-up is practical account-wide.
Missing value [aircraft]
Missing shipping error will occur if you didn't provide your shipping rates to Google. It's a required attribute for all Merchants, no matter the location or vertical. It also applies if you offer costless shipping. To fix it, you need to provide shipping toll and country.
Step past Footstep Solution
Method one
Via the data feed
You can quickly add aircraft information to your feed in DataFeedWatch - navigate to 'Edit Feed' and gyre downward to the 'Shipping' section. Then, specify location and toll.
- With a flat shipping fee, you can employ a simple 'add static value' rule:
If you offer costless shipping make sure to enter 0.00, and not 'complimentary' .
- If your shipping price varies depending on other factors, due east.g. product weight (and you lot determine your shipping toll), the rule could look like this:
Method 2
Directly in the Google Merchant Middle (GMC) account
That way y'all can apply shipping settings globally - to all the feeds held under your account. Likewise, if your shipping rates are dynamic and calculated by the shipping carrier - you will have to apply this method to provide your shipping details.
Click the tools icon > Shipping and returns > Click the + sign > Fill in the needed fields.
Here you tin observe farther instructions from Google on this process.
Tip: If your shipping rates are calculated based on bundle weight, you will need to add an additional 'shipping_weight' field to your data feed. Read more than almost it beneath.
Missing 'shipping weight' attribute
The issue may appear to yous in the Merchant account as Missing shipping weight, or even Missing shipping data. It oft occurs later on yous've but changed your feed to a new one. Why?
Your Google Merchant Centre shipping rules are probably gear up-upwardly based on production weight, and your new feed doesn't comprise the 'shipping_weight' attribute.
Step by Step Solution
-
Go to boosted fields in the Edit Feed section and select the 'shipping_weight' field.
-
Map it with a proper field from your shop data. Don't forget to add the measurement unit of measurement (g, lbs, kg)!
-
Re-fetch your feed in Google Merchant Center and it's fixed.
Tip: If yous're using Shopify, the 'grams' field is what you lot're looking for.
Back to top or Volume an good feed consultation [Costless]
Also few subattributes for attribute: shipping
This error occurs if y'all haven't specified both of the required attributes for shipping: price and country.
Step past Stride Solution
Add all the necessary data. You lot can do it through the information feed or past navigating to the Merchant Center shipping tab and completing the shipping details at that place:
Tools icon > Aircraft and returns > Click on the shipping service name to edit it
Opting for the latter gives you the benefit of applying your shipping settings account-wide.
More on setting upward shipping in Google Merchant Center hither.
Missing value [tax] /or/ Too few subattributes for aspect: tax
Tax information is only required and allowed if the targeted country is the U.s.. If you lot're seeing this error, information technology ways you lot skipped tax info when submitting your information. Or, not all of the required tax values have been specified.
Stride by Footstep Solution
Add tax rates either through your feed or via the Tax tab in the Google Merchant Center.
In the Merchant Center:
Tools and settings menu > select Sales tax > click the Tax Settings tab > Add taxation data accordingly
In the feed:
Go to 'Edit feed' and scroll through the mapping interface to the Shipping and Tax department. Then insert the proper rates.
We recommend setting up the Tax data directly in the Merchant Center business relationship - that manner they are applied account-wide.
Unique Product Identifiers (GTIN / MPN / Brand) errors
Google uses UPIs (Unique Product Identifiers), especially GTIN, to improve understand and classify your products. Permit'south zoom in on what that means for you if you provide correct & consummate identifiers:
- Shopping Ads showing for more relevant searches (which equals increased Conversion Charge per unit)
- Increased visibility through unpaid production listings (The new 'Compare by shop' feature is based on GTIN information)
- College Quality Score (which helps you relieve up on CPC)
Read more well-nigh the role of GTINs and how to get a GTIN here.
Limited performance due to missing identifiers [gtin, mpn, make] & Limited performance due to missing value [gtin]
Affected products are nevertheless eligible to show among Shopping Ads, only their performance is negatively impacted. The 'limited functioning' may limited itself through lower advert rank, being excluded from 'Compare past shop' feature (introduced along with gratis product listings), and other disadvantages.
- Limited performance due to missing identifiers will occur if your items are missing more than than i product identifier
- Limited performance due to missing gtin will occur when yous're missing this one specific identifier.
In September of 2019, Google loosened its UPIs (Unique Production Identifiers) policy, making them [GTIN, Brand, MPN] optional for Google Shopping. However, items with identifiers provided are given higher priority, compared to items without submitted identifiers.
The 'Limited performance due to missing identifiers [gtin, mpn, brand]' warning came to life as a result of this shift, replacing the error of 'Missing ii out of iii attributes [GTIN, Brand, MPN]'.
Step by Step Solution
Provide Google with your product identifiers. Here's how you can include GTINs in the feed:
Method i
Match the GTIN attribute with a corresponding field from your store.
Depending on your shopping cart, it might be 'barcode', 'UPC', 'GTIN', or something else. A unproblematic 'Rename'-dominion will be enough.
Method two
If your data source doesn't incorporate GTINs, you can still provide them using a 'lookup table':
In a csv file or a Google Spreadsheet make full in 2 columns:
- The 1st cavalcade should contain an aspect that could be used for detail identification in DataFeedWatch. Good choices might be variant_id, SKU, mpn.
- The 2nd column will incorporate the unique GTIN per detail.
Connect the prepared file in DataFeedWatch & specify which attribute y'all've chosen to match GTINs to products. Voila!
Invalid value [gtin] & Ambiguous value GTIN & Unsupported value reserved or restricted [gtin]
Google verifies all the GTINs submitted and will notify you lot if yours are wrong. Permit's take a wait at what each error / warning means:
Invalid GTIN
GTIN submitted is incorrect. It might be a matter of additional, particularly non-numeric characters in the product code. The but way to verify that would exist to check the affected items in Google Merchant Middle Diagnostics. If the GTINs seem alright to you, try contacting the manufacturer to request an up-to-engagement list of GTINs.
Ambiguous GTIN lawmaking
Google cannot recognize the GTIN submitted as it might take likewise many or besides few digits. Global Merchandise Detail numbers are unremarkably 8, 12, 13, or 14-digits long.
Reserved GTIN
The GTIN you submitted hasn't been released for use yet by GS1. It's reserved for hereafter use.
Restricted GTIN
The GTIN you lot've submitted is invalid because it has 1 of the post-obit prefixes: "two", "02", or "04". These production codes are restricted for special purposes and internal systems, therefore cannot exist used as a GTIN aspect for Google Shopping.
If you have any doubts nigh the GTINs yous accept at disposal, y'all may notice the GTIN Validation Guide useful.
Step past Step Solution
The instructions given below apply to fixing GTIN settings in your data feed. If you lot don't have correct GTINs at your disposal you should contact the manufacturer or become in bear on with GS1. If you are based outside of the US, you can utilize this website. Diverse mapping functionalities in DataFeedWatch can help y'all go your GTINs in order. Let us consider the two most common examples:
Example i
If GTINs contains additional characters, eg. letters which shouldn't exist included - remove them in 'Edit values'. Enter the exact characters you lot wish to remove or utilise a regular expression if appropriate.
The in a higher place rule would remove whatsoever letter of the alphabet-characters present in the GTIN field.
Example 2
13-digit EAN codes commonly start with a 0, peradventure you lot're missing it for some products? You can add a prefix to any GTIN that doesn't start with a 0:
Wrong value [identifier exists]
Incorrect value for 'identifier_exists' tin can mean a few things:
-
Value exterior of the predefined range : yous've submitted a value outside of the accustomed range (True/Simulated)
-
Falsely 'false': you've marked this attribute as 'Simulated' but Google recognized the items submitted equally products with existing identifiers
-
Falsely 'true': y'all've submitted 'identifier_exists' every bit 'True' for items that don't have identifiers
Because that this product attribute is prepare to TRUE by default (even if you don't include information technology in your feed) - scenario #3 is the almost likely of all.
'Identifier_exists' attribute tells Google whether universal identifiers (brand, GTIN & mpn) are bachelor for your products. Accustomed predefined values are: 'false' / 'no' and 'true' / 'yeah'. And heads up - chances are you're not gonna come beyond this attribute in your feed (if not included in the feed, it defaults to 'true').
Footstep by Stride Solution
Scenario i
Value outside of the predefined range
Correct your feed mapping to include but the allowed values (True or Faux). Using 'add together static value' mapping type will come in handy here:
Scenario 2
Falsely 'false'
If you don't have product identifiers, but they practise exist, don't mark the 'identifier_exists' field as 'faux'. Google will find out anyways and render an mistake. Instead, you should keep the 'identifier_exists' attribute set to 'truthful' and simply not submit identifiers (GTIN, brand, mpn) if you don't take admission to them.
Spring to fault Limited performance due to missing identifiers [gtin, mpn, make] to discover out why it's recommended to obtain product identifiers.
Scenario iii
Falsely 'true'
There are certain products groups for which identifiers don't exist, those would be:
- products you're the only seller of
- vintage items
- custom-made goods
For those cases, set the 'identifier_exists' feed aspect to Faux. Also, don't submit any of the post-obit attributes: brand, mpn, GTIN. Hither'due south how the fix-upward could look like:
- Select 'identifier_exists' from 'Optional fields' and assign a static value of 'Faux'.
- Brand sure that brand, GTIN & mpn are not included in the feed. Remove them completely from your feed or apply the 'leave empty' selection.
Notation: Submitting any one of the identifiers while 'identifier_exists' is gear up to FALSE trigger another error: 'Production identifiers provided, but 'identifier_exists' ready to false'.
Production identifiers provided, just 'identifier_exists' prepare to fake
The error means that yous've provided at to the lowest degree 1 production identifer (GTIN, mpn, make) while submitting 'identifier_exists' aspect with value 'simulated'. That is interpreted by Google as contradictory information.
Step by Footstep Solution
Arrange 'identifier_exists' and relevant attributes:
Method 1
If identifiers are bachelor for your products, change the 'idetifier_exists' value to TRUE.
Ensure you've mapped production identifiers such as Brand & GTIN or Brand & MPN for your items.
Method two :
If brand, mpn or GTIN was submitted by mistake or containing invalid information - remove those fields from your feed, or change mapping type to 'exit empty'.
Method iii:
If you lot have a mix of custom made items AND products with identifiers, you can configure your feed properly through provisional mapping. Here's how the rules could be structured for individual fields:
- Identifier_exists:
- 'Brand':
- 'GTIN' & 'mpn': Lucifer them with appropriate attributes from your store, without additional 'IF statements'.
Description-related errors
Some other surface area in which Google recently decided to set the bar college (likely in relation to introducing free Google Shopping ads) is the 'description' attribute. Starting from September 2020 the 'description' field becomes required for all products. Although products without descriptions will be eligible to display, they will exist given lower priority.
And we all know what that means - lower ad operation.
Missing value [description] & Text too short [description]
Your feed is missing the 'description' completely or the one you submitted is too curt. While Google only specifies the maximum grapheme count (5000) for a product clarification, with no mention of the minimum length, information technology's safety to presume information technology should be longer than the production title. Otherwise - you're likely to be served with the warning.
Pace by Stride Solution
Method 1
If you have a long description in your source data - use information technology!
You tin even use a few different description fields depending on which one is available:
Method 2:
If y'all don't have descriptions ready for your items, y'all tin starting time by combining diverse product attributes to compose them.
You may even customize it for different production groups:
Method 3
Feeling creative and take some spare time?
You can attach a fully-customized, killer description to each product (or perchance you'd like to do it for your bestsellers but?). The lookup table option will come up in handy:
Back to summit or
Encoding problem in attribute: clarification
This encoding error message in Google Merchant Center means that some of your descriptions contain 1 or more than characters considered invalid in your current encoding setting. Information technology may also occur in your Merchant account as Invalid UTF-8 encoding [description] mistake.
According to Google's assistance pages, Google Merchant Centre supports UTF-8, UTF-16, Latin-1, and ASCII encoding types. The beginning one beingness the well-nigh popular.
Bad news?
Google volition only indicate out products that the error is continued with, it won't serve yous the invalid characters on a silver platter. It's upwards to you to find the ones that triggered the consequence.
Good news?
We've got yous covered :)
Footstep by Pace Solution
One time you've identified the products concerned, keep to the 'Shop Products' page to review their descriptions. The default encoding setting in DataFeedWatch is UTF-8, then you lot should be able to observe those inaccuracies with the naked eye.
Then, go on to the mapping section and remove or supercede the unwanted characters in the 'Edit Values' section for descriptions.
Dorsum to top or Book an expert feed consultation [FREE]
Paradigm-related errors in Google Merchant Middle
There are several quality factors Google will check for when yous submit your product images. Let's look at a few most common prototype-related errors and how to get them fixed.
Promotional overlay on image [epitome link]
Google has strict rules almost including promotional overlay in your Shopping Ads images. And the dominion says - no promotional overlay. If y'all're seeing this error, there are a few potential solutions you could consider.
PS: You tin can larn more nigh how to optimize your Shopping Ads images in 1 of our previous articles.
Step by Footstep Solution
Depending on how many product images yous have at mitt and which of them are actually eligible to serve on Google Shopping, the solution could differ:
Method 1
Use Google's ' Automatic Image Improvement ' feature
As this is a new option in Google Merchant Middle (GMC), not all GMC users take discovered its existence. All yous need to exercise is enable the image improvement tool in your account and let Google do its magic. Information technology will remove the promotional texts from your images.
How to fix up the characteristic?
- In your Merchant Center account, select 'Automatic Improvements' from the Tools dropdown
- Confirm 'Enable automatic image improvements' and salvage
This is an opportunity for a nada-effort fix, but keep in heed - machines don't always go it right. Check the updated prototype - if the system'southward attempt to improve information technology fails (for example promotional text is but partially removed), you'll demand to upload a new paradigm.
Method 2
Change image consignment
If yous take multiple product images for your products in your online shop, 1 of the easiest ways to get rid of the error would be to select another image. 1 that is in line with Google'due south epitome requirements for Shopping Ads.
Instead of using your primary image for all products, you could switch, for example, to the 3rd product image. You can make that change for all products or exclusively for those affected past the fault.
In your mapping panel in DataFeedWatch, navigate to the paradigm attribute setting and match it with another epitome in your source information:
The example dominion in the screenshot above is gear up to change image assignment merely for products affected by the image error. To let the system know which products have been afflicted past the mistake you lot could use a list of SKUs / IDs / GTINs of rejected items. CSV or TXT file, or a Google Spreadsheet will practice fine for this purpose.
Method 3
Create new images
This one is pretty straight-frontward. Your product images got rejected. If y'all tin can't fix the consequence using method 1 or 2, mentioned in a higher place, y'all will need to arrange for new product images that will be in line with Google's guidelines.
One time you have them ready, revisit the mapping department of your feed and assign epitome links properly (see example above). In the meantime, if you wish to keep your account error-free, you tin can exclude the disapproved products from the feed.
For this purpose, y'all could utilize an exported listing of rejected items. More on how to leverage lists in your production feed here.
Epitome as well small-scale & Low image quality [image link]
Google'south minimum size requirements for production images sit at 100x100 pixels, and 250x250 for products within the clothing & clothes category. If your images don't fit that description yous will need to provide Google with new ones.
If up until now you were quite certain of the good quality of your images - maybe your product feed is not properly mapped. For example, it pulls the smaller images from your store, instead of the full-size quality images you take.
Pace past Step Solution
Outset, information technology's important to verify whether the images you can run into the error for in your Merchant Center account are available in a larger size. Start past checking the affected items in the error study.
If those images are available in bigger size:
Review your feed mapping and make sure yous assign the right source field from your store.
For example, for Shopify store owners the main product image comes in a few sizes: small, medium, big, grande and thumbnail. The biggest version is normally located in the 'image_1' field. That's the one you should use.
If they aren't available in bigger size:
If the biggest size of the given prototype is already uploaded to Google Merchant Center, try following the aforementioned solutions equally for the 'Promotional overlay on epitome [image link]' error:
- Change paradigm consignment
- Create new images
Dorsum to meridian or
Incorrectly assigned Google Product Category
This isn't the type of error you lot're gonna see in the Merchant Eye Diagnostics. Rather, it's something you can discover yourself when reviewing the product list in Google Merchant Center.
The taxonomy is crucial for the product ads as information technology helps Google to identify if your products are a good match for a given shopper query. Product categorization used to be the merchant's task until recently. Today, Google conducts automatic category assignments.
With this new evolution there comes a risk of getting your products categorized incorrectly. The repercussions could include:
- serving your ads to the wrong audition
- Google wrongly enforcing boosted attributes on yous (e.one thousand. colour, size, or age_group for products exterior of the apparel & accessories range)
- tax-related bug, if you're targeting the U.S.
That's why we recommend keeping an eye out for any miscategorization and fixing it as soon equally you spot information technology!
Stride by Step Solution
Say you've identified that your purifying skin masks collection got categorized equally 'protective medical masks'. Now, yous probably won't exist getting many sales out of serving these ads.
Fortunately, Google allows y'all to overwrite the automatically assigned value. And, there'south an piece of cake mode to assign the correct categories in DataFeedWatch, or fifty-fifty two:
Method 1
Categorization via motorcar-generated rules: 
We take created a system to match each product type to the most appropriate Google subcategory, in a matter of seconds:
Step one: Cull a field from your store containing product blazon information,
Stride 2: Commencement typing in a keyword & y'all will receive a list of categories to choose from,
Pace iii: Select a proper Google category for each item group.
Method 2
Categorization via manual rules
Handy if your source feed is lacking a field to base the categories on. To add a category, proceed as follows:
Footstep 1: Outset typing in a keyword and select the all-time category match from the list.
Step 2: Create rules to specify the products the category should exist applied to.
Example: Y'all tin assign categories based on certain keywords that could be found in titles or descriptions:
What is the right category for my product?
The near relevant i. All in all - it would be a judgment telephone call.
Tip : Swoop into the subcategories and exist as specific as you tin can. With over 6000 unique Google categories it'southward usually possible to find an exact match. If not - the dominion of thumb is to go with the closest match. We've covered Google Product Category in-depth in one of our previous articles.
Back to top or
Missing boosted product information errors [gender, color, age group, size]
For certain countries, Google requires boosted information (gender, colour, size, age_group) to be provided within the feed if you're selling fashion-related goods. Failure to produce them results in product disapproval.
- Missing required aspect [gender]
- Missing required aspect [age_group]
- Missing required attribute [size]
- Missing required attribute [color]
These all are examples of Apparel & Accessories category related errors. Although they are separate errors, they often come up together equally a 'parcel'.
If you don't sell any products that could be classified equally 'Apparel & accessories' and you are seeing these errors, chances are your products got miscategorized. Bank check the 'Incorrectly assigned Google Product Category' error.
Step past Step Solution
The error(s) will go away every bit soon as you provide the required information. Permit'south do a quick run-through:
Gender
In this instance you only go 3 values: 'female person', 'male', 'unisex'. You could either match this feed aspect with its equivalent from your store (if it exists), or gear up appropriate provisional rules. Here's how information technology could look like:
In example you lot already have a dedicated field in your data source specifying gender - a unproblematic rename dominion will work. If your dedicated field contains values outside of the accustomed range, you tin can still pair it with the 'gender' feed attribute. You will only need an boosted aligning before pushing it to Google:
Age_group
Some other Google Shopping attribute that comes with a set of predefined values. Those are:
- 'Newborn' (Upward to 3 months old)
- 'Infant' (3–12 months old)
- 'Toddler' (i–5 years old)
- 'Kids' (5–13 years old)
- 'Developed' (typically teens or older)
To ready it upwardly in your production feed you lot can apply similar logic to the one described above for the 'gender' attribute. In instance you're simply selling products for only 1 age group, the rule would wait similar this:
Size
For a smoothen shopping experience, follow the formatting guidelines of the state y'all're selling in when assigning size. You tin read more than about size attribute requirements and best practices here.
Usually, merchants go for matching their source field for sizes with the size attribute in the feed. Similar in the screenshot below:
Tip : If you're with Shopify, you'll likely exist well-off using the 'size_option' field.
Color
When assigning colors - call up of your target audience. How are your customers looking for products? What colors could they use in their search queries?
Nosotros've covered several ways of adding missing color information to your feed in ane of the previous errors in this article.
Missing or invalid data [condition]
The errors related to the product'south condition (new, used) are often thought to be incorrectly submitted 'condition' feed attribute. That's inappreciably ever the case!
If you're seeing this mistake, it almost certainly means issues with your microdata on product landing pages.
Condition data may be completely missing from your structured markup code, or it may state a value that is invalid e.k. 'expert condition'.
Google volition crawl your website for automatic item updates and to improve understand various attributes of your products (eg. availability, condition, price). Microdata helps Google discover mismatches betwixt your product data and your landing folio. This ensures accuracy of Shopping ads and helps prevent disapprovals related to outdated data in the feed.
Footstep past Step Solution
Add microdata to your product landing pages. You may need a manus from our website programmer or an SEO specialist to consummate this fix.
To verify whether your schema markup contains the right information, you may utilize a structured information testing tool from Google or Rich Results Examination.
Excessive capitalization [championship]
Annotation that this mistake applies exclusively to the production feed and non to your product landing pages. Your production titles in the product feed are capitalized and Google doesn't like it. It's specifically the use of uppercase that is triggering the error in your Merchant Center account.
- Product titles on your website can exist capitalized to the extent that you want and Google won't mind
- The production title passed via the information feed needs to exist de-capitalized
In general, you are immune to apply capitalized words across your titles (even in the data feed) as long equally it'due south moderate. There are no clear boundaries in place, but let's say having your make name in uppercase while the rest of the championship is composed of non-capitalized text should exist fine.
Step by Step Solution
You lot need to get rid of excessive capitalization in your product titles that are passed via the product feed. In that location are a couple of approaches you could take:
Method 1
Change capitalization in the feed, leave information technology be on your website.
In DataFeedWatch you can easily fix your capitalization across the unabridged feed in a matter of seconds. All you need to practise is visit the 'Edit values' section for the 'title' attribute and cull what you desire to do:
- Capitalize: this choice will apply a 1st-letter-uppercase rule. You can cull whether you'd similar to employ this rule the unabridged title or maybe just parts of it. An exemplary product title would await like this:
Adidas Beloved Desert Sneakers, Blue, Size 38
- Uppercase: text will be all capital letters. While you lot are straying away from capitalization to resolve the error, yous could always cull to apply uppercase to specific parts of the title. For instance - the brand proper name. Hither'due south how a product title could and so await like:
ADIDAS Honey Desert Sneakers, Blue, Size 38
- Lowercase: if yous utilize it to the entire title, it would be devoid of whatever capital letters. For example:
adidas love desert sneakers, bluish, size 38
Depending on what your original titles looked similar, y'all may need to utilise one or more of these rules to get your title into the perfect shape. As you polish them up, you can always have a peek into the preview.
Method two
Change capitalization directly in your web-shop.
Probably a more time-consuming method, but if you want to continue your titles the aforementioned on both the landing pages and in the feed - that'due south the way to become. The store data is unremarkably a live source for the production feed then any changes you make over there would carry over to your Shopping feed.
Invalid or missing required aspect: id
The product ID is your product's transaction history and quality score information carrier. Without it your Shopping ads won't run.
Footstep past Step Solution
Every product submitted to Google Shopping needs to own a unique ID in order to pass Google'southward verification and be served among the Shopping ads results.
Step 1: Identify which items are missing the ID value.
You can do it by reviewing the written report in Google Diagnostics, or checking out the Feed Products tab in DataFeedWatch.
Pace ii: Assign a proper attribute from your online shop.
It should be a field that is populated, and unique, for all products. Popular choices would be SKU, variant_id, or a UPC.
In DataFeedWatch you can review your shop items in a filtered view to easily identify the right field. If none of your ID fields is populated for all products, y'all tin can besides populate this aspect using rules - for example by calculation a static value or using a lookup table.
CSS not selected for this destination
The error ways y'all haven't selected your 3rd party CSS partner to represent you lot for the 'surfaces across Google' program (aka free product ads). The solution involves creating a new Google Merchant Middle 'shell' account.
Important: this issue is non influencing your paid Shopping Ads in any way.
Step by Pace Solution
You will need to create an additional Google Merchant Business relationship (GMC) that will serve as a remote command for the account that is continued with a CSS partner. That new account doesn't need to contain any feeds or exist utilized for whatever other purpose. It can be a 'vanquish' business relationship.
one. In the new GMC account, you will need to verify and claim your domain
Whatever Merchant Account yous have with 3rd party CSS is exempt from verifying a domain. Because of that, Google cannot treat it every bit a verified entity to manage 'surfaces across Google' representation.
2. The newly created business relationship volition default to 'Google Shopping' as the CSS partner, allowing you to activate the tertiary political party CSS for 'surfaces across Google' in your old business relationship.
Note: If you're using multiple CSS partners, you lot tin just select only ane to correspond you lot for the costless Google advertising space.
1. Select representation for 'surfaces across Google' in the CSS Dashboard (from the new account)
Click the tools icon > click Shopping ads setup under 'Tools' > Go to the CSS activity dashboard
From there y'all will exist able to select the CSS to represent you for 'Surfaces beyond Google' and the error should go abroad.
Important: if y'all already have a Merchant Business relationship that is running via 'Google Shopping' as the CSS partner, you don't need to create an additional account. Merely utilize the existing ane to manage the opt-ins and opt-outs across other accounts you have with other CSSes.
Back to summit or
Product or Account is not eligible for enhanced listings on Surfaces Across Google
This issue may touch y'all on the product level or on the account level. Let'southward wait into both scenarios.
Product-level ineligibility:
If you lot're seeing this fault for one or several products across your inventory, chances are you accept incomplete or invalid product information. You volition then likely see other errors or warnings listed for the affected items. Resolving them will be the central to unlocking Surfaces across Google (SaG).
Step 1: Expect into production diagnostics to identify the accompanying product data issues
Step two: Resolve errors and warning to articulate your mode to enhanced complimentary listings
For instance, you might see that your product is ineligible for enhanced listings for SaG, and at the same time, its description is missing. The likely cause of both errors is the missing description as it is a required attribute for enhanced listings (for a complete list of required attributes click here).
For tips on how to resolve each additional error, check out other errors described in this article.
Business relationship-level ineligibility:
The account-level mistake is more than catchy as the exact crusade of it is not disclosed. There are two chief factors that might influence your account eligibility:
Trust factor
Trust is one of the fundamental determinants when it comes to existence able to serve enhanced listings on SaG. The nearly important factors impacting your trust score are:
- Client Reviews
Does your website characteristic reviews from customers nerveless over the concluding half-dozen months to one year? If non - this may be the very reason for rejecting your business relationship for enhanced listings. Product reviews from your customers are considered ane of the strongest trust signals for Google.
If you lot oasis't washed so yet, start collecting reviews, and overtime your account trust score should go upwards.
- Connecting your Merchant Center to a 3rd party platform
A swell way to bank check this 1 off the listing would exist to connect your Paypal business relationship.
Yous can exercise that by going to Settings in Merchant Centre > Linked Accounts > Platforms > and connecting your Paypal account from there.
- Connecting Google My Business account
Similarly, as above, go to Settings > Linked Accounts > Google My Business organization > and then, connect your Business business relationship.
Fulfilling these steps should go you into the SaG space with enhanced listings, or at least get you much closer to it!
Prod uct data quality
If you take other feed errors and warnings affecting the majority of your products your entire business relationship may be seen as 'ineligible'. Ensuring information correctness is central.
A very of import area to pay attention to is UPIs (Unique Product Identifiers). Although Google has made product identifiers optional, they remain crucial for the performance of your feed and they have a huge impact on your product data quality score.
If y'all oasis't included GTIN, MPN, or brand, providing them should be your adjacent step. You may notice it useful: How to become your GTIN number.
Following these steps should get your account to turn eligible for enhanced listings. If it remains ineligible regardless - contact Google support for more information.
Feed processing errors/warnings in Google Merchant Middle
Offer quota total, items rejected
This mistake could appear to you lot upon uploading a data feed to your Google Merchant Eye account, and it will stop Google from verifying your feed for Shopping Ads.
At that place are a few potential reasons you're seeing the error:
- Google'south internal error - the most probable reason for this event.
The solution would be to attempt the feed upload once more with a several minutes suspension. Upon the 2nd or tertiary endeavour, the error commonly goes abroad and Google proceeds with the verification and approving process.
- Too much data - your data feed file contains too much data. Try excluding a part of your product inventory and re-upload the smaller feed file to the Merchant Center. Here you tin can check how to exclude products from a data feed in DataFeedWatch.
- Too many data errors in your feed - a bully role of your information feed contains errors. Attempt running a feed review start and resolving the errors before uploading your products again to Google Merchant Center.
Item uploaded through multiple feeds (warning)
It's recommended to only provide any unique product through ane feed. If you lot upload the same particular through two different feeds, yous volition receive a warning, simply it won't cause product disapproval. Google volition ignore the duplicate items in ane of the feeds.
To resolve the alarm:
- Remove the duplicate items from ane of your feeds
Observe out how to remove specific items from your feed in DatafeedWatch in one of our other articles.OR
- Alter product IDs for duplicate items
Google recognizes products by their unique ID. If you upload the same product twice, but with a unlike ID - it will be seen equally ii unique products. This solution is only recommended if you'd like to annunciate the same item in a unlike fix-up.For example, when yous're conducting product title A/B testing, and i feed holds a different version of the production name than the other one.
Awaiting initial review /or/ Image not retrieved (crawl pending)
This mistake generally turns out to exist Google's internal delay. It doesn't indicate any problems with the images uploaded.
The simply solution in this case is to expect. If y'all keep seeing this fault after 72 hrs, contacting Google Merchant Centre Support is advisable.
Wrong feed URL
If yous come beyond issues, such every bit 'wrong data feed URL' or 'error with processing information file', while submitting your product feed URL in Google Merchant Middle, you lot've likely included additional characters in your feed URL, or used incorrect format.
According to Google Shopping feed specifications, the data feed file should come in 1 of the following formats: text (. txt) and XML (. xml).
If you've verified that the format is right, try uploading the feed URL once more. Make certain at that place are no accidental spaces or other characters added.
Detail disapproved due to policy violation
Unlike the other errors we've covered in this commodity - this ane doesn't requite you clarity on what is wrong with your feed. If there is 1 determination to be drawn from the mistake message alone information technology would be that Google'due south algorithms have plant elements in your feed (or in your online store), which are not in line with Google Shopping policies.
Which elements? That remains a mystery, until…you contact Google.
To sort out this outcome, you first need to learn the reply to the virtually fundamental question: 'what was the policy violation on my part?'. Once you lot've established the exact reason for disapproval - information technology's fourth dimension to prepare the feed (if that's where the issue lies). Or, make suitable changes in your online store.
Fixing the feed will mean different things depending on what the violation is. It might involve:
- Removing products from the feed
- Replacing or removing banned words from titles or descriptions
- Changing images
- And many more...
Also, if you feel like y'all've stock-still all the issues & exhausted all your options and your production is notwithstanding disapproved - it might be that is has been blacklisted past Google.
- Check out this Pro Tip to find out how to deal with blacklisted products.
Not sure what could be the solution for you lot? Feel free to reach out to us anytime! ;)
Recommended Farther Reads
- Four winning bidding strategies on Google Shopping
- Abound Your Business With Facebook and Google Ads
- PPC Strategies for Google AdWords and Facebook [+ Tips to Accomplish 542% ROAS]
- seven Tips for Google Shopping Feed Optimization [Adept Level]
- [Guide] Get the nigh out of Free Google Shopping Ads
-
Finding GTINs For Your Products
Source: https://www.datafeedwatch.com/blog/common-google-merchant-center-errors
0 Response to "Merchant Center Oops Something Went Wrong Please Try Again Later Account Linking"
Post a Comment