Docs / Store for Wix / Troubleshooting

AEO Ultimate Store for Wix

When something looks wrong

Most problems on this app are credentials — a key pasted in the wrong form, or a property ID that does not match. The messages below are the real ones, so search this page for whatever you are seeing.

The Google service account key will not save

Google hands you several things that look like credentials. The one this needs is the service account JSON key file — roughly 2KB, containing both client_email and private_key. Paste the whole file contents, not a fragment.

Common mistakes:

• Pasting an API key (a short string) rather than a service account key.
• Pasting an OAuth client JSON, which has no private_key.
• Pasting only the private_key value.
• “That file is too large to be a service account key — expected a ~2KB JSON file”: you have almost certainly pasted an export of something else entirely.

If a previously working connection starts failing with “The stored service account key is missing client_email or private_key — re-paste it in Settings”, the stored value was truncated on save. Paste it again in full.

Google rejected the credentials

The key is well-formed but Google will not accept it. Two usual causes: the service account has not been granted access to the property, or the relevant API is not enabled on that Google Cloud project.

The step people miss is the first one. Creating a service account does not give it access to anything — you have to add its client_email address as a user on the GA4 property, exactly as you would a colleague.

GA4 property not found

The property ID is a plain number — something like 123456789. It is not the Measurement ID that starts G-, which is what most people reach for because it is the one they see everywhere else.

Find it in GA4 Admin → Property details. If the number is right and it still fails, the service account has not been granted access to that property.

Bing rejected the API key or the site URL

Two distinct failures with different fixes.

“Bing rejected the API key” — check it is copied correctly and still active in your Bing Webmaster Tools account. Bing keys can be revoked or regenerated without warning.

“Bing rejected the request for [url]. The site URL must match a verified site in your account exactly — including https” is the fiddly one. Bing treats these as different sites:

Copy the site URL exactly as it appears in your Bing Webmaster Tools dashboard — including the protocol, the www or lack of it, and any trailing slash.

An AI feature says the key is not configured

“Anthropic API key is not configured. Add it in Settings.” — and the same for OpenAI and Gemini. Each provider is separate: configuring one does not configure the others, so switching provider means adding that provider’s key.

You supply and control these keys, and you pay the provider directly at their rate. If a key is present but calls fail, check the balance and any spend cap in your own account with that provider before assuming the app is at fault.

Image sourcing declined to fetch an image

The app verifies a brand’s official website through Wikidata before fetching from it. When it cannot: “Couldn’t verify an official website for [brand] through Wikidata, so there’s no trusted domain to fetch an image from.”

That is a refusal, not a failure — rather than guessing at a domain and pulling an image from somewhere unrelated, it stops and asks you. Paste the manufacturer’s address yourself, in the form brand.com.

“apply must be an http(s) image address” or “That doesn’t look like a full address” means you pasted the page rather than the image. Right-click the image itself and choose Copy image address.

My paid features stopped working

Check the subscription in your Wix account. This app is billed by Wix as a monthly subscription, so if it lapses, access to paid features ends — that is Wix’s billing model, not a fault in the app and not something we can override.

The free plan continues to work. See the terms for how this differs from buying direct, where the software keeps running indefinitely.

Nothing here matches my problem

Send the exact message and what you were doing when it appeared. That is usually enough to reproduce it.