F FEED.SHOPTOK.COM

Check if your product feed is ready for Shoptok

Paste the public URL of your XML or CSV product feed. We check access through our proxy, validate the format, inspect required fields, test sample product pages, and test sample images.

Feed URL Use a public HTTP/S URL that opens without login, captcha, or geo blocking.

Access check Requests are made through proxy.shoptok.com (IP: 46.224.2.158) with user-agent EponudaBot/1.0 (contact: support@eponuda.com).

You get a result URL immediately while the check continues in the background.

What happens next

Access check

We fetch the feed through the Shoptok proxy and detect DNS, timeout, WAF, Cloudflare, login, redirect, or permission problems.

Format validation

We detect XML or CSV, check that the file can be parsed safely, and report malformed structure or encoding issues.

Required field review

We inspect product rows for required fields, aliases, empty values, invalid prices, and examples of problematic products.

Sample image test

We try a small set of image URLs through the proxy and verify access, content type, dimensions, and obvious blocking.

What we check

The result page tells you what is OK, what needs work, and how to fix blocked access or feed data issues.

Format check

Field check

Image check

Feed specification

Field guide, XML structure, and resources

Use this as the practical checklist while preparing or exporting your merchant feed.

Feed specification

A good feed has one product per item, stable identifiers, public product URLs that open real product pages, numeric prices, UTF-8 text, and direct image URLs that can be fetched through the Shoptok proxy.

Best practice Use the official Shoptok XML names for required data: sku, product_category, product_brand, product_name, product_url, product_price, and product_image_url. When a model or MPN is available, add it as optional product_mpn. Aliases are detected, but official names make validation and support much clearer.

Required data Every product must include SKU, category, name, brand, URL, price, and at least one direct image URL.

XML structure Use one <products> root and one <product> element per product.

Encoding Export as UTF-8 and escape XML characters such as &, <, and >.

All fields in this table are required The checker accepts common aliases. Each required field must have a usable value on at least 95% of products; smaller remaining gaps are shown as advisory warnings. Currency is not a separate required field. Common labels and symbols inside the price value are accepted and ignored during validation.

Field	Accepted aliases	Requirement	Good example
`sku`	`skuidproduct_idg:id`	Stable product identifier. Do not change it when price, image, or stock changes.	`SKU-1001`
`kategorija_proizvoda`	`product_categorycategoryg:product_typegoogle_product_category`	Category name or full category path that helps classify the product.	`Home > Lighting > Lamps`
`naziv_proizvoda`	`product_nametitleg:title`	Readable product title in UTF-8. Avoid internal codes as the only title.	`Oak desk lamp 45 cm`
`proizvodjac`	`product_brandbrandvendorg:brand`	Brand, manufacturer, vendor, or producer name.	`Example Brand`
`proizvod_url`	`product_urllinkg:link`	Public product detail URL that opens without login, challenge, geo block, or private network access.	`https://example.com/products/sku-1001`
`cena`	`product_pricepriceregular_priceg:price`	Current positive product price. Values such as `129.90`, `129,90 EUR`, `1.299,00 RSD`, or `129,90 KM` are accepted.	`129.90`
`slika`	`product_image_urlimage_urlimage_linkg:image_link`	Direct public product image URL. It must return image content, and should be at least 500 x 500 px.	`https://example.com/images/sku-1001.jpg`

Recommended optional fields

product_mpn, mpn, or model for a stable manufacturer model code and stronger matching.
product_description for clean UTF-8 product details.
product_ean, gtin, or ean for stronger matching.
product_stock or product_availability for availability checks.
product_delivery_price and nested attributes > attribute > key/value technical specifications when available.

XML rules

Start with <?xml version="1.0" encoding="UTF-8"?>.
Use lowercase element names consistently across all products.
Publish the feed on a stable URL and refresh it after product, price, stock, or URL changes.
Keep the feed at or below 3 GB and allow HEAD plus GET.

Formatted XML example UTF-8

<?xml version="1.0" encoding="UTF-8"?>

<product_category>Home & Garden</product_category>

<product_brand>Example Brand</product_brand>

<product_mpn>MODEL-1001</product_mpn>

<product_name>Example product</product_name>

<product_url>https://example.com/products/sku-1001</product_url>

<product_price>129.90</product_price>

<product_description>Short UTF-8 product description</product_description>

<product_image_urls>

<product_image_url>https://example.com/images/sku-1001.jpg</product_image_url>

</product_image_urls>

<product_stock>12</product_stock>

