A material study photographed in bright daylight. A wall of closely spaced clear turquoise glass fins sweeps around a vertical bend on the right of the frame, the near fins reading thick and deeply coloured and the far ones pale and clear, with a polished pearl silver ribbon rising through the bend. The left of the frame is empty pale mint.
  1. Home
  2. Services
  3. Websites and Platforms
  4. Content platforms

Part of Websites and Platforms

Content platformsand publishing systems.

A content platform is where the answers your team gives out loud live permanently, in a publishing system your marketing team runs without a developer. It is one of three services under Websites and Platforms.

A publishing system your team actually uses, and a structure that makes each new piece stronger than the last.

Book a discovery call Request a performance audit

Know what you are building? Book a discovery call. Not sure where the problem is? Request the audit.

HUREAL / Material studies

In your words

Soundslike this?

  1. We have a blog and the most recent post is from two years ago.

  2. Publishing one article takes three emails and a developer.

  3. Buyers research us for weeks before they call, and there is nothing on the site to research.

  4. Our specifications live in files nobody can search.

  5. We have hundreds of old posts and no idea which ones still earn anything.

  6. Our support team answers the same question so often they have a saved reply for it.

  7. We would like to be the answer an assistant gives, and there is nothing here worth quoting.

If the pages exist and the problem is that nothing links them together or ranks, the page for that is Search and AI Visibility.

In plain language

A place to publish,and a reason it keeps happening.

Most of what a buyer wants to know before they call is something your team already explains out loud. A content platform is where those answers live permanently: the guides, the specifications, the comparisons, the questions with real answers.

A blog is a habit. A content platform is a structure.

The publishing engine matters as much as the content. If a post takes three emails and a developer, nothing gets published. So the content model is built around your actual content types, with the approval flow your organization really uses, with previews, scheduling and roles.

Structure is the other half. Topics get proper homes with related pages around them, internal links follow the shape of the subject, and every answer is marked up so a search engine or an assistant can lift it cleanly. That is why the thirtieth piece is worth more than the first: it lands inside something.

When this is not the answer. If nothing is written down and nobody has writing in their job description, a publishing system is a machine with no fuel, and we will say so rather than sell it. The smaller honest project is the ten answers your sales team already gives, written once and structured properly on the site you have, which is Corporate and marketing websites.

The capability table

What a contentplatform includes.

Fourteen capabilities, what each one does in plain words, and what it changes for the business. The system is listed before the content, because the system is the reason the content keeps arriving.

Content platforms and publishing systems, the capability table
Capability What it does What it changes
The structureBefore anything is published
The question list What buyers ask, what your team answers repeatedly, and what the current site does not cover. The programme starts from demand rather than from a calendar.
Topic architecture Pillar pages, clusters, and the linking rules between them. Each new piece makes the pieces around it stronger.
A content model per type Guides, articles, specifications, cases, questions, glossary, documents, events, releases. A specification stops being a file and starts being a page.
Taxonomy and tagging A structure your team can maintain without breaking it. Filing stays consistent after the person who designed it leaves.
The publishing systemWhy it keeps happening
Editorial workflow Draft, review, approve, schedule, publish and expire, with the roles you already have. Publishing stops needing a developer.
Previews and scheduling See it before it goes, and set when it goes. A launch is a date rather than an evening.
Author profiles and revision history Who wrote it, when, and what has changed since. Readers and machines can both tell the page is maintained.
Media handling Images, diagrams, video and downloadable documents, under the same rules as everything else. A diagram is findable rather than buried in a file.
FindabilityFor people and for machines
Site search that understands intent People find the thing they meant rather than the words they happened to type. Fewer calls that start with saying it could not be found.
Structured data per content type Article, question and specification markup, authored with the page rather than added later. An assistant can use your answer as an answer.
Subscription and distribution Email capture, newsletter and syndication where it is relevant. A reader who is not ready still stays reachable.
Migration with redirects Old content audited, then kept, merged or redirected. Never deleted silently. You do not lose traffic you already had.
Reporting per piece Which pieces produce inquiries, not only which ones produce visits. The programme is judged on work rather than on volume.
A written editorial standard Written for the people who will use it after we leave. Quality survives a change of staff.

Scroll the table sideways to read it.

How it works

How a piece of writingturns into an inquiry.

The parent's drawing, read from the top left. On this service the first plate is not a landing page, it is a piece somebody published, and the report at the far right is what decides the next one.

Scroll the drawing sideways to read it.

The same seven steps, entered three weeks earlier. A reader who is researching is not a buyer yet, and the next step has to be sized for that.

What the system does

The work, the path it takes, and everything HUREAL builds. It never means anything else.

What stays with a person

The line, its single opening, and the plate standing in it. On a light board it is the one dark plate.

What you already run

Present, named, and not for sale. The lowest contrast on the board, deliberately.

  1. They arrive with a question, not a brand.

    Search, a referral and an assistant all lead to the piece that answers the question, which is almost never the home page. The piece is the front door, and the structure around it decides what gets read next.

  2. One piece, one job.

    A guide that tries to cover a whole category answers nothing precisely. A piece that answers one question well is the one an assistant can lift and the one a reader can act on.

  3. The next step is sized to a reader, not a buyer.

    A related guide, a specification, a comparison, or a subscription. Somebody three weeks from a decision is not filling in a contact form, and asking them to is how a content programme reports zero.

  4. The form is the small one.

    A download, a subscription or a question, with only the fields somebody downstream will actually use.

  5. The record says which piece did it.

    Source, owner and arrival time, with the piece attached. That is the whole reporting argument: a programme judged on inquiries per piece survives a budget conversation, and one judged on visits does not.

