Your robots.txt names GPTBot, ClaudeBot, PerplexityBot and six other AI crawlers "so they are never blocked by accident". But the homepage, pricing, results, feature and partner pages arrive as a 5.8 KB shell that says "You need to enable JavaScript" and "Loading...". AI crawlers and link previews do not run your app, so they get the title and nothing else: no plans, no testimonials, no FAQ. The same app-first build is why phones wait 16 seconds for the hero in Google's test, and real visitors fail Core Web Vitals with an 8.2-second largest paint.
First action
Fetch commenter.ai with JavaScript off and list what is missing.
How to measure it
Homepage-to-register rate on phones
- Now
- –
- Target
- +30%
- By
- 60 days
Steps
Audit
Fetch the six routes without JavaScript and record what a crawler sees.
Co-founder & CTO 1 hour
Choose the method
Build-time prerender of public routes, or move them into WordPress.
Co-founder & CTO 1 day
Ship pricing first
Plans, limits and FAQ in plain HTML.
Co-founder & CTO 3 days
Ship the rest
Home, results, feature, about and partner pages.
Co-founder & CTO 1 week
Add structured data
FAQPage and SoftwareApplication with price and rating.
Growth Lead 1 day
Defer the app
Load the app bundle and chat only after first paint.
Co-founder & CTO 2 days
Track AI answers
Weekly prompts to ChatGPT, Claude and Perplexity; log citations.
Growth Lead weekly
Why it works
Prerender the six public routes to static HTML at build time (or move them to the same WordPress that already serves the blog), keeping the app for logged-in paths. Put the hero, plan table, FAQ and three testimonials in the HTML itself, add FAQ and SoftwareApplication structured data, and load the app bundle only after the page is visible. Then ask ChatGPT, Claude and Perplexity "best AI LinkedIn comment tool" weekly and log whether Commenter AI is cited.
A growth hire will spend on content, partners and ads; all of it lands on these pages. Making them readable to answer engines and fast on phones raises every channel at once, and it is a one-off engineering job.
Ready to use
ChecklistPublic pages, crawler-ready
[ ] / renders hero, proof and CTA without JavaScript [ ] /pricing renders both plans, limits and FAQ [ ] /results renders before/after examples [ ] /feature and /become-a-partner render full copy [ ] FAQPage + SoftwareApplication JSON-LD [ ] App bundle and chat load after first paint [ ] Social share image and favicon on every page
Risks and how to handle them
Two versions drift apart
Generate the static HTML from the same components at build time.
Rankings dip during the switch
Keep URLs, titles and canonicals identical.
Evidence
- Your websiterobots.txt (checked November 4, 2026) names GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Perplexity-User, Google-Extended and CCBot with the comment "AI crawlers are named explicitly so they are never blocked by accident", and allows them everywhere except the logged-in app paths.Source
- Your websiteThe HTML served for the homepage, /pricing, /about, /results, /feature and /become-a-partner is about 5.8 KB each: a per-page title, description and canonical tag, then "You need to enable JavaScript to run this app" and a "Loading..." splash. The pitch, plans, testimonials and FAQ only appear after the JavaScript app runs.Source
- Google PageSpeedHomepage on a phone scores 10/100 (desktop 25): the main content (the hero "Turn Comments and DMs Into Opportunities with AI") appears after 16.0 seconds in the lab test, layout shift is 0.82 (the footer disclaimer moves), 1,065 ms of blocking time, 8.4 MB in 142 requests with 5.7 MB of images and 23 third-party services. Real Chrome visitors fail Core Web Vitals: largest paint 8.2 seconds and layout shift 0.17 at the 75th percentile, interaction 443 ms. Biggest savings: unused JavaScript (about 3.0 s), cache lifetimes (about 2.1 s), render-blocking requests (about 1.1 s).Source
- Your websiteSitemap lists 10 app pages (home, pricing, register, partner, about, feature, results, contact, privacy, terms), all last modified October 2, 2026; there are no comparison, use-case or integration pages outside the blog. The homepage shows 27 logos and a testimonial carousel; the about page lists a co-founder and CTO.Source