XML Sitemap & Google News

説明

本プラグインは、XML サイトマップGoogle ニュース・サイトマップの規定に従った動的フィードを動的に生成します。
マルチサイトや、PolylangWPML にも互換性があり、静的なファイルは作成されません。

投稿種別とアーカイブページ (用語分類や筆者のページような) を含め、どのサイトマップを有効にするかを管理する設定があります。ほかにも、優先度と最終更新日をどう計算するか、どこに Ping するか、WordPress 管理画面内から robots.txt のルールの追加を設定できるようになりました。

他の XML サイトマップ用プラグインと比べて、本プラグインの便利な特徴は単純さです。ファイルやフォルダのアクセス権を変更したり、ファイルを移動したり、プラグイン設定のための難しい調整に時間をかける必要はありません。

あなたやマルチサイトの管理者は、他の多くの XML サイトマップ用プラグインのように複雑な設定に悩まされないでしょう。大半の環境では標準設定で十分です。

XMLサイトマップのインデックスは、yourblog.url/sitemap.xml (美しい URL のパーマリンク構造を使用していなければ yourblog.url/?feed=sitemap) からすぐ利用可能になり、標準設定で投稿やページを参照しており、Google、Bing、Yahoo、AOL、Ask のような検索エンジンによるインデックス作成への用意が整います。Google ニュースのサイトマップを有効にすると、yourblog.url/sitemap-news.xml (またはyourblog.url/?feed=sitemap-news) を利用可能にし、Google ニュースによるインデックスに備えられます。この両方は、動的に作成された yourblog.url/robots.txtrobots.txtから自動的に参照され、検索エンジンにそのサイトの XML サイトマップがどこにあるかを示します。Google と Bing は、それぞれの新たな公開記事に Ping します。

Google ニュースに掲載された記事を取得する方法については、FAQ をご覧ください。

キャッシュをフィードするための、WP Super Cache, W3 Total Cache and Quick Cache のようなキャッシュ用プラグインに互換性があり、お腹をすかせたスパイダー (リンク網を作るプログラム) にも、パパッとごちそうを与えます。

注:

  1. 美しい URL を使っていない (URL がスラッシュ区切りではない) か、WordPress サブディレクトリにインストールされている場合には、動的な robots.txt は生成されません。自分で作成し、サイトのルートディレクトリにアップロードする必要があります ! FAQ 参照のこと。

  2. 巨大なサイトでは、WP Super Cache, Quick Cache, W3 Total Cache などの優れたキャッシュ用プラグインを使うことおすすめします。これにより、サイトサイトマップの反応速度が改善されます。

機能

  • PolylangWPML を使用中の多言語サイトに互換性があり、すべての言語を等しくインデックス化できます。
  • Option to add new robots.txt rules. These can be used to further control (read: limit) the indexation of various parts of your site and subsequent spread of pagerank across your sites pages.
  • 人がサイトマップを読めるように XLS スタイルシートを同梱。
  • サイトマップのテンプレートとスタイルシートは、テーマのテンプレートファイルによって上書き可能です。

XML サイトマップ

  • サイトマップのインデックスには、標準設定で、投稿、ページ、著者が含まれます。
  • 追加で独自の投稿種別、カテゴリー、タグをサイトマップに含めることも可能です。
  • 独自の URL をサイトマップに追加可能。
  • 独自 / 静的なサイトマップをインデックスに追加可能。
  • マルチサイトでも有効化すればすぐに動作します。
  • title 付きで特集画像や添付画像を含める。
  • 新たな投稿の公開を Google, Bing & Yahoo に PING
  • サイトマップに含む投稿種別や用語を設定できます。
  • 投稿の修正やコメント時に最終更新日時を更新。
  • 投稿種別ごと、用語ごと、個々の投稿ごとに優先度を設定。
  • 投稿や固定ページを個別に除外。

Google ニュースサイトマップ

  • ニュース用のサイトマップのタグが必要です: 公開名、言語、題名、公開日時。
  • ニュース公開名やサイト名を設定。
  • 独自の投稿種別に対応。
  • 特定の投稿カテゴリーに含めるのを制限。
  • 5分に1回、新しい公開投稿を Google に Ping する。