The structure is worth more than the first ten pieces. Work published into a structure compounds. Work published into a feed does not.

How this site publishes

The deliverables

What youend up with.

  • A publishing system your team uses

    Without asking anyone for help, with the roles and approvals you already have.

  • A topic architecture

    Pillars, clusters and the linking rules, as a document as well as a build.

  • The question list

    What buyers ask, ordered by how often, with the piece that answers each one.

  • Structured data per content type

    So a search engine or an assistant can use your answers as answers.

  • Site search that understands intent

    Tuned against real questions rather than left at a default.

  • The migration record

    Every old piece audited, what happened to it, and the redirect.

  • Reporting per piece

    Which pieces produce inquiries, not only which produce visits.

  • A written editorial standard

    So quality survives a change of staff.

What is not on this list. The writing, forever. We produce a first wave, enough to prove the structure works, and we build the system and the standard your team runs afterwards. Where you want us to keep producing, that is a run arrangement and it lives on Care and Optimization. The ranking work a content programme feeds is Search and AI Visibility.

By category

What a content platformconnects to.

By category, because the category is the question. A publishing system that cannot reach the place your specifications already live is a second place to keep them up to date.

  • Content management

    Where the model, the workflow and the roles live.

    headless platforms, WordPress, an in house CMS

  • Marketing automation and email

    Where a subscription becomes a sequence.

    Mailchimp, Klaviyo, HubSpot, Campaign Monitor

  • CRM

    Where a download becomes a record with a source and an owner.

    Salesforce, HubSpot, Zoho, Dynamics

  • Search and analytics

    Where a piece is measured against the question it was written for.

    Google Search Console, Google Analytics

  • Document and asset storage

    Where the specifications, drawings and certificates already live.

    SharePoint, Google Drive, Dropbox

  • Product and catalogue data

    Where a specification page gets its numbers, so two places cannot disagree.

    an ERP, a product information system, your own database

  • Support and knowledge tools

    Where your team's saved replies already are.

    Zendesk, Freshdesk, Intercom

Every connection is validated by HUREAL's engineers during scoping and confirmed in writing before signature. Where a system genuinely cannot be connected, you hear it during discovery rather than during the build, and the scope is drawn around it instead of making a platform migration the price of entry.

Asked and answered

Questions peopleactually ask.

  • How often do we have to publish?

    Less often than most people fear, and more regularly than most manage. A schedule you can hold beats a burst you cannot. We set a cadence with your team against the resources you actually have, and build the system so the cadence is achievable.

  • Can AI write the posts?

    It can do a great deal of the drafting, and we use it in our own publishing. What it cannot decide is what is worth publishing, what your company actually believes, and which specifics make a piece worth citing. The process is assisted drafting with a person accountable for every published word.

  • We have hundreds of old posts. What happens to them?

    They get audited. Some are updated and kept because they still earn visits, some are merged into stronger pages, and some are redirected. Nothing is deleted without a redirect, because deleting a page that ranks is the fastest way to lose traffic you already had.

  • Who owns the content model?

    You do, along with the code, the content and the data, in your own accounts. The model is documented and it is built on mainstream technology, so somebody who has never met us can maintain it.

  • Will an assistant quote us?

    It can only quote what it can read. Answers are written as answers, marked up per content type, and kept on pages rather than inside downloads, which is most of what makes a page liftable. What nobody can promise is that a given assistant will choose you on a given day.

  • How is this different from a blog?

    A blog is a list of posts in date order. A content platform is a structure: topics with homes, pieces that link along the shape of the subject, content types that are not all articles, and reporting per piece. The system is what makes the tenth piece cheaper than the first.

  • What does it cost?

    The build price is set after the discovery call and sent in a written proposal, because an honest number needs the scope, and here the scope is mostly how many content types you really have. The number is written into the signed scope and does not move once it is signed.

Three pages next to this one

Where thissits.

Close

Two ways to start.Both end with a document you own.

Book a discovery call

For when you know the site has to change and want the scope before the spend. A discovery call with the people who own the outcome. We agree the job, the audience, the decision path and how success is measured, and afterwards you get a written proposal with a scope, a price and a timeline you can sign or walk away from.

Book a discovery call

Request a performance audit

For when you want the evidence before the decision. We look at what you have against the job you want it to do, and give you a prioritised plan with the arithmetic attached. The document is yours either way.

Request a performance audit

Know what you are building? Book a discovery call. Not sure where the problem is? Request the audit. If neither is right for you, we will say so, and tell you what is.

Not ready for either? Talk to the demonstration in your browser for three minutes, or paste your own address and hear it answer as your business. No form and no booking, and the transcript arrives by email a minute later.

Hear it work
A material study photographed in bright daylight. A thin sliver of the monumental pleated turquoise glass wave enters from the right edge of a very wide frame, its fins and one polished silver ribbon catching the light at the crest, above a pearl reflective floor that runs the full width. The left of the frame is an almost empty pale mint room.

Answers that keep working after the call.

HUREAL / Material studies