I Clicked Generate Script on a Product Demo Page. Nothing Happened.

I clicked "Generate Script" on a product demo page. Nothing happened.

Not an error message. Not a spinner that got stuck. Literally nothing. I typed a
topic, pressed the button, and the results panel stayed hidden, the fields stayed
empty, and the console stayed clean.

That is the worst possible failure mode for a page whose entire job is to let a
stranger test before they pay — because there is nothing to read, nothing to
report, and nothing for a buyer to evaluate. A broken demo that errors at least
tells you the page is alive.

Here is what I found, how I proved it, and why it matters more than any feature
list on the same page.

The page claims a working demo

The sales page for Faceless Video Automation sells a local video workflow:
automated script generation, AI asset creation, local rendering, multi-platform
scheduling. It is a $79.99 digital package delivered by email.

The section a buyer hits first is titled "Try it now — Video Script Generator".
Its own copy promises:

Enter a topic, pick your platform and style, and watch the automation produce a
complete video script — hook, body, CTA, and everything in between.

So the demo is not a screenshot. It is not a video. It is a control the visitor is
invited to operate. That is a real promise, and it is the thing I went to test.

What I actually did

Three steps, all of them boring on purpose.

1. Read the page source. The generator is one inline <script> block. Inside it
are four lookup tables: hooks, intros, contentTemplates, ctas, outros —
keyed by platform (youtube / tiktok / instagram) and style (educational /
entertainment / motivational / news). Twelve combinations. A generateScript()
function pulls one entry from each table, substitutes {topic}, and writes the
result into seven elements by id.

2. Loaded the page in a real browser. Checked which of those elements exist in
the DOM.

3. Typed a topic and clicked the button. Then read the results panel.

The result

What the script looks up	Exists in the page?
sg-topic (the topic input)	no
sg-generate (the Generate button)	no
sg-hook, sg-intro, sg-content, sg-cta, sg-outro	no
sg-title, sg-desc	no
sg-canvas (preview canvas)	no

Every single one. Zero for twelve.

The page's real markup uses different names entirely: topicInput,
generateBtn, sgTitle, sgDesc, sgSections, copyBtn, animCanvas. The two
sides were never reconciled. The script queries data-platform and data-style
attributes on the selector chips; the chips in the HTML carry data-value. Not one
chip matches. So clicking "TikTok" does not even change the selection state — I
verified that too: the chip's selected class never moves.

Then the click test, which is the part that settles it:

topic set: productivity
click Generate: clicked
sgResult className: sg-result          <- never gains the "visible" class
sgResult offsetParent: False           <- still display:none
sgTitle: ""
sgDesc: ""
sgSections html len: 0
console errors: []                     <- silent, not a crash

generateScript() calls document.getElementById('sg-topic').value.trim() on an
element that does not exist. That throws immediately — before a single field is
written, before sg-result ever gets its visible class. The browser swallowed
it as an uncaught error in a click handler, which is why the console looked quiet.

The panel is hidden with .sg-result { display: none; } and only becomes visible
when the class flips. That flip never happens. So the visitor sees: press button,
nothing moves, page looks dead.

Why this is the finding, not a footnote

Everything else on the page is a claim I cannot verify from a browser tab. "Local
rendering engine" — I can't test that from a landing page. "Schedule directly to
YouTube, TikTok, Instagram Reels, and Facebook" — same. Those are promises about
software the buyer receives after paying.

The demo is the only part of the page the buyer can check before paying. It is the
one thing the page does not have to be trusted on. And on the live page, today, it
does not function.

I want to be precise about the limit of my own test: I did not buy the package, so
I cannot tell you whether the delivered scripts work. This defect is in the marketing
page's sample generator, not in the product. It is entirely possible — likely, even —
that the shipped workflow is fine. But a buyer cannot find that out from the page,
because the page's own test harness is disconnected from the page.

The boring part that actually caused it

This is a merge that shipped half-finished. The markup was renamed at some point
(sg-topic → topicInput, sg-generate → generateBtn, sg-result → sgResult,
sg-copy → copyBtn, animCanvas instead of sg-canvas), and the script block
kept the old names. Two versions of the same widget, coexisting in one HTML file.

The rename is the tell: the new markup is more complete. It has a sgSections
container, a copyBtn, and an animCanvas with play/restart controls — none of
which the script knows about. Someone rebuilt the UI and left the old logic
attached to it.

If you are the seller, this is a two-line fix

I am not going to guess at your build process, but the shape of the fix is
mechanical:

1. Re-point the script's getElementById calls at the ids that actually exist in the markup (topicInput, generateBtn, sgTitle, sgDesc, sgSections).
2. Change the two querySelectorAll selectors from .sg-chip[data-platform] / .sg-chip[data-style] to match the real chips — either add those attributes to the chips, or read data-value and lower-case it to match the lookup tables.

Then open the page, click the button, and confirm the panel appears. That is the
whole acceptance test, and it takes about ninety seconds.

How to buy Faceless Video Automation

The package is $79.99 and delivered digitally.

• PayPal — send to [e-mail]. Write a note saying what you are buying; it gets confirmed in the inbox.
• Crypto — 0x078fE079A9440631Bc6AD722D7143dC382b4ea4f on the Base network (ETH / USDC / USDT).
• Western Union / MoneyGram — also accepted.

The page lists [e-mail] as the contact address for purchase
requests.

The takeaway for anyone selling digital products

I have now done this source-level pass on a few different demo pages, and the
pattern that separates the good ones from the dead ones is not the quality of the
demo's logic. It is whether the page and its script still speak the same language.

A demo is a contract. The buyer brings attention; the page is supposed to return a
result. When the ids drift apart, the contract is broken, and it breaks silently —
no error page, no support ticket, just a visitor who clicks once, sees nothing, and
leaves. You never find out it happened. There is no analytics event for "the button
did nothing and the person closed the tab."

Every product page I have tested that leads with a working interactive demo earns
more trust than every one that leads with a feature list — and the difference is
exactly this: the working demo is checkable, and the feature list is not.

If you sell anything with a demo on the page, click it yourself before you send
anyone there. It is the cheapest QA you will ever run.

---

Method note: all findings above come from reading the live page's HTML and inline
script, then loading the page in a real browser and clicking the actual button.
No purchase was made, so the delivered package was not tested.