プロ版の機能

Google News Advanced

  • 複数の投稿種別 – 同じニュースのサイトマップに、1つ以上の投稿種別を含める。
  • Keywords – Add the keywords tag to your News Sitemap. Keywords can be created from Tags, Categories or a dedicated Keywords taxonomy.
  • Stock tickers – Add stock tickers tag to your News Sitemap. A dedicated Stock Tickers taxonomy will be available to manage them.
  • Ping のログ記録 – Google への最近の Ping を正確な日時と応答ステータスを保存します。

個人情報 / GDPR

本プラグインは、利用者または訪問者のデータやブラウザーのクッキーの設定を収集しません。このプラグインの使用による、サイトの個人情報保護方針への影響はありません。

公開されるデータ

XML サイトマップのインデックスには、すでに公開されているあなたのサイトの選択した種類の投稿記事の URL を含む他のサイトマップを参照するもので、投稿の最終更新日時と関連画像の URLや、選択した公開アーカイブの URL が共に含まれています。

Google ニュースのサイトマップには、あなたのサイトの、選択した種類のニュース投稿の公開された最近 (48時間以内) の URL が、公開日時と関連画像の URL と共に含まれています。
著者のサイトマップや、著者のアーカイブページへのリンクを含めることもできます。これらの URL には著者/ユーザー用のスラッグが含まれており、著者のアーカイブには著者の経歴を含めることができます。これらをパブリックドメインにしないようにするに、著者のサイトマップを無効にし、SEO プラグインで noindex をヘッダーに追加してください。

送信されるデータ

検索エンジンに活発に送信されるデータは、あなたのサイトマップの場所と公開日時です。これは「設定 > 投稿」の Ping の設定が1つでも有効になっていれば、各投稿の公開時に発生します。この時、選択した検索エンジンに対しサイトマップの場所と更新状態が通知されます。

貢献

本プラグインに満足いただけましたら、簡単な評価サポート掲示板で他のユーザーの支援もお考えください。

本プラグインの開発を手伝ってくださるのであれば、お使いの言語に翻訳したり、Github 上でのコードの開発に貢献ください。歓迎します。

クレジット

XML Sitemap Feed は、Patrick Chia 氏によるプラグイン Standard XML Sitemap Generator をベースにしています。以降、完全に書き換えられ、多くの方法で拡張されてきました。

スクリーンショット

  • 普通のブラウザーで表示した XML サイトマップ。あなたが見るためです 😉
  • 検索エンジンが読み取る XML サイトマップのソースコード。

インストール

WordPress

I. 以前から別の XML サイトマップ用プラグインを使っていれば、サイトのルートディレクトリに作成された sitemap.xml や sitemap-news.xml とまた (手動で管理していなければ) robots.txt があれば削除します。

II. 以下を使いプラグインをインストールします:

Covered Web Services でかんたんインストール !

… または …

管理画面のプラグイン > 新規追加から xml sitemap feed を検索しインストールします。

… または …

以下の手順に従います:

  1. 圧縮ファイルをダウンロードします。

  2. 「プラグイン > 新規追加 > プラグインのアップロード」からzip ファイルをアップロード…あるいは…展開し、お好きな FTP クライアントで /plugins/ フォルダーにアップロードします。

III. 本プラグインをプラグインページ上で有効化します。

完了です ! ブラウザや、なんらかのオンライン XML 検証ツールから yourblogurl.tld/sitemap.xml (もちろんドメイン名はあなたのサイトにし) にアクセスし、新しい XML サイトマップが作成されているのをご確認ください。また、サイトマップが yourblogurl.tld/robots.txt ファイルに記載されていることも確認できます。

マルチサイトで WordPress バージョン3以上

上記と同じですが、ネットワーク上の各サイトで XML サイトマップが利用できるようにするために、ネットワークで有効化を実行します。

Installed alongside WordPress MU Sitewide Tags Pages, XML Sitemap Feed will not create a sitemap.xml nor change robots.txt for any tag blogs. This is done deliberately because they would be full of links outside the tags blogs own domain and subsequently ignored (or worse: penalised) by Google.

