AplyNow's 356 content pages are built well and served as full HTML. But the pages those pages sell to are not: the homepage, /pricing, /outplacement (for HR leaders), /agencies and /partner-program all reach a crawler as the same empty 6 KB shell, none is in the sitemap, and any made-up URL such as /careers returns that shell with a 200. Search engines and AI answers can read "How to become an Accountant" but not your prices, your 30-day interview guarantee or your outplacement offer, and an HR leader searching for outplacement in India cannot find the page built for them.
First action
Run curl on /pricing and confirm the plan names appear in the HTML.
How to measure it
Key pages indexed
- Now
- –
- Target
- 6 of 6
- By
- 30 days
Steps
List the pages
Homepage, pricing, outplacement, agencies, partner program, sprint.
Growth Lead 1 hour
Prerender
Move them into the static build or prerender at deploy.
Frontend Engineer 3 days
Write head tags
Own title, description, canonical and Open Graph per page.
Growth Lead 1 day
Add structured data
Offer on pricing, FAQ on the guarantee.
Frontend Engineer 1 day
Fix 404s
Unknown paths return 404; ad variants get noindex.
Frontend Engineer 2 hours
Update the sitemap
Add the six pages and resubmit.
Frontend Engineer 1 hour
Verify
URL inspection in Search Console and a link-preview test.
Growth Lead 1 day
Why it works
Render the homepage, /pricing, /outplacement, /agencies, /partner-program and /30-day-sprint as static pages in the same build that produces the guides (or prerender them), each with its own title, description, canonical and visible text. Add Product and Offer data to /pricing and FAQ data to the guarantee. Add them to the sitemap, return a real 404 for unknown paths, and keep the ad variants (/starter-999-monthly a to d) out of the index.
Your growth engine is content that sends readers to "See pricing" and "Try AplyNow free"; the pages at the end of that path should rank and be quotable too. This is a build change, not new writing.
Ready to use
ChecklistKey page check
[ ] curl shows the page text [ ] Own <title> and description [ ] Self-canonical [ ] In sitemap-0.xml [ ] Unknown paths return 404 [ ] Ad landing variants are noindex [ ] Link preview shows the right title
Risks and how to handle them
Prices drift between the app and the static page
Generate both from one price file.
Evidence
- Your websiteSitemap (356 URLs, checked November 4, 2026): 61 each of resume examples, cover-letter examples, interview questions and LinkedIn headline examples, 61 "how to become" career pages, 28 guides, 7 alternatives, 6 comparisons and 5 audience pages, all served as full HTML. It does not list /pricing, /outplacement, /agencies, /partner-program or /30-day-sprint. Those pages, and any made-up path such as /careers, return the same 6 KB JavaScript shell with status 200.Source
- Your websiteHomepage as rendered in a browser: H1 "Land 3× more interviews by reaching hiring managers directly"; "Your AI agent finds your best-matched roles, maps the hiring manager, recruiter, or referral to reach at each, then drafts a personal message from your own Gmail"; "Cancel anytime" and "30-day interview guarantee"; "We find your best-matched jobs across 30+ job boards & ATS" (LinkedIn, Indeed, Naukri, Greenhouse, Ashby and others). The raw HTML served before JavaScript runs contains only the title, description and an empty <div id="root"></div>.Source
- Your websiteB2B pages in the app: /outplacement, "For HR & People leaders", "Help your people land their next role", with a done-for-you AI job search for departing employees and notes on Section 37 deductibility and the Industrial Disputes Act; /agencies, "For career-service & staffing teams", "Run 5× more job-search clients", with a "Book a workflow audit" button and client-ready reports.Source
- Your websiteAudience pages such as "For freshers" sell "Find fresher friendly roles", "Reach the hiring manager", "Apply from your own Gmail" and "pricing in INR alongside USD", and end with "Try AplyNow free" and "See pricing". Six slugs in the career pages read "how-to-become-a-accountant", "-a-account-executive", "-a-administrative-assistant", "-a-electrical-engineer", "-a-executive-assistant" and "-a-operations-manager", while their titles correctly say "an Accountant".Source