First, identify what is missing

A sitemap lists addresses that search engines can discover. A listed page is not guaranteed a place in Google.

Absent from the sitemap: Check the sitemap generator, page settings, and the address you searched for.
Listed, but absent from Google: Check indexing separately. Adding the same address again does not solve that problem.

Imagine a plumbing business with /services/boiler-repair/. This hypothetical page should be public and searchable.

1. Open the active sitemap

Try https://your-business.example/wp-sitemap.xml with your domain. WordPress includes core sitemaps from version 5.5.

The first file may list other sitemaps. Open the pages sitemap, then search for the boiler-repair address.

If it has several numbered files, check each relevant file. Searching only the index can miss every service page.

An SEO plugin may replace the core sitemap. Use its sitemap settings to find the active address.

Yoast commonly uses /sitemap_index.xml. Other plugins can use different paths; check your installed plugin's instructions.

Open the boiler-repair page in WordPress. Check its publication status, scheduled date, and visibility.

A saved draft or private page is not the published service page you intended. Publish it only when ready.

Then open its public address while signed out. It should show the service, not a preview, login, or error.

Under Settings → Reading, inspect "Discourage search engines from indexing this site." Keep it off for a public business site.

That setting can disable the core sitemap. Keep it enabled on a private test site when that is intentional.

Inspect both the individual page and its content type in your SEO plugin. A service can be a custom content type.

Look for sitemap exclusions and search-visibility settings. In Yoast, content excluded from search results also leaves its sitemap.

For our boiler-repair example, remove an accidental exclusion only if the page should appear in search.

Controls vary by plugin. Do not assume a core sitemap and a plugin sitemap apply identical rules.

If settings look correct, ask your developer to check sitemap filters and cached XML before changing plugins.

A canonical URL is the preferred address for a page. Compare it with your sitemap entry and internal links.

Perhaps the old boiler-repair address redirects to /boiler-repairs/. Search the sitemap for that final address too.

Open the page source and find rel="canonical", or ask your developer to report its value.

If it points somewhere unexpected, review the page's canonical setting. Do not point all service pages to your homepage.

Include the preferred, working address in the sitemap. A canonical suggestion does not force Google to select it.

Refresh the active sitemap after correcting settings. Clear its relevant cache if it still shows an old version.
Confirm the intended boiler-repair address appears in a child sitemap.
Open that address and confirm it serves the page directly, without a redirect or error.
Check that public service pages allow crawling and do not carry an unintended noindex instruction.
Keep useful links to the service page from your website. A sitemap does not replace those links.

Submit the active sitemap URL through your site's Search Console Sitemaps report. Check its processing status for errors.

If the page is listed but not indexed, use URL Inspection to read Google's reason. Submission is only a hint.

Tin GEO's documented checks cover sitemap completeness, accidental search blocks, and canonical tags.

They match the three questions here: is the page listed, can it be read, and which address is preferred?

Explore the WordPress setup above. These checks do not promise support for every plugin or prove completed work on your site.