アンインストール

本プラグインのアンインストールは、管理画面 > プラグインのページから行います。プラグインの設定とメタデータはデータベースから削除されます。uninstall.php ファイル内の注意事項をご覧ください。

マルチサイトでは、uninstall.php は、各サイトのアンインストール処理を行うために、ネットワーク内のすべてのサイトを巡回可能です。しかしこれは大規模なネットワークには対応しないので、wp-config.php 内で define(‘XMLSF_MULTISITE_UNINSTALL’, true); が明示的に設定されている場合にのみ、各サイトのアンインストールを行います。

FAQ

Where are the options?

On Settings > Reading you can enable the XML Sitemap Index and (if needed) the Google News Sitemap. There is also an Additional robots.txt rules field.

Once a sitemap is enabled, its options can be found on Settings > XML Sitemap or on Settings > Google News.

Ping settings can be found on Settings > Writing.

How do I get my latest articles listed on Google News?

Go to Suggest News Content for Google News and submit your website info as detailed as possible there. Give them the URL(s) of your fresh new Google News Sitemap in the text field ‘Other’ at the bottom.

You will also want to add the sitemap to your Google Search Console account to check its validity and performance. Create an account if you don’t have one yet.

Can I manipulate values for Priority and Changefreq?

You can find default settings for Priority on Settings > XML Sitemap. A fixed priority can be set on a post by post basis too.

Changefreq has been dropped since version 4.9 because it is no longer taken into account by Google.

Do I need to submit the sitemap to search engines?

No. In normal circumstances, your site will be indexed by the major search engines before you know it. The search engines will be looking for a robots.txt file and (with this plugin activated) find a pointer in it to the XML Sitemap on your blog. The search engines will return on a regular basis to see if your site has updates.

Besides that, Google and Bing are pinged upon each new publication by default.

NOTE: If you have a server without rewrite rules, use your blog without fancy URLs (meaning, you have WordPress Permalinks set to the old default value) or have it installed in a subdirectory, then read Do I need to change my robots.txt for more instructions.

Does this plugin ping search engines?

Yes, Google and Bing are pinged upon each new publication. Unless you disable this feature on Settings > Writing.

Do I need to change my robots.txt?

In normal circumstances, if you have no static robots.txt file in your site root, the new sitemap url will be automatically added to the dynamic robots.txt that is generated by WordPress.

If you use a static robots.txt file in your website root, you will need to open it in a text editor. If there is already a line with Sitemap: http://yourblogurl.tld/sitemap.xml you can just leave it like it is. But if there is no sitemap referrence there, add it (adapted to your site url) to make search engines find your XML Sitemap.

Or if you have WP installed in a subdirectory, on a server without rewrite_rules or if you do not use fancy URLs in your Permalink structure settings. In these cases, WordPress will need a little help in getting ready for XML Sitemap indexing. Read on in the WordPress section for more.

My WordPress powered blog is installed in a subdirectory. Does that change anything?

That depends on where the index.php and .htaccess of your installation reside. If they are in the root while the rest of the WP files are installed in a subdir, so the site is accessible from your domain root, you do not have to do anything. It should work out of the box.

But if the index.php is together with your wp-config.php and all other WP files in a subdir, meaning your blog is only accessible via that subdir, you need to manage your own robots.txt file in your domain root. It has to be in the root (!) and needs a line starting with Sitemap: followed by the full URL to the sitemap feed provided by XML Sitemap Feed plugin. Like:

Sitemap: http://yourblogurl.tld/subdir/sitemap.xml

If you already have a robots.txt file with another Sitemap reference like it, just add the full line below or above it.

Do I need to use a fancy Permalink structure?

No. While I would advise you to use any one of the nicer Permalink structures for better indexing, you might not be able to (or don’t want to) do that. If so, you can still use this plugin:

Check to see if the URL yourblog.url/?feed=sitemap does produce a feed. Now manually upload your own robots.txt file to your website root containing:

Sitemap: http://yourblog.url/?feed=sitemap

