Media and publishing websites
Editorial sites live or die on three things. How fast a page paints. How well the archive is structured. Whether search engines can find the piece you published this morning. Volume turns every small mistake into an expensive one.
What is different here
Every sector claims to be a special case. These are the constraints that really change how the build gets done. Not a services list with a different noun bolted on the front.
Volume magnifies every decision
A structural mistake on a ten-page site is an annoyance. Across ten thousand articles it becomes a migration. Taxonomy and URL structure get decided before publishing starts.
Page speed is the business model
Editorial traffic arrives from search and social, on mobile, and leaves if the article does not paint quickly. Every script you add is a cost every single reader pays.
The archive has to stay findable
Categories, tags and internal linking decide whether a two-year-old piece still earns traffic or vanishes. Most publishing sites lose that fight quietly.
Editors publish, not developers
The publishing workflow has to be quick for people using it dozens of times a day. Friction there costs you more than any feature wins back.
Crawl budget runs out
At scale, search engines do not crawl everything you publish. Sitemaps, canonicals and pagination decide which pages get seen and which get skipped.
Migrations threaten rankings
Replatforming an archive without mapped redirects is how publishers lose years of search equity over a single weekend.
Work in this sector
Real projects rather than a claim of experience. Each one is live; partner work is credited to the studio it was delivered with.
Client project
AustRecipes (opens in a new tab)
An Australian recipes site on WordPress, with keyword research shaping how the content is organised.
Client project
TalesKids (opens in a new tab)
A children's story site on WordPress, with keyword research behind how the content is organised.
Partner project with Youniwemi
Hespress (opens in a new tab)
Web integration for a high-volume news publisher, plus support on the interface design.
Partner project with Youniwemi
Hesport
Web integration for a sports news publisher.
Partner project with Youniwemi
Goud.ma (opens in a new tab)
Interface design and web integration for a news publisher.
What we build most often
The work that comes up repeatedly in this sector. Anything outside it is named in the written scope before the build starts.
Editorial builds and integration
Templates and front-end integration for publishing teams, including work alongside an existing platform and in-house staff.
Content structure and taxonomy
Categories, tags and URL patterns that keep an archive navigable as it grows.
Technical SEO at scale
Crawlability, canonicals, pagination, structured data and sitemaps for sites with a lot of pages.
Performance on article pages
Core Web Vitals on the templates that carry your traffic, not just the home page.
The services behind it
Projects in this sector usually combine these. They are listed separately because the work is genuinely different, not because they are sold separately.
Web Development
Website creation and web development from a senior-led studio. WordPress, Next.js and Astro builds, with semantic markup, accessibility and performance handled while the site is being made.
SEO
SEO services from a senior-led studio: keyword research, technical and on-page SEO, structured data and Core Web Vitals, plus the off-page work that builds authority over time.
UI/UX Design
Web design and UI/UX for websites, dashboards and mobile apps. Delivered as a design system of tokens and components, built on real content and accessible from the start.
Media & Publishing questions
The questions that come up before this kind of project starts. If yours is not here, ask it on a first call.
Can you work alongside our in-house team?
Yes, and that is how the publishing work here has usually run. On Hespress, Hesport and Goud.ma the job was web integration and interface work, delivered in partnership with Youniwemi. We fitted into an existing team and platform instead of replacing either.
Our archive gets no traffic. Can that be fixed?
Often, and usually without writing anything new. Older articles stop earning because they are orphaned, badly categorised, slow, or competing with each other for the same search. It is an audit question first. The fix turns out to be structural far more often than people expect.
We are replatforming. How do we not lose rankings?
Redirect mapping, done before the move and not after it. Every existing URL needs a destination. The old sitemap needs keeping so you can compare. The new structure needs settling before any content shifts. Migrations lose rankings when redirects become a launch-day chore.
How much does page speed really matter for articles?
For traffic arriving from search and social on mobile, it decides whether the reader ever sees the article at all. It feeds rankings too. The work itself is unglamorous: images, fonts, third-party scripts, the ad stack. Article templates are where it pays off, because that is where your traffic lands.
Another sector?
Building in this sector? Let’s scope it.
Tell us what the site has to do and what already exists. You get a straight answer on whether it is a fit, and a written scope before anything starts.
- Senior-led from first call to launch
- Written scope before any build starts
- Built to WCAG 2.2 AA and tested
- No quote until you are ready