Let a WordPress Page Agent Navigate Filters and Cart Steps for Your Visitors

A shopper types “trail shoes, size 43, add one to my basket” into your WordPress chat widget. The bot replies with a paragraph and a link. They still have to open the catalog, find the filter, pick a variant, and hit Add to cart alone.

That is answer-only AI. Fine for “what is your return window?” Useless when the job is doing the navigation for them.

Generatify is the DaftPlug AI plugin. Its page agent is built for the doing job: the visitor says what they want; the agent navigates to the page, applies filters, adds to basket; every step is shown and stoppable; you set limits on what it may and may not do. It is not the helpdesk agent (answers) and not the admin assistant (dashboard). Three different surfaces.

For the answer-only helpdesk path, see Run a WordPress helpdesk agent that answers from your own pages. Use that when the visitor needs a policy. Use the page agent when they need an outcome on the live site.

What Generatify actually ships for the page agent

Keep the list honest:

• Page agent that navigates and acts on the front end
• Visitor describes a goal; the agent opens pages, applies filters, adds to basket
• Every step shown and stoppable
• You set limits on what it may / may not do
• Site owner connects the API key (ChatGPT, Claude, Gemini, or Kimi). Visitors do not bring their own key. Free has no model connected; Pro plugs in the owner’s key
• Supporting Generatify pieces nearby: helpdesk agent, admin AI assistant grounded in site content, Smart Compose, content generation in the editor, bulk tags/categories/meta/alt, comment scoring, product recommendations, usage analytics

Do not blur page agent with helpdesk. Helpdesk answers from your pages and can hand off to a human. Page agent moves through the UI. Admin assistant lives in wp-admin. Pick the tool that matches the job.

Why “chat that only answers” fails on stores and catalogs

Three quiet failures show up on WooCommerce and large catalogs:

1. It describes the site instead of using it. The visitor still does the filter and cart work. You paid for AI and got a talking FAQ.
2. It sounds smart on stock and variants it cannot see. Generic answers invent sizes or claim something is available. Acting on the live page is safer when the task is navigation, not policy.
3. It trains people to wait for text when they wanted an outcome. On a store, the outcome is a filtered list or a filled cart. A paragraph is not that outcome.

The page agent exists for that gap. The visitor stays in control because every step is visible and stoppable. You stay in control because limits define the sandbox.

How to set up the page agent in wp-admin

1. Connect your own API key (Pro)

In Generatify settings, connect the owner API key for ChatGPT, Claude, Gemini, or Kimi. Free has no model connected. Visitors never paste a key into the widget. Usage runs on the key you control, which is why usage analytics matter later.

Without a key, there is no page agent to demo. Connect first.

2. Enable the page agent on the front end

Turn on the page agent for the templates where navigation help matters: shop, category, product, maybe search. You do not need it on a legal page that only needs FAQ answers. Those can stay on helpdesk.

Confirm the widget or entry point appears for logged-out visitors the way you intend. Test in a private window.

3. Write hard limits before the first public session

Limits are the safety layer. Spell out what the agent may and may not do. Typical starting policy for a store:

• May: open shop/category/product pages, apply listed filters, add a single item to basket, open cart for review
• May not: place the final order, change account email, apply arbitrary coupons you did not allow, leave your domain, edit quantities into absurd bulk

Keep the list short and testable. If a step is irreversible money, keep a human (or a clear checkout) in the loop.

4. Walk a real goal with step visibility on

As a visitor, ask for something concrete: “Show blue size M hoodies under $60 and add one to cart.” Watch the agent open the right page, apply filters, and attempt add-to-basket. Confirm each step is shown. Hit Stop mid-flow and confirm it halts.

If a theme uses custom filter widgets the agent cannot see, fix the theme markup or narrow the allowed actions. Do not ship a demo that fails on your best-selling category.

5. Separate helpdesk from page agent in the visitor’s head

If both widgets exist, label them by job. “Ask a question” vs “Help me shop” (or your own wording). Mixing answer mode and act mode in one ambiguous bubble confuses people and burns tokens.

Helpdesk stays grounded in your pages, products, and policies. Page agent stays on navigation and cart steps. Admin assistant stays in the dashboard for your team.

6. Watch usage analytics after launch

Check which goals burn tokens, which steps fail, and whether people stop the agent often. High Stop rates on one template usually mean limits are wrong or the UI is too custom for the agent’s allowed actions. Tighten limits or fix the template before you scale traffic to the feature.

What good looks like

A working page agent session looks like a guided tour with a brake pedal:

• The visitor states a concrete goal in plain language.
• The agent opens the right catalog or product surface.
• Filters the visitor asked for actually apply on the live page.
• Add to basket happens only inside your allow list.
• Every step appears in the UI so the visitor can follow along.
• Stop halts the run immediately, with no surprise final clicks.
• Helpdesk still handles “what is your return window?” without trying to drive the cart.

If people use Stop constantly on one category, that template is the bug. Fix filters or narrow limits there before you advertise the agent sitewide.

Pitfalls (the ones that bite)

Shipping page agent without limits. An unbounded agent that can click anything is a support incident waiting to happen.

Expecting visitors to bring API keys. They do not. You connect the key. Free stays disconnected until Pro.

Using helpdesk copy for a navigation job. “Here is a link to shoes” is not “filtered size 43 and added to basket.”

Hiding steps. If visitors cannot see or stop the agent, trust collapses on the first weird click.

Enabling on checkout-critical flows on day one. Start on browse and add-to-cart. Earn the right to go deeper.

Ignoring theme quirks. AJAX filters, shadow DOM mega-menus, and off-canvas drawers can block actions. Test production markup.

Confusing recommendations with the page agent. Product recommendations from browse/order history are a different Generatify feature. Useful, not the same.

Practical checklist before you call it done

1. Connect owner API key on Pro.
2. Enable page agent on shop/category/product (or your catalog equivalents).
3. Write allow / deny limits for navigation and cart actions.
4. Run a live goal: navigate → filter → add to basket.
5. Confirm every step is visible and Stop works.
6. Keep helpdesk for Q&A; keep admin assistant in wp-admin.
7. Review usage analytics after the first real sessions.
8. Fix theme filter quirks before promoting the feature in marketing.

Takeaway

Answer-only chat leaves shoppers with homework. A page agent does the homework on the live site, with steps they can see and stop, inside limits you define.

Generatify ships that page agent beside helpdesk, admin assistant, Smart Compose, and the rest of the AI toolkit, running on the API key you connect. Start with browse and add-to-cart goals. Keep irreversible checkout human.

One Pro membership unlocks Generatify plus Progressify, Lightify, Rankify, and Snapshotify. New Pro plugins join existing memberships. Plans differ by site count only. See pricing when you want visitors to finish catalog tasks without a scavenger hunt.

Ship one limited goal. Stop it mid-run on purpose. When the UI freezes cleanly, the agent is ready for real traffic.