Every potential.com page arrives as an empty JavaScript shell with only a title and a description. Google can render it, slowly, but tools that read the HTML directly, including many AI assistants' crawlers, see a blank page, and link previews on LinkedIn and WhatsApp show no image. For a company selling to ministries and enterprises that research on AI assistants and share links internally, the case studies and proof are invisible.
First action
Fetch the homepage without JavaScript and record what a crawler sees.
How to measure it
Key pages pre-rendered
- Now
- –
- Target
- 100%
- By
- 30 days
Steps
Baseline
Plain HTML fetch of the top 20 pages.
Head of engineering 1 hour
Choose approach
Static build per route or a pre-render service.
Head of engineering 2 days
Render
Home, platform, solutions, case studies, Ayla, partner.
Head of engineering 1 week
Share images
One per page.
Head of Marketing 2 days
Structured data
Organization and case studies.
Head of engineering 1 day
Verify
HTML fetch, LinkedIn inspector, Search Console.
Head of engineering 1 day
Monitor
Indexed pages and AI-assistant answers for "Potential.com".
Head of Marketing monthly
Why it works
Add pre-rendering or server-side rendering (for example a static build of each route, or a pre-render service) so each page's text is in the HTML. Give every page its own share image, title and description, add Organization and case-study structured data, and check the result with a plain HTML fetch and LinkedIn's post inspector.
Content that can be read is content that can be cited; it costs nothing per visit and helps every channel at once.
Ready to use
ChecklistReadable-site check
[ ] Page text present in raw HTML (curl test) [ ] Unique title and description per route [ ] og:image per page, checked in LinkedIn post inspector [ ] Organization structured data [ ] Case-study pages with structured data [ ] Sitemap lists only live, readable pages [ ] Search Console coverage checked [ ] Ask three AI assistants "What is Potential.com?" monthly
Risks and how to handle them
Rendering differs from the live page
Test pages side by side before switching.
Articles are many
Start with the 20 commercial pages, then articles.
Evidence
- Your websiteHow the site is built: every page is delivered as an empty JavaScript shell (<div id="root"></div>) with only a title and description in the HTML, so anything that does not run JavaScript sees no page text; the homepage has no social share image; the viewport sets "maximum-scale=1", which blocks pinch-zoom; the production page loads Replit's development banner script ("adds a banner on the top of the page when opened in development mode") and a Google AdSense ad script.Source
- Your websiteSitemap (540 URLs): 480 /articles, the newest dated March 31, 2026 ("Resilience During War"); most 2025 articles are about AI voice agents ("AI Voice Agents vs IVR", "8 Common Myths About AI Voice Agents", "AI Voice Agents for Small Businesses") or general topics ("8 Proven Strategies for Successful Direct Mail Advertising"); 40 blog category pages, about a dozen of them Arabic, though there is no Arabic version of the site. Case examples on the site also include "Email campaign promoting the BMW 5 Series Special Offer" and "A 360° campaign for Office 365 reaching SMEs across the UAE".Source
- Your websiteProof points on the site: "20+ Years of Delivered Initiatives"; "Proven programs implemented in 80+ countries"; "Over two decades, Potential.com has worked alongside Fortune 500 companies, global governments, and impactful organizations"; programme figures such as "3,000+ women trained", "5,000+ Entrepreneurs engaged", "250+ Idea prototypes developed", "20+ regional partners onboarded". 38 client logos, including ADGM, Cartier Women Initiative, Cisco, DCT, EDB, Google and the Government of Dubai.Source