One character in a namespace URI, and Google silently ignores every g: attribute

A near-miss RSS namespace URI -- https instead of the specified http -- parses as perfectly valid XML while Google ignores every single g: attribute in the file.

This is one of the things Product Feed & Merchant Center Compliance already handles. Get your products into Google Shopping and keep them from being rejected.

Buy for $1292 of 3 clean-room builds passed · full refund if it fails on your machine

Is this you?

Writing the Google namespace declaration with https:// instead of the exact http:// URI Google specifies produces a feed that is completely well-formed XML -- every validator that checks "is this valid RSS" passes it -- while Google's own parser doesn't recognize the namespace at all, and silently disregards every g:price, g:availability, and g:gtin attribute in the entire feed.

Why this one is easy to get wrong

https is the more modern, more secure-looking choice for any URL an agent writes today, and a namespace declaration is easy to treat as an ordinary URL rather than an exact string constant Google's parser matches literally. Nothing about the resulting feed looks wrong -- it validates as XML, it has all the right elements -- because the failure is entirely in namespace resolution, not structure.

What you get instead

The pack hand-writes the roughly 40 lines of RSS 2.0 output itself specifically so the two things a wrapping library would hide -- the exact namespace URI and whether an absent attribute is emitted empty or omitted -- are pinned as literal constants in one place (rss.ts) rather than delegated to a dependency's own defaults. escapeXml() is likewise a single named function, not a generic templating pass, so nothing downstream can accidentally double-escape or under-escape a title or description.

Source: ARCHITECTURE.md 'No feed-generation library' — checkable in the pack you receive

How you actually use this

You don’t install a library or wire up an SDK. Your own coding agent builds the code in your project, and you keep it — no runtime dependency on us.

Step 1
Download and unzip
You get a folder: the docs that tell an agent what to build, a starting skeleton, and the test suite that decides when it's done.
Step 2
Open it in Claude Code or Cursor
Point your coding agent at the folder. Nothing to install, no account with us, no API key.
Step 3
Paste one prompt
The pack contains the exact prompt. Paste it as your first message and leave it alone — it works through the build itself, choosing a cheaper or stronger model per task.
Step 4
Run ./verify.sh
One command. It prints a pass or fail for every check. Green means the build is done — the same script we ran to produce the receipt on this page.

Typical build: about 44 minutes of your agent working, mostly unattended. Then you integrate the working module into your app the way you would any code you’d written yourself.

Why you can believe this

2 of 3 runs passed

We ran this pack from an empty folder 3 times and published exactly what happened — every check, the model, the token cost, the wall time. Not a testimonial, and not our opinion: the same verify.sh you run yourself. Read the full receipt →

Buy for $129 14-day refund if verify.sh fails →