• I have this problem, the site has simple addresses ie with a question mark. But google after adding the site map in webmaster tools does not recognize the map and does not fetch the addresses.

    The map has this page address ?tsf-sitemap=base and goggle does not recognize it.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Sybre Waaijer

    (@cybr)

    Howdy!

    It’s always best not to use the “plain” permalink structure. Since this structure is discouraged, few people use it, so I have little data on its behavior in edge cases, even though I ensured everything should work with it.

    What does Google say exactly, and on what report did that say that? Do you have a URL for me to inspect?

    Thread Starter Danishsard

    (@danishsard)

    For search engines today it is indifferent whether it is a static url or a dynamic one. It’s long gone when static was better.

    My site map address https://nasza.nsfera.pl/?tsf-sitemap=base

    Bing webmaster tols it without a problem, google can’t recognize it because it can’t download it – that’s the message.

    Here it is not about the url in the map, but about the map address the add-on generates.

    If it was an xml address suffix perhaps it would be different.

    Plugin Author Sybre Waaijer

    (@cybr)

    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.

    Thread Starter Danishsard

    (@danishsard)

    I’ve done tests on many sites already, and it’s always better recent sites just with simple addresses than those too long static ones – sometimes the titles of the posts are long and the addresses become too long.

    .xml cannot be added to such an address – because it redirects to the home page.

    But well, if after a week google doesn’t wake up – it will solve it in another way. That is, its own type of link with /id static but not the title of the name of the entries.

    Thank you for your help.

    • This reply was modified 1 month, 2 weeks ago by Danishsard.
Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.