Check Your Pagelayer Pages Before Launch with AI
A read-only check of your Pagelayer pages for sample text, dead buttons, missing alt text and heading problems.
Prerequisites
A site connected to WPVibe running Pagelayer 2.2.2 or newer (tested on 2.2.2, free) on WordPress 6.9 or newer, with an administrator account.
My WordPress site uses the Pagelayer page builder. Check my Pagelayer pages before launch. Do not change anything; this is read only. [Check only these pages: list them.] 1. Run get_ability_info for pagelayer-pages/get-page. If it is not found, run rest_api GET /wp/v2/plugins with search pagelayer. If Pagelayer is active, tell me this recipe needs Pagelayer 2.2.2 or newer on WordPress 6.9 or newer, and stop. If it is installed but not active, tell me to activate it, and stop. If it is not installed, tell me this recipe is for the free Pagelayer plugin, and stop. 2. List my Pagelayer pages with pagelayer-pages/list-pages (limit 100). Check every page it returns, scheduled and private ones included. If it returns 100, tell me there may be more. 3. On each page, run pagelayer-pages/validate-page (post_id set to the page id) and note its errors and warnings: sample text left in a widget, images with no image or no alt text, no H1 or more than one, widgets this install does not have, settings Pagelayer drops when it renders, and inline CSS. If it answers invalid_input, the page was built in Pagelayer's editor, which the validator cannot read: mark it not checked by Pagelayer's validator and give it step 4 only. validate-page reads Pagelayer's AI copy of the layout, which can be older than the page: confirm each of its findings in the page HTML from step 4 before reporting it, and mark it unconfirmed on pages that cannot be fetched. 4. Fetch each published page as a visitor sees it with get_page_html. Check only the Pagelayer layout (elements whose class starts with pagelayer-) and the page title; report anything in the site header, footer or menus once at the end, not per page. Check what validate-page does not: buttons with no text or no link, buttons and links with an empty destination or just #, lorem ipsum or other filler text, raw shortcode text starting with [pl_ printed on the page (a widget this install lacks), a second H1 from the page title my theme prints above the Pagelayer layout, images whose alt text is empty in the page HTML (validate-page misses images given by address), and images loaded from another site. For that last check, first look up where my media library lives: rest_api GET /wp/v2/media with per_page 1 and _fields source_url; images on that same host are mine, even when it is a storage or CDN address. Do not report accordion toggles (links with the class pagelayer-accordion-tabs and no destination) or leftover template text in double braces inside class names: they are how Pagelayer renders, not problems a visitor sees. Draft, pending, private and scheduled pages cannot be fetched this way; say which ones only had step 3. 5. Give me one table with the page, the problem, the exact text or element id, and a suggested fix, with the pages that have the most problems first. Then stop. Make no fixes in this conversation.
Skip pasting the full prompt. Drop this into your AI on a site that already has WPVibe:
Run the “Check Your Pagelayer Pages Before Launch with AI” recipe from the WPVibe cookbook on my connected site.
Before a site goes live, every page built with Pagelayer needs a last look: sample text left in a widget, a button that still links to #, an image with no alt text, a page with two main headings. Clicking through each page in the editor to find them is slow, and the small ones are easy to miss.
The AI lists your Pagelayer pages, runs Pagelayer’s own validator on each one it can read (the validator only reads pages built with Pagelayer’s AI abilities), and then checks each published page as a visitor sees it for what the validator does not cover: empty or # links, filler text, raw shortcode text and the page title your theme adds above the layout. You get one table with the worst pages first.
It changes nothing, so it is safe to run on a live site. Fix what it finds in Pagelayer’s editor.
Outcome
One table of the problems on your Pagelayer pages, worst pages first, with a suggested fix for each.