AI visibility report
Checked Tue, 06 Oct 2026 17:22:54 GMT
49grade D
14 things hurting your AI visibility
llms.txt
No /llms.txt: the emerging standard map that tells LLMs and agents what your site is and where the key docs are.
→ Publish the generated llms.txt below at https://yoursite/llms.txt.
JSON-LD structured data
No schema.org JSON-LD found.
→ Add JSON-LD (generated below) so engines know your entity, product and pricing unambiguously.
Entity / product schema
No Organization / Product / SoftwareApplication schema.
→ Add Organization + Product/SoftwareApplication schema with name, url, logo, sameAs (socials), offers.
XML sitemap
No /sitemap.xml and none referenced in robots.txt.
→ Publish /sitemap.xml and reference it from robots.txt with `Sitemap: https://yoursite/sitemap.xml`.
Meta description
Missing. AI engines often quote this as your one-line summary.
→ Write a 50-160 char description stating exactly what the product does.
Scannable section headings
0 H2 headings. LLMs chunk pages by headings.
→ Break the page into H2 sections: what it is, how it works, pricing, FAQ.
Content visible without JavaScript
239 words of readable text in the raw HTML.
→ Server-render or pre-render key pages (Next.js/Astro SSG), and explain clearly what you do, who it's for and pricing in plain text.
Machine-usable interface (API / MCP)
No OpenAPI spec, MCP server or API docs discovered. AI agents can read about you but can't act (sign up, query, buy).
→ Expose an MCP server or OpenAPI spec and link it from llms.txt so agents can use your product, not just read about it.
Pricing is machine-readable
No pricing found. Agents comparing tools for users skip products without clear prices.
→ Add a plain-HTML /pricing page and `offers` in your JSON-LD.
Descriptive title tag
"About" (5 chars)
→ Use a 15-70 char title: `Product: what it does for whom`.
Docs / help content linked
No docs/help links. Agents rely on docs to answer how-to questions about you.
→ Publish public docs/how-to pages and link them from the homepage and llms.txt.
robots.txt present
No valid /robots.txt. Crawlers fall back to defaults.
→ Add a /robots.txt that explicitly welcomes AI search bots (see generated file below).
Question & answer content
No FAQ section found.
→ Add an FAQ answering the exact questions buyers ask ChatGPT ("best X for Y", "X vs Y", "how much does X cost").
Linked brand profiles
1 social/profile links. Corroborating profiles help AI trust and identify your brand.
→ Link your X, LinkedIn, GitHub, Product Hunt pages and list them in schema `sameAs`.
AI search & answer bots allowed
ChatGPT, Perplexity, Claude, Google and Bing can all read this page.
Page is indexable
No noindex directive.
AI training crawlers
Models can learn about your brand from your site.
Served over HTTPS
Secure connection.
Fast response
Homepage responded in 738 ms. AI fetchers often time out on slow pages.
One clear H1
1 H1: "Partnership on Generative AI for Humanitarian Applications"
Open Graph tags
og:title and og:image set.
Language declared
html lang attribute set.
Your free fix files
Generated from your homepage. Edit, then publish at your site root.
# About > About Key facts for AI assistants: who it's for, main use cases, pricing, and how to get started. ## Key pages - [Home](https://www.pgai.dev/) - [Pricing](https://www.pgai.dev/pricing) - [Docs](https://www.pgai.dev/docs) ## Optional - [Sitemap](https://www.pgai.dev/sitemap.xml)
This was just your homepage.
RankRoot Pro scans up to 50 pages and generates llms.txt, llms-full.txt and JSON-LD for every one of them.
Show your score
Add this badge to your README or footer. It updates automatically.
[](https://rankroot-ai.netlify.app/report?url=https%3A%2F%2Fpgai.dev%2F)
Share this report: rankroot-ai.netlify.app/report?url=https%3A%2F%2Fpgai.dev%2F
Scan another site
No signup. 20+ checks across ChatGPT, Perplexity, Claude, Google AI and AI agents.