Your buyer searches for a deadline before they search for a product
An HR manager at a 300-person company does not wake up wanting an HRMS. She wakes up because Form 16 has to go out, a PF challan is due, or finance has asked why the gratuity provision moved. That is the query she types. It has nothing to do with your product name and everything to do with whether she lands on your site or a competitor's.
This is the structural advantage HR tech has over most software categories. A page titled 'what is an HRMS' competes with fifty near-identical pages and attracts students. A page that explains the EPF contribution split correctly, with the arithmetic shown, attracts the person who eventually signs the invoice — and the payroll executive who tells her which tool to shortlist.
The statutory content layer, mapped
Four query families do most of the work. They aren't equal. Some bring HR ops, some bring finance, and some bring employees who will never buy anything — but who link, share, and get your page quoted in an AI answer about Indian payroll.
- Write for the person, not the persona. An employee searching 'how to withdraw PF online' is not your buyer, but they are the reason the page earns links. Serve them properly and your buyer-facing pages inherit the authority.
- Show the arithmetic. Every one of these queries has a number at the end of it. A page that explains the rule and refuses to run an example loses to the page that runs it.
- Put the effective date on the page, not in a schema field nobody reads. 'Rates as applicable from [date]' at the top costs a line and buys credibility with both readers and reviewers.
| Query family | Who is actually searching | What the page must contain |
|---|---|---|
| EPF and PF — rates, withdrawal, UAN, challan | HR ops and employees, in roughly equal measure | The 12% employee and 12% employer contribution, how the employer share splits between the pension and provident components, the ₹15,000 statutory wage ceiling, and a worked example in rupees. |
| ESI — eligibility, contribution, benefits | HR ops at companies sitting near the threshold | The ₹21,000 gross wage limit, the 0.75% employee and 3.25% employer split, which establishments are covered, and what happens when an employee crosses the limit mid-contribution-period. |
| Gratuity — eligibility, calculation, tax | Employees first, finance second | The five-year continuous service rule, the last-drawn-salary × 15/26 × years formula, the tax-exempt ceiling, and a calculator that runs the number for them. |
| Form 16, TDS and professional tax | HR in May, employees in June and July | Part A versus Part B, what to reconcile against Form 26AS and the AIS before filing, and the fact that professional tax is a state subject with different slabs and different due dates. |
Templates and calculators do the lead capture your blog can't
The best-performing asset in HR tech SEO is rarely an article. It's a thing the HR team downloads on a Tuesday because payroll runs on Wednesday: an offer letter format, a salary structure sheet, a full-and-final settlement template, a gratuity calculator, a CTC-to-in-hand breakdown.
These work for two reasons. They sit at the exact moment of need, and they are linkable in a way a 2,000-word guide isn't. Another HR blog will link to your gratuity calculator. Nobody links to your gratuity article.
- Don't gate the first interaction. An email wall on the calculator kills the links that make it rank. Capture on the result screen instead — 'email me this breakdown' converts better than a gate, because the person already has the value.
- Ship templates in the format they actually use. Excel and Google Sheets. Not a PDF of a screenshot of a spreadsheet.
- One page per template, never a downloads hub. A hub ranks for nothing. Fifteen separate pages rank for fifteen separate queries and carry fifteen separate sets of links.
- Instrument them. Track which downloads precede a demo request. You will usually find a short list of assets doing most of the pipeline work — find yours before you build the sixteenth.
Feature and integration pages that read like a product, not a brochure
Two page types carry the middle of an HR tech funnel, and both are usually written by whoever had capacity that sprint.
Feature pages
One page per module — payroll, attendance, leave, onboarding, performance, ATS — each written against the query patterns [module] software and [module] software for [segment].
The failure mode is six pages that are the same page with the module name swapped. If your leave management page could be turned into your attendance page with find and replace, Google is right to pick one and ignore the rest. That's keyword cannibalization with extra steps, and it's why your feature pages plateau.
Integration pages
Indian HR stacks are held together by accounting software and biometric devices. [your product] Tally integration, [your product] Zoho Books integration, [your product] biometric attendance integration — every pairing is a query with a buyer at the end of it who is already paying for one side of it.
A real page per integration — what syncs, what doesn't, how the field mapping works, what breaks at month-end close — is programmatic SEO nobody can call thin, because each page describes a genuinely different system. That's the distinction we've written about in where programmatic SEO crosses the scaled content line: templating is fine, publishing pages nobody would miss is not.
Comparison pages in a category where everyone claims full compliance
Every HRMS sold in India says it handles PF, ESI, professional tax and TDS. Buyers know that's the claim, and they search for the comparison anyway: X vs Y, X alternatives, best payroll software for startups. Somebody is going to own those pages. It may as well be the vendor telling the truth on them.
- Compare on the things that genuinely differ: how many states are supported for professional tax, whether challans are generated or merely calculated, multi-entity handling, how a mid-period ESI threshold change is treated, API limits, and what implementation actually costs on top of the licence.
- Name who should buy the other product. A comparison page that concedes nothing gets screenshotted in your competitor's sales channel and cited by nobody. A fair one gets linked, and increasingly gets quoted by AI assistants, which summarise pages that read as neutral.
- Keep the pricing rows current or delete them. A stale price on a comparison page is the fastest way to lose a deal you were winning.
- Don't compare against a product you've never run. It shows. In a category this small, the other vendor's team will point it out to your prospect.
SMB and enterprise are two keyword sets pretending to be one
A 40-person startup and a 4,000-person manufacturer both search 'HR software India'. Only one of them is your customer, and if you sell to both you need two page sets — not one page with a segment dropdown.
- Separate templates, separate internal linking, separate calls to action, separate reporting. Blending them produces pages that half-address both and convert neither.
- Report keyword → landing page → signup or demo → qualified. A report built on sessions tells you nothing here, because the enterprise set will always look like a rounding error on traffic and carry most of the revenue.
| SMB and startup | Enterprise | |
|---|---|---|
| Typical queries | payroll software for small business, free HR software India, best HRMS for startups | multi-state payroll compliance, HCM implementation, HRMS RFP checklist, [legacy system] alternative |
| What they want on the page | Price, setup time, whether it runs without a dedicated HR team | Security posture, data residency, integrations, references, implementation timeline |
| What converts | A self-serve trial or a 20-minute demo | A downloadable RFP template, a security page, and a named human who replies |
| How it breaks when merged | Enterprise language scares off a founder in month two | SMB pricing on the page ends the enterprise conversation before it starts |