What This Guide Solves

A sitemap does not force Google to index a site, but it gives Google a clean list of the canonical URLs you want discovered. For a new WordPress publisher site, that matters because the site can change quickly: demo pages get removed, default posts get retired, trust pages go live, and the article library starts filling up.

The mistake is submitting whatever sitemap URL happens to exist without checking it first. If the sitemap includes junk pages, broken URLs, private drafts, tag archives you do not want in search, or the wrong domain version, Search Console can still fetch it, but the signal is messy.

For Eiway, Rank Math SEO is now the active sitemap layer. The sitemap index to submit is:

https://eiway.com/sitemap_index.xml

On May 12, 2026, that URL returned 200 OK as XML for browser-style and Googlebot-style requests. Rank Math also responds at https://eiway.com/wp-sitemap.xml, but the clean Search Console submission target is the Rank Math sitemap index.

The current Rank Math sitemap index includes only:

• https://eiway.com/post-sitemap.xml
• https://eiway.com/page-sitemap.xml
• https://eiway.com/category-sitemap.xml

This guide shows the exact submission path and the checks to run before using the Sitemaps report in Google Search Console.

Official Google references used for this workflow include Build and submit a sitemap, Manage your sitemaps using the Sitemaps report, and the URL Inspection tool documentation.

Disclosure: This is an informational technical SEO guide. Eiway may add affiliate links or product links later, but the workflow is based on official Google documentation, live sitemap verification, and the current Eiway launch baseline, not on commission.

Recommended Setup

Use Rank Math's sitemap index for Eiway because Rank Math is already installed, active, and configured for the site. The active path is:

/sitemap_index.xml

For Eiway, that means submitting this path in Search Console:

sitemap_index.xml

Use the domain property if you have DNS access because it covers protocol and subdomain variants. If you only have a URL-prefix property, make sure the selected property matches the live canonical site exactly: https://eiway.com/.

Do not submit a sitemap until these checks pass:

• the sitemap returns HTTP 200 OK
• the response is XML, not a theme page or 404 page
• robots.txt does not block the sitemap
• the sitemap uses the live canonical domain
• draft, demo, staging, and private URLs are not included
• important pages are internally linked from the site

What Google Actually Does With The Sitemap

Google says submitting a sitemap is a hint, not a guarantee that Google will download it or use it for crawling every URL. Search Console is still valuable because the Sitemaps report shows whether Google could fetch and read the sitemap, along with processing errors.

That means the goal is not "submit and wait." The goal is:

1. submit the clean sitemap
2. confirm Search Console reports Success
3. check discovered page counts
4. inspect important URLs that still are not indexed
5. keep the sitemap clean as the site changes

Step-by-Step Process

Step 1: Confirm The WordPress Sitemap URL

Open the sitemap in a browser:

https://eiway.com/sitemap_index.xml

For a Rank Math sitemap, you should see a sitemap index that points to child sitemaps such as posts, pages, and selected taxonomies.

For Eiway, the current live sitemap index includes:

• https://eiway.com/post-sitemap.xml
• https://eiway.com/page-sitemap.xml
• https://eiway.com/category-sitemap.xml

That is the correct lean setup for the current Eiway publication. Posts and pages are included, categories are included because the published guides now use a real AdSense Readiness category, and author/product/tag sitemaps are excluded.

Step 2: Check The HTTP Status And Content Type

Run:

curl.exe -A "Googlebot/2.1 (+http://www.google.com/bot.html)" -I https://eiway.com/sitemap_index.xml

The target result is:

• status: 200 OK
• content type: XML
• no login redirect
• no security challenge
• no WordPress 404 template

Eiway passed this check with a Googlebot-style request. A plain default curl.exe request can trigger a host-level 406 Not Acceptable ModSecurity response on this server, so the practical verification command uses an explicit user agent.

Step 3: Check robots.txt

Open:

https://eiway.com/robots.txt

The sitemap line should be present and the sitemap path should not be blocked.

If robots.txt references the older WordPress sitemap path, that is not an emergency because Rank Math serves the sitemap index and Search Console can be given the active sitemap directly. The cleanest final state is to reference:

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

This is useful because Google can discover the sitemap from robots.txt even before you submit it in Search Console. Search Console submission is still worth doing because it gives you tracking and error visibility.

Step 4: Remove Junk URLs Before Submission

Before submitting the sitemap, clean the site. Do not use Search Console to submit a sitemap that still reflects a half-built WordPress install.

For Eiway, the cleanup rule is:

• no default Hello world! post
• no demo /home/ variant competing with the root homepage
• no raw shortcode or placeholder product page
• no staging hostname competing with the live site
• no placeholder trust pages
• no articles without final prose or proof assets

If a page should not be indexed, remove it, redirect it, draft it, or use the correct index-control method. Do not rely on robots.txt to hide pages from search results.

Step 5: Open Search Console

Open Google Search Console and choose the correct property for the live domain.

