Pocketpills is hiring a media buyer to scale six-figure monthly budgets at a target CPA. The free channel that should lower that blended CPA is held back by two small file problems: robots.txt blocks /_next, the folder that holds every script and stylesheet the Next.js site loads (66 of them on the homepage alone), and the sitemap robots.txt points to is written as a page list instead of a sitemap index, so the 9,500 drug, city and pharmacy pages behind it may only be found if someone submitted each file by hand.
First action
Change the robots.txt line and resubmit the sitemap index today.
How to measure it
Organic signups from drug and city pages
- Now
- –
- Target
- +20%
- By
- 90 days
Steps
Baseline
Indexed pages, impressions and clicks per sitemap section in Search Console.
SEO Lead 1 day
Fix robots.txt
Allow /_next/static; keep API and tracking paths blocked.
Web Engineering Lead 1 hour
Fix the index
Serve /sitemap/index.xml as a <sitemapindex> with lastmod dates.
Web Engineering Lead 2 hours
Resubmit
Submit the index and each child sitemap in Search Console and Bing.
SEO Lead 1 hour
Inspect pages
URL Inspection on 10 drug, city and consult pages: rendered HTML and screenshot.
SEO Lead 1 day
Track
Weekly indexed count and signups by section.
SEO Lead weekly
Report to growth
Organic signups next to paid CPA in the weekly growth review.
Head of Growth monthly
Why it works
Allow /_next/static in robots.txt (keep /ppapi and tracking paths blocked), rewrite /sitemap/index.xml as a <sitemapindex> that lists the seven sitemap files, and submit it in Search Console. Then check a few drug and city pages with URL Inspection to see the rendered page Google gets, and watch indexed pages and clicks by section for four weeks.
Google's own guidance warns that blocking CSS and JavaScript can stop it rendering and judging pages properly. Fixing a crawl blocker is the cheapest acquisition there is, and every extra organic signup makes the paid CPA target easier to hit.
Ready to use
ChecklistCrawl fix list
[ ] robots.txt: Allow: /_next/static/ and /_next/image [ ] Keep Disallow: /ppapi and /mixpanel/track [ ] /sitemap/index.xml served as <sitemapindex> [ ] lastmod on every child sitemap [ ] Resubmit in Search Console and Bing Webmaster Tools [ ] URL Inspection on 10 sample pages [ ] Weekly indexed count by section
Risks and how to handle them
Unblocking exposes API paths
Allow only /_next/static and /_next/image; keep everything else disallowed.
Thin pages get indexed too
Pair the fix with the city-page clean-up (idea 4).
Evidence
- Your websiterobots.txt (checked November 4, 2026) contains "Disallow: /_next" and points to one sitemap, /sitemap/index.xml. The site is built on Next.js, and the homepage HTML references 66 files under /_next/static, which holds the site's scripts and stylesheets.Source
- Your websiteThe file robots.txt names as the sitemap, /sitemap/index.xml, is written as an ordinary page list (<urlset>) whose seven entries are other sitemap files, not as a sitemap index (<sitemapindex>). The seven files hold 2,610 drug pages, 6,399 pharmacy-near-me pages, 504 city pages, 7 landing pages, 5 consult pages, 2 telehealth pages and 1 press page.Source
- HiringSenior Media Buyer (Growth & Performance), open on the Pocketpills job board: "lead our paid social and emerging channel strategy" across Meta and TikTok while testing AppLovin, Snap and Pinterest; "manage and scale six-figure monthly budgets" at "target CPA thresholds"; run a "Never-Ending" testing roadmap on "audiences, offers, landing pages, and creative formats"; understand MMM, MTA and incrementality testing.Source
- Google PageSpeed (Chrome UX Report)Real Chrome visitors to pocketpills.com pass Core Web Vitals: largest contentful paint 1,444 ms at the 75th percentile (31% faster than before), interaction to next paint 125 ms, layout shift 0.05.Source