Changelog
What we've been shipping
A running log of launches, improvements, and fixes.
Global Geo SEO + Industry vertical pages
- ·Launched 108 city-specific landing pages across 10 regions
- ·Added 23 industry vertical pages with vertical-specific content + schema
- ·Programmatic SEO infrastructure now unlocks ~900+ indexable URLs
- ·New /locations directory with search + region grouping
10 Hire-X landing pages + 12 platform comparisons
- ·Dedicated landing pages for hiring Shopify, WordPress, React, full-stack, SEO, email, app, SaaS, automation & GHL talent
- ·BOFU comparison pages: Shopify vs WooCommerce, Klaviyo vs Mailchimp, WordPress vs Webflow, and 9 more
- ·Searchable, category-filtered /compare hub
Resource hub: 10 guides + 4 interactive calculators
- ·10 long-form playbooks on Shopify, SEO, email, SaaS, security, and pricing
- ·4 free calculators: Shopify revenue, SEO traffic value, email ROI, hourly vs monthly hire
- ·8 gated agency templates available on request
Schema, sitemap, and SEO infrastructure overhaul
- ·Fixed Google Search Console "multiple aggregate ratings" error
- ·Refreshed sitemap.xml with 167+ active URLs
- ·Added FAQ + breadcrumb schema to all dynamic templates
- ·Stable @id linking across schema entities
93 sub-service detail pages unlocked
- ·Each of our 9 core services now exposes 8-13 sub-service pages
- ·SubServiceDetail dynamic route auto-generates SEO-rich content per slug
- ·Internal linking refreshed across all service hubs
Helper pages: FAQ, Book a Call, Guarantee, Careers, Industries
- ·/faq, /book-a-call, /guarantee, /careers, /thank-you, /resources all live
- ·Navbar restructured: Resources + Company dropdowns + top-level Locations
- ·Footer attribution: "Created by Livin Services"
Blog post routing fix
- ·Resolved 404 on individual blog posts (post.slug → post.id mapping)
- ·FeaturedBlogPosts component now correctly links to live posts
- ·Sitemap now uses real blog post IDs
Server-side hardening + .htaccess
- ·Force-HTTPS, SPA fallback, gzip, browser caching, security headers
- ·301 redirects for deleted services
- ·PWA manifest, browserconfig, humans.txt, security.txt all shipped
Site relaunch on React + TypeScript + Tailwind
- ·Full rebuild on a modern React stack with route-level code splitting
- ·New dark theme, Framer Motion micro-interactions, accessibility pass
- ·9 service hubs, case studies, blog, and resource center scaffolded
Subscribe to Updates
Get notified when we launch new services, update our processes, or release new tools. No spam, just the changelog.
Questions about this changelog
Including whether a change here affects a project already under way. It does not.
What is this changelog actually a log of?
Changes to how we work and what we offer — new services, revised process, corrections to published information. It is not a log of client projects, which are private, and it is not a product release feed, because we are an agency rather than a SaaS.
Do your prices change, and would that show up here?
We do not publish prices for project work, so there is no price list to change. What can change is how we quote, and that would appear here — as would any change to the guarantee or the refund policy.
Does a change here affect our existing project?
No. Your scope document and the terms in force when you signed govern your project. Changes to how we work apply to new engagements, and if something genuinely needs to change mid-project we will ask you rather than announce it here.
Why does an agency publish a changelog at all?
Because our terms, our guarantee and our published process are things you may rely on when deciding to work with us. If we change one of them, you should be able to see that it changed rather than discover a different version later.
Do you log corrections as well as additions?
Yes, and those are the entries worth reading. When we find that something published on this site was wrong — an unverifiable figure, a claim that contradicted our own policy — we remove it and record that we did, rather than quietly editing the page.
How often is it updated?
Whenever something changes that affects clients. There is no schedule, because a changelog padded to hit a weekly cadence stops being a record and becomes marketing.
Can we request a change or a new service?
Yes, and several entries here started as a client asking for something we did not formally offer. Message us. If enough people need the same thing, it becomes a service rather than a favour.
How do we get notified about changes?
Subscribe on this page, or watch the RSS feed. We will not use the list for anything else, and it is one email when something meaningful changes rather than a newsletter.
Is this the same as a status page?
No. This records deliberate changes to what we offer. The status page covers uptime and incidents — things going wrong rather than things being changed on purpose.
Do you ever remove entries?
No. A changelog you can edit backwards is not a record. If an entry itself was wrong, we add a correction rather than delete the original.
Where do I find the current terms rather than the history?
The Terms of Service, Refund Policy and Guarantee pages always show the version in force now, each with its own last-updated date. This page tells you what moved and when.
What if a change here contradicts something on another page?
Tell us, because that is a bug rather than fine print. The whole point of publishing all of this is that the documents agree with each other, and we would rather hear about it than have a client find it during a dispute.
Not the question you had? Send it to us on WhatsApp or email it. We answer in writing — no call required, and no obligation.
Product communication & changelogs
How we run a public changelog, versioning, sunsets, and release comms that earn customer trust.
Changelog Categories We Use: New, Improved, Fixed, Deprecated, Security
The five changelog categories we use across every product — what goes in each, why it matters for scannability, and the order that works best.
RSS for Changelogs: The Quiet Distribution Channel Most Teams Ignore
Why we ship an RSS feed for every changelog — and the underestimated audiences (power users, sales engineers, integrators) who quietly rely on it.
Killing Features: How We Announce Sunsets Without Losing Customers
Our playbook for announcing feature sunsets — timing, comms cadence, migration support, and the rare cases where reversal is justified.
Versioning Without Pain: SemVer, CalVer, or Just Date-Based?
A practical look at SemVer, CalVer, and date-based versioning — when each fits, and what we recommend for SaaS, agencies, and internal tools.
How to Write a Changelog Entry Sales Can Actually Use
A copy framework for changelog entries that sales can paste into deals — outcome line, technical line, link line, plus the talk track behind each.
The Tooling Stack We Use to Maintain Our Public Changelog
The exact tooling — GitHub PR labels, automation, copy review, deploy hooks — that keeps our public changelog accurate without slowing engineers down.
Ready when you are
Tell us the goal in one sentence.
You get a written scope, one fixed price and a start date back — usually within two business days. No form to complete first, and no call to sit through before you know anything.
- We usually reply within a couple of hours in working time.
- No discovery fee, no deposit to hold a slot, and no retainer attached to a build.
- We write the scope down and attach one fixed price to it, before any work starts.