XML Sitemap Generator for Google
Generate XML and HTML sitemaps for your website with ease using the XML Sitemap Generator for Google. This plugin enables you to improve your SEO rankings by creating page, image, news, video, HTML, and RSS sitemaps. It also supports custom post types and taxonomies, allowing you to ensure that all of your content is being indexed by search engines. With a user-friendly interface, you can easily configure the plugin to suit your needs and generate sitemaps in just a few clicks. Keep your website up-to-date and make sure that search engines are aware of all of your content by using the XML Sitemap Generator for Google. The plugin supports all kinds of WordPress generated pages as well as custom URLs. Additionally it notifies all major search engines every time you create a post about the new content. Supported for more than a decade and rated among the best, it will do exactly what it’s supposed to do – providing a complete XML sitemap for search engines! If you like the plugin, feel free to rate it! 🙂 Related Links: Support Forum License Good news, this plugin is free for everyone! Since it’s released under the GPL, you can use it free of charge on your personal or commercial site. Translations The plugin comes with various translations, please refer to the WordPress Codex for more information about activating the translation. If you want to help to translate the plugin to your language, please have a look at the sitemap.pot file which contains all definitions and may be used with a gettext editor like Poedit (Windows).
Top keywords
- engines4×1.51%
- search4×1.51%
- search engines4×1.51%
- sitemap4×1.51%
- xml4×1.51%
- content3×1.13%
- sitemaps3×1.13%
- xml sitemap3×1.13%
- custom2×0.75%
- generate2×0.75%
- generator2×0.75%
- generator for google2×0.75%
Override Post Title with First Content Heading
This plugin is developed at Shepherd Interactive for the benefit of the community. No support is available. Please post any questions to the support forum. On a singular post/page, normally in The Loop the_title() returns post_title; if, however, this needs to be overridden so that a custom content heading is displayed (i.e. for SEO purposes), then an h1 or h2 element may be supplied at the beginning of the post_content and the contents of this heading element will be returned by the_title() instead of post_title. From a technical perspective, the site title in the main header should be an h1 element and the page/post title should in an h2 element within an article, per HTML5: Sections may contain headings of any rank, but authors are strongly encouraged to either use only `h1` elements, or to use elements of the appropriate rank for the section’s nesting level. This is seen in the default WordPress theme and the HTML specifications. However, SEO places higher priority on the contents of an h1 element, so if every page of a site has the exact same h1 contents (the site name), then search engines may not be as likely to rank the page based on the unique contents of the h2. It has been suggested therefore that the h1 and the h2 elements be swapped, so that the site title appears in an h2 and so that the unique page title appears in the h1. While the specifications don’t prefer this arrangement, it is not incorrect, also per HTML5: Both of the documents are semantically identical and would produce the same outline in compliant user agents. So if different heading levels are semantically equivalent, and if search engines really place that much importance on h1, then SEO wins. In both cases, content section headings should be coded with h3 and below. Technical note: If the $post object is not passed into the_title filter, then the page’s the_title() must be called before every other the_title() call in_the_loop()
Top keywords
- title11×3.17%
- h18×2.31%
- post7×2.02%
- page6×1.73%
- element
