Skip to content
Boomspot
  • Home
Loading...
Boomspot

Daily tech news, software development coverage, Apple reporting, and the gear behind modern music making.

TwitterLinkedIn

Browse

  • Categories
  • Tags
  • Authors

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  • Unsubscribe

© 2026 Boomspot. All rights reserved.

Built by Boomspot
Updated hourly

AI Content Disclosure: Articles on Boomspot are researched, written, and edited with the assistance of advanced AI systems. We combine software-assisted research with editorial oversight to deliver useful, accurate, and practical technical and music production content. Learn more about our editorial approach.

Browse by Category

Technology681Coding193SEO66Linux66Studio Gear47Music Production42Apple Rumors11

Popular Posts

Speed Up Linux Kernel Compile Time: 7 Practical Fixes

Speed Up Linux Kernel Compile Time: 7 Practical Fixes

8 min read
Is Linux on PS5 Worth It? pLinux5-NG vs. a Mini PC

Is Linux on PS5 Worth It? pLinux5-NG vs. a Mini PC

7 min read
How to Test Budget DJ Headphones and Speakers at Home

How to Test Budget DJ Headphones and Speakers at Home

10 min read
Beginner-Friendly Terminal Editor: TTT vs micro vs Edit

Beginner-Friendly Terminal Editor: TTT vs micro vs Edit

8 min read
Affiliate Site Audit: Measure Your Google Traffic Risk

Affiliate Site Audit: Measure Your Google Traffic Risk

11 min read

Recent Posts

Google Automated Calls Business Profile Setting Audit

Google Automated Calls Business Profile Setting Audit

Nov 20, 2026•9 min
Voice Agent Latency Budget: Where a Turn's 1,000 ms Goes

Voice Agent Latency Budget: Where a Turn's 1,000 ms Goes

Nov 20, 2026•8 min
Ansible Touch Always Changed: Make the File Task Idempotent

Ansible Touch Always Changed: Make the File Task Idempotent

Nov 20, 2026•7 min
Yamaha NS-10 Alternatives for a Home Studio: What to Buy

Yamaha NS-10 Alternatives for a Home Studio: What to Buy

Nov 20, 2026•7 min
Check Installed OpenJDK Versions on Linux After Java4Shell

Check Installed OpenJDK Versions on Linux After Java4Shell

Nov 20, 2026•9 min
  1. Home
  2. SEO
  3. WordPress Sitemap Showing Raw XML in Chrome? Audit Steps
seo8 min read

WordPress Sitemap Showing Raw XML in Chrome? Audit Steps

Opened /wp-sitemap.xml in Chrome and saw a wall of tags? Here is a 10-minute audit to identify your sitemap generator, prove crawlers can read it, and decide whether to act.

S

Staff

November 20, 2026

Reviewed byDorian

WordPress Sitemap Showing Raw XML in Chrome? Audit Steps

You opened /sitemap_index.xml or /wp-sitemap.xml in Chrome and got a wall of angle brackets plus a console warning. Before you reinstall a plugin or message your developer, run a 10-minute audit. It answers three questions: which generator serves the sitemap, whether crawlers can read it, and whether you need to do anything.

The cause in short: the sitemap file references an .xsl stylesheet that older Chrome versions used to turn XML into a tidy table, and Chrome 158 no longer runs it. The file underneath is unchanged. The steps below prove that for your site instead of asking you to take it on faith.

Step 1: Identify which sitemap your site serves

The fix depends on who generates the file, so start here. According to Search Engine Journal, WordPress core serves /wp-sitemap.xml, while Yoast SEO, Rank Math and All in One SEO (AIOSEO) serve /sitemap_index.xml, and /sitemap.xml redirects there. A plugin sitemap normally replaces the core one.

Run these quick checks:

  1. Open /wp-sitemap.xml and /sitemap_index.xml in a browser tab each. Note which one loads, which redirects, and which returns a 404.
  2. Open Plugins in the WordPress admin and note whether Yoast SEO, Rank Math or AIOSEO is active.
  3. Open your robots.txt and see which sitemap URL it lists. Then check which URL is submitted in Search Console (Step 4).

