WP sitemap: help Google find your WordPress pages

Why a WordPress sitemap matters for leads

A useful sales page cannot bring you search visitors if Google has not found it. This matters when you launch a service, publish Spanish content or expand a product catalog. A sitemap gives search engines a maintained list of the pages you want considered.

• New sites

  A new business website may have few incoming links. Its sitemap gives Google another discovery route while you build useful content and connections.

• Large catalogs

  Property portals and stores can have pages several links away from the homepage. A sitemap helps expose those URLs, alongside clear categories and navigation.

• Bilingual services

  English and Spanish pages need their own discoverable addresses. Their language relationships should be explicit so each audience can reach the appropriate version.

Google's sitemap overview explains why sitemaps are especially useful for new and large sites. Keep internal links too: a service page should be reachable through your menu, related services or a relevant guide. See the broader priorities in our WordPress web design hub.

Find your wp sitemap and choose one generator

WordPress has included XML sitemaps since version 5.5, normally at /wp-sitemap.xml. The WordPress sitemap reference documents the built-in system. You may already have a sitemap without installing anything extra.

Yoast's XML sitemap guide and Rank Math's sitemap guide explain their generators. An SEO plugin can take over from the core sitemap. Use one active generator, with one agreed source for inclusion rules, rather than overlapping SEO plugins or an old uploaded XML file.

Keep your WordPress sitemap focused

Start with pages that deserve a search visitor: services, useful articles, relevant category pages and available product information. Use their preferred final addresses, called canonical URLs. The Google sitemap building guide recommends listing the URLs you want shown in search.

Have your team compare the sitemap with your actual service list, not just its URL count. A missing high-value service matters more than hundreds of intentionally excluded filter pages. Store owners can pair this review with our WooCommerce optimization guide.

Bilingual sitemap XML with hreflang

Hreflang identifies equivalent pages in different languages. Each translated page should have its own URL and normally a canonical pointing to itself. Making every Spanish page canonical to English undermines treating the Spanish version as a separate search page.

<?xml version="1.0" encoding="UTF-8"?>
<urlset
 xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
 xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <url>
    <loc>https://example.com/services</loc>
    <xhtml:link rel="alternate" hreflang="en"
      href="https://example.com/services" />
    <xhtml:link rel="alternate" hreflang="es"
      href="https://example.com/es/servicios" />
  </url>
  <url>
    <loc>https://example.com/es/servicios</loc>
    <xhtml:link rel="alternate" hreflang="en"
      href="https://example.com/services" />
    <xhtml:link rel="alternate" hreflang="es"
      href="https://example.com/es/servicios" />
  </url>
</urlset>

Google's localized-page documentation describes this reciprocal structure. XML is one supported place for hreflang; HTML annotations are another. Your multilingual setup must produce consistent language pairs, and adding an SEO plugin alone does not prove that it does.

What's Google Search Console for?

Google Search Console is Google's free tool for understanding how your site appears in Google Search. Verification proves you control the property before you can access its reports. Google's introduction describes its search performance, indexing and troubleshooting features.

Search queries show the language people use before reaching you; they do not prove which clicks became clients. Compare relevant service queries with inquiries or sales in your own records. Review security and manual-action messages promptly, and make sure the property has an actively monitored owner account.

The Core Web Vitals report uses real-user data and may have insufficient data on a low-traffic site. A missing report is not a passing score. Our WordPress speed guide explains how field reports and lab tests answer different questions.

Submit sitemap to Google: a 20‑minute setup

Allow about 20 minutes of hands-on work if you have DNS access and a working sitemap. This is a planning estimate, not Google's processing time; DNS verification and report population can take longer. Google's ownership guide covers the verification options.

1. Step 1

   Choose the property and keep ownership

   Use a Google account controlled by the business. Prefer a Domain property to cover protocols and subdomains together; give your agency its own access rather than sharing the owner's password.

2. Step 2

   Verify through DNS or an HTML tag

   For the Domain property, add Google's supplied TXT record at the active DNS provider without replacing existing records. If DNS access is unavailable, a URL-prefix property can use an HTML verification tag in the homepage head; coverage is limited to that prefix.

3. Step 3

   Check the generated sitemap

   Open the active sitemap index and a child file. Confirm current service URLs, intended exclusions and language pairs, and check that the file is public without a login, browser challenge or server error.

4. Step 4

   Submit the sitemap index

   In the matching property's Sitemaps report, submit the active index address. After Google processes it, check the status and any errors; submitting the index is enough to expose its child sitemaps.

5. Step 5

   Inspect a page that matters

   Use URL Inspection for the homepage, a main service and its Spanish equivalent. Compare the recorded indexing status with a live test, checking access, noindex and the canonical URL; request indexing after meaningful fixes where appropriate.

6. Step 6

   Record the baseline and follow-up

   Save the property, sitemap address, submission status and key URLs checked. Assign someone to review indexing after reports populate and confirm that verification remains in place after theme, DNS or plugin changes.

Search Console pages not indexed: find the fix

Open Page indexing, choose an exclusion reason and inspect an affected business page. Use Google's Page indexing guide to distinguish expected exclusions from faults. Focus on useful final URLs, not on making the entire report green.

• Crawled, currently not indexed

  Google fetched the page but did not include it. Review usefulness, duplication and whether the intended content renders before requesting another crawl.

• Discovered, currently not indexed

  Google knows the URL but has not fetched it yet. Check internal links, server reliability and unnecessary URL variations; resubmitting the same file does not fix those causes.

• Duplicate without user-selected canonical

  Google sees competing versions. Choose the preferred URL and align canonical tags, internal links and sitemap entries; redirect redundant versions when appropriate.

• Excluded by noindex

  The page asks to stay out of search. Keep that for intentional exclusions; remove an accidental noindex on a public service page and verify the live result.

• Page with redirect

  The listed URL sends visitors elsewhere. Keep the final destination in the sitemap and inspect that destination if it should appear in search.

A practical order is to check the live response, indexing instructions, canonical choice, internal links and page value. Document what you changed and review again after recrawling. A booking page accidentally marked noindex needs a different repair from a deliberately excluded thank-you page.

Sitemap rules that prevent mixed signals

Sitemap: https://example.com/sitemap_index.xml

The Google sitemap building guide also documents this robots.txt discovery method. Keep that address aligned with the file submitted in Search Console. If a cached sitemap is stale, fix its refresh rules rather than repeatedly submitting an obsolete list.

fer.marketing/robots.txt

Monitor Google and Bing after site changes

Treat the sitemap as part of ongoing maintenance, especially after a redesign, migration or SEO plugin change. A file can still load while omitting an entire content type. Our WordPress update guide explains why verification must follow changes.

• After publishing

  Check that the new page appears in the right child sitemap and has a link from a relevant page. For bilingual launches, check both language versions and their reciprocal alternates.

• After technical changes

  Recheck verification, sitemap addresses, exclusions and key canonicals. Inspect your highest-value service pages after a domain move, multilingual change or SEO plugin replacement.

• During care reviews

  Review new exclusions and important page status, plus security messages. Record affected URLs, business impact, action, owner and follow-up rather than sending a screenshot of a total count.

Bing Webmaster Tools and IndexNow

Bing has its own Webmaster Tools, where you can verify your site and submit a sitemap. IndexNow can notify participating search engines when URLs are added, updated or removed. Keep the sitemap too; neither notification nor submission guarantees indexing.

Agree on these checks in your WordPress maintenance scope. For agencies, keep the client's ownership clear and deliver findings under your brand. We can set up and monitor Search Console with a written scope that identifies which pages and reports we review.