Webhooks are quietly failing
Entry publishes stop firing the Netlify build, or ISR revalidation never runs, and no one notices for a week because the editor sees the entry go green inside Contentful.
Deliveries verified and alerted on
Working with Contentful?
Contentful is a strong CMS when the content model is deliberate and a painful one when it has been grown by five different agencies. Most of the trouble we see is in the shape of the entries, the branching between spaces, and webhooks that fire into endpoints nobody owns anymore. We fix the model first and everything else gets easier.
What it is
Contentful is a headless CMS founded in Berlin in 2013 by Sascha Konietzke and Paolo Negri. Instead of coupling content to a theme the way WordPress or Drupal do, it stores structured entries behind a REST and GraphQL API, and leaves the presentation to whichever front end you choose.
The platform is used heavily by enterprise marketing teams, large ecommerce sites and multi-brand publishers. It supports content types, references, assets, localisations, environments for staging content changes, and roles with fine-grained permissions. Pricing is plan-based with hard ceilings on API calls, records, locales, users and environments; overages are the single most common surprise on an invoice.
The honest version
No technology is all upside. This is where Contentful earns its place and where it tends to cause trouble.
Sound familiar?
The Contentful problems that bring people to us, and what you have once each one is fixed.
Entry publishes stop firing the Netlify build, or ISR revalidation never runs, and no one notices for a week because the editor sees the entry go green inside Contentful.
Deliveries verified and alerted on
Two editors on the same entry with no lock, or a script using the Management API without reading the current version first, writing over each other's changes.
Optimistic concurrency respected
A front end calling the Content Delivery API per page view without caching, or a GraphQL query without persisted operations fanning out across the site.
Traffic back inside the plan
Content types added by past agencies that nobody uses, fields renamed but never removed, and reference chains that reach five entries deep for no good reason.
Model tidy, documented and tested
Someone deleted the environment master was aliased to, or the alias was never updated after a migration, and production is serving stale content with no warning.
Aliases pointed at live environments
Images over the per-asset size limit, a storage integration that lost its credentials, or an upload from a browser blocked by a corporate proxy before it reaches Contentful.
Media pipeline back to green
A new embedded entry type that the renderer does not know about, or a custom mark removed from the schema while entries still reference it, crashing the build.
Renderer matches the content types
en-US falls back to en-GB which falls back to en-US, and a missing translation shows an empty string instead of a fallback value. Easy to miss until someone browses in the wrong region.
Fallback chain linear and tested
What we do
Call us for one broken webhook, or hand us the whole space.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Usually a receiver that returns 500 on one branch of its logic, a signing secret that drifted after a redeploy, or a firewall that started dropping Contentful's IP ranges. Contentful retries for a while and then gives up, and the editor never sees a warning. We instrument the receiver, verify signatures correctly, and alert on dropped deliveries.
Yes, and it is one of the most common jobs we are handed. We inventory every content type and field against real site usage, identify the unused and the duplicate, and script migrations with the Contentful CLI so the clean-up is reversible. The front end is tested against the new model before anything is published.
Almost always API call overages, either because the front end stopped caching, a new GraphQL query is fanning out per request, or a build is hitting the Management API in a loop. We open the usage dashboard with you, name the top ten offenders, and make the obvious changes before anyone talks about upgrading the plan.
Contentful fits large marketing teams who need roles, environments and enterprise contracts. Sanity fits developers who value the real-time editor and GROQ queries. Strapi fits teams who want to self-host and own the database. We will tell you which one matches your team before anything gets procured.
We define the content model in Contentful first, map WordPress post types, taxonomies and custom fields onto it, then import through the Management API in batches with the original IDs preserved. Media is moved into Contentful's asset library, and redirects from the old permalinks are generated so nothing on the public side drops out of search.
The quote is free and comes with no obligation. Send the space name and the problem, and we return a written plan with a price before any content is touched.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: