Check Your SiteOrigin Pages for Leftover Placeholder Text with AI

My WordPress site uses Page Builder by SiteOrigin. Check my Page Builder pages for leftover placeholder content. Do not change anything; this is read only. [Check only these pages: list them.]

1. Run rest_api GET /wp/v2/plugins with search siteorigin and find Page Builder by SiteOrigin (plugin siteorigin-panels). If it is not installed, tell me this recipe is for Page Builder by SiteOrigin, and stop. If it is not active, tell me to activate it, and stop. If its version is lower than 2.38.0 (compare the numbers part by part: 2.38.0 is newer than 2.9.0), tell me to update it first, and stop: older versions lack fixes these steps rely on. If the plugin list is refused (some multisite setups), ask me which version I have. Then run get_ability_info for siteorigin-panels/layout-get; if it is not found, tell me this recipe needs WordPress 6.9 or newer, and stop.
2. If I named pages, find each with rest_api GET /wp/v2/pages, search set to its title and status publish,draft,pending,private,future, and check at most 5 of them. Otherwise list my 5 most recently edited pages: rest_api GET /wp/v2/pages with status publish,draft,pending,private,future, orderby modified, order desc, per_page 5 and _fields id,title,status,link, and tell me I can run this again for the next five. Look up where my media library lives: rest_api GET /wp/v2/media with per_page 1 and _fields source_url; images on that host are mine, even on a storage or CDN address.
3. Take the pages one at a time. For each, with PAGE_ID set to its id, read its layout with rest_api GET /siteorigin-panels/v1/layouts/PAGE_ID and max_length 80000 (Page Builder's own read-only route: it returns the same as siteorigin-panels/layout-get, which WPVibe cuts off at 50,000 characters on larger pages). If the result is cut off, skip the page and list it as too large to check. Skip it if source is none (no Page Builder layout this check can reach) and say how many you skipped. In its layouts, look in every widget's text, title, headline, link, button and image fields, including lists inside a widget, and in row backgrounds (the style of each entry in grids), for: Lorem ipsum and other filler text; sample testimonials, names, quotes and statistics that look like they came with a layout (say why you think so, and mark them as for me to confirm); buttons and links with an empty destination or just #; more than one level-one heading in the layout; and images loaded from any site other than mine (prebuilt layouts load theirs from layouts.siteorigin.com and demo.siteorigin.com).
4. If the page is published and has a classic layout, fetch it with get_page_html, selector #pl-PAGE_ID and max_length 20000, and check the layout as visitors see it for: links with an empty destination or just #, filler text, and level-one headings. Do not report slider controls (links inside sow-slider-pagination or sow-slide-nav) or other widget controls that use # by design. Draft, pending, private and scheduled pages and Layout Blocks get step 3 only; say which.
5. Before moving to the next page, write down that page's findings in a few lines, and work from those notes from then on.
6. Give me one table with the page, the row label (each row in the layout's grids list may have a label), the widget, the problem and the exact text or link, with the pages that have the most problems first, and a suggested fix for each. Tell me once that many themes print the page title as a level-one heading above the layout, so a level-one heading inside the layout can make two. Then stop. Make no changes in this conversation.