If you use a domain property, select the Eiway domain property. If you use a URL-prefix property, select the https://eiway.com/ property, not the staging domain and not an old HTTP or www variant.

Step 6: Submit The Sitemap

In Search Console:

1. Open the Sitemaps report.
2. In Add a new sitemap, enter sitemap_index.xml.
3. Submit the sitemap.
4. Wait for the status to update.

Do not paste the full URL if Search Console is already showing the correct property prefix before the input field. Use the relative sitemap path shown above.

Step 7: Read The Result

The result you want is:

Success

If Search Console says Could not fetch, first open the sitemap URL in the browser, then run the header check again. Google's Sitemaps report documentation lists common causes such as a wrong URL, robots.txt blocking, server errors, manual actions, too many redirects, or low crawl demand.

If Search Console says the sitemap has errors, open the detail page and fix the listed issue before resubmitting.

Step 8: Inspect Important URLs

For a new publisher site, submit the sitemap first, then use URL Inspection on the most important pages:

• homepage
• article library
• newest published guide
• key trust page
• top monetized guide when affiliate pages begin

Google says requesting indexing does not guarantee indexing and can take days or longer. For many new or updated pages, Google recommends submitting a sitemap with updated pages marked by <lastmod>.

Eiway Implementation Notes

The Eiway sitemap proof uses two original screenshots:

• a live screenshot of the sitemap endpoint
• an Eiway-created Search Console submission checklist showing the exact pre-submit gates

The live technical checks found this state after Rank Math setup on May 12, 2026:

• https://eiway.com/sitemap_index.xml: 200 OK for browser-style and Googlebot-style requests
• content type: text/xml; charset=UTF-8
• https://eiway.com/robots.txt: 200 OK
• active sitemap index entries: post, page, category
• author sitemap: not referenced
• product sitemap: not referenced
• currently published Eiway guides: 4
• next Search Console action: submit sitemap_index.xml

The actual Search Console submission still requires property access. This article prepares the public proof and exact submission path so the owner can submit the sitemap without guessing.

Verification Commands

Use these commands before submitting:

curl.exe -A "Googlebot/2.1 (+http://www.google.com/bot.html)" -I https://eiway.com/sitemap_index.xml

curl.exe -A "Googlebot/2.1 (+http://www.google.com/bot.html)" -L https://eiway.com/sitemap_index.xml

curl.exe -L https://eiway.com/robots.txt

Then use Search Console to submit:

sitemap_index.xml

After submission, check the Sitemaps report for Success, Last read, and Discovered pages.

Common Mistakes

• Submitting the staging sitemap instead of the live domain.
• Submitting an old http or www property when the site is canonical on https://eiway.com/.
• Submitting before demo pages, default posts, or raw shortcode pages are removed.
• Blocking the sitemap with robots.txt.
• Including non-canonical duplicate URLs.
• Submitting both wp-sitemap.xml and sitemap_index.xml after Rank Math is active.
• Assuming a submitted sitemap guarantees indexing.
• Ignoring the Sitemaps report after submission.
• Trying to request indexing for many URLs one by one instead of keeping the sitemap clean.

Monetization Notes

This article can support affiliate monetization later, but the first version should stay tool-light. Eiway now uses Rank Math because the site needs sitemap controls, schema defaults, redirect monitoring, Open Graph defaults, and archive/index rules in one place.

When affiliate recommendations are added, place the disclosure before the first monetized link and explain the real operating reason for the tool.

Search Console Submission Checklist

Before submitting Eiway's sitemap, confirm:

• the Search Console property is for the live domain
• sitemap_index.xml returns 200 OK
• the response is XML
• the sitemap index includes only intentional child sitemaps
• staging URLs are not part of the live sitemap
• demo/default content is removed
• the homepage, article library, and trust pages are live
• the first four guides are published
• URL Inspection is reserved for the highest-priority URLs after sitemap submission

Sources Used

• Build and submit a sitemap
• Manage your sitemaps using the Sitemaps report
• URL Inspection tool

FAQ

Does submitting a sitemap guarantee indexing?

No. Google says sitemap submission is a hint, not a guarantee. It helps discovery and gives you Search Console reporting, but indexing still depends on crawlability, quality, canonicalization, and Google's systems.

Should I submit `sitemap.xml` or `wp-sitemap.xml`?

Submit the sitemap your site actually uses. For Eiway right now, Rank Math is active, so submit sitemap_index.xml.

Should I submit every child sitemap separately?

Usually no. Submit the sitemap index first. If you later want more granular tracking, you can submit child sitemaps separately, but the simple path for a new WordPress site is the index.

What should I do if Search Console says `Could not fetch`?

Open the sitemap URL directly, check the HTTP status, confirm robots.txt does not block it, and make sure the property matches the live domain. Fix the fetch problem before resubmitting.

What is the next Eiway step?

Review the article 05 WordPress draft preview, then publish it after final approval.