For the complete documentation index, see llms.txt. This page is also available as Markdown.

Is your shop supported?

Short answer: quite possibly — even if you've never seen it on a list. Here's why, and how to check in a minute.

Why so many shops work

Most online stores publish their product details in a structured, machine-readable form — LD+JSON and microdata — so search engines like Google can show the price, rating and availability in results. Affiliate Egg reads that same data. If a shop has done the work to look good in Google — and most have — there's a good chance Affiliate Egg can read it too.

On top of that:

  • Specific shops have their own tuned parsers, for stores that need special handling.

  • A general parser reads the structured data directly and covers many of the rest.

So "supported" isn't really a fixed list — it comes down to whether a shop exposes clean product data. Many do.

How to check your shop

The fastest way is to just try it:

  1. Create a storefront.

  2. Paste a direct product URL from the shop.

  3. If Affiliate Egg pulls in the title, price and image, you're set.

If nothing comes back, it's one of two different problems — and each has a different fix.

If it doesn't work

  • "No product data found." Affiliate Egg reached the page but couldn't read product details from it — the shop probably doesn't expose structured data in a form it recognizes. This is exactly what a custom parser is for: one written for that specific shop so its products read reliably.

  • "Blocked by the site" (503 / 403). That isn't a support problem — the shop is refusing automated requests. See When a shop blocks access.

A custom parser solves reading a shop, not getting past a block — and a scraping service is the reverse. If you're not sure which you're hitting, the on-screen message tells you: "no product data" means reading, "blocked" means access.

Last updated