For government

Municipal, provincial and federal program teams who need the official page to rank

Glass forms on a pale studio surface, standing in for clear public-sector information.
The official source should be the one people find.

When a resident searches a program, they should land on your page, not a third-party summary of it.



Government sites lose in search for a boring reason: the real answer is trapped in a PDF, a news release, or a page that was never given a title a human would type. Directories and media then rank for the program you actually run.

We work with comms directors, program managers and digital teams. The job is to make the official page unambiguous to Google and to AI assistants: clear titles, bilingual keyword research that is not a translation, structured data, and an information architecture that can survive a CMS you do not fully control.

If search is not the constraint, we will say so in the first email. Accessibility debt, a broken CMS, or a PDF library is a different project, and it should not be billed as SEO.

The services that usually move first for public-sector teams:

Bring the program page that should be ranking.

An email from your comms or digital lead is enough to tell you what is actually in the way.

Let's talk

Frequently asked questions

Can a government program actually outrank a directory or news site?

Yes, for the queries that describe a specific program, a city, or an eligibility rule. Directories win generic national searches because of domain authority. They lose when someone searches the name of your benefit, your intake process, or your local office. That is the traffic that should land on the official page.

We publish in English and French. Does that change the work?

It is the work. Translated keywords are not the terms Francophone residents actually type. We run separate keyword and entity research for each language, then structure the French and English pages so neither is a thin copy of the other.

Our site is a CMS we do not control. Can you still help?

Most of our government work is written as tickets a departmental developer or vendor can ship: titles, schema, information architecture, PDF-to-HTML priorities. You do not need us inside the CMS if the people who are inside it have a clear spec.

Who should write?

The comms or digital lead who owns the site, plus anyone who will have to defend the work to a director. A first email is enough to tell you whether search is the lever, or whether the problem is actually IA, accessibility, or a PDF library that should never have been the source of truth.