<product_availability>in stock</product_availability>

<product_ean>3830000000000</product_ean>

<key>Color</key>

<value>Black</value>

</attribute>

<key>Material</key>

<value>Stainless steel</value>

</attribute>

</attributes>

</product>

</products>

Official Shoptok instructionsFull field guide, XML rules, formatting notes, and image requirements. Open example XMLUse the sample feed URL directly in the checker.

Platform integrations

Most commerce platforms can publish a stable product feed URL. Use the platform export that gives you public XML or CSV, one product per row or element, and consistent field mapping.

WooCommerce

Use the Woo Product Feed Pro plugin.
Create an XML or CSV product feed with a stable public URL.
Schedule refreshes after product imports, stock changes, or price updates.
Allow proxy.shoptok.com (IP: 46.224.2.158) in Wordfence, Cloudflare, CDN, cache, and bot-protection rules.

Shopify

Use the Product Feed Shopify app.
Export XML or CSV with one product per row or element.
Use public storefront product URLs, not admin URLs.
Use direct Shopify CDN image URLs for product_image_url.

Google Merchant

Common Google aliases are detected: g:id, g:title, g:brand, g:mpn, g:link, g:price, and g:image_link.
Use stable IDs and direct public product URLs.
Include brand, GTIN, MPN, category, price, and images whenever available.
Check the Google product data specification when mapping fields.

Meta / Facebook catalog

Common catalog fields are detected: id, title, description, availability, condition, price, link, and image_link.
Keep CSV or XML headers consistent across all rows.
Use brand, GTIN, MPN, category, and image fields where possible.
Review Meta catalog data feeds for platform-specific guidance.

Shared mapping rule Whatever the platform calls the field, map it to the same commercial meaning: stable product ID, category, readable title, brand, model/MPN, product URL, price, and direct image URL.

Woo Product Feed ProRecommended WooCommerce feed plugin.

Shopify Product FeedRecommended Shopify feed app.

Google product data specOfficial Merchant Center feed reference.

Meta catalog referenceDeveloper documentation for catalog integrations.

Proxy allowlist

Feed and image access is tested through the Shoptok proxy, so merchant firewalls and bot-protection tools must allow that traffic.

Allowlist target Allow traffic by proxy.shoptok.com (IP: 46.224.2.158) or by user-agent EponudaBot/1.0 (contact: support@eponuda.com). Best setup: allow both signals for feed, product page, and image URLs.

HTTP rules

Allow HEAD and GET for the feed URL.
Allow GET for product image URLs.
Do not redirect the feed to login, consent, or captcha pages.
Keep redirect chains short and public.

WAF rules

Bypass bot challenges for Cloudflare, Akamai, Imperva, DataDome, Sucuri, AWS WAF, and similar tools.
Allow the proxy endpoint/IP or the Shoptok user-agent. If your WAF supports it, allow both together for a stricter rule.
Check for geo, ASN, country, and rate-limit rules that may block server traffic.
Return a clear 200 response with XML or CSV content.

Cloudflare custom rule example

Create a WAF Custom Rule for the feed URL, product URLs, and image URLs:

(ip.src in {46.224.2.158}) or (http.user_agent contains "EponudaBot/1.0 (contact: support@eponuda.com)")

Action: skip managed WAF rules, bot challenges, and rate limiting for those feed-related paths only. Use or when Cloudflare can match either signal; use a stricter and rule only if both signals are always present in your setup.

FAQ

Short answers for the most common feed setup questions.

What feed URL should I submit?

Use a public XML or CSV URL that returns product data directly. The URL should not require login, cookies, a browser session, or manual captcha solving.

Can I use a Google or Meta feed?

Yes. Common Google Merchant and Meta catalog aliases are detected, including ID, title, brand, link, price, and image fields.

What if Cloudflare or another WAF blocks the check?

Allow proxy.shoptok.com (IP: 46.224.2.158) or the user-agent EponudaBot/1.0 (contact: support@eponuda.com). Best setup is to allow both. The feed URL, product URLs, and image URLs should allow HEAD and GET.

Which plugin should I use?

For Shopify use Product Feed. For WooCommerce use Woo Product Feed Pro.

How should prices and encoding look?

Use UTF-8. Prices must contain one positive numeric value. Common labels and symbols such as EUR, €, RSD, DIN, BAM, KM, HRK, kn, and USD are accepted and ignored.

Why do images matter?

Each product needs a direct image URL. The checker samples image URLs to verify access, content type, dimensions, and obvious blocking.