Getting Started With WordPress: Choose a Theme and Essential Plugins
When you start a WordPress site, pick a theme that matches how you want to edit your pages, and add plugins only…
On a WordPress site, Yoast SEO can create XML sitemaps: files that list eligible URLs so search engines can discover them. Yoast groups those files under a sitemap index, a file that lists separate sitemaps for posts, pages, and other content. The index normally appears at https://yourdomain.com/sitemap_index.xml.
Turn on Yoast XML sitemaps, then choose which content search engines can show. Check that the files list the expected URLs. Google Search Console lets you check whether Google fetched the index after you submit it. It does not guarantee that Google will crawl or index the listed pages.
In the WordPress dashboard, open Yoast SEO → Settings → Site features. Under Technical SEO, switch XML sitemaps on, then select View the XML sitemap to open the index. These are the steps in Yoast’s current instructions. Older plugin interfaces may use different labels or menus.
The index should load at /sitemap_index.xml on your site. It links to the individual sitemap files Yoast creates for eligible content. A browser may show raw XML instead of a formatted page; that appearance alone does not indicate an error.
Yoast uses search visibility settings to choose which content types and taxonomies appear in its sitemap. A post type is a WordPress content type, such as a post, page, or product. A taxonomy groups content, as categories and tags do.
Review the relevant settings under Content types for posts, pages, and custom post types. Review Categories & tags for taxonomies, and check Advanced for archive settings. Yoast’s sitemap customization instructions explain how these settings affect the sitemap. After changing them, save and reopen the index to confirm the expected child sitemaps appear.
For a single post or page, edit that item and open Advanced in the Yoast sidebar. Set Allow search engines to show this Post in search results? to No, then update the content. Yoast excludes the item from its sitemap as a result.
This setting controls both whether search engines can show the page and whether Yoast includes it in the sitemap. If you want Google to keep a page out of search results, Google must be able to crawl the page and read its noindex instruction. A noindex directive asks search engines not to show a page in search results; blocking the page in robots.txt can prevent Google from seeing the directive. Google’s indexing guidance explains this distinction. Simply leaving a URL out of the sitemap does not reliably keep it out of search results.
Open /sitemap_index.xml and confirm that it loads and lists the sitemaps you expect. Open relevant child files and spot-check their URLs. Check that each URL uses your preferred version of the site address, including HTTPS and the correct www or non-www form.
A missing URL does not always mean something is wrong. Yoast excludes content such as pages set to noindex, private or password-protected pages, and pages with a different canonical URL. A canonical URL identifies the preferred address for a page when similar or duplicate URLs exist. Yoast’s functional specification describes these exclusions and the sitemap’s structure.
Also check that the index you opened is actually generated by Yoast. Yoast’s index normally uses /sitemap_index.xml; another plugin, WordPress, or a physical file may generate a /sitemap.xml endpoint. If the two addresses show different results, identify the source of each before submitting one to a search engine.
You can submit the sitemap index through Google Search Console’s Sitemaps report. Enter sitemap_index.xml or the full index URL, depending on the property shown in Search Console. You can also make the sitemap discoverable by referencing it in robots.txt. Google’s sitemap documentation describes both options.
Search Console shows whether Google accessed the sitemap and whether it reported processing errors. Google treats a submitted sitemap as a hint: it does not guarantee that Google will fetch the file, crawl every URL, or index any particular page. For more on the Search Console steps, see submitting your Yoast sitemap.
If /sitemap_index.xml returns an error or does not load, first confirm that XML sitemaps are enabled. If the index still fails, visit Settings → Permalinks in WordPress and save the settings without changing them. Yoast recommends this step to refresh WordPress’s permalink settings.
If recent content does not appear, check whether WordPress, a plugin, your hosting provider, or a content delivery network is serving a cached copy. Clear the relevant cache, or exclude sitemap URLs from caching so visitors and search engines receive the updated files. Yoast’s sitemap update troubleshooting covers caching as a common cause.
If expected posts or pages are missing, review the item’s search visibility setting, its post-type settings, and its canonical URL. Also check whether the item is private or password-protected. For an empty or invalid response, inspect the XML itself and check for plugin or theme conflicts; a raw XML display in the browser is different from a blank page or an XML error.
Most sites work with Yoast’s default sitemap settings. Yoast’s customization documentation gives a default of 1,000 entries per sitemap. Google allows up to 50,000 URLs or 50 MB of uncompressed data in an individual sitemap file. The first number is Yoast’s default batch size; the second is Google’s maximum. Developers can use Yoast filters to exclude selected content or change sitemap behavior, but most sites do not need to adjust the default.
Google ignores the priority and changefreq values in sitemaps, so tuning those values does not improve how Google handles the URLs.
Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.
Take a look at vroni.com