Pass: one clear sitemap index URL, consistent across robots.txt, Search Console and the active plugin. Fail: two competing sitemaps, a 404 on the URL you submitted, or a robots.txt line pointing somewhere that no longer exists. That is a real configuration problem, and it has nothing to do with Chrome.

Step 2: Check the HTTP status and content type

A browser can show a page that looks fine while the server sends something odd. Open DevTools, go to the Network tab, reload the sitemap URL and click the first request. If you prefer a terminal, curl -I https://yourdomain.com/sitemap_index.xml shows the same headers.

Pass: status 200 and a content type that contains xml. No redirect loop, and no more than one redirect hop (for example /sitemap.xml to /sitemap_index.xml). Fail: a 404, a 5xx, a login or cookie-wall page, or a content type of text/html. Also fail it if an X-Robots-Tag header on the sitemap carries something you did not intend. A security plugin or CDN rule is the usual culprit.

Step 3: View the source and look for the .xsl reference

Type view-source: in front of the sitemap URL. This shows the raw response instead of Chrome's rendering of it.

Pass: the file begins with an XML declaration, and the root element is either <sitemapindex> (the index) or <urlset> (an individual sitemap). It lists <loc> entries with your canonical, live URLs. Fail: HTML tags, a PHP error message, an empty file, or <loc> entries pointing at staging domains, http versions or redirected URLs.

Now look near the top for a line that starts with <?xml-stylesheet and points to an .xsl file. If it's there, you've found the source of the console warning. Its path also hints at the generator (this is an inference: core and each plugin ship their own stylesheet, so the folder name usually gives it away). Seeing the reference is not a failure. It explains what Chrome shows.

For a second opinion, open the same URL in Firefox or Safari. Search Engine Journal says both still support XSLT for now, so you may see the styled table there. That makes a useful screenshot for a client, though it may change.

Step 4: Confirm Google reads it in Search Console

Open Search Console, pick the property, and go to Indexing, then Sitemaps. Look at the submitted sitemaps table. We cover related ground in google places api 120 results limit workaround (python) explained.

Pass: the sitemap you identified in Step 1 is listed, the Status column says Success, the last read date is recent, and the discovered URL count looks plausible for your site. Fail: Couldn't fetch, a parsing error, or a last read date from months ago. If the sitemap isn't submitted, submit it and recheck after Google has had time to fetch it.

This is the evidence that matters, and it has limits. Success means Google fetched the file and parsed the XML. It does not mean every listed URL was indexed, that the URLs are the right ones, or that rankings will move. For indexing questions, use the Pages report and URL Inspection on specific URLs. That is a separate audit.

Worked example (illustrative, not a real client audit)

Imagine a 40-page service business site, run by a freelancer for a small-business owner. The owner emails a screenshot of raw XML at /sitemap_index.xml and asks if the site is broken. Here is how the checklist might play out. Every detail below is invented to show the method.

Step 1: /sitemap_index.xml loads, /sitemap.xml redirects to it, and /wp-sitemap.xml no longer serves a sitemap. A Rank Math-style SEO plugin is active, and robots.txt lists /sitemap_index.xml. Pass.

Step 2: DevTools shows a 200 with an XML content type and no extra redirects. Pass.

Step 3: view-source shows a <sitemapindex> with child sitemaps for posts, pages and categories, all on the https canonical domain. An xml-stylesheet line is present. Pass, and the warning is explained.

Step 4: Search Console shows Success, a read date from this week, and a URL count in line with the site. Pass.

The verdict: the sitemap is healthy, and the owner only saw a display change. The owner mentions that staff liked skimming the old table, so the freelancer recommends leaving the XML alone and adding a simple HTML page for people.

Step 5: Pick one of three actions

Leave it. This is the right call for most sites. Search Engine Journal recommends it, since crawlers read the raw XML and the stylesheet is cosmetic. Pick this when Steps 1 to 4 pass and nobody needs a pretty view.

Suppress the core XSLT reference. This only applies to the core /wp-sitemap.xml. Do it if a QA tool, automated site-health check or fussy stakeholder keeps flagging the console warning. Add a file at wp-content/mu-plugins/disable-sitemap-xsl.php:

