# Attribute “xmlns:o” not allowed here. > Canonical HTML version: https://rocketvalidator.com/html-validation/attribute-xmlns-o-not-allowed-here > Attribution: Rocket Validator (https://rocketvalidator.com) > License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) In XML and XHTML, the `xmlns` attribute is used to declare namespaces that allow elements and attributes from different vocabularies to coexist without naming conflicts. The `xmlns:o` prefix specifically declares the Microsoft Office namespace (`urn:schemas-microsoft-com:office:office`), which enables Office-specific elements and attributes like `` (Office paragraph markers) within the document. HTML5, however, is not an XML language. The HTML5 specification only permits the `xmlns` attribute on the `` element (and only with the value `http://www.w3.org/1999/xhtml`), along with `xmlns:xlink` on SVG elements. Custom namespace prefixes like `xmlns:o`, `xmlns:v` (VML), and `xmlns:w` (Word) are not recognized as valid attributes on any HTML5 element and will trigger validation errors. ## Why This Happens This issue most commonly occurs when: - **Content is pasted from Microsoft Word** into a WYSIWYG editor or CMS. Word generates its own flavor of HTML that includes Office namespace declarations and proprietary elements. - **HTML files are exported from Office applications** like Word, Excel, or Outlook. These exports produce markup heavily reliant on Office-specific namespaces. - **Email templates** are built using tools that generate Office-compatible HTML, carrying namespace baggage into standard web pages. ## Why It Matters - **Standards compliance**: HTML5 does not support arbitrary XML namespace declarations, so these attributes make your document invalid. - **Bloated markup**: Office-generated HTML often includes not just the namespace declarations but also large amounts of Office-specific elements, conditional comments, and inline styles that increase page size significantly. - **Maintenance difficulty**: Office-flavored HTML is harder to read, edit, and maintain compared to clean, standards-compliant markup. - **Potential rendering issues**: While browsers generally ignore unrecognized attributes, the accompanying Office-specific elements (like ``) can occasionally cause unexpected spacing or layout behavior. ## How to Fix It 1. **Remove all `xmlns:o` attributes** from your HTML elements. 2. **Remove any Office-specific elements** such as ``, ``, or similar tags that rely on the Office namespace. 3. **Check for other Office namespaces** like `xmlns:v`, `xmlns:w`, `xmlns:m`, and `xmlns:st1` — these should also be removed. 4. **Clean pasted content** before inserting it into your HTML. Many text editors and CMS platforms offer a "Paste as plain text" option that strips out Office formatting. 5. If you use a CMS or rich text editor, look for a **"Clean up Word HTML"** or similar feature to automatically strip Office artifacts. ## Examples ### ❌ Invalid: Office namespace declarations on elements ```html Company Report

Quarterly Report

Revenue increased by 15% this quarter.

Expenses remained stable.

``` This markup contains three Office namespace declarations on the `` element and uses `` elements inside paragraphs — all of which are invalid in HTML5. ### ✅ Valid: Clean HTML without Office namespaces ```html Company Report

Quarterly Report

Revenue increased by 15% this quarter.

Expenses remained stable.

``` ### ❌ Invalid: Namespace on a `div` element ```html

Meeting notes from Tuesday.

``` ### ✅ Valid: Clean version ```html

Meeting notes from Tuesday.

``` Notice that in the corrected examples, the `class="MsoNormal"` attribute was also removed. While `MsoNormal` is technically a valid class name that won't cause a validation error, it's an Office-generated class with no purpose unless you have corresponding CSS rules — removing it keeps your markup clean. If you genuinely need XML namespace support for document processing, use a proper XHTML document served with the `application/xhtml+xml` content type, or handle the XML processing separately from your web-facing HTML.