User-agent: *
Allow: /

You can also choose to notify major search engines of your new XML sitemap manually. Start with getting a Google Search Console account and submit your sitemap for the first time from there to enable tracking of sitemap downloads by Google! or head over to XML-Sitemaps.com and enter your sites sitemap URL.

Can I change the sitemap name/URL?

No. If you have fancy URL’s turned ON in WordPress (Permalinks), the sitemap url is yourblogurl.tld/sitemap.xml but if you have the Permalink Default option set the feed is only available via yourblog.url/?feed=sitemap.

I see no sitemap.xml file in my site root!

There is no actual file created. The sitemap is dynamically generated just like a feed.

I see a sitemap.xml file in site root but it does not seem to get updated!

You are most likely looking at a sitemap.xml file that has been created by another XML Sitemap plugin before you started using this one. Remove that file and let the plugin dynamically generate it just like a feed. There will not be any actual files created.

If that’s not the case, you are probably using a caching plugin or your browser does not update to the latest feed output. Please verify.

I use a caching plugin but the sitemap is not cached

Some caching plugins have the option to switch on/off caching of feeds. Make sure it is turned on.

Frederick Townes, developer of W3 Total Cache, says: “There’s a checkbox option on the page cache settings tab to cache feeds. They will expire according to the expires field value on the browser cache setting for HTML.”

The Google News sitemap is designed to NOT be cached.

I get an ERROR when opening the sitemap or robots.txt!

The absolute first thing you need to check is your blogs privacy settings. Go to Settings > Privacy and make sure you are allowing search engines to index your site. If they are blocked, your sitemap will not be available.

Then, you might want to make sure that there is at least ONE post published. WordPress is known to send 404 status headers with feed requests when there are NO posts. Even though the plugin tries to prevent that, in some cases the wrong status header will get sent anyway and Google Search Console will report a vague message like:

We encountered an error while trying to access your Sitemap.
Please ensure your Sitemap follows our guidelines and can be
accessed at the location you provided and then resubmit.

If that did not solve the issue, check the following errors that might be encountered along with their respective solutions:

404 page instead of my sitemap.xml

Try to refresh the Permalink structure in WordPress. Go to Settings > Permalinks and re-save them. Then reload the XML Sitemap in your browser with a clean browser cache. ( Try Ctrl+R to bypass the browser cache — this works on most but not all browsers. )

404 page instead of both sitemap.xml and robots.txt

There are plugins like Event Calendar (at least v.3.2.beta2) known to mess with rewrite rules, causing problems with WordPress internal feeds and robots.txt generation and thus conflict with the XML Sitemap Feed plugin. Deactivate all plugins and see if you get a basic robots.txt file showing:

User-agent: *
Disallow:

Reactivate your plugins one by one to find out which one is causing the problem. Then report the bug to the plugin developer.

404 page instead of robots.txt while sitemap.xml works fine

There is a known issue with WordPress (at least up to 2.8) not generating a robots.txt when there are no posts with published status. If you use WordPress as a CMS with only pages, this will affect you.

To get around this, you might either at least write one post and give it Private status or alternatively create your own robots.txt file containing:

Sitemap: http://yourblog.url/sitemap.xml

User-agent: *
Allow: /

and upload it to your web root…

Error loading stylesheet: An unknown error has occurred

On some setups (usually using the WordPress MU Domain Mapping plugin) this error occurs. The problem is known, the cause is not… Until I find out why this is happening, please take comfort in knowing that this only affects reading the sitemap in normal browsers but will NOT affect any spidering/indexing on your site. The sitemap is still readable by all search engines!

XML declaration allowed only at the start of the document

This error occurs when blank lines or other output is generated before the start of the actual sitemap content. This can be caused by blank lines at the beginning of wp-config.php or your themes functions.php or by another plugin that generates output where it shouldn’t. You’ll need to test by disabling all other plugins, switching to the default theme and manually inspecting your wp-config.php file.

I see only a BLANK (white) page when opening the sitemap

There are several cases where this might happen.

