• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Smart Update forecast - about the 100 checked pages

Mark_NLD

Basic Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.66 Update #2
Good afternoon,

I really like the Smart Update within WordPress Toolkit. I have a question in regards to the 100 pages that are checked:

Code:
- Test Run Summary

-- 100 pages checked

1: website.nl/blog
2: website.nl/en/blog/this-is-an-example
3: website.nl/en/blog/fast-hosting-drives-conversions

My questions:
Can we influence the amount of pages that are checked? We have 1000's.
Can we influence what type of pages are checked? In this example the WordPress posts are tested (post-sitemap.xml) while we want the WordPress pages to be tested (page-sitemap.xml).

I guess a good solution would be if we can define the sitemap(s) that should be used to run the tests.
 
WP Toolkit tries following, to get list of pages to check:
  • gets site.url/smart-update-sitemap.xml
    syntax is the same as in any sitemap files. You can manually put any url that you want to check during smart updates
  • gets site.url/sitemap.xml
    default sitemap file
  • gets internal fallback sitemap
    that includes site_url and all posts
WP Toolkit uses the first existing file only! Even if the first file contains 1 url, WP Toolkit doesn't try next option.

number of pages you can change via this configuration option(in panel.ini file):
[ext-wp-toolkit]
smartUpdateCrawlerPagesLimit=100

if you see a result with posts urls only, that may mean this site doesn't provide any sitemap file and WP Toolkit chose fallback option.
So you can create smart-update-sitemap.xml file and put into it pages that will be used especially for Smart Updates. Or create default sitemap.xml that will be used also for search bot indexing.
 
Last edited:
Awesome! That is great to learn.

The issue must be related to smartUpdateCrawlerPagesLimit , because the sitemap is working fine.
Thank you! Problem solved!
 
Back
Top