Home / Guides / Cleaning AI text for WordPress and other website editors

Cleaning AI text for WordPress and other website editors

In short

Clean the text, paste it as plain text, and build the structure with the editor's own heading and list blocks. WordPress also converts straight quotes to curly ones when it displays text, so put code in a code block and check the preview before you publish.

Website editors look forgiving, but what you paste ends up as HTML on a public page, so small problems become visible to every reader and to search engines. A few minutes of tidying before you publish saves you from stray symbols, empty gaps and broken links.

What goes wrong when AI text hits a CMS

  • Markdown symbols such as ** and ## can show up in the middle of the page, depending on how the editor treats the paste.
  • Several blank lines become empty paragraphs or large gaps between sections.
  • Headings are typed as bold text, so the page has no real structure for readers using screen readers or for search engines.
  • Links keep tracking parameters, and some point to pages that don't exist.
  • Hidden characters sit inside words and make on-page search and internal search miss them.

Step 1: clean first

Paste the text into Paste & Wash and read the report. Turn on Markdown symbols if you see asterisks or hash signs, and leave line breaks on so runs of blank lines are collapsed. Hidden characters, odd spaces, citation markers and tracking parameters are removed by default.

Copy the result from the second box. You now have text with nothing in it but words, punctuation and single paragraph breaks.

Step 2: paste as plain text

In the WordPress block editor, Ctrl+Shift+V (Cmd+Shift+V on a Mac) pastes without source formatting. The older Classic editor has a Paste as text button on its toolbar. Pasting plain text stops inline fonts, colours and wrapper tags from the source arriving in your page, which keeps the HTML underneath short and predictable. Some versions of the block editor also try to turn pasted Markdown into blocks, which can save time but is not always what you want, so check the result.

If you are curious what a paste produced, WordPress lets you switch to the Code editor and read the HTML. Seeing span tags with style attributes is a sign that formatting came along.

Step 3: build the structure with blocks

Use the editor's heading block for headings and its list block for lists. Your page title is normally the top-level heading, so use second-level headings for main sections and third-level headings for the parts inside them, without skipping levels. This gives screen reader users a way to jump through the page, and it gives search engines a clear outline.

Add descriptive alt text to every image. If an image was generated with AI, say what it shows, not that it was generated.

Quotes, dashes and code

WordPress runs a text-formatting step when it displays posts. Among other things, it turns straight quotes into curly ones and sequences of hyphens into dashes. That is helpful for ordinary prose, but it is a problem for code, commands and anything a reader will copy and run, because curly quotes and long dashes make commands fail.

Put code and commands in a code block, where this conversion does not apply. If you want your prose quotes to match exactly, decide whether you prefer curly or straight and keep it consistent across the site.

Step 4: check links, preview and publish

  • Click every link in the preview. Remove tracking parameters and replace any link that doesn't open.
  • Preview on a phone as well as a desktop. Long unbroken strings and wide tables are the usual culprits.
  • Check the title, the summary shown in search results and the first paragraph. These are what people read before they decide to open the page.
  • Read the whole page once as a visitor, not as the writer.

Before you press publish

Tidy formatting is not the same as a good page. Check the facts, add something from your own experience that the AI could not know, and ask whether the page helps a reader more than the pages that already exist on the topic. The pre-publish checklist guide walks through those questions in order.

Questions people ask

Should I paste into the Code editor? Only if you are comfortable with HTML. Pasting plain text into the visual editor and using blocks is safer for most people.

Why did my quotes change after I published? WordPress converts straight quotes to curly ones when it displays text. That is deliberate typography, and it matters only where the exact characters matter, such as code.

Do I need to remove tracking parameters from links? You don't have to, but they add nothing for your readers, they make links longer, and they can muddy your own analytics if they label visits with a source you did not choose.

How long should a post be? As long as it takes to be useful. A tidy 600-word answer that solves a problem is better than a padded 2,000-word one.

Try the cleaner to see what is hiding in your own text.

Related guides

Browse all 20 guides