Classification
Invisible metadata & code inflation (rich-text bloat)
Origin
Desktop word processors — Microsoft Word / the Office XML schema
Target
WYSIWYG web editors — WordPress Gutenberg, Shopify, Squarespace

The problem

Content creators draft articles and product copy in heavy desktop word processors. Those apps produce beautiful print layouts by embedding large arrays of hidden parameters directly into the file. Select, copy, and the system clipboard carries those background schemas along invisibly. Paste that unfiltered stream into a browser-based editor and the styling architecture leaks into your clean source code, overriding your site's CSS and breaking layout continuity.

What it looks like in the editor

After a direct, unfiltered paste, a normal paragraph picks up unexpected font changes, oversized line heights, and stray highlighting:

Before · pasted from Word into the CMS

Our spring collection launches next week — with twelve new pieces and free returns on every order. Read the lookbook.

The visible mess is only half the story. The real damage is in the code behind it.

The code payload a crawler actually reads

That slightly-messy paragraph generates catastrophic backend HTML. Instead of a clean, lightweight string, the markup is stuffed with non-standard proprietary office tags — MsoNormal, mso-spacerun, empty <o:p> elements, and hardcoded inline fonts:

Before · the raw HTML behind one sentence
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt;
  line-height:normal;mso-pagination:widow-orphan">
  <span style="font-size:11.0pt;
    font-family:&quot;Calibri&quot;,sans-serif;
    mso-fareast-font-family:Calibri;color:#1F1F1F;
    mso-ansi-language:EN-US">
    <o:p></o:p>Our spring collection
    <span style="mso-spacerun:yes">&nbsp; </span>launches next week.
  </span>
</p>
≈ 612 bytes for one sentence
After · the same sentence, cleaned
<p>Our spring collection launches next week.</p>
48 bytes · pure character data

Passing the payload through the local sanitation in cleanplaintext.com deletes the proprietary schemas. The output is stripped to raw text, ready to inherit your design's global styles automatically.

Why the bloat actually hurts

The presence of MsoNormal, mso-spacerun, and hardcoded inline fonts causes three real problems:

  • Responsive layout failures. Absolute line heights and pixel font sizes stop mobile browsers from scaling text dynamically, so the page breaks on small screens.
  • DOM inflation. The extra markup bloats the page and the database, slowing render times and queries for every visitor.
  • SEO penalties. Crawlers read unstructured proprietary code blocks as low-quality layout, which can drag down the authority of the page they sit on.

The clean fix

Before pasting Word content into your CMS, run it through cleanplaintext.com first. The proprietary schemas are stripped locally on your device, and what you paste into the editor is plain text that adopts your site's own styles — lean, responsive, and crawler-friendly by default.