Notes on building websites that work.
What we've learned building sites, apps and maps, written plainly, with the specifics left in. No listicles, no filler.
-
EngineeringHeadless CMS, explained without the jargon
What headless actually means, when separating your content from your website is worth the extra setup, and when a traditional CMS is the better buy.
-
Maps & dataLocal SEO when you have more than one location
How to structure location pages so each clinic, branch or store ranks in its own suburb, without creating thin duplicate pages that rank for nothing.
-
Search & AEOWhat belongs on a service page
The sections that make a service page rank and convert, in the order visitors actually read them, and how to write one that AI assistants will quote.
-
EngineeringMulti-language and multi-region websites
How to structure a site for more than one language or country, which URL pattern to pick, and the hreflang mistakes that quietly split your rankings.
-
DesignWebsite accessibility: where to start
What WCAG actually asks for, the handful of fixes that cover most of it, and why accessible websites tend to be faster and rank better too.
-
PlatformsDo you actually need a CMS?
When a content management system earns its place on a website, when it just adds cost and complexity, and how to pick one that your team will really use.
-
ProcessHow long does it take to build a website?
Realistic timelines for a custom website, what each stage involves, and the three things that decide whether you launch on time or three months late.
-
Search & AEOSchema markup: a plain guide for business websites
What structured data is, which types matter for most businesses, and how it helps search engines and AI answer engines understand your site.
-
Apps & AIPractical AI automations for small businesses
Useful, low-risk ways to add AI and automation to the tools you already run, with examples and what to watch out for.
-
Apps & AICustomer portals and dashboards: build or buy?
When an off-the-shelf tool is enough, when a custom portal or dashboard pays off, and what a custom build involves.
-
Maps & dataBuilding a store locator that also helps your SEO
Most store locators are invisible to search engines. Here is how to build one that helps customers find you on your site and in search.
-
Maps & dataMapbox vs Google Maps vs MapTiler
A practical comparison of the three map platforms we use most, covering design control, data, pricing models and which suits which project.
Updated
What does the Plyo blog cover?
The blog covers websites, migrations, design, search, interactive maps and web applications. Articles explain the practical decisions behind each topic.
Where should I start if I am moving a website?
Start with the migration articles on planning redirects, carrying content across and deciding which platform fits your site.
Where can I see Plyo’s approach on a real project?
The case studies show how Plyo’s founders approached design and engineering on individual projects.
Custom Astro websites. Built on Cloudflare.
Plyo Studio is an independent web studio that designs and builds fast, search-ready websites, web apps and interactive maps. Sites are custom-built in Astro and hosted on Cloudflare, so they load quickly and are easy for search engines and AI answer engines to read.
Founded by Chloe Nixon, a full stack developer and UI/UX designer from Australia, and Micky, a software engineer from New Zealand. Clients work directly with the founders from the first call to launch. Typical work: custom websites, migrations off Webflow, WordPress, Wix and Squarespace, web apps, and interactive maps and GIS. Projects are quoted at a fixed price before work starts.