Open your sitemap in a browser and look at the source code. This can usually be seen by hitting Ctrl+U or right-click then select ‘View source…’ Then scan the produced source (if any) for errors.

A. If you see strange output in the first few lines (head tags) of the source, then there is a conflict or bug occuring on your installation. Please go to the Support forum for help.

B. If the source is empty or incomplete then you’re probably experiencing an issue with your servers PHP memory limit. In those cases, you should see a messages like PHP Fatal error: Allowed memory size of xxxxxx bytes exhausted. in your server/account error log file.

This can happen on large sites. To avoid these issues, there is an option to split posts over different sitemaps on Settings > XML Sitemap. Try different settings, each time revisiting the main sitemap index file and open different sitemaps listed there to check.

Read more on Increasing memory allocated to PHP (try a value higher than 256M) or ask your hosting provider what you can do.

Can I run this on a WPMU / WP3+ Multi-Site setup?

Yes. In fact, it has been designed for it. Tested on WPMU 2.9.2 and WPMS 3+ both with normal activation and with Network Activate / Site Wide Activate.

評価

2020年5月24日
My site was running with all in one seo pack XML module. As it was indexed on Google news, i was looking for a plugin able to supply both classic xml and google news sitemap. This plugin offers both perfect functions, and can be set as we want.RavanH is there for any answer, he anwsers quickly and has a large palett of knowledge. Thanks for this plugin Yvan
68件のレビューをすべて表示

貢献者と開発者

XML Sitemap & Google News はオープンソースソフトウェアです。以下の人々がこのプラグインに貢献しています。

貢献者

“XML Sitemap & Google News” は6ロケールに翻訳されています。 翻訳者のみなさん、翻訳へのご協力ありがとうございます。

“XML Sitemap & Google News” をあなたの言語に翻訳しましょう。

開発に興味がありますか ?

コードを閲覧するか、SVN リポジトリをチェックするか、開発ログRSS で購読してみてください。

変更履歴

5.3

TODO verify date archive redirect Yoast Pro?
TODO custom post type root pages
TODO prime meta caches button
TODO Google News Feed tab
* NEW: Author sitemap
* NEW: allow custom theme templates and stylesheets
* NEW: request filters xmlsf_request and xmlsf_news_request
* NEW: news template filters xmlsf_news_publication_name and xmlsf_news_title
* NEW: sitemap template action hook xmlsf_url
* NEW: sitemap template action hooks xmlsf_news_url and xmlsf_news_tags_inner
* Moved news template action hook xmlsf_news_tags_after to after closing tag
* Less DB queries, smaller memory footprint
* Better debug info with SAVEQUERIES
* FIX: invalid form control not focusable when meta box is hidden
* FIX: force Status 200 response
* FIX: priority calculation last modified for post type
* FIX: news sitemap redirection with Polylang

5.2.7

  • NEW: Ad Inserter compatibility check
  • NEW: xmlsf_urlset and xmlsf_news_urlset action hooks, thanks to Stanislav Khromov (@khromov)
  • Exclude hierarchical post types from news sitemap

5.2.6

  • NEW: xmlsf_tags_after, xmlsf_url_after and xmlsf_news_url_after action hooks
  • Make stylesheet paths relative to prevent exclusion when using different language domains
  • FIX: Taxonomy selection not available to new installs

5.2.4

  • NEW Rank Math incompatibility admin warnings
  • FIX undefined index
  • FIX invalid form control

5.2.3

  • FIX Cannot use return value in write context
  • FIX issue #30 for sql_mode=ONLY_FULL_GROUP_BY, thanks @silvios
  • FIX invalid form control not focusable when meta box is hidden

5.2.2

  • FIX invalid date format on some PHP versions
  • FIX Can’t use function return value in write context
  • FIX non-cyrillic URLs stripped from External Web Pages field
  • FIX Call to undefined function xmlsf_cache_get_archives()

