Verse is hiring a Director of Enterprise Payor Growth to build brand recognition with health plans, and it already has Payor Network and Payor Case Management pages. But every URL on versemedical.com returns the same empty page titled "Verse Medical" until JavaScript runs: search engines, AI assistants and link previews see one identical page, /robots.txt and /sitemap.xml return that page too, and made-up URLs answer 200. A health plan executive who searches for Verse and DME savings may never find the payor page.
First action
Publish a real robots.txt and sitemap.xml today.
How to measure it
Public pages indexed with unique titles
- Now
- –
- Target
- All 8
- By
- 30 days
Steps
List public pages
Home, providers, payor network, case management, about, contact, careers.
Marketing 1 day
Write titles
A title and description per page.
Marketing 1 day
Prerender
Static HTML for public routes at build time.
Engineering 1 week
Robots and sitemap
Real files, blog included.
Engineering 1 day
Proper 404s
Unknown URLs return 404.
Engineering 1 day
Share images
PNG per page.
Product Designer 2 days
Submit
Sitemap in Search Console.
Marketing 1 hour
Monitor
Indexing and search queries for payor terms.
Marketing weekly
Why it works
Prerender the public pages (home, providers, both payor pages, about, contact) to static HTML with their own titles, descriptions and headings; publish a real robots.txt and an XML sitemap that includes the blog; return 404 for unknown URLs; and add a PNG share image per page. Then check indexing in Search Console.
The payor pages start appearing for health plan searches and look right when sellers share them, at almost no cost.
Ready to use
ChecklistPublic site visibility
[ ] robots.txt served as text, app paths disallowed [ ] sitemap.xml with public pages and blog posts [ ] Unique <title> and description per public page [ ] Page content present in the HTML before JavaScript [ ] 404 status for unknown URLs [ ] PNG og:image per page [ ] Sitemap submitted in Search Console
Risks and how to handle them
Prerendered and live content drift apart
Generate both from the same source at build time.
Logged-in routes indexed by mistake
Disallow app paths in robots.txt.
Evidence
- Your websiteChecked October 22, 2026: every versemedical.com URL, including /payor-network and /for-providers, returns the same HTML with the title "Verse Medical", the same description and an empty page body until JavaScript runs. /robots.txt and /sitemap.xml return that same page instead of a robots file and a sitemap, and made-up URLs return status 200. The share image (og:image) is an SVG file.Source
- HiringDirector of Enterprise Payor Growth (remote, posted October 16, 2026): "We've established our business with a strong footprint in the Provider vertical. Now we are excited to be further expanding by deepening our Health Plan business"; closes "complex 6-18 month sales cycles" with national and regional health plans; will "Collaborate with marketing on positioning and materials development ... as we continue to grow our brand recognition in this new vertical" and "Turn what you learn into a repeatable playbook".Source
- Your websitePayor Network & Contracting page copy: "10-20% savings on DME", "Comprehensive service in 49 states and DC", "Delighted members and prescribers", "Payors manage hundreds to thousands of DME contracts", "Delayed deliveries lead to grievances and high-cost care"; the Payor Case Management page: "With Verse, case managers eliminate back and forth & maintain order visibility through delivery to the member."Source
- Google PageSpeedMobile performance score 40 (desktop 37); lab largest contentful paint 22.0 s on mobile and 3.0 s on desktop. Real Chrome visitors fail Core Web Vitals: LCP 4.7 s, interaction to next paint 315 ms, layout shift 0.24 for the homepage; site-wide LCP 6.1 s and 19% slower than the previous period. The page loads two JavaScript files of about 2.5 MB and 2.7 MB that also hold the logged-in ordering app.Source