How to Invoice as an SEO Specialist: Rates, Terms and Templates

SEO work spans technical fixes, content briefs, and ongoing measurement. Clients often misunderstand that results lag implementation—your invoice should tie fees to deliverables and time boxed work, not rankings, unless you have an explicit performance agreement (which most specialists avoid for good reason).

Separate one-off audits from monthly retainers, and call out tools or data purchases you pass through.

Good SEO invoices double as project documentation: they show what shipped in a period, which matters when developers, writers, and executives each remember the roadmap differently. Tie line items to tickets or briefs you can point to later.

Typical rates

Project pricing for audits, migrations, or content sprints; monthly retainers for ongoing optimization and reporting; hourly for advisory or training. Enterprise and e-commerce scopes command more than local SEO packages. Google’s Search Central documentation is a useful external reference when clients ask why certain technical tasks matter—use it to support scope, not as a promise of outcomes.

Link-building or content production outsourced to vendors should appear as its own lines or reimbursements with transparency.

Local packs, multi-language, and JavaScript-heavy stacks are not interchangeable effort—if you price differently by complexity, say so on the invoice (“technical remediation hours” vs “content production hours”).

Payment terms

50% upfront on large audits or migrations; monthly in advance for retainers is common. Net 14–30 may apply to established in-house marketing teams—get a purchase order reference on the invoice. For multi-month roadmaps, invoice per agreed phase so stalled clients do not leave you with unpaid deep work.

Document what happens if the client delays access (GA, GSC, CMS)—your contract clause can be noted on revised invoices when timelines slip.

If a client pauses retainer work but wants ad hoc fixes, switch to hourly or mini-project lines on the next invoice so scope does not silently shrink while expectations stay enterprise-sized.

What to include

Billing period or milestone name, hours or fixed deliverables (crawl fixes, schema tasks, briefs delivered), meetings if billable, tool fees, tax, total, due date. Our guide to writing an invoice covers numbering and business identifiers.

Add assumptions (e.g. “covers sites X and Y”) to prevent scope creep arguments later.

Reference what belongs on every invoice for tax IDs, addresses, and numbering—enterprise AP teams reject incomplete PDFs more often than you would expect.

Common mistakes

Selling “rankings” without defining leading indicators—invoice on work completed. Bundling disallowed link schemes into generic “SEO”—keep tactics ethical and describable. No change log for dev-heavy tickets—attach or summarize completed tasks. Retainers without meeting caps—unlimited calls erode margin.

Auto-charging after a client cancels without checking contract end dates creates bad will—align final invoices with termination notices.

Copying last month’s hours without narrative—stakeholders forget what shipped; a one-line summary per major deliverable prevents “what did we pay for?” churn.

Template link

Start from our SEO services invoice template for audit, retainer, and reporting line items.

Reuse the same section headers each cycle so finance recognizes the pattern; only the quantities and milestone names should change.

---

Join early access to standardize SEO invoices across clients.