5.2

  • Image query optimization and meta caching
  • Last comment date meta caching
  • Lastmod and publication dates in local time
  • Removed ignored image tag from news sitemap
  • Max memory limit for post type and taxonomy term sitemaps
  • Prevent CDN file urls
  • Zlib before GZhandler on .gz request
  • FIX: don’t ping for excluded posts
  • FIX: traditional and simplified Chinese with WPML
  • FIX: redundant front page url
  • FIX: array_filter() expects parameter 1 to be array
  • FIX: possible division by zero
  • FIX: update_term_modified_meta
  • FIX: rewrite rules on deactivate/uninstall

5.1.2

  • FIX: admin notice dismiss button failing
  • FIX: date archive redirect notice showing for inactive post types
  • Plugin support and rate links on plugins page

5.1.1

  • FIX options page not found
  • FIX news sitemap only ping

5.1

  • SEOPress and Catch Box incompatibility admin messages
  • FIX bbPress incompatibility
  • FIX failing last modified date for taxonomy sitemaps
  • FIX sitemap showing when only private posts
  • FIX possible sitemaps for no longer existing post types in index
  • Admin interface improvements: highlighting and scroll
  • Upgrade routines in own class only to be included when needed
  • Moved metabox methods to dedicated classes
  • NEW Respond to .gz requests (with ob_gzhandler output buffering if needed)
  • NEW filters xmlsf_disabled_taxonomies, xmlsf_news_keywords, xmlsf_news_stock_tickers
  • NEW action xmlsf_ping
  • NEW Tools: Ping search engines and Flush rewrite rules

5.0.7

  • Allowed domains back to Settings > Reading
  • FIX static files check on activation
  • NEW Admin warning on conflicting plugin settings
  • FIX Empty post priority saved as 0.0
  • FIX Call to undefined function xmlsf_get_archives()
  • FIX force LC_NUMERIC locale to C
  • FIX Call to private method
  • FIX Custom post types with a hyphen not showing
  • FIX Admin static files message fatal error, thanks @kitchin
  • FIX Improper if statement in upgrade routine, thanks @kitchin
  • FIX PHP 5.4 compatibility issues

5.0

  • Complete code restructure and cleanup: MVC and JIT inclusion
  • Fewer DB queries, much smaller memory footprint on normal queries
  • NEW Admin interface with dedicated options pages and help tabs
  • NEW Taxonomy term options: priority and automatic calculation
  • NEW Admin warning on conflicting static files
  • NEW Option to delete conflicting static files
  • NEW Filters for post types: xmlsf_post_types and xmlsf_news_post_types
  • NEW Filters for priority values: xmlsf_post_priority and xmlsf_term_priority
  • Removal of Genre, Keywords and Access tags as Google dropped support
  • Taxonomy term sitemaps speed improvement: get lastmod date from database
  • Exclude Woocommerce product_shipping_class taxonomy
  • PHP 7.2+ compat: create_function deprecated
  • No more domain filtering for custom URLs and sitemaps
  • FIX Gutenberg editor GN genre taxonomy not showing
  • FIX Plain and /index.php/ permalink structure
  • FIX Clear all options on uninstall
  • FIX Pings

4.9.4

  • FIX: missing featured images, thanks @flyerua
  • FIX: double content type response header filtering

4.9.3

  • Reinstate filter_no_news_limits, allowing post type array
  • Improved language handling and new language filter xmlsf_post_language
  • Force text/xml Content-Type response header

4.9.2

  • FactCheck genre causes error in Search Console

4.9.1

  • FIX: double genre terms on upgrade from 4.4, thanks @mouhalves
  • FIX: wp_count_posts uncached and too heavy on large sites, thanks @carlalexander
  • Last-modified response header now linked to Update on comments setting
  • FIX: plugin_basename propagation

4.9

  • Code cleanup
  • NEW: FactCheck genre
  • Changefreq tag dropped
  • NEW: translation strings for genres
  • FIX: zlib.output_compression compatibility, thanks @alicewondermiscreations
  • FIX: permalink issue with Woocommerce account page endpoints
  • FIX: undefined index in news post types

4.8.3

  • fix get_lastpostdate array/string
  • restore pre PHP 5.4 compatibility (popular request)

4.8

  • NEW: Conditional functions is_sitemap() and is_news()
  • code cleanup and annotation
  • new google ping URL
  • revisit get first/last date/modified functions and cache key set/delete
  • FIX: cache key missing timezone
  • FIX: wp_rewrite init before flush_rules