<?php
/**
 * Plugin Name: Disable Sitemap XSL
 */
add_filter( 'wp_sitemaps_stylesheet_url', '__return_false' );
add_filter( 'wp_sitemaps_stylesheet_index_url', '__return_false' );

The sitemap still shows as plain XML. You only lose the warning. Search Engine Journal says WordPress 7.2 removes the stylesheet and deprecates both filters, so delete this file after upgrading or it will only produce deprecation notices. The article covers this fix for core only, so don't edit plugin files to chase the same result.

Also read: block gptbot, allow oai-searchbot: a robots.txt audit in depth

Build an HTML sitemap. Do this when humans need a browsable list. Create a page such as /sitemap/ and use the Page List, Categories or Latest Posts blocks, as Search Engine Journal suggests. It gives editors and clients a readable directory. It doesn't change what crawlers read from the XML sitemap, and block-based lists may not cover every post type you care about, so check the result.

Decision table

| Setup | What Search Engine Journal says | Recommended action | |---|---|---| | WordPress core (/wp-sitemap.xml) | WordPress 7.2, scheduled for Dec. 8, removes core's stylesheet | Leave it, or use the mu-plugin if the warning is flagged. Delete the plugin after 7.2. | | Yoast SEO | 28.9 replaces XSLT with CSS. As of Nov. 17 it was at RC5, with 28.8 the stable release | Leave it. The styled view should return once 28.9 is stable. | | Rank Math | Said the change is visual only. Its changelogs listed no stylesheet fix | Leave it. Add an HTML sitemap if people need a readable list. | | AIOSEO | Still serves XSLT-styled sitemaps, with no announced alternative | Leave it. Add an HTML sitemap if people need a readable list. |

Re-check before acting. The table reflects the Search Engine Journal article published Nov. 19, 2026. Plugin release dates, the Yoast 28.9 status and the WordPress 7.2 schedule can change, so read the current plugin changelogs and the WordPress release page first.

What to tell the client

Use this template, filled in with your own evidence:

Chrome recently stopped supporting the styling file that made our sitemap look like a table. The sitemap itself is unchanged. We checked that it returns a normal 200 response as XML, that its contents list the correct URLs, and that Google Search Console reports it as read successfully on [date]. This is a display change in one browser, not a site fault. We are [leaving it as is / hiding the browser warning / adding a readable page for people]. We will re-check when [plugin or WordPress update] ships. This does not mean any change in rankings, and we are not making that claim either way.

Attach the Search Console screenshot and the view-source screenshot. Don't promise that the sitemap guarantees indexing, because it never did.

What to expect next

Expect the browser view to change again as vendors ship their updates. Core should drop the stylesheet in 7.2, and Yoast's CSS-styled view depends on 28.9 reaching stable. Rank Math and AIOSEO had announced nothing at the time of the Search Engine Journal article. Put a reminder in your calendar after each release, rerun Steps 2 to 4 once, and update the client note. If a check fails, fix that specific problem.

Tags

Developer ToolsWeb DevelopmentCoding TutorialsOpen-source

Keep reading

MCP Implementation at HubSpot: Elevating CRM with Context
Coding•4 min read

MCP Implementation at HubSpot: Elevating CRM with Context

Explore HubSpot's transformative MCP implementation for their CRM, detailing key strategies, challenges, and best practices for developers.

Sep 20, 2025

Your Guide to GitHub Universe 2025: Schedule Launched!
Coding•3 min read

Your Guide to GitHub Universe 2025: Schedule Launched!

Get ready for GitHub Universe 2025! Check out the schedule, create your personalized agenda, and sign up for mentoring sessions. Join us for an exciting experience!

Sep 13, 2025

Unlocking ChatGPT Developer Mode: Full MCP Client Access
Coding•4 min read

Unlocking ChatGPT Developer Mode: Full MCP Client Access

Unlock the power of ChatGPT Developer Mode with full MCP client access. Discover how to enhance your coding projects and streamline development.

Sep 11, 2025

More stories for your next project

Get tech, coding, and music production updates in your inbox.

Unsubscribe anytime.