Persqo inside your Base44 app's admin. One prompt to set it up.

Add a Persqo admin page to this Base44 app. Persqo tests my live site your-app.example like a real visitor and shows the results, fix prompts and AI search (GEO) checks in a dashboard. You will not rebuild that dashboard: Persqo serves it, and this app only frames it for admins.

Persqo project: prj_YOUR_PROJECT
Persqo site: env_YOUR_SITE (https://your-app.example)

1. The API key, server side only
Ask me for a secret named PERSQO_API_KEY with the secure secret input (or tell me to add it in the app's settings under Secrets). I will paste a Persqo API key there. Never ask me to paste the key into chat or code, and never put it in a page, a component, an entity or any frontend file.

2. The server code
Create a backend function named persqoEmbed. In its handler (not at the top of the file):
1. Create the client with createClientFromRequest(req) from "npm:@base44/sdk" and get the user with await base44.auth.me(). If there is no user, return 401. If user.role is not "admin", return 403.
2. Read the key with secrets.get("PERSQO_API_KEY") from "base44:runtime" (if this app's functions use Deno.env.get instead, use Deno.env.get("PERSQO_API_KEY")). If it is missing, return 500 with the message "Add the PERSQO_API_KEY secret".
3. Call Persqo with fetch:
POST https://persqo.com/api/v1/embed/sessions
Headers: Authorization: Bearer <the PERSQO_API_KEY secret>, Content-Type: application/json
Body: {"site_id": "env_YOUR_SITE", "platform": "base44"}
Answer (201): {"url": "...", "expires_at": "...", "verified": true or false, ...}
4. Return only {"url": <the url from the answer>} to the page. Never return or log the key. If Persqo answers with an error, return its status and its error.message.

3. The admin page
Create an admin page named "Persqo" at the route /admin/persqo and add it to the admin navigation if the app has one.
Each time the page opens, call base44.functions.invoke("persqoEmbed", {}) and put the returned url in an iframe: width 100%, height calc(100vh - the header height), no border, title "Persqo", allow="clipboard-write". Do not cache or store the url: it works once and only for five minutes, so a reload asks for a new one. Show a short loading line while it loads, and the error message with a Try again button if the call fails.

4. Who can open it
Only admins may see the page: hide it from the navigation for other users and show "Admins only" if a non-admin opens the route. The backend function's role check is what really protects it. If this app has no sign-in at all, turn on Base44's login for this page and make me the admin.

5. Site verification
Add this tag inside <head> of index.html (or the root layout's head), as it is served, not added later by a script, so Persqo can verify that I own the site:
<meta name="persqo-verification" content="YOUR_VERIFICATION_TOKEN">
If Base44 cannot edit the head, tell me, and I will add a DNS TXT record on your-app.example with the value persqo-verify=YOUR_VERIFICATION_TOKEN instead. Persqo frames its dashboard only on my verified domains and on Base44's own preview hosts, so publish the change before opening the page on my own domain.

When you are done, tell me which files and functions you added, where the page is, and the name of the secret to fill in. If this project syncs with a GitHub repository, also tell me its name, so I can connect it in the Persqo page and get pull requests for file fixes. Do not add anything else to the public site.

Yours has your own project and verification token, and never your API key.