![]() “We believe we found a good balance, which will be scalable and doesn’t open the can of worms that full caching exposes us to,” said Muller. “While sitemaps can have up to 50,000 URLs per sitemap, we found that capping it at 2,000 is acceptable from a performance perspective and totally acceptable from a search engine perspective.” The team decided to stick with a default of 2,000 URLs per sitemap and to provide a filter hook for plugins to alter if necessary.įinding a solution for the lastmod date was not as easy. “Addressing the number of URLs per page is fairly trivial,” said Muller. The lastmod date in the index.xml file. ![]() “We believe that we landed on a solution that doesn’t need full caching and will still be scalable.”įor performance, there are two primary challenges: “Solving the performance issue is not trivial, and we have looked into various solutions,” said Muller. Without a full caching solution built into core, it presented some hurdles for the team. One of the primary concerns with the initial proposal is how well a core sitemaps feature would perform and scale, particularly on larger sites. Ideally, WordPress would provide a registration flag for post types and taxonomies. There is also a filter hook available to change which post types, taxonomies, and users are indexed. ![]() The feature plugin currently indexes the following URLs for a site:Ĭustom post types and taxonomies are registered only if they are public. “Ambitiously 5.4,” said Muller of the release goal. WordPress users may see this feature arrive in major update this year. “At a high level, expanding the number of WordPress sites with Sitemaps ultimately speeds up content discoverability by search engines and re-crawl fresher content flagged by the lastmod date faster than a scheduled bot would,” Muller said of the primary reasons the feature belongs in core. Some were worried about performance and others felt like the feature should remain in plugins. However, several people questioned whether WordPress should ship with XML sitemaps. “This makes a lot of sense, looking forward to seeing the v1 of this in core and for it to evolve in future releases and cement WordPress’ well-deserved reputation of being the best CMS for SEO,” he said. Many praised the initiative, such as WordPress project lead Matt Mullenweg. However, several other major content management systems ship with sitemaps as part of their core codebase. Traditionally, WordPress has left this feature to plugins to implement, and many have filled this role over the years. Instead, plugins would offer users various options on how their sitemaps work.Ī team created by Google, Yoast, and other contributors originally proposed XML sitemaps as a core WordPress feature in June 2019. Therefore, sitemap plugins would not automatically disappear. It will also offer an API for plugin developers to manipulate. The project aims to ship a basic version of an XML sitemaps feature to all WordPress installations. ![]() Update (January 31, 2020): The Core Sitemaps feature plugin is now available in the WordPress plugin repository. The plugin should also be available in the WordPress plugin directory by next week. It is currently open for testing and feedback. After seven months of development, the team has made the XML Sitemaps feature plugin available on GitHub. Thierry Muller, a Developer Relations Program Manager at Google, and several contributors posted an update on the XML sitemaps feature that may land in WordPress this year.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |