Before I describe the communications strategy behind Heritage Guide, I want to be clear about something: this project is, first and foremost, an act of love for my country. I am deeply proud to be Canadian, and at a time when Canada faces real challenges to its national sovereignty, I believe preserving our stories matters more than ever. The places in the Canadian Register of Historic Places are not just buildings and landmarks — they are the physical record of who we are and where we came from. Letting that record disappear was not something I could stand by and watch.
Heritage Guide is a public service for Canadians. I built it because I love this country and because I wanted to give something back. The heritage preservation mission is what matters most to me personally — it is why I built the site in the first place and why I continue to maintain it.
That said, a public service that nobody can find is not much of a service. Building Heritage Guide in 24 hours made for a good story. But a good story that nobody hears is just a server running in a closet. The communications strategy behind Heritage Guide was as deliberate as the engineering — and it drew on the same combination of technology and political campaign thinking that defines everything I build.
The goal was straightforward: make Heritage Guide the default destination for anyone searching for Canadian heritage sites, and get the story in front of journalists who would understand why it mattered. The execution combined three things — search engine optimization at scale, AI-assisted journalist outreach, and the rapid-response campaign infrastructure of Shift Media.
SEO strategy for a 27,500-page heritage website#
Heritage Guide has over 27,500 pages — every heritage site in both English and French, plus city pages, topic pages, and static content. That scale is both an opportunity and a challenge for search engine optimization.
The opportunity is that each page targets a highly specific long-tail query. Someone searching for “Rideau Canal National Historic Site” or “site patrimonial Vieux-Québec” should land on a page that is purpose-built to answer that query — with the heritage value statement, character-defining elements, photographs, and geographic context that no other site assembles in one place.
The challenge is making sure Google actually indexes and ranks 27,500 pages on a brand-new domain with zero authority. Several decisions in the architecture were made specifically with this in mind.
Every page has a unique, descriptive title tag and meta description drawn from the heritage data itself. The URL structure uses human-readable slugs derived from the place name — clean, predictable, and keyword-rich. Bilingual pages are cross-linked with proper hreflang annotations so that Google understands the English and French versions are translations of each other rather than duplicate content. A comprehensive XML sitemap — actually multiple sitemaps, segmented by content type and language — was submitted to Google Search Console on launch day.
The prerendered static HTML architecture pays dividends here. Every page is a fully rendered HTML document that search engine crawlers can parse immediately — no JavaScript execution required, no client-side rendering delays, no hydration gaps. The Raspberry Pi serves these pages through nginx with minimal latency. Google’s crawlers see exactly what a human visitor sees, instantly.
City pages and topic pages serve a dual purpose: they are useful navigational tools for visitors, and they create internal linking structures that distribute page authority across the site. A city page for Halifax links to every designated heritage site in the city, and each of those site pages links back. The same pattern applies to building types, themes, and provinces. This internal linking web helps search engines understand the relationships in the dataset and gives every page multiple paths to discovery.
Within the first weeks, Google had indexed thousands of pages and Heritage Guide was appearing in search results for heritage site queries across Canada. For many specific site names, Heritage Guide now outranks the original Parks Canada pages — which, given that those pages are scheduled for deletion, is exactly the outcome the project needs.
AI-powered journalist outreach using geospatial data#
The Heritage Guide story had obvious news value — a national heritage database about to be deleted, rebuilt by one person in a weekend, running on a Raspberry Pi. But news value alone does not generate coverage. Journalists receive hundreds of pitches. The challenge is reaching the right reporters with a pitch that makes the story feel local and urgent to their audience.
Shift Media maintains a national database of thousands of regional outlets and reporters across Canada. The question was how to turn a national story into hundreds of local stories — and how to do it fast enough to ride the wave of attention from the Parks Canada shutdown announcement.
The answer was already sitting in Heritage Guide’s own infrastructure. The same MongoDB database that serves the site includes geospatial coordinates for every one of the 13,554 heritage sites. I built a process that used AI to cross-reference Shift Media’s reporter database against Heritage Guide’s geospatial data, identifying the closest nationally significant heritage sites to each reporter and outlet. A journalist in Halifax would receive a pitch anchored to specific Nova Scotia heritage sites that their readers would recognize. A reporter in Winnipeg would get a pitch referencing Manitoba landmarks. A French-language outlet in Quebec City would receive a pitch in French, built around the designated sites in their region.
AI then generated customized regional pitches for each reporter, weaving the local heritage sites into the broader national narrative — Parks Canada was about to delete the records for these specific places in your community, and Heritage Guide had preserved them. Each pitch was reviewed by the Shift Media team before deployment, but the heavy lifting of geolocation matching, site selection, and draft generation happened automatically. What would have taken a team days of manual research was completed in hours.
The conversion rate was striking. CBC published a full feature. Radio-Canada ran two separate pieces. The story was syndicated by Yahoo News Canada and picked up internationally. This was not a viral accident — it was a targeted outreach campaign that used Heritage Guide’s own data infrastructure to make every pitch feel like a local story, deployed at national scale by a team that knows how to run time-sensitive communications campaigns.
National campaign infrastructure with Shift Media#
The third element was Shift Media. Running a communications campaign for Heritage Guide was not fundamentally different from running a political rapid-response operation — you need to move fast, control the narrative, and put the right message in front of the right audience at the right time.
Shift Media provided the campaign infrastructure: the strategic communications planning, the media contact database, the distribution channels, and the experience of running time-sensitive public affairs campaigns. When the CBC first broke the story about the Parks Canada shutdown, the window for Heritage Guide to enter the conversation was narrow. Having a national campaign firm ready to execute meant the difference between being part of the story and being an afterthought.
The rollout was sequenced deliberately. The site launched first, quietly, to ensure everything worked. Then the outreach began — timed to coincide with the peak of public attention on the Parks Canada shutdown. The messaging was consistent across every touchpoint: this was not just a technology project, it was a statement about what one person with modern tools could accomplish versus what a federal department said was impossible.
Social media amplification followed the earned media coverage. Each article was shared with commentary that reinforced the core narrative. The LinkedIn announcement generated significant engagement from the heritage community, including from people who had been directly involved in the original Historic Places Initiative. This organic engagement from credible voices in the heritage space lent authority to the project that no amount of self-promotion could have achieved.
How SEO, media coverage, and campaign strategy compound#
These three elements — SEO, AI outreach, and campaign infrastructure — were not independent strategies. They compounded each other.
Media coverage drove backlinks, which accelerated SEO authority. SEO visibility drove organic traffic, which validated the project’s relevance to journalists considering follow-up coverage. The campaign framing shaped how journalists wrote about the project, which in turn shaped how the public understood it — not as a hobby project, but as a credible alternative to a government service.
This is the pattern I keep returning to in my work: technology and strategy are not separate disciplines. The best technical infrastructure in the world is useless if nobody knows it exists. The most brilliant communications strategy falls flat without a product that delivers on the promise. Heritage Guide worked because both sides were executed with the same level of intent.
The National Trust for Canada sounded the alarm about the shutdown. Heritage Guide provided the answer. And a deliberate communications strategy made sure the two were connected in the public conversation.
Heritage Guide is live at heritageguide.ca. For the story of why it exists, see Saving Canada’s Heritage Register. For the technical details, see Building Heritage Guide: A Technical Deep Dive.
