ホーム > React > It seems like priority and changefreq are not necessary for sitemaps
React

It seems like priority and changefreq are not necessary for sitemaps

Thank you for your continued support.
This article contains advertisements that help fund our operations.

⇨ Click here for the table of contents for Vue articles

⇨ Click here for the table of contents for React articles

⇨ Click here for the table of contents for Laravel articles

There is the following description in Google Search Central.

Google Search Central

Google ignores the values of priority and changefreq.

Google uses this value when it can verify that the lastmod value is consistently accurate (compared to the page's last update).

What is priority?

It was originally a field to indicate how high the priority is within the site.

Currently, it seems like Google does not use numerical values in the sitemap to order them. Maybe.

What is changefreq?

It was a field to indicate the frequency of updates for the page.

Currently, it seems like Google does not use numerical values in the sitemap for this purpose.

What is lastmod?

It is a field to indicate the last modification date.

When it is confirmed to be accurate compared to the update date of the page, Google will use this value.

Would it be counterproductive not to accurately specify it?

In conclusion, you only need to write the URL and lastmod in the sitemap.

That's the conclusion!!!

Related Articles

How to create a sitemap in Laravel for SEO measures

Adding lastmod to the sitemap in Gatsby

Summary

That's all, it's minimal information, but I hope it helps someone!

If you have any complaints or corrections, please contact me via DM on Twitter below.

That's it!

Please Provide Feedback
We would appreciate your feedback on this article. Feel free to leave a comment on any relevant YouTube video or reach out through the contact form. Thank you!