Title: Invalid priority “default”
Last modified: June 10, 2023
---
# Invalid priority “default”
* Resolved [robzy](https://wordpress.org/support/users/robzy/)
* (@robzy)
* [3 years, 2 months ago](https://wordpress.org/support/topic/invalid-priority-default/)
* As of the last update (to version 4.3.9), the plugin erroneously outputs “default”
in the priority section of sitemap URLs:
* ```wp-block-code
```
* The value of priority has to a numerical value between 0.0 and 1.0, it cannot
be a string like “default”. It may be set to “default” in the plugin’s sitemap
settings (in the admin), but that should still translate to a numerical value.
* Perhaps this bug slipped in with the recent performance improvements?
- This topic was modified 3 years, 2 months ago by [robzy](https://wordpress.org/support/users/robzy/).
- This topic was modified 3 years, 2 months ago by [robzy](https://wordpress.org/support/users/robzy/).
Viewing 7 replies - 1 through 7 (of 7 total)
* [funnychickdoon](https://wordpress.org/support/users/funnychickdoon/)
* (@funnychickdoon)
* [3 years, 2 months ago](https://wordpress.org/support/topic/invalid-priority-default/#post-16810313)
* Hey ! I faced the same issue.
* Open the AIOSEO Dashboard > Sitemaps > Scroll towards down and Check Advanced
Settings > Remove Default settings and change to 0.0 to 1.0 basis your requirement.
Load the sitemap again and submit to Google Search Console, it works !!
- This reply was modified 3 years, 2 months ago by [funnychickdoon](https://wordpress.org/support/users/funnychickdoon/).
* Thread Starter [robzy](https://wordpress.org/support/users/robzy/)
* (@robzy)
* [3 years, 2 months ago](https://wordpress.org/support/topic/invalid-priority-default/#post-16811329)
* Even after setting the priorities manually in the Advanced Settings, many URLs
in the category sitemap are still assigned a priority of “default”. Which is
weird, because why would some category URLs be assigned the manually set priority(
0.8) and others “default”, when they ought to use the same setting?
* ```wp-block-code
```
* This happens even after I ungroup the taxonomy priority score settings and set
a value for each one of them individually.
- This reply was modified 3 years, 2 months ago by [robzy](https://wordpress.org/support/users/robzy/).
- This reply was modified 3 years, 2 months ago by [robzy](https://wordpress.org/support/users/robzy/).
- This reply was modified 3 years, 2 months ago by [robzy](https://wordpress.org/support/users/robzy/).
- This reply was modified 3 years, 2 months ago by [robzy](https://wordpress.org/support/users/robzy/).
- This reply was modified 3 years, 2 months ago by [robzy](https://wordpress.org/support/users/robzy/).
* Plugin Author [arnaudbroes](https://wordpress.org/support/users/arnaudbroes/)
* (@arnaudbroes)
* [3 years, 2 months ago](https://wordpress.org/support/topic/invalid-priority-default/#post-16811958)
* Hey [@robzy](https://wordpress.org/support/users/robzy/), [@funnychickdoon](https://wordpress.org/support/users/funnychickdoon/)
I hope you’re both doing well and had a great weekend. I’m sorry to hear that
you’re running into this issue.
* In our latest update we modified the data type of our priority column in the
database to significantly speed up loading times for the sitemap. It looks like
the relevant database queries didn’t run for you when you updated. This happens
occasionally for a few select users.
* I’m not sure if you’re familiar and have access to your site’s database using
PhpMyAdmin or Adminer, but if you do, then you can easily resolve this issue
by running these two queries:
* ```wp-block-code
UPDATE wp_aioseo_posts SET priority = NULL WHERE priority = 'default';
ALTER TABLE wp_aioseo_posts MODIFY priority float;
```
* You’ll need to replace the `wp_` prefix for the table names in the queries with
the relevant table prefix for your own site.
* If you’re not familiar with any of this, please let me know and I’ll see if our
support team can resolve this for you.
* Thread Starter [robzy](https://wordpress.org/support/users/robzy/)
* (@robzy)
* [3 years, 2 months ago](https://wordpress.org/support/topic/invalid-priority-default/#post-16812077)
* Thanks, Arnaud. The ALTER TABLE seems to have run OK (or had successfully run
while updating), but the UPDATE query gets stuck:
* _Truncated incorrect DOUBLE value: ‘default’_
* A SELECT shows that those rows currently have a priority value of 0, so it probably
gets hung up on that not being a float (or that ‘default’ cannot possibly be
a value of a FLOAT field). It’s only 12 rows so I updated those manually.
* That only affects posts, though. After clearing caches I still see a ‘default’
priority for about 2/3 of the URLs in the category sitemap.
* Do I also need to update wp_aioseo_terms? Any other places?
- This reply was modified 3 years, 2 months ago by [robzy](https://wordpress.org/support/users/robzy/).
* Plugin Author [arnaudbroes](https://wordpress.org/support/users/arnaudbroes/)
* (@arnaudbroes)
* [3 years, 2 months ago](https://wordpress.org/support/topic/invalid-priority-default/#post-16812155)
* Hey [@robzy](https://wordpress.org/support/users/robzy/),
* Yes, you’ll need to run the same queries for the terms table. Simply replacing
the table names should do the trick.
* Can you let me know whether you ran then UPDATE statement before the ALTER statement,
or after? The order is important. The UPDATE statement should have succeeded
as long as you ran it before and not after the ALTER statement.
* Thread Starter [robzy](https://wordpress.org/support/users/robzy/)
* (@robzy)
* [3 years, 2 months ago](https://wordpress.org/support/topic/invalid-priority-default/#post-16812255)
* I ran them as you posted them here, so the UPDATE first, followed immediately
by the ALTER. But it’s possible that the ALTER still ran after the UPDATE failed
because I ran them as one command (separated by semi-colon), I’m not sure.
* Just updated the _terms table and everything seems to be working again.
* Thanks for your assistance!
* Plugin Author [arnaudbroes](https://wordpress.org/support/users/arnaudbroes/)
* (@arnaudbroes)
* [3 years, 2 months ago](https://wordpress.org/support/topic/invalid-priority-default/#post-16812591)
* No problem, I’m glad we were able to sort that out.
Viewing 7 replies - 1 through 7 (of 7 total)
The topic ‘Invalid priority “default”’ is closed to new replies.
* 
* [All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)](https://wordpress.org/plugins/all-in-one-seo-pack/)
* [Frequently Asked Questions](https://wordpress.org/plugins/all-in-one-seo-pack/#faq)
* [Support Threads](https://wordpress.org/support/plugin/all-in-one-seo-pack/)
* [Active Topics](https://wordpress.org/support/plugin/all-in-one-seo-pack/active/)
* [Unresolved Topics](https://wordpress.org/support/plugin/all-in-one-seo-pack/unresolved/)
* [Reviews](https://wordpress.org/support/plugin/all-in-one-seo-pack/reviews/)
* 7 replies
* 3 participants
* Last reply from: [arnaudbroes](https://wordpress.org/support/users/arnaudbroes/)
* Last activity: [3 years, 2 months ago](https://wordpress.org/support/topic/invalid-priority-default/#post-16812591)
* Status: resolved