# WP sitemap: help Google find your WordPress pages > A wp sitemap is an XML file that lists the WordPress pages you want search engines to discover and consider for indexing. Connect it to Google Search Console to check whether your service pages, products and bilingual content can appear in search. Submission helps discovery; Google still decides what to index and where to rank it. Canonical: https://fer.marketing/wordpress-sitemap Author: Fernando Marcano, Fer Marketing Updated: 2026-10-17 - **Built in:** /wp-sitemap.xml since WordPress 5.5 - **Ownership:** One active sitemap generator - **Search Console:** Verify, submit, inspect, monitor - **Two languages:** English + Spanish with hreflang ## 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](https://developers.google.com/search/docs/crawling-indexing/sitemaps/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](https://fer.marketing/wordpress-web-design). > **Discovery, indexing and leads are different:** Discovered means Google knows the address; indexed means the page is eligible for search results. Turning a visit into a call still depends on the page's offer, trust and contact journey. A successful sitemap submission proves none of those later outcomes. ## 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](https://developer.wordpress.org/reference/classes/wp_sitemaps/) documents the built-in system. You may already have a sitemap without installing anything extra. | Generator | Main address | Check | | --- | --- | --- | | WordPress core | /wp-sitemap.xml | Public content | | Yoast SEO | /sitemap_index.xml | XML feature on | | Rank Math | /sitemap_index.xml | Sitemap module on | [Yoast's XML sitemap guide](https://yoast.com/help/xml-sitemaps-in-the-wordpress-seo-plugin/) and [Rank Math's sitemap guide](https://rankmath.com/kb/configure-sitemaps/) 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. > **One generator can produce many files:** A sitemap index is a directory of smaller sitemaps, often split into pages, posts and products. That is normal. Open a child file and confirm it contains current public URLs before submitting the index; several child files do not mean several competing generators. ## 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](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap) recommends listing the URLs you want shown in search. **Review a sample from every content type** - [ ] Include public, useful pages with working addresses.: Check that representative services, posts and products load normally and do not redirect. Use the preferred HTTPS domain consistently. - [ ] Exclude pages marked noindex.: Noindex tells search engines to leave a page out of results. A sitemap should not simultaneously invite Google to index that same page. - [ ] Leave out thank-you and private journey pages.: A form confirmation should follow a submission, not become a search landing page. Account pages and private records need access controls; sitemap exclusion does not protect private content. - [ ] Review thin tag and author archives.: An archive that repeats a few links without helping a visitor may not deserve indexing. Keep useful curated archives; exclude thin ones consistently through your SEO settings. - [ ] Use accurate update dates and current translations.: Do not make every page look newly edited each day. Check that newly published content appears and removed or redirected URLs disappear. 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](https://fer.marketing/woocommerce-optimization). ## 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. **Illustrative XML: one page, two languages** (correct) ``` https://example.com/services https://example.com/es/servicios ``` An example for your technical team, not a file to paste over your generated sitemap. Each URL lists both alternates, including itself. [Google's localized-page documentation](https://developers.google.com/search/docs/specialty/international/localized-versions) 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. > **Inspect our public implementation:** Our [live bilingual sitemap](https://fer.marketing/sitemap.xml) lists English and Spanish pages with hreflang alternates. Fer.marketing runs on Next.js, with prerendered pages, rather than WordPress. These are the same principles we apply on WordPress: final URLs, complete language pairs and a generated file that stays current. ## 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](https://support.google.com/webmasters/answer/9128668?hl=en) describes its search performance, indexing and troubleshooting features. | Report | Tells you | Action | | --- | --- | --- | | Sitemaps | File processing | Fix fetch errors | | Page indexing | Included or excluded | Review key URLs | | URL Inspection | One URL's status | Test the live page | | Performance | Queries + clicks | Match buyer intent | | Core Web Vitals | Real-user experience | Review page groups | | Manual actions | Policy actions | Read and resolve | | Security issues | Detected threats | Investigate quickly | 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](https://support.google.com/webmasters/answer/9205520?hl=en) 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](https://fer.marketing/wordpress-speed-optimization) explains how field reports and lab tests answer different questions. > **Want Search Console set up and monitored?** We can verify the property, check your sitemap and investigate exclusions affecting important pages. Add a documented review process to your WordPress care scope. https://fer.marketing/services/wordpress-maintenance ## 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](https://support.google.com/webmasters/answer/9008080?hl=en-EN) covers the verification options. 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. **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. **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. **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. **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. **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. > **Submission is the start of verification:** Sitemap success means Google processed the file, not that every listed page was indexed. Keep the DNS record or HTML tag after verification, and review important URLs when data becomes available. A live test can confirm access without guaranteeing indexing. ## 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](https://support.google.com/webmasters/answer/7440203?hl=en) 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. > **Do not block crawling to remove noindex:** Google must be able to fetch a page to see an updated noindex instruction. A robots.txt block and a noindex tag serve different purposes; neither is a substitute for protecting private content. Keep staging private and investigate any staging URLs appearing in the reports. ## Sitemap rules that prevent mixed signals **Do** - Keep one generator and submit its current index. - List useful, indexable final URLs and real translations. - Link important pages from relevant public pages. - Review exclusions against the page's intended purpose. **Don't** - Install another SEO plugin to solve every warning. - List redirects, noindex pages or thin tag archives. - Treat a processed sitemap as a ranking guarantee. - Change every modification date to today automatically. **robots.txt: point to the active sitemap** ``` Sitemap: https://example.com/sitemap_index.xml ``` Replace the example with your actual public index. This discovery line belongs alongside your existing crawler rules; it is not a complete robots.txt file. The [Google sitemap building guide](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap) 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's public robots.txt with named AI crawler rules](https://fer.marketing/guides/wp/fer-robots-txt.webp) *Our public robots.txt is a separate file from our sitemap. Inspect both files during a discovery review; crawler permissions alone do not prove that pages are indexed.* ## 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](https://fer.marketing/wordpress-updates) 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](https://www.bing.com/webmasters/about), where you can verify your site and submit a sitemap. [IndexNow](https://www.bing.com/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](https://fer.marketing/services/wordpress-maintenance). 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. ## Want us to set up and monitor Search Console? We can connect your WordPress sitemap to a business-owned property and investigate important indexing exclusions. We agree the setup and recurring checks in writing before work starts. - Search Console verification and delegated agency access. - One sitemap generator with agreed content exclusions. - English and Spanish URL and hreflang checks. - Sitemap submission and inspection of key service pages. - Documented indexing reviews and alert responsibility. https://fer.marketing/services/wordpress-maintenance ## FAQ ### Where is my WordPress sitemap? Try /wp-sitemap.xml on your domain for the built-in WordPress sitemap. If Yoast SEO or Rank Math manages it, the main index is usually /sitemap_index.xml. Confirm which generator is active and open a child sitemap to check the pages inside. ### Do I need a plugin to create a wp sitemap? No. WordPress has included a built-in XML sitemap since version 5.5. An SEO plugin can provide a different generator and controls, but installing multiple sitemap tools is unnecessary. Choose one maintained system and verify its output. ### How do I submit a sitemap to Google? Verify your website in Google Search Console, open the matching property's Sitemaps report and submit your active sitemap index address. Check processing status afterward and use URL Inspection for important pages. Submission does not guarantee indexing. ### What's Google Search Console, and is it free? It is Google's free tool for site owners to review search queries, clicks, indexing, Core Web Vitals where data exists, manual actions and security issues. It helps diagnose search visibility; it does not replace your sales records or show which inquiries became paying customers. ### Why does Search Console say my sitemap succeeded but pages are not indexed? Success describes processing of the sitemap file. Individual pages can still be duplicates, redirected, marked noindex or not selected for indexing. Inspect a relevant URL and its stated reason before changing settings or submitting again. ### Should I remove every not indexed page? No. Thank-you pages, private account routes, redirects and duplicate variations may be intentionally excluded. Prioritize useful service, product and content pages that should appear in search. Correct the underlying settings or content rather than chasing a zero-exclusions report. ### How should a bilingual WordPress sitemap work? Give English and Spanish pages distinct URLs and include the indexable versions. If hreflang is implemented in the XML, each language entry should list itself and its equivalent translation. Check that those relationships match the live pages and their canonical URLs. ### How much does Search Console setup and monitoring cost? Fer Marketing's WordPress maintenance plans start at $250 per month per site. We agree the specific setup, monitoring and repair scope in a fixed written quote before work begins. White-label delivery is available for agencies, and we reply the same business day. Send your website to fer@fer.marketing for a fixed written quote, with maintenance from $250 per month per site, a same-business-day reply and white-label delivery for agencies.