Content Lock-in & How to Avoid it.

Written By PhilG

Bradford Marketing Hub contains articles and information that help small and medium service businesses.

What is WordPress content lock-in?

All WordPress websites have a WordPress theme, and most have some kind of page layout plugin or proprietary page design blocks.

These proprietary page design blocks make it easy to add fancy page layout sections to your pages and posts. However! If you ever change theme or disable the plugin that fancy page layout section depends on, your content can become ugly, or even disappear altogether.

My simple rule of thumb:

On pages I use any fancy design my theme or page layout plugin offers. But on blog posts, I stick to a few content blocks that are part of the core WordPress software.

My reason is that WordPress websites usually have a few pages, such as: home, about, services, contact, etc. But they often have many blog posts. If you redesign your website you will want to redesign the home, about, services, and contact pages. But redesigning dozens, or even hundreds of blog posts will be way beyond your redesign budget.

If you’re interested in WordPress website content lock-in, read on for more details.

Why content lock-in happens (plain English)

Content lock-in happens when the meaning of a blog post is mixed up with its presentation.

Many themes and plugins encourage you to style headings, paragraphs, lists, and images using special blocks or visual controls. The post looks good only because that theme or plugin is present.

When it’s removed or changed:

  • Headings lose size or spacing
  • Text becomes hard to read
  • Images stack badly or float oddly
  • Sometimes content vanishes altogether

The problem isn’t WordPress itself.
It’s using tools designed for layout and design inside blog content, where they don’t belong.


The goal

Write blog content that:

  • Still makes sense if the theme changes
  • Still looks acceptable with any decent theme
  • Can be edited by a non-technical client without fear
  • Will age well over 5–10 years

That means simple, boring, reliable choices.


5 rules for lock-in-free blog content

Rule 1: Use only the core text blocks for writing

Principle:
If WordPress can’t show the content without a theme or plugin, don’t use it for blog posts.

Use:

  • Heading
  • Paragraph
  • List
  • Image

Avoid:

  • Theme-specific text blocks
  • “Advanced” heading blocks
  • Styled content boxes
  • Anything labelled “Pro”, “Enhanced”, or “Design”

Do this:

Heading → Paragraph → List → Paragraph → Image

Not this:

“Fancy Heading” → “Text Card” → “Feature List” → “Media Object”

If a block isn’t available in a fresh WordPress install, treat it with suspicion.


Rule 2: Let headings mean structure, not style

Principle:
Headings describe the shape of the article, not how big the text should look.

Use headings to:

  • Break content into sections
  • Help readers scan the page
  • Help search engines understand the post

Avoid:

  • Using headings just to make text bigger
  • Skipping heading levels (e.g. H2 straight to H4)

Do this:

  • Post title = H1 (WordPress handles this)
  • Main sections = H2
  • Sub-sections = H3

Not this:

  • H4 because “it looks nicer”
  • Headings used for emphasis instead of meaning

If the theme changes, good heading structure survives. Styling does not.


Rule 3: Keep paragraphs boring and readable

Principle:
Paragraph text should be clean, predictable, and easy to re-style later.

Do:

  • Write short paragraphs (2–4 lines)
  • Use plain paragraph blocks
  • Let the theme control fonts, colours, and spacing

Avoid:

  • Inline font sizes
  • Custom colours inside posts
  • “Highlighted text” blocks
  • Multiple font styles in one paragraph

Do this:

Plain paragraph text that looks fine everywhere

Not this:

Paragraphs with custom sizes, colours, or backgrounds

If text needs special styling to work, it probably belongs on a page, not in a blog post.


Rule 4: Use lists for clarity, not decoration

Principle:
Lists exist to make information clearer, not more stylish.

Use lists when:

  • You’re explaining steps
  • You’re listing features, tips, or examples
  • Order matters (numbered list)
  • Order doesn’t matter (bullet list)

Avoid:

  • “Icon lists”
  • Multi-column lists
  • Lists built with layout blocks

Do this:

  • A simple bullet or numbered list

Not this:

  • A styled feature grid pretending to be a list

Plain lists survive theme changes. Decorative lists usually don’t.


Rule 5: Treat images as content, not layout tools

Principle:
Images in blog posts should support the text, not control the layout.

Do:

  • Insert images between paragraphs
  • Use centre or wide alignment only
  • Let images stack naturally on mobile

Avoid:

  • Text wrapped around images
  • Side-by-side image/text layouts
  • Image grids inside posts
  • Using images to fake columns

Do this:

Paragraph → Image → Paragraph

Not this:

Image floated left with text wrapped around it

If an image’s position is critical to the layout, it belongs on a page — not in a blog post.


A simple test (give this to trainees)

After publishing a blog post, ask:

“If I changed the theme tomorrow, would this still read clearly?”

If the answer is yes:

  • You’ve done it right

If the answer is “only if we keep this theme/plugin”:

  • You’ve introduced lock-in

Final mindset to pass on

For low-budget client work, reliability beats cleverness.

Your job isn’t to show how many tools you know.
It’s to leave behind content that:

  • Still works when you’re gone
  • Doesn’t trap the client
  • Doesn’t create future rebuild work

That’s how you squeeze every last drop of juice from the orange — by mastering the basics instead of adding more tools.

Read more useful articles like this in my blog...