4.7.6

  • FIX Open_BaseDir issue on IIS server

4.7.5

  • FIX: On cache_flush purge also the respective time_key cache entry,
    props @e2robert https://wordpress.org/support/topic/object-cache-issue-results-in-outdated-last-modified-values-on-index-sitemap/
  • FIX: Variable variable php 7 compat
  • Detect if headers are already sent and print warning in source

4.7.4

  • Another WPML compat issue fixed, special thanks to hermes3por3

4.7.3

  • NEW: xmlsf_excluded filter
  • IMPROVEMENT: Polylang and WPML compatibility issues
  • FIX: “Only variables should be passed by reference” strict warning
  • FIX: PHP 5.3 compatibility

4.7

  • WPML compatibility
  • FIX: News Sitemap chinese language tag
  • FIX: flush rules on plugin re-activation

4.6.3

  • NEW: filter xmlsf_custom_sitemaps
  • BUGFIX: empty custom urls sitemap

4.6.2

  • NEW: filter xmlsf_custom_urls
  • More cleanup
  • BUGFIX: broken Polylang compatibility reported by @zesseb

4.6.1

  • Code cleanup
  • POT file update
  • Dutch translation update

4.6

  • NEW: xmlsf_news_tags_after action hook
  • Attempt to remove static sitemap files left over by other sitemap plugins

4.5.1

  • fix Persistent/Stored XSS vulnerability on admin page, thanks to Sneha Rajguru @Sneharajguru

4.5

  • Set Google News access tag per post
  • Exclude posts from Google News sitemap
  • News Sitemap stylesheet text/links update
  • FIX: cache_delete cached key instead of cache_flush as suggested by Jeremy Clarke https://wordpress.org/support/topic/please-stop-running-wp_cache_flush-whenever-posts-are-edited
  • NEW: Nginx Helper compatibility to purge cache sitemap URLs from FastCGI Cache or Redis

4.4.1

  • BUGFIX contribution by alejandra.aranibar: multiple news post types makes get_lastdate return oldest instead of newest date
  • BUGFIX plugins_url filter not working, reported by Michael
  • Dropped GN Geolocation tag support
  • Dropped XMLSF_POST_TYPE and XMLSF_NEWS_POST_TYPE defines support
  • Multiple default genres

4.4

  • Pings max once per hour (5 minutes for news sitemap)
  • Seperate ping for Google News Sitemap
  • Append custom/static sitemaps to the index
  • Include other post types in News Sitemap
  • Optionally limit posts to certain categories in News Sitemap
  • Noindex response header for sitemaps to keep them out of search results
  • Static sitemap stylesheets
  • Controversial default robots.txt rules removed
  • DB query streamlining
  • BUGFIX: fatal error on . (dot) as category base in permalinks
  • BIGFIX: PHP Strict notices
  • Force object cache flush on post publication

4.3.2

  • Italian translation
  • BUGFIX: html esc / filter image title and caption tags
  • BUGFIX: empty terms counted causing empty taxonomy sitemap appearing in index
  • BUGFIX: custom taxonomies where lastmod cannot be determined show empty lastmod tag

4.3

  • Google News sitemap settings section
  • Google News tags: access, genres, keywords, geo_locations
  • Improved Google News stylesheet
  • Custom Google News Publication Name
  • Image tags in Google News sitemap
  • Custom URLs
  • Allow additional domains
  • Image caption and title tags
  • Ping Yandex and Baidu optional
  • BUGFIX: Ineffective robots.txt rules
  • BUGFIX: Priority value 0 in post meta not saved
  • BUGFIX: Ping for all post types
  • BUGFIX: Custom taxonomy support
  • BUGFIX: Split by month shows year

4.2.4

  • NEW: Image tags
  • Rearranged settings section
  • FIX: replace permalink, title and bloginfo rss filter hooks with own

4.2.3

  • BUGFIX: Empty ping options after disabling the main sitemap
  • BUGFIX: Empty language tag for Google News tags in posts sitemap
  • Small back end changes
  • NEW: Custom post types split by year/month

