scanned Apr 28, 2026
pageai.pro
PageAI is an AI-powered website builder that generates production-ready websites from a single prompt.
Tier 3 · Agent-Accessible
Scored by asking 15 questions a buyer of a ai-ml product asks, then grading this site’s own pages: answered, hedged (partial or vague), or silent (no page answers it). How scoring works
15 buyer questions · graded against the site’s own pages
Goes silent · pricing · high importance
I'm comparing annual vs monthly billing — what's the exact percentage I save by paying yearly for the Pro plan?
Goes silent · pricing · high importance
If I subscribe and change my mind, how many days do I have to request a refund?
This report is public. Own pageai.pro? Claiming is free: crawl every page, re-audit as you fix, and track your score over time.
Sign in to claim58 points sit between pageai.pro and 100: 12 open questions and 4 missing protocol checks, ordered by estimated payoff.
Point estimates are per fix under scoring v2. They are not additive to a promised total.
I'm comparing annual vs monthly billing — what's the exact percentage I save by paying yearly for the Pro plan?
No page on the site addresses this.
Add detailed pricing information to the pricing page including plan tiers (Pro, etc.), monthly vs annual billing options, and exact percentage savings for annual payment.
confidence high · grounding world-knowledge · weight 0.00 · Absent
If I subscribe and change my mind, how many days do I have to request a refund?
No page on the site addresses this.
Add a refund policy FAQ to the Pricing page or create a dedicated refund/returns policy page. Common practice is to state the refund window (e.g., '14-day money-back guarantee') prominently on the pricing page.
confidence high · grounding world-knowledge · weight 0.00 · Absent
Can I use my own domain on the Starter plan, or is custom domain mapping locked to Pro only?
No page on the site addresses this.
Retrieve the actual pricing page content at https://pageai.pro/pricing or https://pageai.pro/docs/getting-started/pricing to determine plan-specific feature limits for custom domains.
confidence high · grounding world-knowledge · weight 0.00 · Absent
On the free tier, is there a hard cap on how many sites I can generate per month, or is it unlimited with slower speeds?
No page on the site addresses this.
Add a dedicated pricing or FAQ section that clearly explains free tier limits, including whether there is a hard cap on sites per month or if usage is unlimited with slower speeds.
confidence high · grounding world-knowledge · weight 0.00 · Absent
I'm building sites for clients — how many team members can access my account before I need to upgrade?
No page on the site addresses this.
Add a pricing or FAQ page that specifies team member limits per plan, or include collaboration/seats information in plan comparisons.
confidence high · grounding world-knowledge · weight 0.00 · Absent
I have an existing Lovable project — is there any automated import path or do I need to rebuild from scratch?
No page on the site addresses this.
Create a dedicated migration or 'Import from other platforms' documentation page that addresses common migration scenarios, including whether automated import from Lovable is supported and what manual steps are required if not.
confidence high · grounding world-knowledge · weight 0.00 · Absent
If I delete a generated site from my dashboard, how long does PageAI keep the source code on their servers?
No page on the site addresses this.
Add a data retention policy or FAQ entry explaining what happens when a user deletes a generated site from their dashboard, including how long source code is retained on PageAI servers and whether users can request permanent deletion.
confidence high · grounding world-knowledge · weight 0.00 · Absent
Is there a guaranteed response time for Pro plan support tickets, or is it just 'best effort'?
No page on the site addresses this.
Add a dedicated support/SLA page or pricing plan comparison table that specifies response time guarantees (or lack thereof) for each plan tier including Pro.
confidence high · grounding world-knowledge · weight 0.00 · Absent
The local dev server defaults to port 3000 — if that's taken, does it auto-increment or do I need to configure it manually?
No page on the site addresses this.
Add documentation about the default port (3000) and whether the dev server auto-increments if the port is taken, or how to manually configure an alternative port (e.g., via environment variable or CLI flag).
confidence high · grounding world-knowledge · weight 0.00 · Absent
A buyer gets something, then has to guess the rest. Expand any row for the evidence and the fix.
I need Google Analytics 4, not just Vercel or PostHog — does PageAI support gtag injection or do I need to manually edit the code?
PageAI's documentation explicitly covers setting up Vercel Analytics and PostHog Analytics (chunk [4], [1]), but does not mention Google Analytics 4 or gtag injection specifically. The site generates a Next.js codebase that you fully own and can deploy anywhere, so you would need to manually add GA4/gtag to the code yourself.
Create a dedicated documentation page for Google Analytics 4 setup (gtag.js or Google Tag Manager) similar to the existing PostHog and Vercel Analytics guides, or add GA4 as a third option in the Analytics section.
Where we looked: /docs/vibe-coding-with-pageai, /docs/vibe-coding-with-pageai, /docs/pageai-documentation
confidence medium · grounding synthesized · weight 0.65 · Page missing
The Cursor rules file that comes with my project — am I allowed to modify it, or will that break future AI edits?
The chunks describe what Cursor rules are and how they work, including a "Self-Improvement Rule" that explicitly encourages modifying rules as your codebase evolves. The Self-Improvement Rule states: "Modify Existing Rules When: Better examples exist in the codebase; Additional edge cases are discovered; Related rules have been updated; Implementation details have changed." However, the chunks do not explicitly address whether modifying the rules will break future AI edits or how the AI handles modified rules.
Add explicit guidance on whether users can safely modify the provided Cursor rules, and whether modifications persist across AI sessions or could cause conflicts with future AI-generated edits. A dedicated FAQ or note in the Self-Improvement Rule section would address this buyer concern directly.
Where we looked: /docs/pageai-cursor-rules-explained, /docs/pageai-cursor-rules-explained
confidence medium · grounding synthesized · weight 0.65 · Vague
For the metatags to actually help with SEO, does PageAI generate static HTML at build time or is everything client-side rendered?
PageAI generates Next.js codebases with 'dynamic meta tags for SEO' and 'article SSR with layouts, embed & SSR of media, code blocks etc.' The mention of SSR (Server-Side Rendering) suggests that meta tags are rendered server-side rather than purely client-side. However, the chunks do not explicitly state whether this results in static HTML at build time (SSG) versus runtime SSR, or how this specifically impacts SEO crawler visibility.
Add explicit documentation explaining whether metatags are statically generated at build time (SSG) or server-rendered per request, and clarify the SEO implications for search engine crawlers.
Where we looked: /docs/pageai-documentation
confidence medium · grounding synthesized · weight 0.65 · Vague
3 of 15. Answered with enough specificity for a buyer to act on. This is the bar the queue above is chasing.
When I generate a site, can I export it as plain HTML/CSS or only as a Next.js project?
PageAI generates a Next.js codebase, not plain HTML/CSS. When you download or deploy, you get "the entire codebase" which is a Next.js project with TypeScript, Tailwind CSS, and Shadcn UI. The chunks do not mention any plain HTML/CSS export option.
confidence high · grounding synthesized · weight 0.95 · Answered
I'm running Node 18 on my machine — will the local dev server work or do I need to upgrade?
You need to upgrade. PageAI officially supports Node.js 22.x and npm 10.x for running the local dev server. Node 18 is not listed as a supported version.
confidence high · grounding stated · weight 1.00 · Answered
When I create a custom MDX component for the blog, can I import external npm packages in it or only use built-in React?
Yes, you can import external npm packages in custom MDX components. The documentation shows an example of creating a donut chart component that imports from 'react-chartjs-2' and 'chart.js': `import { Doughnut } from 'react-chartjs-2'; import { Chart as ChartJS, ArcElement, Tooltip, Legend } from 'chart.js';`
confidence high · grounding stated · weight 1.00 · Answered
The other half of the score: 11 checks for the files and headers agents look for. The 4 below are installs, not judgment calls, and most are an afternoon. Expand any for the snippet and the standard it follows. They sit after the queue because none of them changes what your pages say.
User-agent: * Content-Signal: search=yes, ai-input=yes, ai-train=no Allow: /
StandardCloudflare proposalVendor proposal
StandardSitedex metricSitedex metric
StandardRFC 9110 + 7763IETF RFC
Sitedex generates this file from your crawl. Grab it in Files from this audit below.
StandardW3C WebMCP draftW3C / WHATWG
Already passing 7 of 11: robots.txt, sitemap.xml, llms.txt, AI crawler access, Server-rendered content, MCP card, OpenAPI spec.
Sitedex already serves pageai.pro as an MCP endpoint. Ask pageai.pro anything an AI agent might ask, and see what its index returns. (To score your own site, use the form below.)
For developers and the engineer-on-call: copy these into your tools or your site.
Files from this audit
Built from this crawl. Download or copy each, then install it at the path noted.
Built from this crawl. Install at /llms.txt so agents start here.
Organization JSON-LD, pre-filled from this crawl. Wrap in a ld+json script.
MCP server card built from this crawl. Host at /.well-known/mcp/server-card.json.
WebMCP discovery manifest built from this crawl. Host at /.well-known/webmcp.json.
MCP endpoint
https://mcp.sitedex.dev/s/pageai-pro/mcp
The URL anyone's agent points at. Read-only; safe to share.
Claude Code
claude mcp add pageai --transport http https://mcp.sitedex.dev/s/pageai-pro/mcp
One command, then the agent has it.
Cursor / Continue
{
"mcpServers": {
"pageai": {
"url": "https://mcp.sitedex.dev/s/pageai-pro/mcp"
}
}
}Drop into mcp.json.
WebMCP: two parts
WebMCP-capable browsers run the widget at runtime. Crawlers without JS rendering need the discovery manifest to find your tool surface. Install both.
1 · Widget script
<script async src="https://sitedex.dev/widget.js"></script>
Drop in <head>. WebMCP-capable browsers (Chrome 146+ Origin Trial) call navigator.modelContext.provideContext() via this script.
2 · Discovery manifest
{
"$schema": "https://wellknownmcp.org/schemas/webmcp.json",
"name": "pageai.pro",
"tools": [
{ "name": "search", "description": "Search pageai.pro's indexed content." },
{ "name": "get_page", "description": "Fetch a page from pageai.pro as markdown." }
]
}Host alongside the script at /.well-known/webmcp.json. Crawlers that don't render JS rely on this.
Your turn
See which of these questions your site goes silent on.
Free, about 5 minutes. We crawl your site, test it against the buyer questions your category asks, and name what’s vague, contradictory, or missing, plus the files AI agents look for.