Add a Call to Action Above the Footer on Every Blog Post with AI
One template above the footer of every blog post, with your offer and a button, checked before it goes live.
Prerequisites
A site connected to WPVibe running Elementor (free is enough) and Ultimate Addons for Elementor 2.9.5 or newer (tested on 2.9.5, the free version) on WordPress 6.9 or newer with a classic theme, with UAE's AI tools on: in wp-admin, UAE > Settings > AI Tools, switch on Enable Abilities and Enable Edit Abilities. A published footer made with UAE that shows on blog posts.
My WordPress site uses Elementor and the free Ultimate Addons for Elementor plugin (UAE). Add a call to action above the footer on every blog post: heading "[heading]", text "[one or two sentences]", and a button "[button text]" linking to [URL].
1. Run discover_abilities with category hfe-templates. If no uae/ abilities come back, stop and tell me to turn them on in wp-admin: UAE > Settings > AI Tools, switch on Enable Abilities and Enable Edit Abilities. If an ability a later step needs is missing (run discover_abilities without a category to check), stop and tell me to switch on Enable Edit Abilities and that ability's own switch on the same screen.
2. Run uae/templates-list with type type_footer and status publish. If no published UAE footer covers blog posts, stop and tell me to make one first: without it, on a theme UAE does not support natively, a before-footer template removes my theme's footer from every post. Run uae/theme-get-info; if the compatibility method is css-override, tell me this recipe was only tested with the default method, and stop. Then run uae/templates-list with type type_before_footer, status publish and then draft. If one exists, show it to me and stop: change that one in Elementor instead of making another.
3. Run uae/design-system-get-tokens for my colors and fonts. Create the template with uae/templates-create, type type_before_footer, status draft. Use one Info Card widget (hfe-infocard). For every widget you use, run uae/builder-get-schema (type widget, tab style for colors, tab content for text and links) and use only the setting keys it lists. UAE's own build examples name some keys that do nothing: the search icon color is toggle_color, the site title color is heading_color, the copyright text color is title_color. A key the widget doesn't have saves without an error and changes nothing. The Search widget's style schema is longer than one result can hold and gets cut off; use toggle_color for its icon color as given. Set the heading, text, button text, button link and colors explicitly so nothing falls back to Elementor's default colors. Build it with uae/builder-build: one section, columns [100], padding top and bottom 48px.
4. Show me what it contains with uae/shortcode-render and wait for my yes.
5. On my yes: uae/display-rules-update with include_locations {"rule": ["post|all"], "specific": []}, then uae/templates-update with status publish, then uae/builder-regenerate-css.
6. Find my newest post with GET /wp/v2/posts?per_page=1, then fetch it and one page with get_page_html. Confirm the call to action is on the post above the footer, the footer is still there, and the call to action is not on the page. If that check fails, clear any page cache on my site and check again; if it still fails, set everything you published in this chat back to draft, undo any rule you changed, and tell me what you saw.
7. Give me the template's Elementor edit link and tell me that setting it back to draft takes it off every post.
Skip pasting the full prompt. Drop this into your AI on a site that already has WPVibe:
Run the “Add a Call to Action Above the Footer on Every Blog Post with AI” recipe from the WPVibe cookbook on my connected site.
Someone who reads a blog post to the end is the warmest visitor you will get, and most sites show them a footer full of links and nothing to do next. Adding a call to action by hand means editing every post, and the old posts never get one.
Ultimate Addons for Elementor has a Before Footer template that sits above the footer. The AI builds one as a draft with your heading, a line of text and a button in your site’s colors, shows it to you, and on your yes shows it on every blog post and nowhere else. It checks a post and a page to prove it.
It needs a footer made with UAE: on themes UAE doesn’t support natively, a before-footer template on its own replaces your theme’s footer on those posts, so the recipe checks first. It is one template, so changing the offer later is one edit. It shows on single blog posts only, not on pages or the blog index, and the posts themselves do not need to be built with Elementor. Set it back to draft to take it down.
Outcome
Every blog post ends with your call to action above the footer; pages are unchanged.