4.2

  • NEW: Image & News tags
  • NEW: Exclude pages/posts

4.1.4

  • BUGFIX: Pass by reference fatal error in PHP 5.4
  • BUGFIX: issue with Polylang language code in pretty permalinks setting
  • BUGFIX: unselected post types in sitemap
  • BUGFIX: 1+ Priority for sticky posts with comments
  • Dutch and French translations updated

4.1

  • NEW: Ping Google and Bing on new publications
  • NEW: Set priority per post
  • NEW: Priority calculation options
  • NEW: Option to split posts by year or month for faster generation of each sitemap
  • Reduced queries to increase performance
  • Improved Lastmod and Changefreq calculations
  • Core class improvements
  • Dropped qTranslate support
  • Dropped PHP4 support
  • BUGFIX: removed several PHP notices

4.0.1

  • NEW: Dutch and French translations
  • BUGFIX: Non public sites still have sitemap by default
  • BUGFIX: Invalid argument supplied for foreach() when all post types are off
  • BUGFIX: Wrong translation dir

4.0.0

  • Moved to sitemap index and seperated post/page sitemaps
  • NEW: options to dswitch off sitemap and news sitemap
  • NEW: select which post types to include
  • NEW: select which taxonomies to include
  • NEW: set additional robots.txt rules
  • NEW: Translation POT catalogue
  • Improved Polylang support
  • Dropped xLanguage support
  • qTranslate currently untested

3.9.2

  • Basic Google News feed stylesheet
  • improvement on XSS vulnerability fix
  • Fixed trailing slash

3.9.1

  • SECURITY: XSS vulnerability in sitemap.xsl.php

3.9

  • Google News Sitemap
  • Memory limit error workaround (for most sites)

3.8.8

  • BUGFIX: PHP4 compatibility
  • BUGFIX: stylesheet URL when installed in mu-plugins
  • core change to class
  • minified sitemap output by default

3.8.5

  • xLanguage support based on code and testing by Daniele Pelagatti
  • new FILTER HOOK robotstxt_sitemap_url for any translate and url changing plugins.
  • BUGFIX: Decimal separator cannot be a comma!

3.8.3

  • filter out external URLs inserted by plugins like Page Links To (thanks, Francois)
  • minify sitemap and stylesheet output
  • BUGFIX: qTranslate non-default language home URL

3.8

  • qTranslate support
  • no more Sitemap reference in robots.txt on non-public blogs

3.7.4

  • switch from add_feed (on init) to the do_feed_$feed hook
  • BUGFIX: is_404() condition TRUE and Response Header 404 on sites without posts
  • BUGFIX: is_feed() condition FALSE after custom query_posts
  • BUGFIX: no lastmod on home url when only pages on a site
  • BUGFIX: stylesheet url wrong when WP installed in a subdir

3.7

  • massive changefreq calculation improvement
  • further priority calulation improvement taking last comment date into account

3.6.1

  • BUGFIX: wrong date calculation on blogs less than 1 year old

3.6

  • massive priority calculation improvement

3.5

  • complete rewrite of plugin internals
  • speed improvements
  • WP 3.0 (normal and MS mode) ready

3.4

  • BUGFIX: use home instead of siteurl for blog url for sitemap reference in robots.txt
  • code streamline and cleanup

3.3

  • automatic exclusion of tags blog in wpmu

3.2

  • rewrite and add_feed calls improvements
  • BUGFIX: double entry when static page is frontpage

3.0

  • added styling to the xml feed to make it human readable

2.1

  • BUGFIX: lastmod timezone offset displayed wrong (extra space and missing double-colon)

2.0

  • priority calculation based on comments and age
  • changefreq based on comments

1.0

  • changed feed template location to avoid the need to relocate files outside the plugins folder
  • BUGFIX: get_post_modified_time instead of get_post_time

0.1

  • rework from Patrick Chia’s Standard XML Sitemaps
  • increased post urls limit from 100 to 1000 (of max. 50,000 allowed by the Sitemap protocol)