Vizard Agent

How to make an ad from a shop's URL alone

Last updated 2026-08-17 · 6 min read

Give Vizard Agent a shop's URL and a length. Vizard Agent reads the site, extracts the brand identity and images, finds the underlying product feed in the page code, collects the real catalogue and prices, and builds a thirty-second ad from what the shop actually sells rather than from its homepage banner.

What is the short version?

An online shop's homepage is a poster. What the shop actually sells — every product, every price, every image — lives in a data feed behind it, and an ad built from that feed is specific in a way an ad built from the banner never is.

  1. Go to Vizard Agent and give it the shop's URL.
  2. Say the length and where the ad is going.
  3. Say if a particular product or category should lead.

What do you need before you start?

A live URL and a length. Vizard Agent handles the reading, the extraction and the design, and the only thing worth adding is a steer — because a shop with sixty products has sixty possible ads, and it will pick one if you do not.

What do you type into Vizard Agent?

One line with the link is a complete brief. Vizard Agent reads the site, finds the catalogue behind it and decides the structure, so anything you add beyond the URL is a steer rather than a requirement — and the shop itself is the source it works from.

Prompt

Make a [30] second ad for this website: [link]

Variants worth knowing:

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real shop ad. Nearly half the run is data archaeology: it went past the rendered page and into the site's own product feed to get the real catalogue rather than the pictures on the front.

  1. Checks the extraction tools and reads the website.
  2. Extracts the brand identity and the images from the page.
  3. Captures the site visually and reads the main brand pages.
  4. Fetches the page source and digs into the code looking for the data behind it.
  5. Looks for the site's data feed and parses the content it returns.
  6. Inspects the data endpoints and locates the product feed, then finds the catalogue route.
  7. Reads the API usage code and probes the product endpoint directly.
  8. Renders the site to see it as a visitor does and checks the sitemap.
  9. Lists the products, finds the real prices and collects the full catalogue, then reviews the product list before building anything.

Steps 4 to 7 are the difference between an ad about a shop and an ad about what the shop sells. A rendered page shows six products; the feed behind it lists all of them with prices, and Vizard Agent went and read it.

What does the result look like?

From the run this page is written from, probed on the delivered file: 1080x1920, H.264, 30fps, 30.0 seconds, AAC audio. Vertical, exactly thirty seconds, built from the shop's own product images, brand colours and real prices, with captions and music.

Vizard Agent keeps the collected catalogue after delivery, so a second ad about a different category is a rebuild from data it already has rather than another pass over the site.

Thirty seconds is around six product beats and a closing card. Vizard Agent paces it so each product is legible at feed size, which matters more than fitting one extra item into the same time.

It is not instant, and this category was not separately measured. Comparable work runs a median of 28 to 38 minutes end to end. Across all projects the median cost by tier is Flash 47, Pro 55, Max 242, Ultra 263 credits.

When does this not work well?

Everything in the ad comes from the shop, which means every fact in it is only ever as current as the shop was at that moment. Vizard Agent reads the catalogue and the prices as published on the day it runs, and an online shop changes daily.

How do you fix a result that came back wrong?

Say what to change. Vizard Agent keeps the extracted brand identity, the product catalogue, the prices and the images, so a different hero product or a corrected price is a rebuild from stored data rather than another crawl of the site.

How does Vizard Agent compare to doing it yourself?

By hand this is screenshotting products one by one, copying prices into a document, exporting images at the wrong resolution, and building the cards in a design tool — and then repeating the whole thing whenever the range or the pricing changes.

By hand Vizard Agent
The product list Copy from the page Read from the site's own feed
Prices Retype and hope Collected with the catalogue
Brand colours Guess from a screenshot Extracted from the site
A second ad Start again Rebuilt from stored data

Common questions

Does it need anything besides the URL? No. Vizard Agent reads the site, extracts the branding and finds the catalogue behind it.

Will it get the prices right? It reads what the shop publishes. Prices change, so re-check before putting money behind the ad.

Can I choose which product leads? Yes, and it makes a sharper ad. Otherwise Vizard Agent picks one from the catalogue.

What if my site blocks automated access? Vizard Agent tries several routes. A hard block means supplying the products and images directly.

Can it make one ad per category? Yes, and cheaply, because the catalogue is collected once.

Can it add a call to action? Yes. Give Vizard Agent the exact wording and it sets it on the closing card in the shop's own colours.

Will it use my product photos? Yes. Vizard Agent pulls them from the site rather than generating stand-ins.