• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

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