Hi again!
I can’t agree with that statement. The reason is that numerical permalinks, like ?p=42
, do not contain keywords or yield a structure, like /category-name/post-name/
. Structured data can come into play to rectify this, but that requires additional processing. Most people are also better at remembering names than numbers, though I doubt many will type in a fully qualified URL.
Plain permalinks also do not allow WordPress to generate the virtual /robots.txt
endpoint, among other things.
In any case, the sitemap responds as intended, headers and all.
TSF simulates the “plain” permalink structure to output the sitemap on plain permalink settings. It actually doesn’t parse the GET-query but simply looks for ?tsf-sitemap=
in the URL. I implemented this trick to support any odd queries from translation plugins. Because of this, you can add .xml
to the URL, and the sitemap will still work, and you could test whether Google wants the “.xml” affix.
Still, people who report the same message from Google say this resolves on its own after a week. If your sitemap has been proposed to them for longer than that, it’s worth looking into it more, such as inspecting the response data Google received from your server.